[00:00] <sil2100> ToyKeeper: the image is now building, the imgbot should pick it up soon
[00:00] <sil2100> pmcgowan: ^ new promotion candidate is building
[00:05] <imgbot> [00:10] <sil2100> ToyKeeper: so, once #269 finishes building, do you know if jibel wanted to have sanity tests ran on it? I suppose so, right?
[00:10] <sil2100> ToyKeeper: so sanity + oxide testing would need to be done
[00:10] <sil2100> ...and the custom tarball bits as well
[00:11] <ToyKeeper> sil2100: Yes, that's the plan.  :)
[00:11] <ToyKeeper> Sanity, two bug fixes, anything else related to the changes.
[00:12] <sil2100> Excellent
[00:12] <sil2100> Thanks for picking this up :)
[00:12] <sil2100> Time for me to finally go to sleep
[00:12] <sil2100> o/
[00:21] <lool> robru: I've merged and uploaded
[00:22] <robru> lool: k, just click build on the silo then. And do whatever testing is appropriate
[00:22] <lool> robru: it's waiting for approval in queue now; I guess you can kill the silo
[00:22] <lool> robru: sorry, I've uploaded to *distro*
[00:22] <lool> not to silo
[00:23] <robru> lool: oh, even better, thanks ;-)
[00:24] <robru> elopio: no qa for autopilot?
[00:27] <veebers> robru: elopio: we did the qa with a couple of gatekeeper job runs
[00:27] <robru> veebers: oh, is not marked as approved by qa
[00:28] <robru> veebers: I'll publish if you say it's good though
[00:28] <veebers> robru: please (both elopio and myself are QA and we approve ^_^)
[00:28] <robru> veebers: ahhhhhhhhhhhhhh sorry i forgot elopio /is/ qa ;-)
[00:28] <robru> Publishing
[00:32] <robru> Wow, four free silos, anybody want one?
[00:40] <veebers> robru: nw
[01:40] <imgbot> [01:40] <imgbot> [02:03] <ToyKeeper> Woot, there it is.  :)
[02:10] <imgbot> [03:45] <imgbot> [03:45] <imgbot> [05:13] <Mirv> kgunn: only now
[05:17] <Mirv> Trevinho: there seems to be a new superseding MP now so probably no need for an action from me. note that I just reflected the fact that the landing was stated to be canceled in the landing spreadsheet, so you'd probably need to ping ted_g again to land it
[07:22] <dbarth> good morning
[07:23] <dbarth> trainguards, i'm looking for help respinning an amd64 build associated with silo 28
[07:24] <dbarth> there were temp build issues still yesterday, and that's all it takes to finish get this silo ready (all other arches packaged fine in the end)
[07:25] <Mirv> dbarth: do you mean ppc64el?
[07:26] <Mirv> that's all I can see having failed https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-028/+packages
[07:26] <Mirv> I kicked a rebuild of that if that failing test is flaky
[07:28] <dbarth> Mirv: ah yes, now that's ppc64
[07:29] <dbarth> thanks
[08:07] <Mirv> dbarth_: hey, you shouldn't have kicked a new build, now there's again a flaky build. please just let's retry in the PPA until they build, and at that point run watch_only instead of rebuilding the others... ppc64el _was_ ok :)
[08:14] <popey> jibel: could you please move this card back to 'needs qa sign off'? https://trello.com/c/DUeVwfPn/1321-ubuntu-rtm-reminders-app-popey
[08:14] <oSoMoN> trainguards: good morning! can I have a silo for line 57, please?
[08:21] <jibel> popey, new card added
[08:21] <popey> magic, thanks
[08:22] <Mirv> oSoMoN: there you go, Mr. Bond.
[08:25] <dbarth_> Mirv: i didn't restart a build; i precisely asked to have it rebuilt at the ppa level; that's why i was confused to see amd64 vs ppc64 now failing
[08:25] <dbarth_> fingers crossed
[08:26] <oSoMoN> Mirv, thanks :)
[08:26] <Mirv> dbarth_: the "rebuild" means "rebuild all archs", while what I was doing is "rebuild 1 arch". so since you rebuilt all archs with a new upload, now it happened that ppc64el succeeded and amd64 failed. what I mean that I manually restart single arch builds until it works and then we'd run watch_only build.
[08:26] <Mirv> dbarth_: for a moment though the ppc64el had succeeded before you restarted all archs and then amd64 failed
[08:27] <Mirv> I'm kicking now a fourth amd64 rebuild
[08:27] <Mirv> it has failed a couple of times already
[08:33] <dbarth_> ok
[08:34] <Mirv> dbarth_: oh, now you reuploaded one more :)
[08:34] <Mirv> but the amd64 was still failing so it doesn't matter
[08:49] <Mirv> dbarth_: now it failed on 3 archs instead of 1 :( please just don't press any buttons so I can try to rebuild them and run the build job with watch_only for you when it's ready
[08:49] <jibel> davmor2, I confirm that after upgrading to 269 the hint screen is displayed on the today scope, can you confirm it?
[08:50] <Mirv> chrisccoulson: re: Oxide - there are different options for rtm and one will be selecter later doay. can you think if anything would need a pre-build in anticipation that it'd be selected?  :D
[08:56] <Mirv> https://ci-train.ubuntu.com/job/ubuntu-landing-028-1-build/52/
[08:56] <Mirv> dbarth_: I just assumed it was you :)
[08:56] <Mirv> a ghost called mardy
[08:56] <mardy> Mirv: ah, sorry!
[08:57] <mardy> Mirv: OK, I won't touch any buttons :-)
[08:57] <Mirv> that's fun, all the miscommunication because of a wrong assumption :)
[08:58] <dbarth_> gosh
[08:58] <dbarth_> mardy: hey i told you i was on it ;)
[09:00] <dbarth_> Mirv: while we're at it, silo 23 landed but the branches are not merged yet
[09:02] <dbarth_> jibel: hi; i have silo 17 marked for a qa handoff, but it doesn't show up on the signoff dashboard
[09:03] <dbarth_> jibel: is that manual? can i do something to accellerate?
[09:07] <Mirv> dbarth_: ok there's a autopkgtest problem, I try kicking it
[09:08] <Mirv> dbarth_: that is, it's still in proposed pocket
[09:11] <jibel> dbarth_, more coffee maybe, created an hour ago https://trello.com/c/6g6zflrH/1365-ubuntu-landing-017-ubuntu-html5-theme-webbrowser-app-dbarth-alex-abreu
[09:21] <sil2100> jibel: how's 269 going?
[09:24] <Mirv> dbarth_: mardy ^ done
[09:25] <mardy> Mirv: \o/ thanks! :-)
[09:27] <davmor2> sil2100: it broke hard
[09:30] <dbarth_> \o/
[09:31] <sil2100> davmor2: really?
[09:32] <sil2100> davmor2: what's broken? We need a respin?
[09:32] <sil2100> oxide is busted? Do we have anyone working on it? This will delay everything I suppose, 1.6 was our only option - besides reverting to 1.2
[09:32] <ogra_> sil2100, oxide isnt usable
[09:33] <ogra_> non mobile websites make it crash hard if you zoom
[09:33] <sil2100> Damn
[09:33] <davmor2> sil2100: browser is fully zoomed in on desktop sites and you can't zoom out, also jibel hit an issue with upgrade that I'm failing to confirm currently
[09:33] <davmor2> ogra_: you can't zoom
[09:33] <ogra_> thats what i said
[09:33] <ogra_> :)
[09:34] <sil2100> jibel, ogra_, davmor2: should we try an oxide revert to 1.2 then? Or is chrisccoulson looking into fixing this?
[09:34] <ogra_> sil2100, not sure ...
[09:35] <rvr> https://bugs.launchpad.net/oxide/+bug/1442458
[09:35] <ogra_> (i'm nozt sure chrisccoulson has been contacted yet)
[09:35] <davmor2> sil2100: currently we figure it is not a decision for us to make
[09:35] <rvr> ogra_: He commented
[09:35] <ogra_> yup, i see that
[09:35] <rvr> on that bug some minutes ago
[09:35] <ogra_> didnt know about that bug :)
[09:37] <sil2100> chrisccoulson: hey, is there anything we can do to get this working then?
[09:38] <ogra_> wait for 1.7 ?
[09:39] <sil2100> To make any serious decisions like these we would need pmcgowan around
[09:43] <chrisccoulson> I'm working on it, but I need to wait for my local arm tree to build
[09:48] <sil2100> chrisccoulson: thanks, keep us updated :)
[09:48]  * sil2100 continues his errands
[09:54] <jibel> sil2100, it means that 1.6 has not been well tested and is not ready for release even if this bug is fixed there are probably  others. I wouldn't land it in vivid in this state and certainly not in RTM. That's a discussion we must have with pmcgowan
[11:19] <pmcgowan> chrisccoulson, do we have a way to patch 1.5.5?
[11:20] <pmcgowan> sil2100, morning
[11:25] <pmcgowan> biab
[11:26] <ogra_> http://i.imgur.com/xq472i3.png i wonder if can make it survive 8 days :)
[11:27] <Mirv> dbarth_: you probably noticed but 023 finalized migration ie. that rekicked autopkgtest worked
[11:46] <dbarth_> Mirv: ah, splendid!
[11:47] <dbarth_> Mirv: if we had a test branch to that difficult silo from this morning, the reconfig won't invalidate the signon package, will it?
[11:47] <dbarth_> the additional branch has tests that can help validate the rest of the silo in particular
[11:57] <Mirv> dbarth_: yes, reconfig is fine, just always write the package name to the packages field when running build
[12:15] <dbarth_> Mirv: ok; ready for a reconfig of silo 28 with that additional branch
[12:15] <dbarth_> Mirv: i'll just rebuild that extra one
[12:17] <Mirv> dbarth_: reconfig done, so run build for uoa-integration-tests
[12:18] <Kaleo> brendand, hey sir, does https://bugs.launchpad.net/camera-app/+bug/1411782 still occur for you?
[12:23] <brendand> Kaleo, haven't tried in a long time
[12:23] <brendand> Kaleo, i'll check in a minute
[12:23] <Kaleo> brendand, thanks
[12:27] <rvr> popey: reminders-app displays fine the one-line note
[12:27] <popey> thanks rvr
[12:27] <popey> is that a +1 for upload?
[12:27] <rvr> popey: Can you update the translation?
[12:27] <popey> i can
[12:28] <popey> r407 will have es, fa, nl and sl updates
[12:28] <rvr> Cool!
[12:28] <popey> do you want to test that?
[12:28] <popey> to confirm?
[12:28] <rvr> popey: Yeah
[12:28] <popey> ok, one mo
[12:29] <popey> rvr: http://people.canonical.com/~alan/reminders/com.ubuntu.reminders_0.5.407_armhf.click
[12:29] <rvr> That was quick!
[12:29] <rvr> Downloading
[12:49] <brendand> Kaleo, i guess it's gone now
[12:50] <Kaleo> brendand, wonderful :) I think a fix of mine did the trick
[12:50] <sil2100> pmcgowan, jibel: I guess besides distro-patching 1.5 with the fix we only have the option of reverting back to 1.2
[12:51] <pmcgowan> mterry, has a branch we can use
[12:51] <pmcgowan> sil2100, ^^
[12:51] <pmcgowan> we need chrisccoulson I think to bless and build?
[12:51] <sil2100> A branch for oxide?
[12:51] <mterry> sil2100, yes
[12:52] <sil2100> mterry: is it a branch for 1.5.5? Or fo 1.6.2?
[12:52] <mterry> sil2100, but these oxide branches don't have debian/ in them?
[12:52] <mterry> sil2100, for lp:oxide/1.5
[12:52] <mterry>  https://code.launchpad.net/~mterry/oxide/mirserver-1.5/+merge/255819
[12:53] <sil2100> Damn, we'll have to mangle the version then
[12:54] <sil2100> Yesterday's decisions were very risky and troublesome if things go wrong
[12:54] <sil2100> And they went wrong
[12:54] <sil2100> So now we'll have to release a 1.6.5.is.1.5.5 version or similar for ubuntu-rtm ;/
[12:54] <sil2100> chrisccoulson: ^
[12:56] <lool> sil2100: heya, is there a way to request a rebuild of a branch (no new merge proposal) into vivid?
[12:57] <lool> or should I create a dumb empty one?
[13:00] <sil2100> lool: the best way is to do an empty merge
[13:01] <lool> sil2100: ok thanks
[13:03] <lool> sil2100: oh actually sorry, I see I can do a sync; I somehow thought the rtm version was smaller but it' shigher
[13:06] <rvr> popey: http://people.canonical.com/~vrruiz/reminders-app-evernote.png
[13:07] <rvr> popey: I see nothing to translate in Launchpad
[13:07] <popey> mzanetti: ^
[13:08] <popey> rvr: can you file a bug pls?
[13:08] <rvr> popey: Yup
[13:10] <mzanetti> thanks
[13:12] <rvr> popey: mzanetti: https://bugs.launchpad.net/reminders-app/+bug/1442614
[13:12] <popey> thanks rvr
[13:12] <mzanetti> thanks rvr
[13:12] <rvr> mzanetti vs mzanetti!
[13:12] <popey> \o/
[13:12] <popey> NOBODY WINS!
[13:12] <mzanetti> ?
[13:13] <rvr> mzanetti: Hurry up, you must destroy the bugs before they enter the distro!
[13:13] <mzanetti> :)
[13:14] <mzanetti> rvr, good thing reminders doesn't enter the distro, just the app store :D
[13:14] <mzanetti> and then the bugs are at least confined
[13:15] <rvr> mzanetti: Just kidding
[13:15] <rvr> mzanetti: I loved Machines vs Machines :)
[13:15] <mzanetti> nice to hear :)
[13:16] <rvr> Are you planning any other game?
[13:16] <mzanetti> rvr, definitely not one that requires sooo much efforts
[13:16] <mzanetti> took me almost a year to get m-vs-m done
[13:17] <mzanetti> and I didn't paint any graphics... mivoligo's time needs to be added on top
[13:17] <davmor2> rvr: read mzanetti guide to adding more levels :)
[13:17] <sil2100> Machines vs Machines was the game that made my girlfriend like Ubuntu Touch
[13:17] <mzanetti> hah
[13:17] <cwayne_> sil2100, mine was dropping letters :)
[13:18] <davmor2> mzanetti: that's it, it's GirlFriend Friendly you can't leave it there ;)
[13:18] <mzanetti> too bad dropping letters only works in english
[13:19] <davmor2> sil2100: see if she likes uu then you really can pick on mzanetti to make more ;)
[13:20] <kenvandine> mzanetti, hopefully you could create something cool more easily now if you used bacon2d, instead of rolling your own :)
[13:20] <kenvandine> i'd love to see another game from mzanetti!
[13:21] <mzanetti> we'll see... I did have a play with bacon2d but I found it somewhat limiting. it works great for some simple things, but if you need something that's not supporte ootb, it gets a pain to get it done
[13:22] <kenvandine> mzanetti, yeah, depends on what you're looking for
[13:22] <mzanetti> maybe I just used it wrong
[13:22] <kenvandine> we need some more behaviors for sure
[13:22] <kenvandine> i'd love to hear what you were trying to do
[13:22] <kenvandine> that'd be better for #bacon2d though :)
[13:24] <chrisccoulson> pmcgowan, mterry, sil2100, the change in https://code.launchpad.net/~mterry/oxide/mirserver-1.5/+merge/255819 is not right for 1.5
[13:24] <mterry> chrisccoulson, yeah I remember you saying there was a complication, but I couldn't find it in an email
[13:24] <chrisccoulson> the right fix for 1.5 (as is in 1.6) is to disable GPU access entirely when the platform is mirserver
[13:25] <mterry> chrisccoulson, is that hard/
[13:25] <pmcgowan> which is  the same as what we had in 1.2?
[13:25] <mterry> ?
[13:26] <chrisccoulson> pmcgowan, I don't understand why people keep mentioning 1.2. 1.2 is ancient, and has the same issue as 1.5 (unrecognized platforms result in us turning on the osmesa backend in Chromium)
[13:26] <chrisccoulson> This hasn't changed
[13:27] <chrisccoulson> I'm pretty sure the browser won't even run with 1.2 anymore
[13:27] <pmcgowan> chrisccoulson, I was assuming that this crash did not occur and we could see the terms page from the wizard
[13:28] <pmcgowan> to be clear we dont want 1.2, just trying to understand when the issue appeared and safest fix
[13:32] <mterry> chrisccoulson, yeah I am also confused on when this bug appeared.  terms & conditions used to work
[13:32] <mterry> but that's not super relevant rightnow
[13:32] <mterry> chrisccoulson, is it difficult to disable GPU access entirely in mirserver mode?
[13:34] <chrisccoulson> mterry, this is the one that fixes it, although it wasn't the original intention of the change http://bazaar.launchpad.net/~oxide-developers/oxide/1.6/revision/944
[13:37] <pmcgowan> chrisccoulson, mterry we need to decide if putting those changes into 1.5.5 is a better plan than fixing and testing 1.6
[13:37] <chrisccoulson> well, 1.6 is fixed already ;)
[13:37] <mterry> chrisccoulson, did you see that there were some regressions found in 1.6?  Do you know how easy those might be to fix / how risky the 1.6 landing is?
[13:38] <chrisccoulson> mterry, I've only been made aware of 1 regression, which I've fixed already
[13:39] <sil2100> chrisccoulson: how well tested is 1.6 then?
[13:40] <sil2100> Since we already have it in rtm and it might be easiest to just get the fixes in and roll with it, but we need to be sure that it has no risk involved
[13:40] <sil2100> Because 14.09 is essentially what the phone users get
[13:40]  * sil2100 thought that releases like these are well tested anyway
[13:42] <dbarth_> hmm, apparently, there is another build issue getting the source tarball in that famous silo 28
[13:44] <chrisccoulson> sil2100, well, I mostly test what I work on in trunk (which is currently 1.7). But this was trunk until 11th March, and has only had changes that fix high severity issues since (basically http://bazaar.launchpad.net/~oxide-developers/oxide/1.6/revision/1017, http://bazaar.launchpad.net/~oxide-developers/oxide/1.6/revision/1021, http://bazaar.launchpad.net/~oxide-developers/oxide/1.6/revision/1022, http://bazaar.launchpad.net/~oxid
[13:44] <chrisccoulson> e-developers/oxide/1.6/revision/1024, http://bazaar.launchpad.net/~oxide-developers/oxide/1.6/revision/1025)
[13:46] <pmcgowan> chrisccoulson, do you have a new build with your fix coming then?
[13:46] <chrisccoulson> pmcgowan, yeah. It takes a little while to create the tarball though :)
[13:46] <sil2100> ;)
[13:46] <chrisccoulson> I've stopped everything else so my machine can go as quick as it can
[13:47] <sil2100> chrisccoulson: thanks!
[13:47] <sil2100> Greatly appreciated
[14:08]  * sil2100 off again
[14:17] <mardy> Mirv: gpg error again: https://ci-train.ubuntu.com/job/ubuntu-landing-028-1-build/55/console
[15:35] <ted> trainguards, could I get silos for lines 63 and 64 please?
[16:15] <Mirv> ted: all full, but I just published one so robert should be able to assign you at least one later
[16:16] <kenvandine> sil2100, i need up upload a fix for syncevolution for silo 30, which is just a dput
[16:16] <kenvandine> the previous upload never got published
[16:17] <kenvandine> so i don't want to bump the revision, since it never made it to vivid
[16:17] <kenvandine> sil2100, i tried just deleting the current package from the PPA, but of course it still rejects it because it knows that version was uploaded to it before
[16:18] <kenvandine> sil2100, if i delete the silo and create a new one, would it let me upload the same  version with different contents?
[16:20] <Mirv> kenvandine: the only possibility is to trick by assigning another silo and uploading there, then cleaning the old one. robru should be able to help with that too when 006 is available and then ted would get 030
[16:21] <cyphermox> psivaa_: can you please check why it seems the installer / vm isn't ever starting lately for the Smoke Testing vivid-desktop-amd64-smoke-default job?
[16:21] <Mirv> the same silo can't be reused no matter what
[16:21] <robru> kenvandine: in theory, yeah, except there are no free silos, so if you free and reassign you'll just get the same ppa back again
[16:21] <kenvandine> oh... no free silos :/
[16:22] <kenvandine> robru, can i get dibs on silo 6 then?  since i'll be giving up silo 30?
[16:22] <robru> kenvandine: I blame SRUs, of which there are 4, and two of them have just been sitting for a month
[16:22] <robru> kenvandine: sure
[16:23] <kenvandine> robru, it's line 40 on the spreadsheet, syncevolution
[16:23] <psivaa_> cyphermox: I'm about to finish in a few minutes, would you mind cihelp for this please?
[16:23] <kenvandine> robru, will you assign that when it's available?
[16:23] <robru> kenvandine: sure
[16:23] <kenvandine> robru, thx!
[16:23] <kenvandine> renatu, ^^
[16:23] <robru> kenvandine: you're welcome. should I free 30 then?
[16:24] <cyphermox> cihelp: could someone please check why it seems the installer / vm isn't ever starting lately for the Smoke Testing vivid-desktop-amd64-smoke-default job?
[16:24] <kenvandine> renatu, i'll upload that once robru does his thing :)
[16:24] <kenvandine> robru, you can
[16:24] <robru> k
[16:24] <kenvandine> as long as we'll get 6 :)
[16:25]  * Mirv sees robru, goes back to living room mode
[16:25] <robru> ted: one silo freed up, do you have a preference for which landing you want to do first?
[16:25] <robru> Mirv: morning ;-)
[16:25] <renatu> kenvandine, thanks
[16:25] <Mirv> robru: morning!
[16:36] <bregma> trainguards, could I get a reconfigure for line 54 (silo ubuntu/landing-014) please?
[16:37] <robru> bregma: on it
[16:39] <robru> Mirv: can I free 18? we're really tight
[16:40] <robru> dbarth: alex_abreu: what's the deal with webbrowser-app in silos 3 and 22? they're dirty and then you have another one in 17 that's awaiting qa. can you combine those? or can I just free 3 and 22 for now since other people are waiting for silos?
[16:41] <alex_abreu> robru, I'll rebuild silo 3 (it is a testing silo pending review), same for silo 22
[16:42] <alex_abreu> robru, we cannot combine them
[16:42] <robru> alex_abreu: you read my mind,ok ;-)
[16:43] <robru> stupid 29 free rtm silos. useless!
[16:44] <robru> boiko: poke about messaging-app in silo 29. are you using that? can I free it? we've run out
[16:51] <ted> robru, The UAL one. The other is more to tide us over until W opens.
[16:56] <robru> ted: heh, ok. with the crazy silo crunch we have right now I don't think I can justify assigning any silos for W. you got UAL in silo 30 for now
[16:57] <ted> robru, Hmm, okay. Is there a way to add silos? In general, we just need a place to collaborate.
[16:57] <boiko> robru: sorry, I was out for lunch, so, I am finishing testing it
[16:58]  * ogra_ always thought we couldnt use a new distro in LP until it has the actual name set up
[16:58] <boiko> robru: you can free silo 21 though, we can get it later to continue testing, that's fine
[16:58] <ogra_> did that change ?
[16:59] <robru> ogra_: no I think these W silos are just building in vivid for early testing before rebuilding for W later
[16:59] <robru> boiko: thanks
[16:59] <ogra_> ah
[17:00] <ted> Yeah, that was the goal. It's a feature, so it isn't for vivid.
[17:00] <robru> kenvandine: ok you got silo 21 for syncevolution
[17:03] <kenvandine> robru, thx!
[17:03] <robru> kenvandine: you're welcome
[17:03] <boiko> robru: I assume om26er is finishing his tests on silo 009 too, so that one is likely to be available if he is happy about it
[17:03] <robru> boiko: great
[17:04] <kenvandine> bfiller, renatu: i uploaded syncevolution to silo 21 and kicked off a watch only build job
[17:05] <psivaa_> cyphermox: just had a brief look at the installation, there seems to be an issue during the installation. Stuck at 'Reticulating splines' stage. I do not have more logs/ information on this. sorry
[17:05] <psivaa_> i really need to go now
[17:06] <robru> bregma: ping
[17:06] <bregma> ungh?
[17:08] <robru> bregma: hey, regarding your two trusty SRUs, I see they're both in proposed. is it ok with you if I free those silos? the packages won't be lost from trusty-proposed, it just means you'll have to manually merge your trusty branches later when the SRUs complete. it's just that we're super-crunched for silos right now and these are the two oldest ones.
[17:09] <bregma> is the list of MPs saved in the spreadsheet sdomewhere so I can consult it for manual merge?
[17:10] <robru> bregma: yeah, but even better, the train has pre-merged them for you (also with the debian changelog entry you need) so it's really just one branch you need to push at the end. I can email you the branch locations
[17:10] <bregma> mo better even
[17:10] <robru> bregma: sweet, thanks
[17:10] <bregma> OK, I'm hip wid that
[17:11] <josepht> cyphermox: I'm in a meeting now, but I'll look into it.
[17:12] <robru> bregma: ok, email sent! freeing silos! thanks again ;-)
[17:14] <robru> ralsina: lool: are either of you actually around to use a silo if I give you one?
[17:14] <ralsina> robru: yes
[17:14] <robru> ralsina: sweet, one sec
[17:15] <robru> ralsina: alright you got silo 2
[17:15] <ralsina> awesome, thx
[17:16] <robru> you're welcome
[17:20] <bfiller> kenvandine: thanks
[17:21] <robru> jgdx: what's the deal with those two spreadsheet rows you have? do you need a silo?
[17:25] <jgdx> robru, yea
[17:26] <robru> jgdx: why are there two rows? can you combine them into one?
[17:27] <jgdx> robru, one sec
[17:27] <jgdx> kenvandine, what do you think about combining rows 32, 31?
[17:27] <jgdx> seb128, you still around?
[17:27] <robru> jgdx: thanks. partly we're short on silos so it's hard to justify assigning two silos, partly it's difficult to coordinate two conflicting silos for the same package like that
[17:28] <jgdx> robru, rog
[17:28]  * kenvandine looks
[17:28] <kenvandine> jgdx, that's fine
[17:31] <jgdx> robru, updated, one silo.
[17:31] <robru> jgdx: thanks
[17:31] <jgdx> thank you
[17:32] <robru> jgdx: ok, you got silo 6. you're welcome!
[17:32] <jgdx> robru, thank you sir
[17:33] <seb128> jgdx, not really no, why?
[17:33] <robru> jgdx: you're welcome
[17:33] <jgdx> seb128, wondering if you're okay with me squeezing battery refresh and bluetooth null device branches into a silo with other uss fixes
[17:33] <jgdx> but let's try it
[17:34] <kenvandine> serious silo shortage
[17:45] <seb128> jgdx, yeah, sure
[17:45] <sil2100> pmcgowan, chrisccoulson, jibel: what's the current status?
[17:45] <sil2100> I just got back, had a really tiring ride home
[17:47] <robru> jgdx: you have to click build on silo 6 ;-)
[18:01] <jibel> sil2100, 3 online account tests left on the regression test plan of 269, test plans of webbrowser and webcontainer fully passed with oxide 1.6 excepted the known 'zoom out' issue, test plan of webapps in progress, url with intent doesn't work with google maps, alex_abreu is trying to reproduce apparently. You can track the progress on the qa board
[18:02] <jibel> sil2100, now waiting for 270 to re-run the sanity testsuite
[18:02] <jibel> sil2100, 270 = 269 + zoom fix
[18:02] <alex_abreu> jibel, yes it does work (gmaps), the thing is that the test case is not valid anymore, gmaps has changed the content of the served website (there are no more intent:// url)
[18:02] <alex_abreu> jibel, welcome to webapps :)
[18:03] <jibel> alex_abreu, nice, thanks.
[18:04] <jibel> sil2100, ^ everything appears copacetic
[18:05] <sil2100> \o/
[18:06] <sil2100> Is the new oxide with the zoom fix still building?
[18:06] <jibel> chrisccoulson, ^
[18:06] <sil2100> Ok, I see armhf still building
[18:07] <sil2100> Might take another 2-3 hours
[18:07] <sil2100> heh...
[18:07] <sil2100> jibel: anyway, good work! I guess we should be indeed good once this one lands :)
[18:11] <jibel> started 3h ago + 2h to build an image, it'll be 1:00AM my time
[18:20] <popey> uh.
[18:21] <popey> cihelp: can someone validate something in jenkins please? I uploaded calculator reboot to the store, and have a horrid feeling it will break the automated testing dashboard because it's not /trunk.
[18:22] <cyphermox> psivaa-afk: josepht: ubiquity itself has no splines that require reticulation, that must be something introduced by utah.
[18:22] <jgdx> robru, done! (silo 6 is building)
[18:23] <robru> cyphermox: stop playing SimCity2000
[18:23] <robru> jgdx: thanks
[18:23] <cyphermox> robru: tell that to whomever bzr blames for that template.
[18:23] <cyphermox> :)
[18:24] <robru> cyphermox: lol
[18:24] <cyphermox> it's the message it shows for success_command; so I'm guessing some late installation scripts for utah are borked.
[18:41] <josepht> popey: it will pull the tests in the click manifest
[18:42] <Mirv> robru: hey. yes we don't need to test 018 more at the moment so feel free to clean it. the unity8 hang one. also, I could fix the version bloat in another silo.
[18:43] <Mirv> also, good night.
[18:43] <robru> Mirv: night, thanks
[18:59] <cwayne> davmor2, yo
[18:59]  * davmor2 logs off quickly in the hope that nobody thinks he is about still
[19:00] <davmor2> cwayne: what's up bud
[19:01] <cwayne> davmor2, just curious if there was an update on what's goin on with oxide and the ota3 image
[19:02] <davmor2> cwayne: still building as far as I know.  I think it will be monday now
[19:05] <cwayne> davmor2, ack.  i'm gonna prepare a custom tar with the caught up clicks from the store just in case you guys want it
[19:05] <cwayne> sound alright?
[19:06] <davmor2> cwayne: cool
[19:08] <cwayne> davmor2, cool beans, I'll send ya out an email when it's ready
[19:08] <cwayne> i'll be off monday but lets be honest I'll be around to push if decided :)
[19:09] <davmor2> cwayne: you are always around ;)  Always!!!!! :D
[19:10] <cwayne> :P
[19:12] <davmor2> cwayne: is it a case of pinging on telegram monday?
[19:13] <cwayne> davmor2, probably yeah
[19:31] <chrisccoulson> sil2100, sorry, I went for dinner
[19:31] <chrisccoulson> were any other issues found with the initial build?
[20:07] <ralsina> robru: looks like row 50 in the spreadsheet is very optimistic: it said "can publish" when I went to mark it as tested :-)
[20:11] <robru> ralsina: yeah so for some reason it's not marked as requiring qa
[20:15] <ralsina> robru: np, I'll just leave it there for QA to pickup, have a nice weekend!
[21:15] <pmcgowan> sil2100, chrisccoulson  oxide is done
[21:42] <robru> cihelp http://d-jenkins.ubuntu-ci:8080/view/Vivid/view/BootTest/job/vivid-boottest-messaging-app/6/ this looks transient, can somebody retry it for me? I don't have permission, thanks
[21:45] <fginther> popey, I took a closer look at the calculator/reboot problem you mentioned. If you can upload a new click from http://s-jenkins.ubuntu-ci:8080/job/calculator-app-reboot-click/109/, I think it should just work
[21:46] <fginther> popey, the branch name wasn't getting set via the cmake variables, it is now.
[21:46] <popey> fginther: r156?
[21:47] <josepht> robru: done
[21:47] <robru> josepht: thanks!
[21:47] <josepht> robru: np
[21:47] <fginther> popey, yes, com.ubuntu.calculator_2.0.156_all.click built by build #109 has the proper branch name
[21:47] <popey> ok
[21:47] <fginther> popey, that was the latest revno
[21:48] <pmcgowan> robru, do you know if sil2100 was going to grab that new oxide and kick a build?
[21:49] <robru> josepht: hmmm, looks like it got the same failure again, thoughts?
[21:49] <robru> pmcgowan: not sure, he didn't say. it's quite late for him now...
[21:49] <pmcgowan> robru, ok
[21:49] <fginther> popey, but I see that lp:ubuntu-calculator-app is also aliased to the reboot branch now. That should also work
[21:49] <robru> pmcgowan: seems like a logical course of action though... want me to do it?
[21:50] <popey> fginther: so, leave it and don't upload, or upload? :)
[21:50] <fginther> popey, one second. Let me triple check :-)
[21:50] <popey> :)
[21:51] <pmcgowan> robru, yeah, you know where the oxide is
[21:51] <pmcgowan> ?
[21:52] <robru> pmcgowan: heh, no.
[21:52] <robru> chrisccoulson: what ppa was oxide building in?
[21:52] <pmcgowan> https://launchpad.net/~phablet-team/+archive/ubuntu/ppa
[21:52] <robru> oh
[21:52] <robru> chrisccoulson: nm
[21:52] <robru> pmcgowan: thanks
[21:52] <pmcgowan> ty
[21:53] <robru> pmcgowan: and you want that published to rtm?
[21:53] <pmcgowan> robru, yes, it has one regression fix
[21:53] <chrisccoulson> remember it needs to be binary copied - if it's rebuilt against rtm then it won't work
[21:53] <robru> pmcgowan: on it
[21:53] <pmcgowan> aha he is here
[21:53] <robru> chrisccoulson: sure thing
[21:53] <chrisccoulson> thanks
[21:53] <pmcgowan> cool
[21:54] <pmcgowan> thanks chrisccoulson
[21:55] <fginther> popey, the old branch is gone. Do we still need to run tests against the 'old' version of the calculator?
[22:00] <fginther> popey, there doesn't appear to be an immediate advantage to doing a new upload, the lp:ubuntu-calculator-app/reboot and lp:ubuntu-calculator-app branches both point to the same thing. But if it becomes a problem, we should be in a better place to deal with it in the future
[22:00] <popey> ok
[22:00] <popey> I'd rather not upload anyway, 11pm on a friday night :)
[22:01] <popey> thanks for looking
[22:01] <fginther> popey, np, have a good night
[22:08] <robru> pmcgowan: wait, I'm confused. does the silo need QA or should I just publish it so they can qa the resulting image?
[22:14] <ev> cyphermox: did you test your ubiquity upload (https://lists.ubuntu.com/archives/vivid-changes/2015-April/007789.html) with an installation?
[22:15] <ev> I am just guessing, but given that it's not rebooting after the install in CI or when run locally, it seems the likely cause
[22:15] <ev> josepht: ^ hi
[22:31] <cyphermox> ev, I did
[22:32] <ev> weird
[22:32] <cyphermox> However, makes sense that would be the Casper issue still
[22:32] <ev> maybe it's transient?
[22:32] <ev> which casper issue is this?
[22:33] <ev> and I had gotten so far without hearing about our friendly ghost of an initramfs
[22:33] <cyphermox> In a vm it looks like it's stuck in graphical mode, but it's really the Casper eject and reboot script that gets started
[22:34] <cyphermox> But sadly on shutdown with systemd Plymouth won't get user input to finish rebooting and it freezes graphical in VMs. I'm still working on a fix that helps with the VMs at least
[22:34] <josepht> cyphermox: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/966480 this one?
[22:34] <cyphermox> Not quite, but similar
[22:34] <cyphermox> That said...
[22:35] <cyphermox> You should still get ubiquity disappearing from the screen I'd expect
[22:36] <cyphermox> I will need help figuring out how to convince plymouth to catch input despite systemd
[22:36] <robru> chrisccoulson: https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-000-1-build/lastSuccessfulBuild/artifact/oxide-qt_packaging_changes.diff/*view*/ this looks weird. what happened to the changelog there?
[22:36] <josepht> cyphermox: mine got to the point where there's nothing on the screen but the aubergine fade background
[22:36] <cyphermox> Right, that's what I'd expect to ser
[22:36] <cyphermox> see
[22:37] <chrisccoulson> robru, did you copy vivid instead of utopic?
[22:37] <robru> chrisccoulson: sure did!
[22:37] <cyphermox> That's plymouth not quite playing nice with systemd on shutdown
[22:37] <chrisccoulson> that's why :)
[22:37] <robru> chrisccoulson: thanks, will grab the right one then ;-)
[22:44] <josepht> cyphermox: is there anything else you need from me?
[22:46] <robru> josepht: can you check http://d-jenkins.ubuntu-ci:8080/view/Vivid/view/BootTest/job/vivid-boottest-messaging-app/ again? seems same failure again, not sure if it's transient or not anymore...
[22:49] <josepht> robru: looking
[22:49] <ev> robru: what is leading you to believe that it was transient in the first place?
[22:52] <robru> ev: because I don't see how a change in messaging-app could result in "failed to provision device", it sounds like a hardware issue, not a failure of the app. was just hoping it was transient rather than some sort of catastrophic hw failure.
[22:54]  * ev nods
[22:55] <ev> hm, they are both happening on krillin 10, and the last success was on 09
[22:57] <josepht> ev: yeah I just saw that, is 10 one of the instrumented ones?
[22:58] <ev> josepht: trying something quickly
[22:59] <ev> shoved it on krillin 08: http://d-jenkins.ubuntu-ci:8080/view/Vivid/view/BootTest/job/vivid-boottest-messaging-app/8/console
[23:00] <sil2100> robru: hey
[23:00] <sil2100> robru: you published the oxide to rtm? :)
[23:00] <ev> I've reconfigured the job to use boottest&&krillin again
[23:03] <sil2100> robru: I think we want to publish oxide as it is without QA sign-off, kick a new image and hand it to QA
[23:03] <sil2100> robru: has it been binary copied to 002?
[23:04] <sil2100> Ok, I see it has
[23:07] <sil2100> robru: ok, I'll publish oxide now, wait for it to migrate, and kick a new image
[23:09] <ev> robru, josepht: that appears to have been the problem. I'm taking krillin 10 out of the mix.
[23:10] <josepht> ev: thanks, is that an instrumented device?
[23:10] <ev> no idea
[23:10] <ev> I can't remember how I found the list the last time
[23:10] <ev> I think it lives in some python script on heymann, annoyingly enough
[23:11] <ev> plars?
[23:12] <josepht> the playbook still refers to ashes
[23:18] <josepht> ev: I'm in heymann
[23:21] <josepht> ev: 10 is in recovery
[23:21] <ev> Stuck?
[23:22] <josepht> idk, adb devices lists it as 'recovery' I can get into it via 'adb shell'
[23:24] <sil2100> Ok, oxide-qt migrated
[23:24] <sil2100> Kicking a new image
[23:26] <josepht> ev: nothing jumps out at me, any ideas or should I 'adb reboot' it?
[23:27] <sil2100> ToyKeeper: new image with the new oxide building as we speak
[23:27]  * sil2100 goes off
[23:27] <sil2100> o/
[23:31] <josepht> ev: it is instrumented according to device_info.py on heymann
[23:32] <ev> Hmm
[23:34] <ev> I think we should leave it disabled for investigation on Monday. Can you send a mail to the team?
[23:34] <ev> Not sure what else to try
[23:35] <imgbot> [23:35] <ev> But I don't want to ask IS to reset it just yet
[23:35] <ev> Not until we know more
[23:39] <josepht> ev: sure, we can reset it ourselves
[23:45] <josepht> ev: email sent.  I'm out before anyone else pings me.  See you in Austin.
[23:52] <robru> josepht: ah, I see silo 9 migrated now, thanks for clearing up that boottest failure
[23:52] <robru> ev: thanks also ^


