[00:33] <ric_s> Laney, mihall119, Are you there? Can you help me answer this question?
[00:33] <ric_s> https://sourceforge.net/p/xoscope/bugs/20/#2eef
[00:33] <ric_s> mhall119
[00:45] <sarnold> Trevinho: does 1552537 make any sense to you? two people report it on wily and xenial :/
[00:52] <Trevinho> sarnold: I can't reproduce that as well...
[00:52] <sarnold> Trevinho: thanks for giving it a look. I've got a feeling that it's user-induced somehow -- it almost always is :) -- but these reports never have enough to go on :(
[00:58] <Trevinho> sarnold: sure, it's better to check.
[05:56] <hikiko>  hi
[07:15] <pitti> Good morning
[09:03] <willcooke> morning all
[09:04] <Laney> morning
[09:10] <davmor2> Laney: guten tag
[09:34] <Laney> hey davmor2
[09:34] <Laney> wie gehts?
[09:41] <davmor2> meh and it's too early in the morning for mehs
[09:42] <davmor2> and too late in the week too
[09:44] <Laney> it's all going to be A OK!
[10:08]  * Sweet5hark1 lols at the npm javascript jenga breakdown.
[10:08] <Laney> oh cute, I'm seeing the new slideshow
[10:08] <Laney> is it me or should the gnome-software screenshot not have a bit of wallpaper on the rhs?
[10:08] <Laney> the others don't
[10:19] <willcooke> Laney, doh!
[10:19] <willcooke> you're right
[10:20]  * willcooke fires up gimp
[10:20] <Laney> heh
[10:20] <willcooke> Laney, have you got that screenshot link handy?
[10:20] <willcooke> I can probably grep for it
[10:20] <Laney> VERY!
[10:20] <Laney> http://people.canonical.com/~laney/weird-things/g-s.png
[10:20] <willcooke> supe
[10:20] <willcooke> r
[10:21] <Laney> I don't visit many other website with "weird" in the url
[10:21] <willcooke> hah!
[10:21] <willcooke> I tried "laney" in mine, but nothing
[10:21]  * Laney is a clickbait nonclicker
[10:22] <Sweet5hark1> "Ten things that Laney made me click -- see if those links will make you click too!"
[10:23] <willcooke> You won't believe ten things laney doesn't click on
[10:23] <Laney> number 8 made me spit out my coffee!
[10:23] <willcooke> :D:D:D
[10:24] <Laney> "You have just inserted a medium"
[10:24] <Laney> #shitubuntusays
[10:24] <willcooke> urgh
[10:25]  * Laney is going to use said medium to look at the hidpi ubiquity session
[10:25] <Laney> back shortly
[10:26] <Laney> realised that I don't have anywhere to install the thing to though which is a tad annoying
[10:28] <willcooke> can you repartition your drive?
[10:29] <willcooke> borrow 10GB from swap for a few hours?
[10:29] <darkxst> Laney, speaking of hidpi, plymouth upstream git now has hidpi support (but no release as yet) do we want to cherry-pick those patches?
[10:31] <Laney> darkxst: I know a-nothing, talk to slangasek maybe
[10:31] <Laney> have you tried it?
[10:31] <darkxst> Laney, I don't have a hidpi laptop, but ricotz says it works well
[10:36] <ricotz> Laney, darkxst, jfyi a package is locate here https://launchpad.net/~ricotz/+archive/ubuntu/staging/+packages?field.name_filter=&field.status_filter=published&field.series_filter=xenial
[10:42] <willcooke> Laney, slideshow fix:  http://bazaar.launchpad.net/~willcooke/ubiquity-slideshow-ubuntu/ubiquity-slideshow-ubuntu/revision/735
[10:42] <willcooke> Laney, will MP it
[10:45] <Laney> thx
[10:46] <willcooke> cyphermox, sorry (again).  Last one.  I'm fairly sure this time ;)  https://code.launchpad.net/~willcooke/ubiquity-slideshow-ubuntu/ubiquity-slideshow-ubuntu/+merge/289880
[10:46] <Laney> darkxst: ricotz: Suggest you speak to slangasek, IMO it would be nice but it's not my decision
[11:00] <desrt> good morning!
[11:03] <willcooke> hi desrt
[11:06] <davmor2> willcooke: one partially successful install from pending \o/
[11:06] <davmor2> willcooke: now to see if oem kills it
[11:06] <willcooke> davmor2, what changed?
[11:07] <davmor2> willcooke: I think infinity fixed the locale/glibc changes he made I could be wrong though
[11:08] <Laney> *I* fixed the locale problem and he fixed the vte one which was stopping ubiquity from launching
[11:08] <Laney> iz gud
[11:10] <Laney> what's up desrt
[11:12] <willcooke> desrt, Laney - any thoughts on this one:  https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1538471
[11:13] <willcooke> jamesh thinks he's narrowed it down to gir
[11:45] <davmor2> Laney: you're awesome sir remind me to slap you less ;)
[12:14] <andyrock> hey all
[12:18] <willcooke> hi andyrock
[12:18] <andyrock> bad news we got a core file
[12:18] <andyrock> but it's empty
[12:19] <willcooke> ha
[12:19] <willcooke> useful
[12:19] <andyrock> https://www.irccloud.com/pastebin/P8dvdGBx/
[12:19] <willcooke> handy
[12:20] <andyrock> but this error can be releated: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
[12:21] <andyrock> but still not sure if it's the cause or a result of the bug
[12:23] <willcooke> andyrock, whats next to try?
[12:24] <willcooke> hikiko mentioned that there were some broken packages as well?
[12:24] <hikiko> yes
[12:24] <andyrock> i'll try to save the core file and restore the snapshot
[12:25] <andyrock> likely we get a full bt
[12:25] <hikiko> andyrock, I've dist upgraded manually
[12:25] <Sweet5hark1> <- out: dentist
[12:25] <hikiko> and I see many problems here and there
[12:25] <hikiko> I believe that if  we fix broken packages/dependencies etc
[12:25] <hikiko> the session wont crash
[12:26] <hikiko> I'll note down the errors
[12:26] <hikiko> and send them to cyphermox
[12:26] <hikiko> he might be able to make more sense
[12:26] <hikiko> andyrock, I got no logs from the gui upgrade either
[12:26] <andyrock> mmm
[12:27] <hikiko> because the filesystem was corrupted after the crash
[12:27] <hikiko> it's very improbable
[12:27] <hikiko> that compiz causes this problem especially when the bug is "can't find libc"
[12:27] <andyrock> https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1555237/comments/10
[12:28] <andyrock> here he's able to make the session crash just upgrading few packages
[12:32] <hikiko> could be helpful :)
[12:34] <hikiko> andyrock,
[12:34] <hikiko> tbh I don't understand how
[12:34] <hikiko> it points out a problem in compiz?
[12:35] <hikiko> how did he end up with these packages?
[12:36] <hikiko>  insserv: warning: script 'cron' missing LSB tags and overrides
[12:36] <hikiko> I got this one too for another package
[12:36] <willcooke> for the record: It may indeed turn out to not be a problem in Compiz (quite likely in fact, but lets see) - however, the point here is not to rule out compiz but to narrow it down to what *is* causing the problem so that we can get it fixed.
[12:36] <hikiko> (willcooke's comment)
[12:36] <hikiko> that looks much more relevant
[12:36] <hikiko> to the error
[12:37] <hikiko> I believe that we have to fix the packages anyway
[12:37] <hikiko> what I would do
[12:37] <hikiko> is to dist-upgrade manually
[12:37] <hikiko> and fix every broken package
[12:37] <hikiko> every time it stops with an error
[12:38] <hikiko> and then try the visual upgrade
[12:38] <hikiko> the problem is
[12:38] <hikiko> I don't know how to do the fixes at all :/
[12:38] <hikiko> if someone could help on that
[12:39] <hikiko> we could make sure that there aren't any upgrade blockers
[12:39] <hikiko> when I perform the visual upgrade something is so broken that causes a kernel panic
[12:40] <hikiko> and the error is that there's no root fs
[12:40] <hikiko> without a proper fs
[12:40] <hikiko> it's impossible to retrieve any other info
[12:40] <hikiko> plus we ll have to fix the packages anyway
[12:40] <hikiko> because we would like the user to be able to complete the dist-upgrase
[12:40] <hikiko> upgrade*
[12:46] <andyrock> well the kernel panic can be a result of a unity crash
[12:46] <andyrock> because the unity crash can cause an X crash
[12:47] <andyrock> so if you leave the upgrade in a bad moment you can get a kernel crash
[12:48] <cyphermox> hikiko: things do *not* stop with an error. As the dist-upgrade gets done, compiz crashes and the session gets taken down before you can finish the upgrade, and it would continue if only there was still X to display prompts
[12:48] <cyphermox> hikiko: you may use an older image to test that, or a newer one than 20160322 provided that glibc was fixed
[12:49] <cyphermox> ie. glibc is a different issue that is already being fixed
[12:49] <Laney> s/being//
[12:49] <Laney> on the latest one anyway
[12:49] <hikiko> cyphermox, which images you suggest I use?
[12:49] <hikiko> when I dist upgrade, compiz doesnt crash
[12:49] <cyphermox> 20160323 should be good, I think
[12:50] <cyphermox> hikiko: no, it's not *just* upgrading compiz
[12:50] <cyphermox> you also need to wait for the screensaver to kick in
[12:50] <hikiko> so cyphermox what's the theory?
[12:50] <hikiko> that the screensaver crashes the visual update?
[12:51] <hikiko> and leaves the system in a weird condition?
[12:51] <cyphermox> I have no idea. compiz crashes, I upgraded manually until there was just the few desktop packages left I wrote down in my comment, because I couldn't reduce it any more than that
[12:51] <cyphermox> and in between I'd let the screensaver activate to try and get the system to crash again
[12:51] <cyphermox> I don't know enough about X or GL or compiz to know why the screensaver would change anything for compiz
[12:52] <hikiko> is it possible
[12:52] <cyphermox> that's why we asked for help
[12:52] <hikiko> that the screensaver
[12:52] <hikiko> uses a library that is upgraded by one of those packages
[12:52] <hikiko> and that's why it crashes?
[12:53] <cyphermox> that's still X or desktop.
[12:53] <cyphermox> have you tried upgrading things at all?
[12:53] <hikiko> cyphermox,
[12:54] <andyrock> cyphermox: X crashes as well here
[12:54] <hikiko> if you disable the screensaver
[12:54] <hikiko> you still have the issue
[12:54] <hikiko> x crashes too
[12:55] <cyphermox> hikiko: sure. if you prefer you may well look into that crash?
[12:55] <hikiko> cyphermox, I'm looking at it but it seems to me that the crash is a consequency of the upgrade crash
[12:56] <cyphermox> the upgrade does not appear to crash, what makes you think that?
[12:57] <hikiko> I think pitti had the same prob with willcooke and me and saw a similar message for insserv and cron
[12:57] <hikiko> cyphermox,
[12:57] <hikiko> after the crash I rebooted
[12:57] <cyphermox> do you have a stack trace?
[12:57] <hikiko> and got a kernel panic
[12:57] <hikiko> no
[12:57] <hikiko> the fs was in bad state
[12:57] <cyphermox> sure, but that's normal if the system freezes while you upgrade
[12:58] <hikiko> my theory is that:
[12:58] <cyphermox> our goal is for the system not to freeze and the X session not to die while upgrading
[12:58] <hikiko> either a post installation script is doing something or something is missing and makes x crash
[12:58] <hikiko> or
[12:59] <hikiko> a visual program crashes and stops the upgrade
[12:59] <hikiko> but I think 1 is more possible
[12:59] <hikiko> because I had dist-upgrade problems
[12:59] <hikiko> plus
[12:59] <hikiko> compiz seems to crash because it cant find libc
[12:59] <cyphermox> hikiko: we asked for help because it would be very nice if you could look into the compiz crash itself or the X crash or whatever, and see if that can be fixed -- if a postinst script tries to do things and causes a crash, it is overwhelmingly still likely to be a bug
[13:00] <hikiko> if libc is missing
[13:00] <hikiko> how could i fix that in compiz?
[13:01] <cyphermox> hikiko: we'll always be replacing libraries from under things. that's what upgrades do, and it wouldn't be different from what upgrading from wily to xenial would do, or vivid to wily
[13:01] <cyphermox> something is triggering that crash, and perhaps there is a way to avoid it
[13:03] <cyphermox> as mentioned earlier, even if you disable the screensaver the whole session eventually freezes, that's verybad and if we'll need help to figure that out too
[13:03] <hikiko> I agree
[13:03] <hikiko> wait
[13:03] <hikiko> you mean that
[13:03] <hikiko> before the crash
[13:04] <hikiko> you disabled the screensaver during the upgrade
[13:04] <hikiko> and got a crash?
[13:04] <cyphermox> I tried both things
[13:04] <hikiko> sorry I didn't understand that
[13:04] <cyphermox> with the screensaver, as soon as the screensaver starts, compiz crashes and I get thrown back to lightdm, and then I can't login
[13:04] <hikiko> that's during the upgrade?
[13:05] <hikiko> what are the steps to reproduce?
[13:05] <hikiko> you start the update manager in compiz
[13:05] <hikiko> then?
[13:05] <cyphermox> without the screensaver (with the screensaver disabled), the upgrade seems to continue slightly longer but eventually the session *freezes*, I can't move the mouse anymore
[13:05] <cyphermox> you just run 'sudo update-manager -d' in a unity session
[13:05] <hikiko> that's what I do
[13:05] <hikiko> but in my case
[13:06] <hikiko> the screensaver doesn't seem to do anything
[13:06] <hikiko> just
[13:06] <hikiko> at some point
[13:06] <hikiko> with or without screensaver
[13:06] <hikiko> everything blacks out
[13:06] <hikiko> and when I ssh
[13:06] <hikiko> I see no logs and X or compiz running
[13:06] <hikiko> and if I reboot
[13:06] <hikiko> I get the kernel panic
[13:07] <hikiko> and the message is that the fs cant be mounted
[13:07] <cyphermox> we explicitly can't care about what happens after you reboot
[13:08] <cyphermox> in this case, the upgrade has not completed so the system may be in any state
[13:14] <Laney> davmor2: want to confirm bug #1560973 / dupe it if you already know?
[13:28] <hikiko> cyphermox, question:
[13:28] <andyrock> i'll try to run the upgrader without compiz
[13:28] <andyrock> on top of metacity
[13:29] <hikiko> the new lts has cron or uses the systemd cron?
[13:29] <hikiko> +1 andyrock
[13:31] <davmor2> Laney: I'll take a look in a second for you just need to finish off test the bit's I'm doing currently
[13:32] <Laney> ja
[13:32] <cyphermox> hikiko: I have no idea about cron
[13:33] <cyphermox> either way the usage should be the same
[13:33] <hikiko> cron stops
[13:33] <hikiko> before the crash
[13:33] <hikiko> I don't know if it's relevant or not
[13:34] <hikiko> but I got the same message as willcooke and I think pitti got it too
[13:35] <hikiko> I don't know if it's worth investigating
[13:37] <Laney> muktupavels: hey, do you know if metacity is supposed to be all good with hidpi?
[13:37] <Laney> trying to understand https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1560162 (sorry for the inflammatory title)
[13:37] <muktupavels> Laney: probably not...
[13:38] <Laney> seems like window placement / decoration drawing is not right
[13:42] <Trevinho> Laney: can you ack https://requests.ci-train.ubuntu.com/#/ticket/1157 ?
[13:42] <Trevinho> Laney: also... Hey! :)
[13:43] <Laney> ok
[13:43] <Laney> hi Trevinho
[13:43] <Laney> how goes?
[13:43] <Trevinho> quite good, you?
[13:43] <Laney> lots of weird stuff going on
[13:43] <Trevinho> weird?
[13:44] <Laney> just bugs
[13:44] <muktupavels> Laney: metacity most likly need something like this - https://git.gnome.org/browse/mutter/commit/?id=57c1078ee742d9f01e80e7fe05c88adfec4b4ac3
[13:44] <muktupavels> I have not done that because I have no HiDPI display :(
[13:45] <Laney> muktupavels: do they have something for window placement too?
[13:45] <Laney> ubiquity has GTK_WIN_POS_CENTER_ALWAYS
[13:46] <Laney> but you can see it's being positioned in the bottom right
[13:46] <Laney> you can set some keys / environment variables to use 2× scaling
[13:46]  * Laney will try on the installed system anyways, but after lunch
[13:47] <Laney> probably have to look at glib/s390x too, which still hangs
[13:47] <muktupavels> Laney: don't remember
[13:50] <Laney> ok
[13:55] <muktupavels> Laney: do you know what environment variables I should use?
[14:09] <davmor2> Laney: so oddly it removed the efi entry for the first ubuntu install however it added it correctly from grub2 so now I guess I really need to test against something other than ubuntu so I'll dig out an image from somewhere
[14:11] <davmor2> Laney: I assume the issue is that the files and path are the same
[14:13] <davmor2> Laney: feel free to change the title of that bug to something more manageable for yourself, I just write what I see and hope it makes sense :D
[14:49] <mvo> Laney: hi, sorry for the trouble with ubuntu-snappy, please just seed ubuntu-snappy-cli instead of ubuntu-snappy
[14:49] <Sweet5hark1> re from the dentist (still drugged though)
[15:04] <Laney> mvo: ok
[15:05] <Laney> davmor2: what do you mean with 'added'?
[15:06] <mvo> Laney: I just uploaded a new ubuntu-snappy that ensures its all working with ubuntu-snappy-cli
[15:07] <Laney> davmor2: note I don't have anything other than xenial installed
[15:07] <Trevinho> ricotz: abi-fixed bamf should be in proposed
[15:07] <davmor2> Laney: so the EFI folder path and file names for Ubuntu installs are the same so it looks to me like they overwrite with the newer version installed.  However there is a new entry in Grub2 for the older install which I think is expected, I'm installing fedora now and I'll do a side by side with that as then the paths should be different
[15:08] <ricotz> Trevinho, great :)
[15:08] <Laney> davmor2: why is it overwriting anything if I just look at the menu and then turn the system off?
[15:08] <Laney> cyphermox: https://bugs.launchpad.net/ubuntu/+bug/1560973 -> grub2, or something else?
[15:08] <davmor2> Laney: I don't know, one for the foundations team
[15:09] <Laney> davmor2: yeah, just throwing it out there :P
[15:09] <Trevinho> ricotz: it should also fix your issue with new starting bamf app created with no desktop file. Although as you said you should fix plank to properly show them
[15:09] <Laney> you don't need to investigate that much
[15:09] <Trevinho> or launchers around
[15:10] <cyphermox> Laney: yeah, grub possibly, though I can't see why it would change anything on the hardware
[15:10] <davmor2> Laney: no I'm just doing a side by side with another os to see if the efi entries are kept then I am assuming they will be but it is always good to know that too
[15:10] <cyphermox> Laney: either it's that or it's some freak BIOS bug
[15:10] <davmor2> cyphermox, Laney: grub2.  Grub doesn't support efi
[15:11] <Laney> it was more 'grub2 or some other component completely?' :)
[15:11] <cyphermox> ^ indeed, but nobody uses grub-not-2.
[15:11] <Laney> cyphermox: yeah, I don't have any other efi installs to check against though I'm afraid
[15:11]  * Laney has grub2-ified it
[15:11] <cyphermox> Laney: I should be able to reproduce on my hardware.
[15:11] <Laney> 'k
[15:11] <cyphermox> if not, it's a BIOS issue
[15:12] <Laney> good job we're friends with superm1
[15:12] <cyphermox> haha yeah ;)
[15:12] <cyphermox> oh, wait
[15:12] <cyphermox> Laney: is that a new install?
[15:12] <cyphermox> what image did you use?
[15:12] <Laney> 20160323
[15:12] <cyphermox> fun.
[15:13] <Laney> just looking at the grub-efi menu thing
[15:13] <cyphermox> could it be the install itself that confused your BIOS?
[15:13] <Laney> you know the one that appears from the install
[15:13] <Laney> s/install/image/
[15:13] <cyphermox> wait
[15:13] <Laney> before you even get to ubiquity or anything
[15:13] <cyphermox> I mean, the system you used to write the image, was it a newly-installed system?
[15:13] <Laney> erm
[15:13] <Laney> no
[15:13] <cyphermox> ok
[15:13] <Laney> I just dd-ed it from my regular install
[15:13] <cyphermox> ok
[15:14] <cyphermox> there's a strong smell of BIOS, in any case
[15:14] <davmor2> cyphermox: confirmed the initial issue if you install ubuntu along side ubuntu I'm just trying fedora23 with ubuntu alongside now to see if that behaves differently I'm hoping it does :)
[15:15] <cyphermox> davmor2: what initial issue?
[15:15] <davmor2> cyphermox: the efi one
[15:16] <cyphermox> bug #? or are you talking about the same thing as Laney?
[15:16] <davmor2> cyphermox: same one as Laney
[15:17] <davmor2> man fedora takes an age to install
[15:17] <cyphermox> well, it's not the same thing if you're installing two things on the same disk side by side
[15:38] <hikiko> andyrock, and cyphermox I check the post inst scripts that have warnings or errors to see if i find something relevant
[15:38] <andyrock> i just managed to reproduce the crash with metacity
[15:39] <hikiko> i told you it cant be compiz
[15:39] <hikiko> the other things i want to check is:
[15:39] <hikiko> 1 libc is multi arch did we changed the dirs?
[15:39] <andyrock> cyphermox hikiko i always get the crash after udev restarting
[15:40] <hikiko> me too
[15:40] <hikiko> and the gvfs-common
[15:40] <hikiko> is the last package i see here
[15:40] <hikiko> so we must probably check its scripts
[15:40] <hikiko> but I have to go
[15:41] <hikiko> I ll be back later to continue investigating
[15:41] <hikiko> I just wanted to let you know what I am looking at
[15:41] <hikiko> maybe you get some better ideas
[15:41] <cyphermox> andyrock: crash with metacity> the session dies and you get back to the login screen?
[15:42] <andyrock> i don't get back to loginscreen
[15:42] <andyrock> but x died
[15:42] <hikiko> libc looks very suspicious to me that's what I am going to check first when i come back
[15:42] <cyphermox> good enough I suppose
[15:42] <andyrock> https://www.irccloud.com/pastebin/AVhCBoaU/
[15:42] <andyrock> cyphermox: ^^^
[15:42] <cyphermox> hikiko: please show what makes you think it's libc; if that's the issue, we can deal with it by letting infinity look at it hard again
[15:43] <cyphermox> andyrock: dmesg?
[15:43] <hikiko> because compiz couldnt find the libc
[15:43] <hikiko> i think
[15:43] <hikiko> at the point of the crash
[15:43] <hikiko> the new libc
[15:43] <hikiko> is installed
[15:43] <cyphermox> right, but what was compiz doing at the time?
[15:43] <hikiko> BUT
[15:43] <cyphermox> do you have a backtrace?
[15:43] <hikiko> the dynamic loader
[15:44] <hikiko> still looks at the old directories
[15:44] <hikiko> i am going to check if it works
[15:44] <hikiko> in i386
[15:44] <cyphermox> please show logs for this
[15:44] <hikiko> when i come back
[15:44] <hikiko> andyrock,
[15:44] <hikiko> do you have the log
[15:44] <hikiko> cyphermox, it was andy's
[15:44] <hikiko> he pasted it yesterday
[15:44] <cyphermox> if it's an issue with libc's pt_chown or something, it might already have been fixed in the new image
[15:45] <hikiko> cyphermox, sorry I haave to go I ll look at it tonight and ping you
[15:45] <hikiko> sorry
[15:45] <hikiko> +it's just a theory
[15:45] <hikiko> I am not sure
[15:45] <hikiko> bbl
[15:46] <cyphermox> mmkay
[15:47] <andyrock> cyphermox i don't have it, i already restarted the vm
[15:47] <andyrock> i'll try to see if I can get a bt of Xorg
[15:47] <andyrock> because it's Xorg that's crashing with or without unity/compiz
[15:48] <cyphermox> well, I suppose that's good news
[15:59] <Laney> mvo: Guess this wants to wait until after beta now
[15:59] <Laney> but I've seeded it anyway
[16:04] <mvo> Laney: thanks
[16:04] <Trevinho> desrt: you here?
[16:08] <andyrock> https://www.irccloud.com/pastebin/Wl0AcISq/
[16:08] <andyrock> cyphermox ^^^
[16:08] <andyrock> do you think it's the libc bug that has already been solved?
[16:08] <Laney> pitti: any chance I/you/we can reboot 'aupkg01' to get it on the -15 kernel?
[16:09] <pitti> Laney: sure
[16:09] <Laney> I'm abusing it a little bit to try to reproduce this blasted glib2.0 hang
[16:09] <desrt> Trevinho: at lunch.  bbiab.
[16:09] <Laney> pitti: JFDI or something more?
[16:09] <Laney> stop workers I guess
[16:09] <pitti> Laney: if you want to be kind, pkill worker and let the current tests finish (or at least settle down a bit)
[16:09]  * Laney nod
[16:10] <pitti> Laney: actually, there's just two pyzmq tests running for 4/7 hours which look stuck
[16:10] <pitti> Laney: so yes, stop workers, dist-upgrade, and reboot
[16:10] <cyphermox> andyrock: no idea tbh
[16:10] <Trevinho> desrt: ok, enjoy... Let me know when you're back
[16:11] <andyrock> cyphermox: is the bug fixed in the last image?
[16:11] <cyphermox> andyrock: it doesn't look that way, and it seems to me like writes should just work too
[16:11] <cyphermox> andyrock: yeah, the bug I was thinking of should laready be fixed in the last image (20160323)
[16:31] <GunnarHj> infinity: Hi Adam, did you notice bug #1560577? If you think my latest idea (minor script modifications) is ok, I can make a real patch. Suppose that change could be accepted in Debian as well.
[16:35] <infinity> GunnarHj: Try again with -0ubuntu2, that behaviour changed.
[16:36] <GunnarHj> infinity: Aha, didn't know. Will do.
[16:52] <desrt> Trevinho: back!
[16:53] <Trevinho> desrt: so, i've slightly updated the MP for hiding window buttons...
[16:53] <Trevinho> desrt: it's at https://code.launchpad.net/~3v1n0/gtk/unity-maximized-headerbar-buttons-hide/+merge/288552, basically I'm checking whether the headerbar is also the toplevel's titlebar before hiding stuff...
[16:53] <Trevinho> desrt: but, we can't avoid to do that if we don't want a double-title/buttons
[16:54] <desrt> in the case where the headerbar contains controls maybe we could hide the title label itself?
[16:54] <Trevinho> I don't think that would cause any breakage since these values are still shown.
[16:54] <davmor2> cyphermox, Laney: so after an hour and 3 minute installing fedora turns out they lvm by default thankfully I haz t'interwebz to help me modify it all.  I now have ubuntu and fedora cohabiting and both entries show in uefi menu
[16:55] <Laney> ok...
[16:55] <Laney> what does this teach us?
[16:55] <Trevinho> desrt: which kind of controls you mean?=
[16:55] <davmor2> fedora's path is EFI/fedora/shim.... and ubuntu's is EFI/ubuntu/shim...
[16:55] <desrt> like all the stuff that apps like gedit shove into the headerbar
[16:55] <desrt> we don't want to hide this stuff
[16:55] <Trevinho> desrt: in fact we don't.
[16:56] <Trevinho> desrt: only the title label is hidden and the window controls (close, maximize, hide)
[16:56] <desrt> ah.  i see that.
[16:57] <Trevinho> desrt: I'm also tempted to force the window contls to always stay left in unity... But that might be too much :P
[16:57] <desrt> looks pretty reasonable
[16:58] <Trevinho> desrt: this is the same app here with the current patch in both restored and maximized state: http://imgur.com/a/VETka
[16:58] <desrt> looks good indeed
[16:58] <desrt> i have no further comments about the patch
[16:59] <Trevinho> desrt: I was thinking also that maybe the headerbar could either hidden if empty (i.e. no custom controls, window buttons, subtitle) when maximized...
[16:59] <Trevinho> But again I'm not sure whether it's too much :)
[17:00] <desrt> trying to figure that out is going to be more difficult
[17:00] <desrt> let's stay with this one for now
[17:00] <desrt> almost all of the apps are putting something in there anyway
[17:00] <desrt> so the empty case is uncommon
[17:00] <Trevinho> well, not sure how it is for normal apps, but fair enough
[17:01] <Trevinho> desrt: as for forcing the window buttons to always stay left, I don't do that, right? :)
[17:01] <desrt> please not
[17:01] <desrt> it certainly has nothing to do with the issue at hand
[17:02] <Trevinho> yeah, I agree.. that would be too much :)
[17:02] <Trevinho> Laney: then... Since seb is enjoying his free time, could you please sponsor https://code.launchpad.net/~3v1n0/gtk/unity-maximized-headerbar-buttons-hide/+merge/288552 for me?
[17:03] <Trevinho> I'd like to land the theme changes as well then
[17:03] <Laney> tomorrow
[17:03] <Trevinho> Laney: sure, no rush
[17:04] <Trevinho> thanks
[17:09]  * Laney weeps
[17:43] <willcooke> Laney, if you have the inspector set up, you could try this simple idea for the linked buttons:
[17:43] <willcooke> http://paste.ubuntu.com/15481356
[17:44] <willcooke> seems the linked buttons in 3.18 are a bit buggy
[17:45] <Laney> it's better, basically makes them unlinked
[17:45] <Laney> buggy why?
[17:46] <willcooke> the separator between the linked buttons is always there
[17:46] <willcooke> you can style it
[17:46] <willcooke> *except* it does respond to a border-radius
[17:46] <willcooke> so I made it the same as the buttons, and then enlarged the border image a bit to make it look like they are unlinked
[17:47] <willcooke> also raveit65 the MATE theme guy said they were
[17:47] <willcooke> :)
[17:48] <Laney> finding it hard to conjure up much sympathy :)
[17:49] <Laney> trying to style a linked button to be unlinked ...
[17:49] <willcooke> :)
[17:49] <willcooke> fair
[17:50] <willcooke> testing with the widget factory now
[17:50] <willcooke> found 1 problem already
[17:50] <willcooke> oh, no
[17:50] <willcooke> thats not changed by this
[17:52] <willcooke> cyphermox, BTW, do you think that latest change to the slideshow will get in to the beta?
[17:52] <willcooke> cyphermox, low priority of course
[17:53] <Trevinho> desrt: I've quickly played with the headerbar to hide it when there's nothing to show in unity... It would be something like this: http://pastebin.ubuntu.com/15481404/
[17:53] <Trevinho> what you think?
[17:57] <cyphermox> willcooke: should already be in: https://launchpad.net/ubuntu/+source/ubiquity-slideshow-ubuntu/109
[17:58] <willcooke> cyphermox, ah... https://code.launchpad.net/~willcooke/ubiquity-slideshow-ubuntu/ubiquity-slideshow-ubuntu/+merge/289880
[17:59] <willcooke> cyphermox, this *really* is it now.
[17:59] <willcooke> well, for today at least
[17:59] <cyphermox> ok, so you mean one new change on top?
[17:59] <willcooke> yeah
[17:59] <cyphermox> that won't be in the beta ;)
[17:59] <willcooke> nw
[17:59] <willcooke> sorry to be a pita
[17:59] <cyphermox> no problem
[18:00] <cyphermox> I'll merge it in a bit, once I'm done with this keyboard magic
[18:00] <willcooke> thanks cyphermox
[18:01] <willcooke> in the meantime I'll carry on reading about steganography.
[18:01] <willcooke> totally unrelated
[18:11] <cyphermox> willcooke: aren't stegosaurii extinct? ;)
[18:12] <willcooke> no, you just can't see them
[18:12] <willcooke> ;D
[18:12] <Laney> nn
[18:12] <muktupavels> Laney: maybe this will help - https://git.gnome.org/browse/mutter/commit/src/ui/ui.c?id=d7c4f57aaebcd1e6da7a7b343765c0c4b6b81b25
[18:12] <sarnold> :D
[18:13] <Laney> muktupavels: will try to look tomorrow
[18:13] <willcooke> Laney, think I've found a better fix... WIP
[18:16] <Laney> cool
[18:22] <muktupavels> Laney: with gsettings set org.gnome.desktop.interface scaling-factor 2 it works better :)
[18:22] <muktupavels> Laney: https://git.gnome.org/browse/metacity/commit/?h=gnome-3-18&id=d06393b4952333883d66c2b0d570eedc19e8e7a0
[18:27] <willcooke> gannin' for me tea. bbl
[18:49] <davmor2> willcooke: ZOMG upgrade is only working
[18:49] <davmor2> jibel: ^
[18:49] <davmor2> well so far at least but I'm pretty sure it has got further than before
[18:49] <davmor2> cyphermox: ^
[18:51] <jibel> davmor2, you must have done something wrong
[18:51] <flocculant> davmor2: still hangs for me from 14.04 to now and appears to have crashed
[18:51] <davmor2> flocculant: don't ruin my optimism with your facts ;)
[18:52] <davmor2> jibel: who knows
[18:52] <davmor2> oh oh it just greyed out :(
[18:53] <jibel> heh
[18:55] <flocculant> davmor2: I did fleetingly think about doing a davmor2 - you have to be joking, no it isn't in #x-dev :p
[18:55] <davmor2> oh just kicked back in
[18:56] <davmor2> libreadlines obviously just takes some setting up
[18:57] <flocculant> davmor2: I left mine all afternoon while off doing my real job - came back - hard reboot - booted into xenial desktop somehow - had to dpkg --configure -awholelotofthings then it's there :)
[18:58] <davmor2> flocculant: lalala I can't hear you :P
[19:00] <flocculant> :)
[19:08] <davmor2> flocculant: it's all your fault it was installing fine till you said it wouldn't ;)
[19:08] <flocculant> \o/
[19:08] <flocculant> I have a use finally :p
[19:09] <davmor2> jibel, willcooke: Looks like it kernel panics/locks up the system at gvfs-common
[19:09] <davmor2> cyphermox: ^
[19:09] <davmor2> still it got further than before \o/
[19:09] <jibel> davmor2, is it in a VM?
[19:10] <davmor2> jibel: it is
[19:10] <davmor2> jibel: takes too long to reinstall on hardware to test there for fun :)
[19:11] <jibel> davmor2, yeah, just wanted to confirm.
[19:13] <davmor2> flocculant: you in vm too I assume right?
[19:36] <willcooke> Laney, better fix I think:  https://pastebin.canonical.com/152650/
[19:37] <cyphermox> davmor2: ack
[19:47] <willcooke> Laney, for you consideration:  https://code.launchpad.net/~willcooke/ubuntu-themes/ubuntu-themes-linkedbuttons/+merge/289967
[19:48] <willcooke> *your
[20:12] <qengho> Man, I dislike git's "ui".
[20:16] <GunnarHj> infinity: Nice improvements in the latest locale-gen. :) Still found a couple of issues, and make a new diff (attached to bug #1560577). Would appreciate if you could take a look.
[20:32] <davmor2> cyphermox: oem install is definitely not right on kvm will try on hardware now
[20:33] <cyphermox> don't worry, multiple reports of oem not quite right; I'm going to have a lot to do there
[20:33] <davmor2> cyphermox: by tomorrow :o
[20:34] <davmor2> cyphermox, willcooke: looks like the end user slide show is missing slides not sure why as the installers is correct unless willcooke renamed them?
[20:35] <davmor2> cyphermox: and then it never completes the end user install so you are left with the oem account on the system and nothing else
[20:35] <willcooke> davmor2, I see the issue.. sec...
[20:36] <cyphermox> davmor2: not by tomorrow
[20:36] <willcooke> cyphermox, those were the sym links I was worried about
[20:36] <davmor2> cyphermox: but tomorrow is the release of beta final ;)
[20:40] <cyphermox> slideshow isn't release-critical
[20:40] <cyphermox> and oem has fewer users than keyboards ;)
[20:53] <willcooke> cyphermox, davmor2 - fixed:  https://code.launchpad.net/~willcooke/ubiquity-slideshow-ubuntu/ubiquity-slideshow-ubuntu/+merge/289974
[20:55] <davmor2> willcooke: nice :)
[20:55] <davmor2> 1 down
[21:38] <TheMuso> willcooke: I did respond to the bug. As it is, the indicator as it was before didn't really work for the mate flavour anyway. Sure you could select a profile, but nothing would really be changed, due to the gsettings being geared to Unity only, and the hard coded profile code not containing any mate settings.
[21:38] <TheMuso> The cleanest way forward is to add support for mate/GNOME flavours, which would need an FFE.
[21:38] <willcooke> ack, thanks TheMuso - lets see if they can get some people to help
[21:55] <willcooke> can someone tell me how I attach a branch to a bug?
[21:55] <willcooke> Is it too late once I've pushed it up to LP?
[21:55] <willcooke> wait, I think I see it
[21:56] <willcooke> yeah, done
[21:58] <TheMuso> willcooke: You're up late. :)
[21:58] <willcooke> fixing bugs!
[21:58] <willcooke> Doing some real work
[21:58] <TheMuso> Yeah, good enough. :)
[21:58] <willcooke> )
[21:58] <willcooke> :)
[22:01] <willcooke> right, got another fix sorted.
[22:01] <willcooke> Got one for rb to run by design tomorrow
[22:02] <willcooke> night all
[22:02] <TheMuso> willcooke: Since you're around, I don't have anything pressing to talk about in our one on one tomorrow your time, so unless you do, I am happy to allow you some extra sleep tomorrow morning if you like. :)
[22:02] <TheMuso> damn missed him.