[04:49] <pitti> Good morning
[05:58] <didrocks> good morning
[07:43] <willcooke> morning all
[07:49] <seb128> hey willcooke
[07:49] <didrocks> hey willcooke
[07:54] <larsu> morning!
[07:57] <seb128> hey desktopers ;-)
[08:04] <willcooke> happyaron, please take a look at:  https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1048161
[08:04] <willcooke> happyaron, it's been hanging around for a long time and is #1 ibus issue
[08:05] <Laney> hallo!
[08:05] <seb128> happyaron, willcooke, #1 e.u.c vivid issue, and not only ibus
[08:05] <seb128> hey Laney, wie gehts?
[08:05] <larsu> morning Laney!
[08:05] <Laney> just had breakfast outside
[08:05] <Laney> climbed yesterday
[08:05] <larsu> nice!
[08:05] <Laney> it is going GREAT
[08:06] <didrocks> morning Laney
[08:06] <Laney> how about you didrocks et larsu et seb128 et willcooke?
[08:06] <willcooke> the sun is shining
[08:06] <seb128> doing good, still summer like today
[08:06] <willcooke> it feels like summer is coming :)
[08:06] <seb128> the classical music yesterday was bit experimental/weird
[08:06] <seb128> was fun but a bit long
[08:07] <Laney> oh yeah
[08:07] <Laney> this unknown guy?
[08:07] <czajkowski> willcooke: time to start working from the garden!
[08:07] <willcooke> czajkowski, :D
[08:07] <willcooke> I really need a better place to sit outside
[08:07] <willcooke> with a bit of shade so I can see the screen
[08:07] <willcooke> and a table which isn't half collapsed
[08:08] <czajkowski> wifi access points are being fitted next weekend and outdoor sockets so can easily work then !
[08:08] <czajkowski> willcooke: shame you dont live closer you could join popey at our co working day once a month
[08:08]  * didrocks has a balcooney for this
[08:08] <Laney> \o/
[08:08] <czajkowski> didrocks: git
[08:11] <seb128> Laney, yeah, that was a creation from the university here, demoing a new intrusment they designed as well
[08:11] <seb128> it was interesting but a bit long
[08:41] <Laney> didrocks: hey, do you know about the fsckd autopkgtest failing? (sorry)
[08:42] <Laney> It can't find /etc/default/grub.d/90-autopkgtest.cfg --- some problem with the host? (it only fails on amd64)
[08:42] <pitti> Laney: fixed yesterday in git
[08:42] <Laney> which git?
[08:42] <pitti> amd64 runs on the cloud now, and these images don't use the adt-setup-vm script
[08:42] <pitti> Laney: the systemd autopkgtest
[08:42] <Laney> ah
[08:43] <pitti> http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=experimental&id=0931f09a80
[08:43] <Laney> are you going to upload it?
[08:43]  * Laney is trying to smooth glib2.0 in
[08:44] <Laney> qengho: chromium-browser's test is failing too
[08:44] <pitti> Laney: ah, I can ignore the systemd failure for now, if that helps
[08:44] <pitti> Laney: yes, I can upload it too
[08:45] <Laney> I could do that too, having it really pass seems better
[08:45] <Laney> will wait for Chad to at least eyeball chromium first anyway
[08:45] <Laney> so no big rush
[08:45] <didrocks> at least, that forced pitti to use fileinput.input() ;)
[08:45] <pitti> chromium seems to be an actual regression
[08:45] <pitti> in the newer version in -proposed
[08:46] <pitti> I suppose it's not glib's fault (but in theory it could be, hence britnye holding it back for human inspection is right IMHO)
[08:46] <pitti> didrocks: indeed, that's a handy trick!
[08:47] <Laney> I usually try to get things in by making the tests pass even if it isn't that upload's fault
[08:48] <Laney> will skip as a fallback though
[08:52] <pitti> Laney: right, me too, I just didn't get to uploading it yet
[08:52] <pitti> last/this week is a bit crasy
[08:52] <pitti> crazy, too
[08:53] <pitti> three security vulns in my stuff in one week, after years of silence :)
[08:54] <Laney> oh, I only saw the dbusmock thing
[08:54] <Laney> there was more?
[08:54] <pitti> yeah, still private
[08:55] <pitti> I can't talk, or Marc will have to -- argh! argh! *nnng* *dump*
[08:55] <Laney> sorry for adding to your stress then :)
[08:55] <pitti> no worries :)
[08:55] <pitti> the switch to nova came as a surprise to me
[08:55] <didrocks> seems pitti watched too much house of cards