[02:15] <Unit193> I PPA'd a thing.
[05:27] -SwissBot:#xubuntu-devel- ::xubuntu-default-settings:: [trunk] r674 Launchpad automatic translations update. (by Launchpad Translations on behalf of xubuntu-dev)
[05:28] <Unit193> Sooo...
[05:31] <Unit193> bluesabre: Which PPAs plan to support all of Bionic's lifecycle?
[06:08] <flocculant> Unit193: yea - asking about core
[06:09] <Unit193> "It contains only the latest and greatest virii"
[06:10] <flocculant> :P
[06:10] <flocculant> I didn't think it had gnome software
[06:11] <Unit193> I, err, might heavily object to that, yes.
[06:11] <flocculant> :D
[06:11] <Unit193> It mainly has numlockx so you won't kill me. :3
[06:12] <Unit193> (Nah, underlaying stuff like that would be a bear to track down, only makes sense to seed.)
[06:12] <flocculant> :)
[06:13] <Unit193> So, would you heavily object if I asked about linking Core at the bottom of the least read release announcements/notes?
[06:15] <flocculant> Unit193: nope - I'd not object to you asking about that, nor would I object to doing it :p
[06:16] <Unit193> I entirely understand if the release people don't approve, tis fine.
[06:16] <flocculant> on the techy one? https://wiki.xubuntu.org/releases/18.04/release-notes
[06:16] <flocculant> assuming you've got access - add it there yourself - beforre Changelogs I think would be best
[06:23] <Unit193> I think I do, also changelogs for xubuntu-(core,desktop,wallpapers) are for the binary packages, not sources, thus 404.
[06:23] <flocculant> can you edit those at the same time then please :p
[06:23] <Unit193> Yeah.
[06:23] <flocculant> cheers - someone mentioned that a short while ago - and I forgot to do anything about it
[06:26] <flocculant> Unit193: you realise that once 18.04 releases I'll copy that note to 18.10 - so anything you add will be there as well?
[06:26] <flocculant> don't suppose that's an issue though until it's finally official ...
[06:26] <flocculant> ...
[06:44] <Unit193> Don't think I see any problem.
[06:49] <flocculant> Unit193: I'll leave it to you then - if you've not got access - get it :D
[06:49] <flocculant> or pm me what you want to say there
[06:49] <flocculant> bbl
[08:25] <ali1234> flocculant: you can remove bug 1756614 from the blueprint - it turned out the bug was entirely caused by a non-xubuntu package
[10:25] <bluesabre> !team | Opinion on color emoji? We opted to use the non-color Symbola emoji font for 18.04, but I wanted to confirm that there was a consensus on this. See below link for more information.
[10:25] <bluesabre> https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1746310
[10:26] <bluesabre> Color: https://ubuntucommunity.s3-us-east-2.amazonaws.com/original/1X/73d2960cc39ab675cf6ad2a0639d4791695edd74.jpg
[10:26] <bluesabre> Symbola: https://i.imgur.com/bnUpVoP.png
[10:28] <bluesabre> It should also be noted that this is only for support in GTK+ 3 applications. QT doesn't support it, Firefox ships their own support, and Chromium does it's own thing.
[10:38] <knome> personally i don't think we need to ship any emoji...
[10:44] <knome> that said, i guess if you want stuff like emoji, color is what you'd likely prefer
[10:44] <knome> whether those fit into the xubuntu looks... dunno
[12:38] <akxwi-dave> hmm.. prefer the colour ones personally.. but very rarely use emojis  😺 🤭  😃 ⛷🏍🍗🥠🍧🌑📈📉🖇📭🆗
[12:43] <slickymasterWork> my I'm with knome, personally I don't see the need in shipping emojis but if we do, then I'd go with the colour ones
[15:17] <donofrio_> how do I fix this https://pastebin.com/PqZ7mEBR
[17:44] <flocculant> bluesabre: I'm +1 to the majority - if there's no majority - I'm +1 what the dev team decide :p
[19:00] <flocculant> ali1234: did that - pretty sure you could have too
[19:03] <ali1234> flocculant: i'm not actually sure where the blueprint is. i only know that bug was on it cos of the little icon next to my list of bugs...
[19:08] <flocculant> ali1234: ok :)
[19:09] <flocculant> ftr you cand get to the blueprints from dev.xubuntu.org
[19:38] <pleia2> color emoji!
[19:51] <Unit193> I'm the only one that'd prefer symbola?  We ship a lot of GTK2, and as stated the color option isn't supported in Qt.
[19:54] <pleia2> yes
[19:55] <pleia2> what happens in GTK2 apps when it "isn't supported"?
[19:58] <Unit193> I presume it shows the typical 򒎃
[19:58] <pleia2> that won't do :(
[19:58] <pleia2> I'd rather have them render B&W everywhere than broken in half the places
[19:59] <Unit193> I don't know for sure, I have symbola.
[20:23] <ochosi> meh, did i miss anything?
[20:24] <Unit193> Since you disconnected or when?
[20:30] <ochosi> yeah
[20:30] <ochosi> stupid bouncer randomly reboots and doesn't reconnect irssi :/
[21:35] <Unit193> I'm fairly confused, I'm pretty sure I recently tried this but dropbox indicator works in sn-plug.
[21:37] <Unit193> I'm wondering if a dropbox update in the meantime finally fixed it?
[21:37]  * Unit193 shrugs.
[21:46] <ochosi> i'd say if it works now there
[21:46] <ochosi> 's less to worry about
[21:47] <ochosi> Unit193: any idea when/where/how the icon cache for elementary-xfce is created?
[21:47] <ochosi> the -darkest variant doesn#t seem to have one for some reason
[21:47] <ochosi> i thought it happens in the xubuntu-artwork package, but seemingly not
[21:47] <ochosi> (or i overlooked it)
[21:48] <Unit193> 	if which update-icon-caches >/dev/null 2>&1 ; then
[21:48] <Unit193> 		update-icon-caches /usr/share/icons/elementary-xfce /usr/share/icons/elementary-xfce-dark /usr/share/icons/elementary-xfce-darker
[21:48] <Unit193> 	fi
[21:54] <Unit193> ochosi: -darkest is just a symlink to -darker.
[22:01] <ali1234> it isn't... it contains symlinks, but it is a real directory and needs its own icon cache
[22:01] <ochosi> but the appearance dialog shows the corresponding warning
[22:01] <ochosi> ali1234: thanks for reporting that bug, i had forgotten about it again...
[22:11] <Unit193>                                 $needs_cache = 1 if -f and (/\.png$/ or /\.svg$/ or /\.xpm$/ or /\.icon$/);
[22:28] <ochosi> Unit193: right, so what do you suggest? just ignore the complaint of appearance settings and say it's expected?
[22:28] <Unit193> ochosi: I simply answered as to "why" it was happening.
[22:33] <ochosi> sry, my question wasn't ironic
[22:33] <ochosi> just wondering how to best fix this or if at all
[22:34] <ochosi> but currently still working on a greybird fix, so i'm happy if you'll take a look
[22:35] <Unit193> Just making it clear I'm not saying we shouldn't, just "why" it's happening.  One could simply add a rule like the above for darkest?
[22:36] <ali1234> what does that do? search for those file types?
[22:36] <ali1234> if so that's the problem. darkest doesn't contain any... it symlinks them. but it is still expected to have a cache
[22:36] <Unit193> dh_icons is what generates the update-icon-caches command from above, that is the search method it uses.
[22:37] <Unit193> I'd argue it should also look for index.theme.
[22:37] <ali1234> right
[22:37] <ali1234> really why search at all?
[22:38] <ochosi> Unit193: i'd tend to agree: if searching at all, it should also search for index.theme
[22:42] <ali1234> what are darker and darkest for anyway?
[22:44] <ochosi> distinguishes between panel and toolbar stuff
[22:44] <ochosi> so darker is bright icons for a dark panel and dark icons for the toolbar
[22:45] <ochosi> and darkest is dark monochrome icons for panel and toolbar
[22:45] <ochosi> all of that is completely superfluous with symbolic icons and gtk3
[22:46] <ochosi> so as soon as panel, thunar etc. are used in their gtk3 versions, we can get rid of all of that
[22:48] <bluesabre> re: emoji fonts, pretty sure the color emoji can only be rendered in gtk3, they'll be b&w everywhere else
[22:49] <bluesabre> I don't mind the b&w, but thought it was fair to ask
[22:50] <ochosi> bluesabre: heya! i need your package update magic before UIF
[22:50] <ochosi> what's my deadline?
[22:51] <ochosi> i just pushed a boatload of updates to elementary-xfce, so that's pretty much ready to ship
[22:51] <bluesabre> ochosi: UIF is tomorrow :D
[22:51] <ochosi> but in greybird from git master there is a tiny regression currently (only certain rare gtk2 widgets affected), unfortunately it seems hard to fix, but then again it would probably be bugfix anyway, no?
[22:52] <bluesabre> ochosi: if elementary-xfce is ready, I'll confirm the dangling icons are not present
[22:52] <bluesabre> ochosi: yes, bugfix
[22:52] <ochosi> k
[22:52] <ochosi> so i'll do a release of greybird and we'll see if i get to a bugfix before final freeze
[22:52] <bluesabre> I have something else for you with Greybird, in Chrome with GTK theme, the window controls are rendered 2x and blurry
[22:52] <ochosi> and for elementary-xfce i'll do a release now
[22:52] <bluesabre> ochosi: waaaaait
[22:52] <ochosi> and we can also pull them into xubuntu-artwork
[22:52] <bluesabre> one sec :)
[22:52] <ochosi> hehe
[22:53] <ochosi> i recently fixed some chrome rendering issues though with greybird, maybe different ones
[22:53] <ochosi> can check
[22:53] <ochosi> what version?
[22:53] <ochosi> i have 64.0
[22:53] <ochosi> and the window controls with gtk look ok
[22:54] <ochosi> but i also don't have hidpi
[22:54] <ochosi> if that's what you're asking
[22:54] <bluesabre> the version I have at work... might be old :)
[22:54] <ochosi> hehe
[22:54] <ochosi> anyway, that's another bugfix imho
[22:55] <bluesabre> agreed
[22:55] <bluesabre> and not seeing it now
[22:55] <bluesabre> so maybe just fixed recently
[22:55] <ochosi> what's only half-ready in greybird currently (and what i'm not going to finish for 18.04 probably) is the hidpi support for CSD
[22:55] <bluesabre> that's fair
[22:55] <ochosi> but as xfwm4 also doesn't have a hidpi theme yet, it's probably not a huge problem
[22:55] <ochosi> i'd love to add it, but i still lack some icons (the basic ones are there though)
[22:56] <ochosi> and knome is slacking... :D
[22:56] <bluesabre> 1 sec might be more, lp:xubuntu-artwork is a behemoth
[22:56] <ochosi> hehe, i know
[22:56] <ochosi> i also added almost 1000 icon changes in the last days
[22:56] <ochosi> drawing and scaling lots of crap
[22:56] <ochosi> to be able to pull in all the upstream goodness
[22:57] <bluesabre> really did the cleaner emblems that landed sometime recently
[22:57] <bluesabre> *dig
[22:57] <ochosi> which ones? the colored circles?
[22:57] <bluesabre> oh
[22:58] <bluesabre> that was a different theme
[22:58] <bluesabre> sorry for my infidelity
[22:58] <ochosi> currently we don't really have that many emblems
[22:58] <ochosi> :o
[22:58] <ochosi> :D
[22:58] <ochosi> it's ok, i'm sure you also switched to arc already ;)
[22:58] <ochosi> (or whatever is hip these days)
[22:58] <bluesabre> ochosi: got a few dangling symlinks
[22:59] <bluesabre> Checking dangling symlinks (after)
[22:59] <bluesabre> lrwxrwxrwx 1 15 Mar 21 18:58 wip/elementary-xfce/actions/128/stock_delete.png -> edit-delete.png
[22:59] <bluesabre> lrwxrwxrwx 1 15 Mar 21 18:58 wip/elementary-xfce/actions/128/editdelete.png -> edit-delete.png
[22:59] <bluesabre> lrwxrwxrwx 1 15 Mar 21 18:58 wip/elementary-xfce/actions/128/stock_not.png -> edit-delete.png
[22:59] <bluesabre> lrwxrwxrwx 1 31 Mar 21 18:58 wip/elementary-xfce/actions/128/edit-delete.png -> ../../places/128/user-trash.png
[22:59] <bluesabre> lrwxrwxrwx 1 15 Mar 21 18:58 wip/elementary-xfce/actions/128/gtk-delete.png -> edit-delete.png
[22:59] <bluesabre> ochosi: actually prefer greybird these days
[22:59] <bluesabre> just the most compatible with everything
[22:59] <ochosi> \o/
[22:59] <ochosi> is those all dangling symlinks?
[22:59] <ochosi> i can quickly fix those..
[22:59] <bluesabre> seemingly
[23:00] <bluesabre> once those are fixed, we should be in good shape
[23:00] <bluesabre> ready for both releases :)
[23:00] <bluesabre> going to get ice cream, bbiab
[23:01] <ochosi> fixed
[23:01] <ochosi> already pushed it
[23:01] <bluesabre> testing again
[23:01] <bluesabre> good to go
[23:01] <ochosi> yay
[23:02] <ochosi> enjoy the ice-cream
[23:02] <ochosi> i'll tag both releases then
[23:02] <bluesabre> thx
[23:02] <ochosi> thanks for doing the last-minute upload
[23:02] <bluesabre> it's my speciality
[23:02] <bluesabre> been doing it for years now
[23:02] <ochosi> :D
[23:03] <ochosi> it's gonna be a pretty awesome release actually
[23:03] <ochosi> much more goodness all over the place than expected
[23:03] <bluesabre> definitely
[23:06] <Unit193> bluesabre: Looks like the b/w versions are basically fallback, and incomplete in my testing.
[23:06] <Unit193> And yeah, really don't work so well in Qt, so I'd be in favor of symbola.
[23:07] <ochosi> bluesabre: https://github.com/shimmerproject/elementary-xfce/releases/tag/elementary-xfce-0.11
[23:07] <Unit193> https://bugs.debian.org/893746
[23:31] <bluesabre> Unit193: I'm in favor of symbola for the consistency between desktops
[23:31] <bluesabre> ochosi: much appreciated
[23:36] <bluesabre> lol
[23:36] <bluesabre> something locked dpkg while I was installing updates
[23:37] <ochosi> bluesabre: https://github.com/shimmerproject/Greybird/releases/tag/v3.22.7
[23:37] <ochosi> nighty!
[23:37] <ochosi> and thanks again
[23:37] <bluesabre> ochosi: thanks! have a good night
[23:46] <Unit193> bluesabre: Also talked to the dh-autoreconf maintainer first, he'll look after bionic release.
[23:47] <bluesabre> Unit193: nice
[23:48] <Unit193> May I presume that you don't plan to migrate any of the packages to git?
[23:48] <bluesabre> not currently planning on git migrations, maybe before 18.04 release though
[23:49] <Unit193> (Meant pkg-xfce svn/git.)
[23:49] <bluesabre> probably not
[23:50] <bluesabre> you should see the messes I'm making in PAPT land
[23:50] <Unit193> There's a nice migration script at least!  But yeeah, I don't want to push any either. :3


