[04:25] <pitti> Good morning
[04:29] <thumper> o/ pitti
[04:47] <TheMuso> Morning pitti. :)
[04:47] <pitti> hey thumper, hey TheMuso, how are you?
[04:48] <thumper> doin' good, busy like normal
[04:48] <thumper> making juju more awesomer during the day, working on my startup at night
[04:48] <thumper> sleeping less
[04:51] <TheMuso> pitti: Very well thanks, yourself?
[04:51] <pitti> thumper: uh, how long can you sustain that :)
[04:51] <pitti> TheMuso: quite fine, thanks!
[04:51] <thumper> pitti: been doing it hard for about a year, very patchy before that
[04:52] <thumper> pitti: every one of my holidays in the last year and a bit has been working on the startup (except for last week - parent help at my daughter's year 8 school camp)
[04:52] <thumper> pitti: it is hard... hoping it will be worthwhile one day
[06:12] <didrocks> good morning
[06:24] <pitti> bonjour didrocks
[06:30] <seb128> hey pitti & desktopers
[06:30] <seb128> wie gehts?
[06:30]  * seb128 upgrades to w
[06:30] <pitti> c'est un seb128 ! salut !
[06:30] <didrocks> hey pitti! (sorry, didn't see your ping)
[06:30] <pitti> seb128: gut, danke! systemd debugging again :)
[06:30] <pitti> seb128: just now? you are soooo late to the werewolf :)
[06:31] <pitti> (it's just boring, nothing really changed yet..)
[06:31] <seb128> pitti, yeah, first upgrade, then contribute to making the thing more exciting :-)
[06:31] <seb128> pitti, desktop debugging or making the phone like systemd? ;-)
[06:31] <pitti> but oh well, it was already some fun to untangle some uninstallability and test regressions this morning :)
[06:31] <pitti> seb128: Laney's schroot-in-lxc woes, so desktop
[06:32] <pitti> seb128: that's the last bug scheduled for the next SRU, then I can go back infecting^Wporting the phone
[06:32] <seb128> great
[06:36] <seb128> Sweet5hark, do you know why libreoffice is triggering alternative failure/fixed emails almost daily
[06:36] <seb128> it's a bit annoying
[06:37] <seb128> it's like "failed" and a few hours later you get "fixed"
[06:37] <seb128> it keeps doing that
[06:37] <pitti> that was part of my fixes this morning
[06:37] <pitti> tzdata was uninstallable in wily
[06:37] <seb128> oh, good
[06:37] <pitti> so libreoffice, cantor, poxml, and chromium-browser failed
[06:37] <pitti> now they are all happy again
[06:37] <seb128> great
[06:37]  * Sweet5hark has a look
[06:38] <seb128> when I clicked on the public url yesterday it was an "empty" label page
[06:38] <seb128> so I couldn't see the issue
[06:38] <seb128> Sweet5hark, hey, seems like pitti already handled it :-)
[06:40] <Sweet5hark> seb128: fwiw. looking at the last failure in vivid, its an 'unexpected EOF' on the source tarball ...
[06:41] <Sweet5hark> seb128: so I would assume libreoffice being this big, it just is more sensible to flaky network connections and other temporary glitches in the matrix ...
[06:42] <pitti> yes, that's my fault, bug 1384706
[06:42] <pitti> it's ridiculously hard to reproduce and investigate, unfortunately :/
[06:44] <Sweet5hark> pitti: http://vmiklos.hu/blog/so-many-bugs.html <- backside of t-shirt applies
[06:44] <pitti> Sweet5hark: ^5s
[07:35] <seb128> grrrr, firefox had some issues yesterday and nucked my password/login db it seems
[07:36] <seb128> chrisccoulson, ^ is there a backup on disk somewhere that I can use for those cases?
[07:37] <pitti> seb128: eek, no backup?
[07:37] <seb128> pitti, backups but not from the full userdir and not from .mozilla...
[07:50] <willcooke> o/
[07:51] <didrocks> hey willcooke
[07:52] <larsu> morning willcooke!
[07:54] <seb128> hey willcooke
[08:02] <willcooke> xmir is fixed!
[08:02] <Laney> meow
[08:04] <willcooke> happyaron, thanks for your email.  I will read it and digest today
[08:05] <willcooke> happyaron, How was Scotland btw?
[12:05] <FJKong>  /quit
[12:42] <tkamppeter> willcooke, hi
[13:17] <theo_> instellen slaapstand scherm
[13:20] <didrocks> ok, all tests are finally passing again
[13:20]  * didrocks goes for a run
[13:28] <seb128> didrocks, enjoy!
[14:52] <Laney> man
[14:52] <Laney> what is this u-s-d media-keys race
[15:05] <didrocks> Laney: around for at least a cycle
[15:06] <Laney> I didn't say it was new
[15:06] <Laney> irritating though
[15:06] <didrocks> yeah, didn't get any useful debug IIRC
[15:07] <didrocks> and didn't reproduce when running u-s-d in debug mode
[15:07] <didrocks> I guess a typical heisenbug
[15:07] <didrocks> you add debug, it slows it down enough to not get the race
[15:08] <seb128> is that when u-s-d starts before compiz?
[15:08] <seb128> or the other way around?
[15:08] <seb128> or nothing to do with that?
[15:17] <Laney> hmm
[15:17] <Laney> could be a race there
[15:17] <Laney> don't know if that causes this though
[15:18] <seb128> the way it's supposed to work is for compiz to do the grabbing and send the events to u-s-d over dbus and u-s-d triggers the actions
[15:19] <seb128> when you get the bug, does hitting the key generate the dbus events?
[15:19] <seb128> of it does the issue is on the u-s-d side
[15:19] <seb128> if it doesn't it's compiz/unity
[15:20] <Laney> org.gnome.Shell AcceleratorActivated happens
[15:20] <seb128> so u-s-d issue I guess
[15:20] <attente> none of the shortcuts are working?
[15:21] <Laney> doesn't seem so
[15:21] <attente> did u-s-d possibly crash?
[15:21] <Laney> nah
[15:21] <attente> because then compiz would keep the grabs
[15:21] <Laney> oh, in the past?
[15:21] <attente> yeah
[15:21] <Laney> umm
[15:22] <seb128> attente, compiz having the grab would be fine?
[15:22] <seb128> it's supposed to work this way no?
[15:22] <seb128> compiz grab and send the dbus messages
[15:22] <seb128> and u-s-d listen to dbus and call the callbacks?
[15:22] <attente> yeah, but if u-s-d crashes, the new instance of u-s-d would re-register new grabs, but the older grabs compiz already has takes priority iirc
[15:23] <seb128> why is u-s-d registering grabs?
[15:23] <seb128> I though compiz was the one grabbing
[15:24] <attente> i mean u-s-d registering grabs with compiz
[15:24] <attente> over dbus
[15:24] <attente> org.gnome.Shell.GrabAccelerator[s]
[15:24] <seb128> how is that working? I though compiz was grabbing the key and just sending on dbus org.gnome.Shell.AcceleratorActivated
[15:25] <seb128> that any u-s-d running instance would listen to
[15:25] <attente> yeah, but it would be sending the old accelerator id
[15:25] <attente> that the crashed u-s-d registered
[15:25] <seb128> oh, I didn't know they had changing ids
[15:25] <attente> the new u-s-d wouldn't know the old u-s-d's ids
[15:25] <seb128> I though each action had a fix enum type number
[15:25] <attente> unless i'm not remembering properly
[15:26] <seb128> I don't know the details of that protocol
[15:26] <seb128> I just had a remote look at the time you guys did the change
[15:26] <seb128> you are probably right :-)
[15:27] <seb128> Laney, since when is u-s-d running for you (compared to unity)
[15:28] <Laney> can't check, sorry, I restarted it
[15:28] <Laney> attente: if I get compiz to ungrab those IDs should it start working again?
[15:29] <attente> Laney: yeah, ungrab over d-bus, then restart u-s-d should work
[15:29] <Laney> it grabs it again
[15:30] <Laney> :|
[16:23] <EphraimMB> What is Unity 8 up to now? Any screenshots?
[17:10] <seb128> EphraimMB, desktop or phone ones? you can probably easily google for some
[17:10] <seb128> happyaron, bug #1380982 is the most reported vivid e.u.c issue, is that something you are looking at?
[17:10] <EphraimMB> Desktop
[17:45] <jcastro> willcooke, I had a concurrent session during the unity8 showoff
[17:45] <jcastro> anything sexy I miss?
[17:46] <willcooke> jcastro, I wasnt there either - too many concurrent sessions :)
[17:46] <willcooke> maybe mzanetti knows? ^^
[17:46] <willcooke> guess we could just watch the video
[17:46] <jcastro> I just need a package name and/or PPA, heh
[17:47] <mzanetti> oh yeah, you did miss something cool :D
[18:29] <happyaron> seb128: sorry, nope, getting something hard to handle with willc