[08:55] <pitti> I've waited for this for a long time, but they didn't wait until we fixed all the known test regressions
[08:56] <pitti> didrocks: no spoiler for me, unless you already know the 4th season :)
[08:56] <didrocks> pitti: no, this spoiler part is almost a no one as it's in the first season :p
[08:57] <pitti> didrocks: well, people die in 2nd too :)
[08:57] <didrocks> oh yeah, the one I was thinking about was in the 2nd actually
[11:16] <Laney> larsu: could you sanity check a reproducer for me please?
[11:16] <Laney> http://paste.ubuntu.com/11112014/
[11:17] <Laney> It's meant to tell you if the bug is reproduced or not, but I never get the callback called after my g_file_trash
[11:18] <Laney> so my reproducer doesn't work ...
[11:21] <Laney> actually it seems like it may have broken with glib 2.45
[11:59] <larsu> Laney: (just back from lunch) sure
[12:02] <larsu> Laney: just hangs for me
[12:02] <Laney> ya
[12:02] <larsu> did I reproduce?
[12:02] <larsu> should I try a different glib?
[12:02] <Laney> well, can you see a bug in the code?
[12:02] <Laney> it should print one or other of the messages instead of hanging
[12:03] <Laney> if you go and trash a file in nautilus it'll notice that btw
[12:03] <larsu> it unrefs the file and then uses it again
[12:03] <Laney> just doesn't see its own one (but this works with 2.44)
[12:03] <larsu> oh wait
[12:03] <larsu> I can't read
[12:06] <larsu> Laney: desrt changed file monitoring right? Maybe it broke the trash:// case?
[12:06] <larsu> code looks good to me otherwise
[12:07] <Laney> yeah maybe
[12:07] <Laney> it's just a bug on top of a bug which is annoying
[12:09] <larsu> indeed
[12:09] <larsu> I'm testing it with .44
[12:09] <Laney> cool
[12:10] <Laney> I had to restart my session with the new glib to get it to work propertly (probably gvfs)
[12:13] <larsu> Laney: trash:///test-file.6 trashed from /home/lars/src/bugs/laney-trash/test-file - bug not reproduced :D
[12:13] <larsu> on 2.44
[12:13] <Laney> ya
[12:14] <larsu> any other test I could do?
[12:14] <larsu> (me is leaving for the afternoon in a bit and will be back tonight)
[12:14] <Laney> no, that's fine, thanks
[12:14] <Laney> guess I get to file two bugs
[12:15] <larsu> yay?!
[12:16] <Laney> yay!
[12:16] <pitti> Laney: uploaded systemd at last, which will hopefully fix the failure on amd64
[12:17] <Laney> thanks pitti!
[12:17]  * Laney sends extra sunshine towards Germany
[12:19] <ogra_> oh, that is where it comes from ?
[12:19]  * ogra_ hugs Laney 
[12:24] <pitti> Laney: even more? thanks :)
[12:24] <pitti> we've had wonderful spring/summer weather since the weekend
[12:28] <nessita> pitti, hey, how are you? I was wondering if you would know if the switch to systemd could make my system boot super super super slow. Today it took "Startup finished in 7.874s (kernel) + 3min 6.652s (userspace) = 3min 14.526s"
[12:29] <pitti> hey nessita
[12:29] <pitti> nessita: it could happen, of course; is it fast if you boot with upstart?
[12:29] <pitti> nessita: what are the topmost entries in systemd-analyze blame?
[12:30] <pitti> that sounds like 6 s regular boot, plus two timeouts
[12:30] <nessita>           5.862s systemd-cryptsetup@sdb3_crypt.service
[12:30] <nessita>           5.420s NetworkManager-wait-online.service
[12:30] <nessita>            627ms plymouth-quit-wait.service
[12:31] <pitti> ok, nothing surprising there
[12:31] <pitti> nessita: can you pastebin "journalctl -b"?
[12:31] <nessita> pitti, haven't tried upstart, let me do that right now. One other symptom is that I need to boot around 3 times, the first two after the grub selection the video signal turns off == blank screen and monitor blinks its power light
[12:31] <nessita> getting output for journalctl
[12:32] <pitti> nessita: also, did you try to boot without quiet and splash?
[12:32] <nessita> pitti, I did, specially when I edit the boot line the video signal is "lost"
[12:32] <pitti> nessita: uh, switching off the display? that sounds like a graphics driver or plymouth issue, but let's see
[12:33] <pitti> nessita: it's also worth a try to boot with utopic's kernel (assuming that utopic still worked)
[12:34] <nessita> pitti, so about video: I have a nvidia card and was using the nvidia drivers, but I purged them to try to see if those were related to the issues (I don't think they are)
[12:34] <Laney> larsu: ah, it works if I use a timeout instead of idle
[12:34] <nessita> pitti, journalctl -b -> https://pastebin.canonical.com/131297/
[12:34] <Laney> I guess my operation is getting in there before the monitor
[12:35]  * Laney tries enforcing the right order
[12:35] <pitti> Job dev-disk-by\x2duuid-c65eebf4\x2d2f76\x2d497a\x2d86d6\x2d0d65ca46c0d5.device/start t
[12:35] <pitti> nessita: ^ it's cropped at the end, but quite clear
[12:35] <pitti> Timed out waiting for device dev-disk-by\x2duuid-c65eebf4\x2d2f76\x2d497a\x2d86d6\x2d0d
[12:36] <pitti> nessita: could be bug 1447282 or bug 1447282, but both should be fixed in vivid-updates
[12:36] <pitti> nessita: anyway, I need: /etc/fstab, /etc/crypttab, and the output of "sudo blkid"
[12:36] <Laney> no, stupid, the monitor should be added before the loop runs
[12:36] <nessita> pitti, on it
[12:37] <nessita> pitti, https://pastebin.canonical.com/131298/
[12:38] <nessita> I'm up to date with vivid, no new packages or updates to install
[12:41] <pitti> nessita: ah, there we go:
[12:41] <pitti> sdb4_crypt UUID=c65eebf4-2f76-497a-86d6-0d65ca46c0d5 none luks,swap,discard
[12:41] <pitti> ^ in /etc/crypttab
[12:41] <pitti> this UUID doesn't exist
[12:41] <pitti> and corresponding entry in fstab (/dev/mapper/sdb4_crypt)
[12:42] <pitti> nessita: ^ so this is indeed a variant of bug 953875, but one which the automatic postinst didn't cover as there were some modifications
[12:42] <pitti> nessita: comment out the broken swap from crypttab and fstab, then it should work
[12:43] <pitti> nessita: that of course is unrelated to the video driver issue, but let's see how far you get with this
[12:44] <pitti> nessita: this got broken somewhere in precise or so, and under upstart we never noticed that we had broken swap partitions; so you've ran without swap for some years, I guess you don't miss it :)
[12:44] <pitti> nessita: if you want it back, you can also fix it manually (see the bug description above), but I guess you shouldn't care -- swap is just so outdated
[12:45] <nessita> pitti, interesting. I did not miss it, as you correctly guessed. Is worth noticing that when I installed from installer the last time (I think it was utopic), I remember the partioning step was problematic, I was not allowed to create an encrypted partition for /mnt if the swap wasn't encrypted, so I just disabled the swap via swapoff
[12:46] <nessita> it was like an chicken-egg situation with unecrypted swap and trying to create an ecrypted partition
[12:46] <nessita> pitti, thanks much!
[12:46] <pitti> nessita: you're welcome!
[12:47] <qengho> pitti: is there a way to get Jenkins RSS feed for all tests from one source package? My alerts weren't triggered because I forgot to add wily to my feed list. I'm going to forget again one day.
[12:47] <nessita> pitti, this swap issue causes the long boot time, right? is it also causing the display being turned off? or to fix that I should go back to the nvidia drivers?
[12:48] <pitti> qengho: sorry, we don't currently have RSS for autopkgtest results; the last uploader gets notified by email
[12:48] <pitti> nessita: it should cure the long boot time, yes; as I said, that's unrelated to video driver issues
[12:48] <pitti> nessita: I don't know how well nouveau works these days, or particularly for you; if it does, so much the better
[12:48] <pitti> but I figure the nvidia driver ought to work, a lot of people use it
[12:49] <nessita> pitti, k, thanks!
[12:49] <qengho> pitti: Eh? On jenkins on result pages is "RSS for failures" but it's specific to this exact test.
[12:51] <pitti> qengho: ah, via jenkins? ok, I didn't try that :)
[13:01] <nessita> pitti, super success! "Startup finished in 7.887s (kernel) + 11.290s (userspace) = 19.177s". Bad news is display was turned off on the first attempt. Will re-install nvidia drivers now and retry
[13:01] <pitti> \o/
[13:12] <desrt> larsu: i changed local file monitoring... trash monitoring happens via gvfs
[13:12] <desrt> although it could be that the file monitoring broke for trash too
[13:12] <desrt> since the backend, itself, uses local file monitors :)
[14:13] <excalibr> Has the method to get the session idle time through dbus changed in the recent Ubuntu or my dbus code in this paste link is wrong?
[14:13] <excalibr> http://pastebin.com/raw.php?i=MMYxPRQQ
[15:01] <happyaron> willcooke seb128 will do that first right away
[15:01] <happyaron> tried once but failed to get a solution
[15:01] <seb128> happyaron, hey, thanks
[15:01] <seb128> if you need help please let us know
[15:01] <seb128> is that the one you mentioning maybe being a glib issue?
[15:01] <seb128> we have people knowing about glib that can reply to questions here ;-)
[15:01] <happyaron> I'm not sure whether it's glib or improper use of glib
[15:02] <happyaron> great
[15:02] <seb128> likely improper use ;-)
[15:34] <willcooke> sorry happyaron was otp - thanks!
[15:35] <happyaron> still not that very well with jet lag, and missed a meeting today...
[15:37] <willcooke> happyaron, I think it will take at least 3 weeks to get back to normal
[15:44] <happyaron> :)
[15:45]  * willcooke -> appointment.
[15:45] <willcooke> bbl
[16:10] <seb128> ok, I'm calling it a day, have a nice evening everyone
[16:10] <Laney> see you seb128!
[16:10] <seb128> see you tomorrow for those who are there, or next week otherwise
[16:11] <seb128> tomorrow is a vac and I've friday off, but I took some hours off work during the week and I'm going to be a bit around tomorrow to work on some things I wanted to get done this week
[16:12] <Laney> what's the occasion tomorrow?