[08:44] <godbyk> thorwil: Interestingly, it looks like I'm increasing the number of lines per page (text block height) from 44 to 54 for US letter paper, but not adjusting A4 paper's default of 49 lines.  I'll have to look into that.
[08:55] <thorwil> godbyk: thanks. let me know if you do change any margin
[08:58] <godbyk> thorwil: I will. I apparently haven't done much with A4 in a while. I'll revisit that after we get this US English edition published.
[09:28] <godbyk> Virtual machines are rather handy.
[15:03] <hannie> hi vibhav how are you dong?
[15:03] <hannie> *doing
[15:03] <hannie> and hi herat too, of course
[15:04] <vibhav> Im fine
[15:04] <vibhav> Looking for some last minute changes
[15:05] <hannie> ok
[15:06] <hannie> next week I hope to get more people who will help editing the manual
[15:06] <vibhav> from where?
[15:06] <hannie> omg, planet etc.
[15:06] <vibhav> cool
[15:06] <hannie> I have to send a good story on what we expect editors to do exactly
[15:07] <hannie> and I haven't figured out what I want to write yet


[06:31] <nishi> Nice to meet you
[06:32] <nishi> ??? aaa...
[06:32] <nishi> what should i do?
[18:53] <animaguy> Hello.
[23:11] <antivapor1> hi! i have two monitors that are mirroring each other. there aren't any alternate options in the display settings,  how do i add those options?
[23:12] <len-1304> under settings look for arandr
[23:14] <antivapor1> got it, have a default setting, what next?
[23:15] <len-1304> If you want it to boot that way go back to setting manager and display and change anything back and forth that wil save it.
[23:16] <len-1304> It 's a bit hacky right now. arandr will save a file that can be fed to xrandr at login too.
[23:17] <antivapor1> do i need to save a second setting or use that script? i currently only have a single 'default' screen shown even though two monitors are connected. :)
[23:18] <antivapor1> and display is same on both
[23:18] <len-1304> arandr should allow you to drag one off the top of the other and position it
[23:20] <antivapor1> http://i.imgur.com/EVvK3.png nobody is beneath it
[23:22] <len-1304> You are right. in arandr  in the outputs pull down menu does it show something that is not enabled?
[23:23] <len-1304> I don't have two monitors to play with. I tested it by bringing my net book and using my desktop monitor for a bit. I'm going from memory.
[23:24] <len-1304> What kind of video are you using? Which driver?
[23:24] <antivapor1> the first drop says 'default' and that has 'active' checked, and then there are also resolution and orientation for output. thanks for testing btw. i suppose i might need a driver, i believe i have an AMD / ATI
[23:24] <antivapor1> ah yes, same thought
[23:24] <len-1304> If you are using the open source driver it should work ok.
[23:25] <len-1304> if you are using the ATI closed source ones then you need the ATI utility to do things.
[23:25] <len-1304> (nvidia is the saem)
[23:25] <len-1304> *same
[23:26] <antivapor1> nope, using open source, but maybe i should get the utility.
[23:26] <len-1304> It looks like X is only seeing one monitor and the IF is just cloning it.
[23:27] <holstein> i had to install the proprietary driver for my nvidia to do dual head
[23:28] <holstein> i should test on my ati hardware, but it really is different from device to device
[23:28] <len-1304> holstein,  I must have been lucky :)
[23:28] <holstein> we cant really have a "how to" that will just work for everyone... its fiddly
[23:28] <holstein> OR, it can be fiddly.. sometimes it just works
[23:28] <len-1304> If xrandr sees it, then things work.
[23:29] <holstein> len-1304: i couldnt seem to get it to "span"
[23:29] <antivapor1> i used lspci -nn  grep VGA to see that I have ATI RS780 [Radeon HD 3200] and  RV620 [Radeon HD 3450], are these the monitors?
[23:29] <len-1304> I'm not sure, I just know I could place the two side by side.
[23:30] <antivapor1> Oh, i think theyre the graphics cards...
[23:30] <len-1304> You have two cards?
[23:31] <antivapor1> I might??
[23:31] <len-1304> You should know :) Did you put a second one in?
[23:31] <holstein> antivapor1: sometimes when im beating my head against the wall, i'll fire up a knoppix live CD (or puppy) configure the dual head, copy the xorg.conf and bring that back to ubuntu and tweak as needed
[23:32] <len-1304> Are both monitors plugged into the same card? Is this a laptop?
[23:32] <holstein> antivapor1: if you look and have 2 graphics cards, then you have 2 graphics cards
[23:32] <len-1304> holstein, cool what do they do different?
[23:33] <antivapor1> no, i didnt put one in, but maybe there was a default one, and then a better one. Both are plugged into same card. I'm dual-booted windows and it works okay there.
[23:33] <holstein> len-1304: knoppix? im not sure, but sometimes it gives me another viable option and an easier place to start
[23:34] <len-1304> Vanilla defaults to side by side these days
[23:34] <holstein> antivapor1: if you dont have the proprietary driver, i would just try that
[23:36] <antivapor1> hmm, i should use fglrx and edit the xorg.conf?
[23:39] <len-1304> I really don't know... It's beyond me.
[23:40] <len-1304> The xsession logs may have some info.
[23:41] <len-1304> /var/log/Xorg.0.log
[23:41] <len-1304> Unplugging the second monitor and seeing what happens and plugging it back in.
[23:42] <len-1304> If the driver is doing anything for the second monitor it should show.
[23:44] <antivapor1> event9)
[23:44] <antivapor1> [    23.412] (II) No input driver specified, ignoring this device.
[23:44] <antivapor1> [    23.412] (II) This device may have been added with another device file.
[23:44] <antivapor1> [ 26649.827] (II) Open ACPI successful (/var/run/acpid.socket)
[23:44] <antivapor1> [ 26649.827] (II) VESA(0): Setting up VESA Mode 0x146 (1400x1050)
[23:47] <len-1304> typing xrandr in a terminal gives?
[23:47] <antivapor1> event9)
[23:47] <antivapor1> [    23.412] (II) No input driver specified, ignoring this device.
[23:47] <antivapor1> [    23.412] (II) This device may have been added with another device file.
[23:47] <antivapor1> [ 26649.827] (II) Open ACPI successful (/var/run/acpid.socket)
[23:47] <antivapor1> [ 26649.827] (II) VESA(0): Setting up VESA Mode 0x146 (1400x1050)
[23:48] <antivapor1> woops
[23:48] <antivapor1> xrandr: Failed to get size of gamma for output default
[23:48] <antivapor1> Screen 0: minimum 640 x 400, current 1400 x 1050, maximum 1400 x 1050
[23:48] <antivapor1> default connected 1400x1050+0+0 0mm x 0mm
[23:48] <antivapor1>    1400x1050       0.0*
[23:48] <antivapor1>    1280x1024       0.0
[23:48] <antivapor1>    1152x864        0.0
[23:48] <antivapor1>    1024x768        0.0
[23:48] <antivapor1>    800x600         0.0
[23:48] <antivapor1>    640x480         0.0
[23:48] <antivapor1>    720x400         0.0
[23:48] <antivapor1> tom@crannog:~$ ^C
[23:48] <len-1304> So still only screen 0
[23:49] <antivapor1> correct
[23:49] <len-1304> When I plug a second screen in I get two screen sections.
[23:50] <len-1304> The "ignoring this device" seems significant to me
[23:51] <antivapor1> agreed. still looking for how to install amd/ati drivers.. will update soon if i find.
[23:54] <antivapor1> you know where hardware drivers manager is?
[23:58] <lelapin> Hi !
[23:58] <antivapor1> ah, support for my chips were dropped, cause i have 3000 series http://wiki.debian.org/ATIProprietary