[07:12] <ppisati> yo
[09:48] <apw> moin, /me reboots to get a lockscreen that actually locks
[10:01] <apw> man a whole new lock screen a whole new set of bugs
[10:02] <ogra_> yay
[10:03] <ogra_> that goes hand in hand with the non-centered new wallpaper ;)
[10:03] <apw> it shows a lot about the testing rigor that the bugs are so obvious
[10:03] <ogra_> i dont have any bugs with mine yet 
[10:08] <cking> it depends on how one defines rigor
[10:09] <apw> i have tended to have an unfortuanate interpretation of it, one you might recognise cking
[10:09] <apw> ogra_, try interacting with the top right menu
[10:10] <ogra_> i did already 
[10:10] <ogra_> no issues on my XPS13 ... might be a graphics driver issue 
[10:10] <cking> i like the way one can start up the character map on the user's desktop when they are locked
[10:10] <cking> and one can shut the machine down too
[10:11] <ogra_> well, my GF likes that she can mute it now when i'm not around :)
[10:11] <smb> That seems to be fixed this morning
[10:11] <cking> ah, progress :-)
[10:11] <smb> ogra_, Could be that feature is gone
[10:12] <smb> Or its a new bug
[10:12] <smb> Who can say
[10:12] <ogra_> did they disable the indicators ? 
[10:12] <smb> They look to be there but I could not drop any action menues down
[10:13] <smb> So solely "indicators" in the literal meaning
[10:13] <ogra_> well, they work fine for me 
[10:14] <smb> ogra_, when did you upgrade?
[10:14] <ogra_> yesterday
[10:14] <smb> see
[10:14] <smb> I did this morning
[10:14] <ogra_> havent been at my laptop today 
[10:15] <smb> Yesterday they behaved as you say
[10:15] <smb> Today is another day
[10:16] <ogra_> oh my
[10:16] <smb> infinity, Somewhat I feel less and less guilty about any issues I may cause with replacing Xen...
[10:23] <tjaalton> was the raring kernel git repo removed?
[10:24] <tjaalton> ah, moved
[10:25] <smb> tjaalton, No more Raring. Only as a HWE branch in the Precise tree
[10:26] <tjaalton> smb: so it gets abi bumps there?
[10:26] <tjaalton> that'd explain it then
[10:27] <smb> tjaalton, Yes, it only will get updated there as long as the version is supported for LTS HWE
[10:28] <tjaalton> right
[10:29] <smb> tjaalton, A pity you only handle the binary-gfx drivers. Otherwise I would have a victim to whine about dual-screen experience in T. But I will have to wait for Sarvatt for that. :)
[10:30] <tjaalton> I don't touch the blobs, it's tseliot land :)
[10:31] <smb> Oh bugger, mixed up the people starting with t... :/
[10:31] <tjaalton> just whine on a bug report against xserver-xorg-video-intel and ickle will whine back :)
[10:31] <smb> Was about to file that next :)
[10:31] <tjaalton> but the first thing would be to <drumroll> try 3.14 ;)
[10:32] <tjaalton> assumed it's an intel issue
[10:32] <smb> Heh, likely
[10:34] <smb> At least could make sure its still there. Not exactly sure its driver or handling of it. Looks to be a problem with lightdm trying to be helpful and arrange screens side-by-side breaking 3D support as that gets wider than 2048
[10:35] <tjaalton> ah
[10:35] <tjaalton> well that's not really a driver bug then
[10:35] <tjaalton> maybe lightdm shouldn't enable both output
[10:35] <tjaalton> s
[10:35] <tjaalton> on older hw
[10:36] <smb> Well it could be as it does not start accdelerating even when I change the setup to something sensible
[10:36] <smb> Yeah, or do mirror mode instead of side-by-side
[10:36] <tjaalton> right
[11:12]  * cking not getting any success with qemu-system-ppc and the trusty ppc image. anyone else got it to work lately?
[11:48] <apw> cking, can't say i have no
[13:50] <apw> rtg, i have just slammed head to add a buglink to an older commit
[13:51] <rtg> apw, ack
[14:42] <rtg> dannf, don't bother with build testing amd64/i386. I've got that figured out. I'd rather see some testing on the Mustang platform.
[14:45] <dannf> rtg: ok, will do. is the fix already in your branch, or do you think the build fix is irrelevant enough that it doesn't also need testing?
[14:47] <rtg> dannf, it has been pushed to that branch and was just a packaging fix.
[14:47] <dannf> ok, cool
[14:47] <rtg> I'm comfortable that it is righteous
[15:33] <ppisati> henrix: do you use git intergration with emacs? if yes, wich package do you use? git.el? magit? what else?
[15:34] <henrix> ppisati: no, not really. i've tried magit but didn't convinced me
[15:34] <ppisati> henrix: ok
[15:35] <ppisati> henrix: but then, how do you handle when e.g. you edit a buffer, write it down, git commit using cli
[15:35] <ppisati> henrix: and when you go back emacs complain about "file changed on disk" etcetc
[15:36] <henrix> ppisati: hmm... that doesn't happen too often i guess :)  and when it does i just re-read it
[15:39] <henrix> ppisati: but why would you have your buffer externally modified after a commit?
[15:39]  * henrix thought ppisati was a vi user btw
[15:39] <ppisati> henrix: actually i was an emacs user who switched to vi cause it was somewhat faster
[15:40] <henrix> :)
[15:41] <rtg> apw, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1292400 looks like your baby
[15:41] <ubot2> Launchpad bug 1292400 in linux (Ubuntu) "task systemd-udevd:1906 blocked for more than 120 seconds." [Undecided,Confirmed]
[16:35] <psivaa> bjf: hello
[16:35] <bjf> psivaa, hi
[16:35] <psivaa> bjf: the saucy xen (amd64 kernel on 64 bit machine) kernel sru is hung on test_stack_collision (__main__.KernelASLRCollisionsTest)
[16:35] <psivaa> bjf: and the kernel log is http://paste.ubuntu.com/7091031/ 
[16:36] <bjf> looking
[16:36] <psivaa> bjf: this is the first run though.. if you think i should rerun to confirm.. i could do that
[16:36] <bjf> psivaa, is just the test hung? how long?
[16:37] <psivaa> bjf: for 5 hrs now
[16:37] <bjf> psivaa, retry it and it shouldn't take longer than 1 hr. max, i would think
[16:38] <psivaa> bjf: ack, yea the test just hung.. i dont see any other issues with the machine 
[16:38] <bjf> psivaa, if it hangs again i'll as sbeattie to look at it
[16:38] <rtg> apw, I pushed 'Add VID:DID for Lenovo OneLinkDock Gigabit LAN' for bug #1291890
[16:38] <ubot2> Launchpad bug 1291890 in linux (Ubuntu) "Add Lenovo ThinkPad OneLink GigaLAN USB ID to ax88179 driver" [Undecided,Confirmed] https://launchpad.net/bugs/1291890
[16:38] <psivaa> bjf: ack, rerunning. thanks
[16:49] <apw> rtg, ack thanks
[16:50] <rtg> dannf, any progress to report ?
[16:50] <apw> rtg, this hyper-v thing looks like an ABBA deadlock in memory hotplug between the balloon driver and udev online
[16:50] <dannf> rtg: not yet; just de-meeting'd, build starting
[16:50] <apw> rtg, i guess i'll pass it upstream and see what they say
[16:51] <rtg> apw, ick!
[17:48] <dannf> rtg: built fine; but initramfs boot fails. looks like the sata driver is correctly waiting postponing probe until the phy is available, but the phy mod doesn't autoload. retesting w/ just XGENE_PHY=y, XGENE_AHCI=m
[17:49] <rtg> dannf, ack, sounds right
[19:14] <dannf> rtg: looks good w/ that caveat, I replied on list. taking off early today, but i'll sync up w/ the thread monday if not sooner.
[19:15] <rtg> dannf, ok. I'm adding the enet driver patches now. I'll send an update on the list.
[19:26] <dannf> rtg: cool. just note that enet relies on the qmtm engine
[19:30] <rtg> dannf, yeah, I was just figuring that out