[00:12] <slangasek> Laney: hi, do you know how /usr/lib/x86_64-linux-gnu/libproxy/0.4.7/pxgsettings gets launched?  I happened to be looking at my process list and found 13 instances of this thing running... and the package doesn't seem to ship any dbus service definition?
[00:17] <cjwatson> I have three of them, which 'ps xf' show to be descended from unity-scope-video-remote, unity-shopping-daemon, and unity-lens-photos
[00:17] <cjwatson> also paired "sh -c" processes indicating that the parent processes are lazily using some equivalent of system() rather than a direct execve
[00:18] <cjwatson> but I guess that's some library interpreting a configuration file or similar ...
[01:47] <stokachu> just to verify, https://wiki.ubuntu.com/Releases should quantal be EOL April 2013 and not 2014
[01:47] <slangasek> cjwatson: ah right, I overlooked that ~half the processes were actually sh -c.... but in my case, ps f doesn't show any parents for them, they've apparently been left behind :-P
[01:48] <slangasek> stokachu: it should not
[01:48] <slangasek> stokachu: 12.10 + 18mo -> Apr 2014
[01:48] <stokachu> oh then raring is off right?
[01:49] <stokachu> or will that change when its made stable
[04:55] <slangasek> stokachu: raring will AIUI be supported until Jan 2014
[04:55] <stokachu> slangasek: ah b/c of rolling release i assume?
[04:56] <slangasek> well, because of the discussion about shortening the support cycle
[04:56] <slangasek> we aren't actually having a rolling release :)
[04:56] <stokachu> :P sounds good to me
[04:57] <stokachu> i should probably catch up on my emails in the non fire group
[05:03] <tjaalton> slangasek: does the plymouth mp look good? :)
[05:05] <tjaalton> oh bah
[05:06] <tjaalton> wrong version number, took the ppa upload as-is
[05:08] <tjaalton> fixed
[10:21] <smartboyhw> kirkland, roaksoax ping. I'm having problems adding a flavour to Testdrive code.
[10:33] <smartboyhw> ^ please ignore, I think I found the problem.
[13:23] <doko> jtaylor, https://launchpad.net/ubuntu/+archive/test-rebuild-20130329/+build/4440877 numpy related?
[14:56] <purezen> Hey guys..!! I wanted to know if the updates enabling Hardware Video Acceleration via UVD on ATI Radeon HD 4000 through MESA have arrived on Ubuntu 12.10 x64 yet..?
[14:59] <jtaylor> doko: numpy related but probably not 1.7.0 -> 1.7.1 related, the headers have not changed
[15:01] <jtaylor> I'll have a look
[15:07] <jtaylor> doko: pytiff sets NPY_NO_DEPRECATED_API but does not set the api version
[15:16] <jtaylor> though there is probably an additional inconsistency in numpy I'll check with upstream
[15:24] <jtaylor> no numpy is fine, just pytiff doing wrong stuff
[15:25] <jtaylor> doko: http://paste.ubuntu.com/5724729/ should fix it
[15:25] <jtaylor> it uses 1.6 API so it can'T disable deprecated api
[15:25] <jtaylor> specifically PyArray_CORDER instead of NPY_CORDER
[15:29] <doko> jtaylor, can you upload?
[15:30] <jtaylor> yes
[15:47] <jtaylor> done
[16:35] <slangasek> bdmurray: is bug #1036081 something we've seen before?  Users are trying to install the 'sysvutils' binary package on 12.04, when that package was last available in lucid
[17:10] <nonickname2> could someone with casper or plymouth knowledge maybe look at bug #1170421 and/or is this bug something for the release notes? only tested on/with kubuntu though, so maybe someone could try to reproduce it on another *buntu (taking the testing results in the bug report into account)?
[17:23] <slangasek> bdmurray: ok, having looked closer I see that this is an issue we've discussed before; but I don't know if there was a master bug for it somewhere?
[17:41] <sreich> i've got uhm..a bit of a concern with clang 3.2
[17:41] <sreich> as in, there's a 100% of the time crash on anything that uses C++11's std::thread with 3.2, from what i can tell.
[17:41] <sreich> the bug is here http://llvm.org/bugs/show_bug.cgi?id=12730
[17:42] <sreich> they fixed it in r178816 (a couple weeks ago)
[17:42] <sreich> thing is i don't think llvm itself backports fixes..is it possible for ubuntu to squeeze that in?
[17:42] <sreich> because that's a pretty serious bug imho
[17:42] <sreich> or should i be contacting llvm to have them backport it (maybe i am wrong and they do push bugfix releases?)
[17:51] <jtaylor> sraue: depending on the invasivness of the fix we can fix it for raring
[17:51] <jtaylor> sreich: ^
[17:51] <jtaylor> though probably via an stable release update at this stage
[17:52] <jtaylor> sreich: forwarding it to debian would also help, llvm is maintained there
[17:52] <sreich> ok
[17:53] <jtaylor> clang 3.0 is not affected?
[17:53] <sreich> no idea
[17:53] <sreich> don't think 3.0 even had std::thread support
[17:53] <jtaylor> probably not I'll try
[17:53] <sreich> but to check you can just run the source file there
[17:55] <jtaylor> hm it doesn'T compile unless you remove a static assert and then it crashes :/
[17:56] <sreich> yeah it's a bit on the edge i guess http://clang.llvm.org/cxx_status.html
[17:56] <sreich> could be 3.1..or 3.2, don't really know
[18:00] <jtaylor> the fix looks quite simple
[18:00] <jtaylor> bit I'd like the debian maintainers opinion on it first
[18:05] <sreich> jtaylor: where can i get them?
[18:05] <sreich> is there a #debian-devel  ?
[18:05] <bdmurray> slangasek: bug 1001904
[18:05] <jtaylor> sreich: by filing a bug
[18:05] <sreich> k
[18:05] <jtaylor> sreich: debian experimental has pretty much the same clang version
[18:06] <jtaylor> sreich: you can use reportbug -B debian clang
[18:27] <sreich> wow, reporting a debian bug on a non-debian system is fun
[18:28] <sreich> they use emails to create bug reports. like..seriously?
[18:28] <sreich> what is this, 1980?
[18:30] <jtaylor> I think its great
[18:30] <jtaylor> the debian bug tracking system is the best I yet encountered
[18:30] <sreich> seriously?
[18:31] <sreich> why? to report a bug..you need to send an email?
[18:31] <jtaylor> everybody has email
[18:31] <sreich> everybody has bugzilla
[18:31] <jtaylor> you usually need to register for that
[18:31] <jtaylor> which requires email
[18:32] <jtaylor> bts just skips this step
[18:32] <sreich> yeah, but it's got a sane interface
[18:32] <sreich> email is error prone
[18:32] <sreich> and as mentioned, reportbug isn't on non-debian systems
[18:34] <jtaylor> reportbug is just for convinience
[18:34] <sreich> yeah, which you don't get on non-debian systems apparently ;)
[18:34] <jtaylor> I usually just write an email with, Package: ... VErsion: .. bugtext
[18:34] <sreich> hence my point about not using a bug management system seems silly
[18:34] <sreich> i could understand having both, but just one?
[18:35] <jtaylor> it is occasionally discussed to add a webinterface
[18:35] <jtaylor> its usually rejected because its to easy to use :)
[18:36] <sreich> heh
[18:36] <jtaylor> "if someone is not able to write an email, the bug report will not be useful anyway"
[18:39] <mlankhorst> but what if its a bug about thunderbird? ;)
[18:47] <dtchen> is there another archive rebuild test running? I just attempted to reload a build log from the 0329 test, and it had disappeared. :)
[18:47] <jtaylor> which package?
[18:47] <dtchen> mysql-workbench, amd64
[18:48] <sreich> jtaylor: not finding clang 3.2 in debian at all
[18:48] <sreich> http://packages.debian.org/unstable/devel/
[18:49] <jtaylor> dtchen: strange, the i386 log is still there though
[18:49] <dtchen> sreich: looks like it's in experimental
[18:49] <sreich> where can i view experimental?
[18:49] <dtchen> jtaylor: yeah, I ended up using that one as a starting point. Thanks.
[18:50] <jtaylor> sreich: the package trackign system has all information: http://packages.qa.debian.org/c/clang.html
[19:16] <xnox> Anyone have any pointers as to where is the code that generates https://patches.ubuntu.com ?
[20:40] <slangasek> bdmurray: right, thanks
[21:51] <cjwatson> xnox: lp:merge-o-matic
[21:55] <xnox> cjwatson: ok, didn't know it's the same =)
[22:05] <stgraber> fauxww
[22:05] <stgraber> chvt 7
[22:06] <stgraber> chvt 8
[22:06] <stgraber> 0~0~/valogXcd ..
[22:06] <stgraber> cd ..
[22:06] <stgraber> cd vanhoof Logan_
[22:06] <stgraber> ls
[22:06] <stgraber> cat xnox 0 | less
[22:07] <xnox> stgraber: ?????
[22:07] <stgraber> qconso
[22:07] <stgraber> ubuntu
[22:07] <stgraber> ubuntu
[22:07] <stgraber> sudo -i
[22:07] <stgraber> ubuntu
[22:07] <stgraber> ps fauxww
[22:07] <xnox> "Ctrl-Alt-t" | stgraber
[22:07] <stgraber> cat /var/log/upstart/li
[22:08] <stgraber> restart lightdm
[22:08] <xnox> I take it stgraber is trying to recover his machine blind =)
[22:09] <ogra_> lol, yeah, good guess
[22:09] <xnox> ogra_: let's just wait for the sudo password =)
[22:09] <ogra_> he obviously uses ubuntu/ubuntu :)
[22:09] <xnox> ogra_: ha, true.
[22:10] <Logan_> hahaha
[22:10] <Logan_> this is quite amusing
[22:10] <stgraber> oops ;)
[22:10] <Logan_> btw, you need a stronger password
[22:11] <xnox> stgraber: or is it focus-failing-to-follow-eyesight-error ?
[22:11] <stgraber> xnox: nope, I'm reinstalling my laptop, running a bare Ubuntu server on it and running Ubuntu desktop inside an LXC container
[22:11] <stgraber> I was at the setting up input devices step ;)
[22:11] <ogra_> it worked !
[22:11] <ogra_> :)
[22:12] <stgraber> which apparently ended up working a bit too well as the X server running in a non-focused VT was still getting the keyboard input (apparently)
[22:12] <stgraber> looks like a reboot fixed it though ;)
[22:13] <xnox> stgraber: i can get a mouse pointer working on a VT sometimes......
[22:13]  * xnox praises Intel graphics
[22:13] <xnox> like a tty1 that is.
[22:13] <stgraber> xnox: yeah, I had that and it's when that happens that you can get in the situation where what you type in tty1 ends up in both the tty and in your focused X window (in my case, irssi)
[22:15] <stgraber> anyway, sorry for the spam, it hopefully won't happen again (will try to keep something else focused when doing my tests ;))