[00:12] <cyphermox> jbicha: ah
[00:12] <cyphermox> jbicha: just b/c of the packaging?
[00:13] <jbicha> cyphermox: well, GDM is very Fedora-centric so it probably needs patching too
[00:14] <cyphermox> ok
[00:14] <jbicha> GDM packaging scares me ;)
[00:15] <cyphermox> jbicha: hehe. not sure I want to jump into that either, I kinda like lightdm
[00:16] <cyphermox> but it would be nice to have the option (that works) in a PPA at least
[00:47] <bryceh> jasoncwarner_, heh they say "this is the most important release in Ubuntu's history" every LTS ;-)
[00:48] <RAOF> Well, it's true every LTS, really :)
[00:48] <jasoncwarner_> bryceh: but this time we mean it ;) those other times? all marketing !
[00:48] <RAOF> Just like each new iPhone is ?the best iPhone yet? :)
[00:49] <jasoncwarner_> RAOF: true :) best. release. ever.
[00:49] <bryceh> at OSDL, "This is the most important quarter ever!" was an on-going joke
[00:54] <TheMuso> jasoncwarner_: Nice email nonetheless.
[00:54] <jasoncwarner_> thanks, TheMuso
[00:55] <jasoncwarner_> bryceh: usually they are...for the ceo ;)
[00:55] <jasoncwarner_> having a too many bad quarters in a row isn't good for CEO and VP of Sales types ;)
[00:55] <bryceh> turned out wasn't too good for OSDL either ;-)
[00:56] <jasoncwarner_> bryceh: so it was the most important quarter ever !
[01:26]  * desrt waits for the "this iphone isn't quite as good as the one before it, but we still think you should buy it" announcement
[01:26] <desrt> i'd settle for "it's about the same, really -- but we rather enjoy continuing to receive your cash"
[01:26] <RAOF> Woah.  Who did the minimise animation on the launcher?
[01:27] <RAOF> Or: when did that minimise animation land?  This is the first that I've noticed it!
[01:32] <smspillaz> RAOF: early last cycle
[01:33] <RAOF> smspillaz: In Natty?  Really?  And it's taken me this long to notice it?
[01:34] <smspillaz> yep
[01:34] <Sarvatt> RAOF: i havent noticed either if it makes you feel better
[01:34] <RAOF> I clearly don't mimimise many windows :)
[01:50] <bryceh> why do some bug reporters make it so hard to help them?
[01:51] <RAOF> I'm guessing: because they have no idea how hard they make it to help them.
[01:53] <bryceh> yep could be
[04:55] <pitti> Good morning
[05:03] <BigWhale> pitti, mom, is that you? *opens one eye*
[05:03] <BigWhale> :>
[05:03] <pitti> hey BigWhale
[05:07] <BigWhale> How's it going?
[05:10] <pitti> pretty ok, except for the cold I'm having
[05:10] <pitti> looking forward to the release :)
[05:14] <BigWhale> cold? yeah same here... and laryngitis... I sound like Darth Vader :>
[05:15]  * pitti hands BigWhale another cup of camomile tea
[05:15] <BigWhale> thanks :)
[05:16] <RAOF> Are we all suffering from release stress, or something?
[05:16]  * RAOF nurses his tired, sore throat.
[05:17] <pitti> RAOF: I at least blame the autumn weather to some degree
[05:17] <pitti> over the weekend I often went out with a T-shirt, as it was some 25 degrees over the day; but in the morning/evening it was rather chilly
[05:17] <BigWhale> Weather here was awesome. We had an indian summer until today basically. Yesterday it was 27 C, today temperatures will plummet... 9 C :/
[05:18] <BigWhale> True, mornings were a bit colder
[05:20] <TheMuso> Morning pitti.
[05:20] <TheMuso> Yeah Sydney has had its first remotely warm day for a while, and in good time too, being mid spring and all...
[05:20] <RAOF> And we've had our week of low-grade drizzle.
[05:24] <rickspencer3> good morning all
[05:26] <pitti> hey rickspencer3
[05:26] <rickspencer3> hey pitti, so just need new lang packs for the CDs today, right?
[05:26] <pitti> rickspencer3: right; I'm polling https://translations.launchpad.net/ubuntu/oneiric/+language-packs
[05:26] <rickspencer3> woohoo
[05:26] <pitti> oh, it landed
[05:26]  * pitti goes to build the packs
[05:27] <rickspencer3> !!!!
[05:28] <rickspencer3> RAOF, hey, I assigned what looks like an xorg bug to the desktop team last night
[05:28] <rickspencer3> sg is having it
[05:28] <rickspencer3> so I thought you might want to see the bug since there's someone with hardware who will help you debug and all
[05:29] <RAOF> Ah, sweet.  A debugging partner?  Awesome.
[05:30] <RAOF> rickspencer3: What was the bug?  It doesn't seem to have filtered into my bugmail.
[05:30] <rickspencer3> RAOF, hmm, I assigned it to canonical-desktop-team
[05:30] <rickspencer3> I
[05:30] <rickspencer3> can get the bug # a bit later
[05:30] <rickspencer3> but I'm not at that particular 'puter atm
[05:30] <rickspencer3> sorry
[05:30] <RAOF> I'd guess it's bug #861426
[05:30] <ubot2> Launchpad bug 861426 in xserver-xorg-video-intel "[Oneiric] [Regression] When disabling onboard LVDS display and just using external VGA screen corruption occurs" [Undecided,Confirmed] https://launchpad.net/bugs/861426
[05:32] <RAOF> Oh, cool.  I've got a GM45 laptop, too.  Potentially bugs in hardware *I own*!
[05:35] <rickspencer3> RAOF, that's the one
[05:35] <rickspencer3> RAOF, it seems that we are having a lot of issues with xorg and with unity for people who use external monitors a lot
[05:36] <rickspencer3> let's get some testing in place for these situations really soon
[05:36] <rickspencer3> catch these issues early and often
[05:36] <rickspencer3> RAOF, and yeah, that's the bug ;)
[05:37] <RAOF> I think part of the problem is that unity was plain broken on multiple monitors for so long.
[05:37] <pitti> I have that (external monitor, internal one xrandr'ed off0
[05:37] <pitti> the only problem that I see is that on resume the screen is broken, I have to switch to VT1 and back to get it fixed
[05:38] <pitti> not sure if that is related to the bug; if it is, I'm a happy victim of logs/tests/etc.
[05:38] <pitti> broken> mostly black, just a short vertical bar of blinking pixels in the top left corner
[05:39] <RAOF> OOooh, yeah.
[05:48] <smspillaz> rickspencer3: aha! there you are!
[05:48] <rickspencer3> hi smspillaz
[05:48] <smspillaz> rickspencer3: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/869316
[05:48] <ubot2> Launchpad bug 869316 in unity "reproducible stacking bug in compiz" [High,Triaged]
[05:48] <smspillaz> that
[05:48] <rickspencer3> yes?
[05:48] <smspillaz> I looked into it all morning, can't reproduce it
[05:48] <smspillaz> though, it's a little ambiguous
[05:49] <rickspencer3> ambiguous?
[05:49] <smspillaz> yeah, so it says
[05:49] <smspillaz> "view the presentation"
[05:49] <smspillaz> then
[05:49] <smspillaz> "stop the recording"
[05:49] <smspillaz> do you close the presentation in between ?
[05:50] <smspillaz> or like, does the presentation view go away in between that
[05:50] <smspillaz> or do you have to switch to another window to make  the panels appear on top and then stop the presentation
[05:50] <RAOF> Bwah.  Ok, it's another manifestation of "gnome-desktop does RANDR changes just differently enough from the xrandr tool that it breaks".  Joy!
[05:51] <smspillaz> (I tried tons of combinations btw, but couldn't find anything to reproduce it :( even using the package version
[05:51] <smspillaz> rickspencer3: what other stuff do you have open while you get this bug? is it *just* LO impress and gtk-rmd or do you have other stuff open too ?
[05:51] <rickspencer3> smspillaz, I wrote the repro steps out
[05:52] <smspillaz> I know
[05:52] <smspillaz> followed them step by step, cant reproduce it
[05:52] <rickspencer3> I may have other apps opened
[05:52] <smspillaz> so there's something else that you've got
[05:52] <smspillaz> ok
[05:52] <smspillaz> what other apps ?
[05:52] <rickspencer3> I dunni
[05:52] <rickspencer3> xchat-gnome
[05:52] <rickspencer3> smspillaz, maybe you can ask other people to try to repro it?
[05:52] <smspillaz> ... can you try and reproduce it again and then tell me what stuff you have open when it happens ?
[05:52] <smspillaz> rickspencer3: so far only you can jane can get it
[05:53] <rickspencer3> someone else repros it?
[05:53] <rickspencer3> are you saying Jane gets it too?
[05:53] <smspillaz> and remote debugging especially for these kinds of things (which are insanely complicated) is pretty much impossible. So I need a way to rreproduce it myself
[05:53] <smspillaz> rickspencer3: neil told me that jane did
[05:53] <rickspencer3> great
[05:53] <smspillaz> rickspencer3: anyways, try and reproduce it again
[05:53] <rickspencer3> she's presenting today at a huge conference
[05:53] <smspillaz> and tell me what stuff I have open
[05:53] <rickspencer3> :/
[05:53] <smspillaz> and please don't tell me things to raise my blood pressure :)
[05:54] <rickspencer3> RAOF, can you help sg with a workaround?
[05:54] <RAOF> Yeah, I'm following up on the bug.
[05:54] <rickspencer3> sweetness
[05:54] <rickspencer3> RAOF, is there an SRUable fix?
[05:55] <RAOF> Not as of this moment, no.
[05:55] <rickspencer3> shucks
[05:55] <smspillaz> rickspencer3: these bugs are insanely complicated and usually a result of applications misbehaving (libreoffice is a serial offender in this category), so please have patience :)
[05:55] <smspillaz> anyways
[05:55] <smspillaz> next time you reproduce it, please let me know what stuff you have open
[05:55] <smspillaz> (or try and reproduce it right now)
[05:56] <RAOF> rickspencer3: But!  Given that it looks like a gnome-desktop problem, it's much more likely to be SRUable than, say, a kernel problem :)
[05:58] <rickspencer3> we can SRU kernels!
[05:58] <rickspencer3> smspillaz, I have this crazy "Director" job that keeps interfering with my "debug unity" job ;)
[05:59] <rickspencer3> I'll try to get to that later today
[05:59] <RAOF> But SRUing a kernel is a significantly more involved undertaking with significantly higher risks than twiddling gnome-desktop code :)
[06:01] <smspillaz> why is it that only people who are directors can reproduce unity bugs :(
[06:01] <smspillaz> RAOF: can you reproduce this bug ?
[06:01] <smspillaz> RAOF: it's basically something like
[06:02] <smspillaz> open a presentation, open gtk-r-m-d, view presentation, alt-tab to gtk-r-m-d, exit presentation, stop recording, yay your stacking is stuffed!
[06:02] <smspillaz> except that the last part doesn''t happen for me
[06:02] <didrocks> good morning
[06:03] <smspillaz> didrocks: ^ and good morning (can you reproduce that ?)
[06:03] <didrocks> smspillaz: wait, I'm first backporting fixes to unity :)
[06:03] <smspillaz> heh, ok
[06:04] <RAOF> That's gtk record-my-desktop, right?
[06:13] <rickspencer3> RAOF, yes
[06:13] <didrocks> smspillaz: please, think to change upstream bug status when merging
[06:13] <rickspencer3> RAOF, thanks for working on sg's but
[06:14] <rickspencer3> RAOF, could you please make your directions just a bit more explicit for him?
[06:14] <rickspencer3> like, should he run that command before disconnecting, etc...
[06:15] <RAOF> Before disconnecting?  There's no disconnecting anywhere in the process, is there?  Anyway, I'll try to reword that to be more obvious.
[06:15] <smspillaz> didrocks: sure
[06:15] <didrocks> smspillaz: well, please ensure about "sure", it's the 3rd time of the week I'm asking you that :)
[06:15] <smspillaz> right, I usually do them all at once
[06:16] <smspillaz> just haven't gotten around to updating all the bugs yet as not all merges are complete
[06:16] <rickspencer3> RAOF, sorry, I thought that was his issue
[06:16] <didrocks> smspillaz: as the merge is manual, please just do it in the merge as I've asked in the numerous emails and pings on IRC :)
[06:17] <smspillaz> you can do it in the merge ?
[06:17] <smspillaz> as in, there is a way to automatically update the bug status whenever a merge happens ?
[06:18] <didrocks> smspillaz: no, do it *when* you merge, you have the bug linked on your merge page, just click on it
[06:18] <smspillaz> ah, right
[06:18] <didrocks> smspillaz: isn't what you asked me already… yesterday… and where I told you "no"? :p
[06:18] <RAOF> smspillaz: Yes.  When you commit, add --fixes=lp:BUGNUMBER.
[06:18] <smspillaz> RAOF: doesn't work, no matter what people tell me :(
[06:18] <RAOF> Bah, yes, you're right.
[06:18] <smspillaz> :(
[06:18] <RAOF> It does generate bugmail, though.
[06:19]  * smspillaz wonders if its possible to make a launchpad hook to do that
[06:19] <rickspencer3> RAOF, never mind
[06:19] <rickspencer3> I'm a dope
[06:20]  * didrocks just spent 5 minutes to change 10 bugs status from dx for the latest fixes
[06:20] <didrocks> retarget to right components
[06:23] <smspillaz> didrocks: isn't there a script that retargets the upstream projects to the downstream ones ?
[06:24] <smspillaz> well, I guess unify only works for milestone releases
[06:26] <didrocks> smspillaz: no, it works for everything, but if you open a wrong component
[06:26] <didrocks> like nux
[06:26] <didrocks> my script can't know that the bug is in unity
[06:26] <didrocks> it will affect unity and nux
[06:26] <didrocks> so ensuring I don't have to dig and run after you guys, please, take this small 30s to make things rigorously ok
[06:30] <smspillaz> ok[A
[06:31] <smspillaz> didrocks: rickspencer3: I need to run out for a bit, let me know if you can reproduce that stacking bug and when you do, please give the me the output of xwininfo -root -tree and also a list of what applications you've got open
[06:31] <rickspencer3> smspillaz, I updated my repro bug with more specific steps
[06:31] <rickspencer3> it happens with only impress and gtk-rmd open
[06:31] <smspillaz> ok, thanks
[06:32] <rickspencer3> didrocks, I guess you are preparing a Unity zero day SRU?
[06:32] <didrocks> rickspencer3: I'm preparing an upload right now rather
[06:32] <smspillaz> rickspencer3: so to clarify, if you *only* had gtk-rmd and impress open, you'd get the bug ?
[06:32] <didrocks> rickspencer3: still time as langpacks are still building
[06:33] <rickspencer3> smspillaz, yes
[06:33] <rickspencer3> didrocks, wait, I'm confused
[06:33] <smspillaz> rickspencer3: thanks
[06:33] <rickspencer3> I thought we were done updating the CD
[06:33] <rickspencer3> except for the lang packs
[06:33] <rickspencer3> and everything else was for SRUing/updates
[06:33] <didrocks> rickspencer3: I'm waiting for pitti, there is a huge crasher fix there
[06:33] <smspillaz> ahh you're switching to another workspace!
[06:33] <smspillaz> critical part
[06:33] <didrocks> rickspencer3: yesterday, we still had some nice fixes
[06:33] <rickspencer3> pitti, ??? ^
[06:33] <smspillaz> ok, lets try that
[06:34] <pitti> didrocks: what?
[06:34] <rickspencer3> didrocks, but every upload brings a risk of regressions
[06:34] <didrocks> rickspencer3: right, that's why I'm dogfooding it
[06:34] <pitti> didrocks: sorry, I'm not aware of a question from you
[06:34] <rickspencer3> pitti, question is from me
[06:34] <rickspencer3> I thought we were done changing the CD
[06:34] <rickspencer3> and I think didrocks is saying that he's about to upload changes
[06:35] <pitti> well, as you say, any upload that we do now must be 100% regression safe
[06:35] <didrocks> pitti: there can be a nice unity upload coming, I'm currently testing it there, it fixes a bunch of stuff, and 3 starred crashes
[06:35] <didrocks> that's why I'm testing it a lot before pushing
[06:35] <pitti> fixing two crashers with obvious two-liners is fine; 30 kB diffs are not any more
[06:35] <didrocks> pitti: I can spunge to only have one fix then
[06:36] <didrocks> pitti: it's one line
[06:36] <didrocks> this one get 4 duplicates an hours
[06:36] <didrocks> hour*
[06:37] <rickspencer3> *sigh*
[06:37] <didrocks> it was a bug that fix considered as "fixed", but it wasn't…
[06:38] <rickspencer3> didrocks, so, in other words
[06:38] <rickspencer3> an upload that caused a regression?
[06:38] <rickspencer3> that's why we need to be hyper cautious now
[06:38] <rickspencer3> throwing in more fixes to fix broken fixes just gets us on a crazy treadmill
[06:38] <didrocks> rickspencer3: no
[06:38] <didrocks> rickspencer3: in other word
[06:39] <didrocks> "a bug that dx think to have fixed with some code, but they didn't"
[06:39] <didrocks> so had to stop apport duplicating to a fix released bug to get a new stacktrace
[06:39] <pitti> didrocks: yeah, this kind of bug/fix is welcome at this point :)
[06:39] <pitti> didrocks: 4 dupes an hour? nobody wrote a bug pattern yet?
[06:39] <pitti> didrocks: want me to write one?
[06:40] <didrocks> pitti: well, it's dispatched in 3 bugs, I didn't check since yesterday evening if we have a bup pattern, will do it in a few
[06:41] <didrocks> rickspencer3: no need to tell me that every upload is a regression risk. I think I already demonstrated that I clearly know that :)
[06:41] <rickspencer3> lol
[06:42] <rickspencer3> didrocks, sorry man
[06:42] <rickspencer3> I'm just not feeling like we have the same level of careful control about changes at this point that we usually do
[06:42] <rickspencer3> maybe it's just because I'm not tacking it like I used to
[06:42] <didrocks> sorry I'm maybe doing a bad job then…
[06:42] <rickspencer3> but when I ask "are we done making changes?" I get different answers from different people
[06:42] <rickspencer3> didrocks, no, it's not you, c'mon
[06:42] <smspillaz> rickspencer3: still can't reproduce it :(
[06:42] <rickspencer3> don't be that way
[06:43] <rickspencer3> I wouldn't be doing my job if I wasn't asking questions
[06:43] <smspillaz> rickspencer3: we need longer cycles :)
[06:43] <rickspencer3> smspillaz, I don't know what else to say
[06:43] <smspillaz> but anyways, I won't continue that discussion
[06:43] <smspillaz> rickspencer3: hmm ok. I'll try opening some other stuff up as well
[06:43] <rickspencer3> smspillaz, please
[06:45] <smspillaz> rickspencer3: what stuff do you usually have open, xchat, chromium ?
[06:46] <rickspencer3> smspillaz, firefox, thunderbird, xchat
[06:46] <rickspencer3> but none of them were opened when I just reproed it
[06:46] <smspillaz> ok
[06:46]  * smspillaz compiles the package verison again just to check
[06:47] <smspillaz> kinda frustrating when I can't reproduce these bugs, heh
[06:48] <smspillaz> yay reproduced it
[06:48] <smspillaz> finally
[06:49] <smspillaz> rickspencer3: ok, I'm going to go down to the shops to get some mountain dew then kill this bug
[06:51] <RAOF> Reproduced here, too.
[06:51] <RAOF> Heh, just in time.
[06:51] <RAOF> :/
[07:00] <jbicha> I use bzr-builddeb for almost all of my building, what am I supposed to do when upstream only ships .tar.xz?
[07:01] <jbicha> rebuild as .tar.bz2?
[07:02] <jbicha> since bzr-builddeb doesn't support xz, perhaps waiting on pristine-tar
[07:02] <micahg> jbicha: do it the old way?
[07:03] <RAOF> Does bzr-builddeb not handle that?  Does it require things to be pristine-tarrable?
[07:04] <micahg> jbicha: better question, what's Debian doing?
[07:05] <jbicha> well, for GNOME, they still use svn and they've got a patch now for svn-buildpackage http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637900
[07:05] <ubot2> Debian bug 637900 in svn-buildpackage "Does not support .xz tarballs." [Normal,Open]
[07:06] <jbicha> micahg: I don't think I ever used the old way
[07:07] <jbicha> UDD's been around for too long or I'm too young or something... :)
[07:07] <micahg> jbicha: well, is this something that we'll be maintaining a diff for?
[07:07] <micahg> s/diff/packaging branch/
[07:08] <jbicha> micahg: probably not, I was trying to package shared-color-targets to fix bug 643168
[07:08] <ubot2> Launchpad bug 643168 in gnome-color-manager "gcm-prefs tries to install nonexistent shared-color-targets" [Undecided,Confirmed] https://launchpad.net/bugs/643168
[07:09] <micahg> jbicha: unless you're trying to cram that into oneiric, maybe do that in svn w/Debian?
[07:10] <jbicha> well it's a bit broken with out it and for some reason policy is we don't backport new packages, so I would like to cram it in
[07:11] <micahg> jbicha: define "backport new packages"
[07:12] <jbicha> a source package not in Oneiric on the release date won't be allowed into oneiric-backports, right?
[07:13] <RAOF> Yes, of course it will.
[07:13] <RAOF> Well, could be.
[07:13] <micahg> jbicha: not true, that's one of the functions of backports
[07:13]  * ajmitch thought that backports would explicitly allow new packages
[07:13] <ajmitch> if there's policy that says otherwise it should be changed to reflect reality
[07:13] <micahg> jbicha: the only reason it wouldn't be allowed is if it would break other stuff
[07:14] <pitti> yes, correct
[07:14] <jbicha> oh I misread the policy, it just needs to be in P first, which I knew
[07:14] <pitti> any application package in precise can be backported, provided it doesn't break anything else
[07:14] <ajmitch> which reminds me, oneiric-backports needs to be created in LP
[07:14]  * RAOF wonders why gnome-settings-daemon thinks setting mode=0x0 ot the output I *didn't* turn off will make me happy.
[07:15] <ajmitch> there was a proposal to open oneiric-backports for new source uploads that would be copied to precise upon the archive opening, I think
[07:15] <ajmitch> not sure if that went anywhere
[07:15] <pitti> RAOF: some people are happier about black screens? no confusing screen contents to worry about
[07:15] <jbicha> any pointers on how to build stuff the old way then?
[07:16] <pitti> RAOF: would you be an appropriate assignee for bug 828623?
[07:16] <ubot2> Launchpad bug 828623 in gnome-control-center "[Regression] gnome control centre does not allow you to disable the laptop screen while leaving an external DisplayPort connected screen working" [High,Triaged] https://launchpad.net/bugs/828623
[07:16] <pitti> jbicha: what is "the old way"?
[07:16] <micahg> pitti: the before time, pre-uDD
[07:17] <pitti> RAOF: your own fault -- you earned too many good credentials wrt. libgnome-desktop :)
[07:17] <pitti> jbicha: apt-get source, change stuff, debuild -S, run debdiff against the old and new .dsc to check?
[07:17] <RAOF> pitti: Oh!  I'm accidentally already working on that one )
[07:17] <RAOF> :)
[07:18] <pitti> jbicha: there are some extra tools available like "uupdate" and "uscan" which you should know about
[07:18] <pitti> RAOF: nice
[07:18] <RAOF> While looking at bug 861426
[07:18] <ubot2> Launchpad bug 861426 in xserver-xorg-video-intel "[Oneiric] [Regression] When disabling onboard LVDS display and just using external VGA screen corruption occurs" [High,Incomplete] https://launchpad.net/bugs/861426
[07:18] <pitti> RAOF: it seemed related, but quite the opposite of "my screen unexpectedly goes black"
[07:19] <pitti> but it's certainly the same code area, that's why I was thinking of you
[07:20] <jbicha> ok, I guess I was just confused then
[07:22] <infinity> Say, are there any desktop people who either have ARM hardware or know how to run qemu who would like to take a hail mary pass at trying to figure out why banshee doesn't work on armel?
[07:23] <RAOF> My experience with debugging under qemu is "don't", sadly.
[07:23] <RAOF> gdb won't work (and, from memory, isn't expected to)
[07:24] <RAOF> I would love to figure out what's happening, though.
[07:24] <infinity> It should work in a full qemu-system-arm, but I wouldn't expect it to work well in a qemu-user-static chroot, no.
[07:24] <pitti> didrocks: thanks for the unity fix, it's in now
[07:24] <infinity> There's no functional difference between a vexpress qemu-system-arm and real hardware, except that qemu's slower. :/
[07:24] <didrocks> pitti: \o/ thanks
[07:25] <RAOF> vexpress?
[07:25] <infinity> But yeah.  We'll be poking at banshee, but we've mostly given up for oneiric and already changed our seeds to use rhythmbox instead.  I'd still love to switch back if someone found the bug.
[07:25] <infinity> RAOF: One of the system options.  We build a vexpress kernel specifically for booting that qemu system.
[07:26] <infinity> (vexpress is an ARM reference platform)
[07:26] <RAOF> How would one install such a VM?
[07:26] <infinity> That, I'm too tired to walk someone through.  We must have wiki docs for it somewhere, though.  One would hope.
[07:27] <didrocks> pitti: do you fell better than yesterday or still have a cold?
[07:27] <pitti> didrocks: both :)
[07:27] <didrocks> feel*
[07:27] <infinity> RAOF: perhaps something like https://wiki.ubuntu.com/ARM/QemuNetInstall with some s/versatile/vexpress/ where it might make sense.
[07:28] <pitti> didrocks: it's usually okay in the mornings, but I tend to get a bit dizzy and heavy-headed in the evenings
[07:28] <infinity> RAOF: But it's bedtime here, so I can't really help much.  I can in the morning, if you're keen on helping debug.
[07:28] <didrocks> pitti: urgh, take care! do you take any medecine?
[07:29] <pitti> chicken soup and a decongestant during the nights, that's all I need :)
[07:29] <didrocks> heh :)
[07:29] <RAOF> infinity: That looks sufficiently easy.
[07:29] <pitti> I'm not a big fan of taking Aspirine, I'll let my immune system do what it thinks is right..
[07:31] <infinity> RAOF: Assuming it works, yeah.  Those instructions are rather old. ;)
[07:31] <infinity> RAOF: But poke me in /msg if you have troubles, I'll be around in ~7.5 hours again. :)
[07:39] <rodrigo_> morning
[07:39] <didrocks> hey rodrigo_
[07:39] <rodrigo_> bonjour didrocks
[07:39] <pitti> good morning rodrigo_
[07:39] <rodrigo_> hi pitti
[07:40] <pitti> ah, my fresh langpacks just finished building
[07:40] <pitti> anyone who wants to test some?
[07:40] <pitti> I usually locally build German and French, but can also do the Spanish ones (*hint* *hint*)
[07:42] <rodrigo_> pitti, what needs to be done for testing?
[07:43] <pitti> rodrigo_: installing them, rebooting, checking that nothign looks strange
[07:43] <pitti> rodrigo_: in particular, we test whether update-manager and firefox work
[07:43] <pitti> opening evolution and checking that it's translated also can't hurt
[07:43] <rodrigo_> ok, I can have a try
[07:46] <rodrigo_> pitti, they will be available for upgrade in a bit, right?
[07:46] <pitti> rodrigo_: yes, but I usually test them before I upload themn
[07:46] <rodrigo_> ah, so where can I get them?
[07:46] <pitti> ... in a second
[07:48] <pitti> rodrigo_: oh, and translated unity/gnome help
[07:48] <rodrigo_> ok
[07:49] <didrocks> pitti: can test French if you want :)
[07:49] <pitti> scp is squeezing them through my thin upstream :)
[07:50] <jbicha> did the new ubuntu-docs make it into this langpack update?
[07:50] <pitti> looks like it
[07:50] <didrocks> hey jbicha
[07:51] <jbicha> didrocks: howdy
[07:51] <pitti> didrocks, rodrigo_: http://people.canonical.com/~pitti/tmp/lp/
[07:52] <jbicha> people decided to send me sushi bugs for some reason ;-)
[07:52] <pitti> jbicha: hm, help isn't translated
[07:52] <didrocks> jbicha: ahah, you touched it! too late :)
[07:53] <jbicha> pitti: oneiric-changes says new ubuntu-docs landed at 04:57:17 UTC yesterday, too late then?
[07:53] <pitti> jbicha: hm, so the old ubuntu-docs stuff is gone
[07:53] <pitti> jbicha: but no new ubuntu-docs translations there
[07:53] <pitti> jbicha: maybe
[07:54]  * didrocks reboots
[07:54] <pitti> jbicha: I'll check, it shoudl be static translations, not gettext
[07:54] <pitti> rebooting as well, to cover the other bits
[07:57] <rodrigo_> pitti, ok
[07:57] <rodrigo_> jbicha, :)
[08:00] <pitti> the rest looks fine for German, I'll investigate ubuntu-docs
[08:01] <seb128> hey
[08:01] <seb128> hey pitti, didrocks
[08:01] <pitti> bonjour seb128
[08:01] <didrocks> salut seb128
[08:01] <seb128> how are you?
[08:02] <didrocks> seb128: I'm fine, thanks, you?
[08:02] <seb128> I think I'm fine, well confirm after some coffee ;-)
[08:02] <dpm> good morning desktop people
[08:02] <didrocks> :-)
[08:02] <didrocks> hey dpm
[08:03] <pitti> good morning dpm
[08:03] <dpm> hey didrocks, happy Friday :)
[08:03] <pitti> dpm: seems someone copied the lucid and natty PPA langpacks to -proposed then?
[08:04] <didrocks> dpm: heh, happy friday too :)
[08:04] <pitti> dpm: I'm currently building oneiric langpacks, will accept the stable ones after that, to not block the buildds too much
[08:04] <seb128> hey dpm
[08:04] <didrocks> brb
[08:04] <dpm> pitti, ah, hadn't noticed about the lucid + natty langpacks
[08:04] <dpm> hey seb128 :)
[08:05] <pitti> dpm: oh, who requested that then?
[08:05] <rodrigo_> hi seb128, dpm
[08:06] <seb128> hey rodrigo_
[08:06] <rodrigo_> pitti, hmm, I don't have any langpack-* package installed on my system
[08:06] <dpm> pitti, perhaps TLE? He was helping with languagepack updates, but I would have thought he'd talk to you or me to request a copy to -proposed
[08:06] <pitti> rodrigo_: language-pack-*
[08:06] <rodrigo_> right
[08:06] <didrocks> pitti: all looks good here with popular apps, apart from the help guide not being translated
[08:06] <rodrigo_> sorry :)
[08:06] <pitti> rodrigo_: great, thanks for testing
[08:06] <rodrigo_> ok, rebooting to test them
[08:08] <RAOF> Hm.  So, in summary: (1) gnome-rr-config does a substantial amount of unnecessary work on modeswitch and (2) gets it wrong.
[08:09] <dpm> pitti, I'm glad to hear the oneiric langpacks were exported and built fine, I'm testing the Catalan ones right now, and one thing I've noticed is that some translations done before the export time don't seem to have made it into the langpacks. Can't say much about the docs, as this release we didn't have the chance to translate them
[08:09] <didrocks> seb128: seems that even nautilus-open-terminal rebuild, nautilus still crashes
[08:09] <seb128> didrocks, ok, we should perhaps conflict on it?
[08:09] <pitti> dpm: ubuntu-docs is missing, investigating right now
[08:09] <seb128> didrocks, something seem to not like the mix of gsettings and gconf or something
[08:10] <seb128> didrocks, I don't use it so I didn't check
[08:10] <seb128> but the stacktrace on the apport bugs is in gconf
[08:10] <seb128> or maybe it relies on nautilus to do the gconf init which it stopped doing
[08:10] <didrocks> seb128: I don't use them as well, just seeing people still complaining about nautilus crashing and I just got confirmed they are using build1
[08:10] <seb128> ok
[08:10] <didrocks> oh right
[08:10] <didrocks> do you want I have a look at this?
[08:11] <didrocks> if it's only gconf init…
[08:11] <seb128> didrocks, it's a random guess, if you want to try please do
[08:11] <didrocks> seb128: let's try that, if I don't find it then, let's conflict it
[08:11] <seb128> didrocks, ok
[08:11] <seb128> didrocks, do you know if somebody checked the upstream vcs to see if they have GNOME3 fixes?
[08:11] <seb128> RAOF, blame it on federico :p
[08:12]  * RAOF gets all blame-y.
[08:12] <didrocks> seb128: looking now, I just looked if there was a new release
[08:12] <seb128> RAOF, thanks for looking at this code btw, we tend to ping pong bugs between xorg and gnome-desktop,gnome-settings-daemon but they always end up just sitting there
[08:12] <didrocks> nothing since 0.19
[08:16] <didrocks> seb128: no, gconf is initialized…
[08:16] <jbicha> some reports claimed that removing ubuntuone helped with the nautilus-open-terminal crashes
[08:17] <seb128> weird
[08:18] <jbicha> but I don't know if that's true or not
[08:18] <didrocks> yeah, I'm seeing that
[08:18] <didrocks> let me have a try
[08:18] <seb128> well we started getting bugs about it recently so I can believe there is a conflict between those
[08:18] <seb128> not sure if that's the gsettings,gconf mix
[08:18] <dpm> pitti, so yes, it seems that some translations in Catalan are missing. Looking at the oneiric/language-pack-ca-base folder, it seems that they were not exported in the full language pack? Things like deja-dup.po and unity.po are missing from there. Am I right in expecting they should be thee, or am I not looking in the right location?
[08:19] <pitti> dpm: hm, the German pack has both
[08:19] <pitti> dpm: oh, wait
[08:19] <pitti> dpm: they are in -gnome-ca-base
[08:19] <rodrigo_> pitti, from a 1st look, a couple things: keyring dialogs are in English, as is the help for language support
[08:19] <rodrigo_> rest seems to be ok, but still checking
[08:20] <rodrigo_> well, apart from some weird translations, like "cuentas en línea" for online accounts
[08:20] <rodrigo_> that's why I use English always, some translations confuse me :)
[08:20] <didrocks> jbicha: seb128: confirmed, its when having both (ubuntuone and open-terminal) that nautilus crashes
[08:21] <seb128> didrocks, "great"
[08:21] <seb128> didrocks, let's claim it's a dobey's bug :p
[08:21] <didrocks> seb128: yeah, let's claim that! :-)
[08:21] <didrocks> I see nothing wrong in the nautilus-open-terminal code
[08:21] <didrocks> it's getting a gconf client
[08:21] <didrocks> and then get some gconf values
[08:22] <dpm> pitti, ah, that explains it, thanks
[08:23] <rodrigo_> pitti, firefox looks ok, except some plugins are still in English, but those are plugins I installed by hand, so I guess it's normal
[08:24] <pitti> rodrigo_: actually, firefox isn't covered by langpacks any more, so that wouldn't chhange
[08:24] <pitti> and yes, it's normal
[08:24] <rodrigo_> ok
[08:25] <rodrigo_> ah, and emacs is still in English also
[08:25] <rodrigo_> it's not covered by langpacks?
[08:26] <seb128> didrocks, btw on my normal account I get "xwininfo: Window id: 0x1600006 (has no name)" on the edge when I get the no reveal issue
[08:26] <seb128> didrocks, so you were right, seems 2 bugs
[08:26] <seb128> one being a stacking one, one being something else
[08:26] <didrocks> seb128: can you xprop it?
[08:26] <didrocks> I'm afraid it is, yeah :/
[08:26] <pitti> rodrigo_: apparently not
[08:26] <seb128> $ xprop
[08:26] <seb128> _NET_WM_ALLOWED_ACTIONS(ATOM) = _NET_WM_ACTION_ABOVE, _NET_WM_ACTION_BELOW
[08:26] <seb128> XdndAware(ATOM) = ARC
[08:26] <seb128> $
[08:26] <seb128> didrocks, ^
[08:26] <didrocks> seb128: yeah, it's the compiz window
[08:27] <didrocks> so 2 bugs
[08:27] <seb128> xwininfo: Window id: 0x1600006 (has no name)
[08:27] <seb128>   Absolute upper-left X:  0
[08:27] <seb128>   Absolute upper-left Y:  2
[08:27] <seb128>   Relative upper-left X:  0
[08:27] <seb128>   Relative upper-left Y:  2
[08:27] <rodrigo_> pitti, ok, that's what I see so far then
[08:27] <rodrigo_> ah, ditto for chromium browser, it's all in English
[08:27] <seb128> didrocks, smspillaz, ohhhh
[08:27] <didrocks> seb128: right, thanks for confirming, we need to ping Jason back
[08:27] <pitti> rodrigo_: cheers
[08:27] <seb128> didrocks, it works!
[08:27] <didrocks> hum?
[08:27] <pitti> rodrigo_: chromium is both universe and not using gettext
[08:27] <didrocks> xprop fixed it? :)
[08:27] <rodrigo_> pitti, right
[08:27] <pitti> rodrigo_: install chromium-browser-l10n if you care
[08:28] <seb128> didrocks, yeah, or something else, weird
[08:28] <rodrigo_> not much, I'll switch back to English in the next reboot
[08:28] <rodrigo_> as I said, some Spanish translations confuse me more than helping
[08:28] <didrocks> seb128: there is clearly something not setting the bit in the hide machine
[08:29] <rodrigo_> pitti, anything else you want me to test?
[08:30] <rodrigo_> ugh, another bad translation, in xchat -> $person has quit -> $person ha cerrado
[08:30] <didrocks> seb128: weird, ubuntuone-gnome-client 2.0.0-0ubuntu1 -> "Stop using gconf in Oneiric" but I still see a lot of gconf code in it
[08:30] <rodrigo_> which means $person has closed :)
[08:30] <didrocks> seb128: so, yeah, let's check with him
[08:30] <pitti> rodrigo_: no, that's fine; thanks!
[08:30] <rodrigo_> pitti, ok
[08:31] <rodrigo_> so, I'm supposed to be swapping today with the weekend, as today I have several things to do, so bbl for some more work before leaving for the day
[08:31] <rodrigo_> so, bbl
[08:31] <didrocks> well, the gconf code is conditional in fact to older nautilus
[08:34] <dpm> pitti, ok, with the correct langpacks installed, Catalan looks good
[08:34] <pitti> dpm: great, thanks; I think I can rescue the ubuntu-docs translations, too
[08:34] <pitti> the static translation tarball is fine, it just didn't get applied for some reason
[08:35] <mhr3> mvo, ping
[08:35] <dpm> pitti, ah, great
[08:37] <mhr3> mvo, i'm looking at the sc database we're using in apps-lens and i'm wondering how exactly do you construct the desktop_file field, i thought it's "app_name:desktop_id", but the second thingie doesn't seem to be desktop id
[08:37] <mvo> mhr3: its just the filename of the desktop file as found in the package
[08:38] <mhr3> mvo, and you're transforming slashes there, right?
[08:39] <pitti> dpm: FYI, filed as bug 869815; I'll manually hack it in this time
[08:39] <ubot2> Launchpad bug 869815 in langpack-o-matic "does not properly install mallard help files" [High,In progress] https://launchpad.net/bugs/869815
[08:39] <pitti> and once they are uploaded, I'll work on fixing it properly
[08:40] <dpm> sounds good, thanks pitti!
[08:40] <mhr3> mvo, cause an example of what i see is: "kcachegrind:kde4__kcachegrind.desktop"
[08:41] <mvo> mhr3: right, that is a expection, if its in a subdir of /usr/share/applications the slash is converted the underscores
[08:49] <seb128> RAOF, still there?
[08:49] <RAOF> seb128:  Ish
[08:50] <seb128> RAOF, just mentioning it in case that's useful, but chrisccoulson has been tracking a g-s-d xrandr dell docking issue before his holidays
[08:50] <RAOF> He's on holidays for another week, isn't he?
[08:51] <seb128> RAOF, when the latitude e are docked the OS gets they keybinding for cycle screen configs
[08:51] <seb128> RAOF, so g-s-d gets a double event, the xrandr one and the keybinding
[08:51] <seb128> RAOF, and it cycle twice
[08:51] <seb128> RAOF, he's back on monday
[08:51] <seb128> RAOF, well I'm just mentioning it in case that's useful for the issue you were debugging on something similar
[08:52] <seb128> RAOF, he said that he thinks the dock station is sending the keybinding maybe to workaround issue on other OSes
[08:55] <RAOF> That doesn't sound entirely unlikely.
[08:55] <RAOF> If by "other OSes" you mean "Windows" :)
[08:55] <pitti> dpm: seems ubuntu-docs does't have Catalan translations yet
[08:55] <pitti> $ ls ubuntu-docs/usr/share/help-langpack/
[08:55] <pitti> cs  da  de  en_AU  es  fi  gl  hu  it  nl  pt_BR  ru  sk  sl  sr  sv  tr
[08:56] <dpm> pitti, that's correct, it's entirely new documentation, and we haven't had the chance to start it this cycle
[08:56] <pitti> uh, and no French either? what happened? :-)
[08:56] <seb128> RAOF, yes ;-)
[08:56] <seb128> RAOF, well anyway just dumping the info in case it's of any use
[08:56] <pitti> seb128, didrocks: how come you French guys didn't already translate the new ubuntu-docs to 100% :-)
[08:56] <RAOF> Ta.
[08:56] <ajmitch> en_AU?
[08:56] <dpm> pitti, they were probably slacking
[08:57] <RAOF> seb128: It looks like there may well be an actual X/kernel bug lying around in there, but one that could be worked around by not doing so much pointless work when disabling the output.
[08:57]  * ajmitch hopes that the english-speaking world isn't going to switch to strine :)
[08:57] <didrocks> pitti: oh really? I can handy ping the translator coordinator
[08:58] <seb128> RAOF, btw is that normal that you can "stack" 2 screens on top of each other?
[08:58] <pitti> seb128: why not? you can align them however you want
[08:58] <pitti> physically and in xrandr
[08:58] <ajmitch> is python-testtools on the cd? I just came across a bug that caused it to break my upgrade a bit
[08:58] <dpm> ajmitch, the Australian team were very active, this cycle, reaching 100% translation (http://people.canonical.com/~dpm/stats/ubuntu-11.10-translation-stats.html), so perhaps... :)
[08:59] <pitti> jbicha: ok, ubuntu-docs translations hand-hacked in, yelp is nicely translated now
[08:59] <ajmitch> dpm: I guess #ubuntu-nz will have to get motivated then
[08:59] <seb128> pitti, because that happened to me on lid closed the other day, I still had the laptop screen on and on top of my external monitor which leads the external monitor to have 2 rows of indicators and 2 titles nautilus background
[08:59] <seb128> pitti, pretty "weird"
[08:59] <dpm> ajmitch, yeah, most definitely :)
[08:59] <seb128> pitti, well the main bug there is that it should stop the laptop screen when the lid is closed
[08:59] <seb128> not stack it over my external monitor
[09:00] <ajmitch> lifeless: fwiw, bug 847827
[09:00] <pitti> seb128: oh you don't mean "one above the other", but stacking in Z direction?
[09:00] <ubot2> Launchpad bug 847827 in python-testtools "python-testtools doesn't install on systems with Python 2.4" [Undecided,Confirmed] https://launchpad.net/bugs/847827
[09:00] <pitti> seb128: like an overlay?
[09:00] <RAOF> Yeah that's quite fun :)
[09:00] <pitti> seb128: right, it never does that here either, I just xrandr off it in my "start session script"
[09:00] <lifeless> ajmitch: meh :P
[09:00] <lifeless> ajmitch: I mean, sorry, I care a great deal.
[09:00] <seb128> pitti, if you use a docked laptop turn off the laptop screen, dnd it over the external one if the xrandr capplet
[09:00] <pitti> so far g-s-d hasn't been very clever at handling docking stations
[09:00] <ajmitch> lifeless: yeah, easy to work around but a pain at this late stage
[09:01] <seb128> re-enable it
[09:01] <RAOF> seb128: It's entirely allowed by the XRandR protocol, though.
[09:01] <jbicha> pitti: thanks, the other apps using /usr/share/help are deja-dup & aisleriot, more will switch in GNOME 3.4
[09:01] <pitti> seb128: fun
[09:01] <lifeless> ajmitch: we should split the tests into a different binary.
[09:01] <pitti> RAOF: yeah, I thuoght in xrandr you can use whichever weird offset you like
[09:02] <RAOF> pitti: Indeed.  g-d-p is actually quite fond of setting up my laptop display at x=8, y=1200 (under my 1920x1200 external monitor).
[09:03] <ajmitch> lifeless: it at least caused me to finally remove python2.4 from my system :)
[09:04] <seb128> pitti, well g-s-d is fine at handling docking sessions
[09:04] <seb128> pitti, but one issue is the one I was mentioning chrisccoulson was working on
[09:04] <seb128> pitti, so station send a "switch resolution" keybinding when you dock
[09:04] <seb128> which leads to a duplicate "switch resolution" event
[09:04] <seb128> and to a buggy config
[09:05] <seb128> i.e g-s-d handle it correctly with the xorg events and then the station send the extra signal that screws it
[09:07] <seb128> jibel, hey
[09:07] <seb128> jibel, indicator* bugs are dx ones, not desktop ones
[09:08] <seb128> jibel, I'm reassigning that indicator sound one to them
[09:08] <jibel> seb128, ah, sorry. thanks for reassigning.
[09:09] <seb128> yw ;-)
[09:12] <seb128> pitti, is that normal that the guest user has access to user directories?
[09:13] <pitti> seb128: erk, no; that was supposed to be fixed with my lightdm upload last Friday
[09:13] <seb128> pitti, seems it's not, well how is the restriction made?
[09:13] <pitti> seb128: what lightdm version do you run?
[09:13] <seb128> pitti, let's me reformulate "is that normal that you have access to user dirs which are 755"?
[09:13] <pitti> seb128: do you have a /etc/apparmor.d/lightdm-guest-session ?
[09:13] <pitti> seb128: no, it's not; /home should be completely blocked by apparmor
[09:13] <seb128> pitti, I'm uptodate from yesterday
[09:14] <seb128> pitti, I've a /etc/apparmor.d/lightdm-guest-session yes
[09:15] <pitti> seb128: if you do "sudo aa-status", does /usr/lib/lightdm/lightdm-guest-session-wrapper appear in "12 profiles are in enforce mode."?
[09:15] <seb128> $ sudo aa-status | grep guest
[09:15] <seb128>    /usr/lib/lightdm/lightdm-guest-session-wrapper
[09:15] <seb128>    /usr/share/gdm/guest-session/Xsession
[09:15] <seb128> 15 profiles are loaded.
[09:15] <seb128> 15 profiles are in enforce mode.
[09:15] <seb128> it's in that list yes
[09:16] <seb128> pitti, well, I open a guest session, click on nautilus, ctrl-L, /home
[09:16] <seb128> and it let me browse the users dirs
[09:16] <pitti> checking here, hope it didn't get broken in the last updates
[09:16] <seb128> oh
[09:16] <pitti> eh, guest user disappeared from user indicator
[09:16] <seb128> pitti, I've no /usr/lib/lightdm/lightdm-guest-session-wrapper
[09:16] <seb128> $ dpkg -S lightdm-guest-session-wrapper
[09:16] <seb128> dpkg-query: no path found matching pattern *lightdm-guest-session-wrapper*.
[09:16] <seb128> pitti, .install screwup?
[09:16] <pitti> eek
[09:17] <pitti> that might also explain why I don't even have a guest session in the indicator
[09:17] <seb128> I've a guest session in the indicator
[09:17] <pitti> seb128: can you please file a bug for trackign this, and I'll look into it in the meantime?
[09:17] <seb128> pitti, ok
[09:17] <seb128> pitti, I'm looking at why it's not installed
[09:17] <pitti> hm, seems user switching is completely gone right now
[09:18] <seb128> there is a fail somewhere
[09:18] <seb128> pitti, http://bazaar.launchpad.net/~lightdm-team/lightdm/1.0/revision/1233
[09:19] <seb128> that seems wrong
[09:19] <pitti> erk, where's the rest of the code?
[09:20] <seb128> dunno
[09:20] <seb128> it seems he merged only a revision or something
[09:20] <pitti> he just merged the second commit of my branch, not the first one
[09:20] <pitti> https://code.launchpad.net/~pitti/lightdm/guest-session-lockdown/+merge/77721
[09:21] <pitti> seb128: I'll fish that out as a patch again then
[09:21] <seb128> pitti, http://bazaar.launchpad.net/~lightdm-team/lightdm/trunk/revision/1242
[09:21] <seb128> pitti, so it seems it might be a trunk to 1.0 backport issue
[09:22] <pitti> seb128: ok, re-opening bug 849027
[09:22] <ubot2> Launchpad bug 849027 in lightdm "lightdm does not provide an equivalent to the gdm guest session AppArmor profile" [Critical,Fix released] https://launchpad.net/bugs/849027
[09:22] <seb128> pitti, do you want a new bug or using that one is ok?
[09:23] <pitti> I'm using that one
[09:24] <seb128> pitti, thanks
[09:27] <seb128> didrocks, btw, http://pastebin.ubuntu.com/703840/ is the duplicates from retracer since yesterday
[09:27] <didrocks> seb128: ah nice!
[09:28] <didrocks> seems we clearly got fixes for the right ones :)
[09:28] <seb128> didrocks, the top 3 are the 3 bugs you closed with your upload today
[09:28]  * didrocks looks at other popular one
[09:28] <seb128> indeed ;-)
[09:28] <didrocks> yeah
[09:28] <didrocks> bug #868514 is the open-terminal one
[09:28] <ubot2> Launchpad bug 868514 in nautilus-open-terminal "nautilus crashed with SIGSEGV in gconf_client_get()" [Medium,Confirmed] https://launchpad.net/bugs/868514
[09:28]  * didrocks dups
[09:29] <seb128> the next one as well
[09:29] <seb128> the next next one is the new gnome-desktop wrapper RAOF added but he said that's not a real issue just apport noise
[09:29] <didrocks> yep
[09:30] <seb128> I will retweak my script
[09:30] <didrocks> ah, an unity 2d crash
[09:30] <seb128> it was making the list with titles using lp
[09:30] <didrocks> seb128: can we get a webpage with cumulative data over days?
[09:30] <didrocks> if you need help, I can give it a look :)
[09:31] <seb128> didrocks, there a 2 issues there
[09:31] <seb128> 1- I don't know how to go from the retracer box to a public space
[09:31] <seb128> i.e how to auto publish the log
[09:31] <seb128> 2- apport logs lack some infos so I need to hack
[09:31] <seb128> I will send a patch to pitti for that
[09:31] <didrocks> oh?
[09:31] <pitti> seb128: for 2-, is there something we need to add (logging) to apport-retrace?
[09:32] <seb128> i.e the line who has the "duplicate of #...." doesn't have timestamp
[09:32] <pitti> seb128: for 1, it's possible, but requires some effort
[09:32] <seb128> pitti, well right now I grep for "duplicate of #..." and sed
[09:32] <didrocks> I think it would be a nice QA tool if we can achieve those
[09:32] <seb128> but I lack the timestamp
[09:32] <seb128> so I can't do "by day"
[09:32] <pitti> that should be trivial to fix
[09:32] <seb128> yes
[09:32] <pitti> and it's running trunk, so we can roll it out immediately
[09:34] <seb128> pitti, I will have a look to make a patch
[09:34] <didrocks> seb128: i guess we need a cumulative view as well (but the timestamped one can help to see when the issue started to raise)
[09:34] <seb128> didrocks, how "cumulative"?
[09:34] <didrocks> seb128: if you need any help, do not hesitate, I like hacking around those tools
[09:34] <didrocks> seb128: like, "this crash got xx duplicates in total"
[09:35] <seb128> didrocks, I think I'm fine thanks, my script from previous cycle works fine to process the datas
[09:35] <pitti> also, if you want crash-digger to keep some statistics, that's probably easier to implement in that code than through grep and sed
[09:35] <seb128> what I've issue with is to get the bugs 'from the day'
[09:35] <pitti> 10/07/11 09:32:06: retracing #869852 (left in pool: 0)
[09:35] <seb128> pitti, well the grep, sed command run on the logs takes like 1 second
[09:35] <pitti> that does have the day?
[09:36] <seb128> pitti, i386.txt.2011107.gz:Report is a duplicate of #861548 (not fixed yet)
[09:36] <seb128> I'm using those
[09:36] <seb128> to see what bugs get duplicates
[09:36] <seb128> pitti, I'm not counting unique retracing, just duplicates
[09:37] <seb128> pitti, i.e I want to see everything which i.e got > 5 duplicates this week
[09:38] <seb128> pitti, so from that line I count 861548 1 duplicate
[09:39] <pitti> seb128: hm, did you recently truncate the logs, or is that a bug in apport?
[09:39] <pitti> ah, apparently so
[09:39] <seb128> pitti, I rotate them daily so I can run a "stats from the day"
[09:39] <pitti> 08/24/11 06:07:46: Report is a duplicate of #824979 (not fixed yet)
[09:39] <seb128> pitti, btw I use that
[09:39] <seb128> $ zcat [ia]*.gz | grep 'duplicate of' | awk '{print $6}' | sort | uniq -c | sort -n
[09:39] <pitti> so the timestamp does exist for python bugs
[09:40] <pitti> Report is a duplicate of #849414 (not fixed yet)
[09:40] <pitti> aah
[09:40] <seb128> right
[09:40] <seb128> those lack the timestamp ;-)
[09:41] <pitti> ah, that's in apport-retrace, not crash-digger
[09:41] <pitti> ok, so it's not a two-second patch
[09:41] <pitti> I'll test new lightdm first, get that pushed out, and come back to this then
[09:41] <pitti> bbl
[09:41] <seb128> pitti, thanks
[09:47] <pitti> ok, lightdm is happy again
[09:47] <pitti> seb128: nice catch!
[09:47] <seb128> pitti, thanks ;-)
[09:47] <seb128> pitti, well rather "useful bugs review"
[09:48] <seb128> there was a comment on a bug asking if that's normal
[09:48] <seb128> pitti, did you try to use the scripts since your changed the retracers?
[09:49] <seb128> $ export PYTHONPATH=$HOME/apport
[09:49] <seb128> $ scripts/subscribe-triagers.py ./bug
[09:49] <seb128> ...
[09:49] <seb128>   File "/home/ubuntu-archive/apport/apport/crashdb.py", line 492, in get_crashdb
[09:49] <seb128>     execfile(conf, settings)
[09:49] <seb128> IOError: [Errno 2] No such file or directory: '/etc/apport/crashdb.conf'
[09:49] <pitti> seb128: no, I didn't
[09:49] <seb128> db = apport.crashdb.get_crashdb('launchpad-credentials')
[09:49] <pitti> oh, that woudln't work
[09:49] <seb128> is the corresponding line
[09:49] <pitti> give me a second
[09:49] <seb128> yeah, no hurry
[10:06] <pitti> seb128: right, get_crashdb() needs /etc/apport/crashdb.conf
[10:08] <pitti> seb128: can you try again?
[10:08] <pitti> seb128: I edited it, but didn't run it
[10:08] <pitti> from apport.crashdb_impl.launchpad import CrashDatabase
[10:08] <pitti> db = CrashDatabase('launchpad-credentials', None, {'distro': 'ubuntu'})
[10:08] <pitti> seb128: get_crashdb() gets the implementation and arguments from /etc/apport/crashdb.conf
[10:08] <pitti> that instantiates the right one directly
[10:09] <pitti> it's also possible to provide a different path to crashdb.conf, but IMHO above is more direct and eaiser
[10:09] <pitti> seb128: if it works for you, I'll apply it to the other scripts as well
[10:12] <seb128> pitti, trying
[10:13] <seb128> pitti, ok, that fixes that error
[10:13] <seb128> I get "ImportError: No module named launchpadlib.errors" now
[10:13] <pitti> good
[10:13] <pitti> eh? that again?
[10:13] <seb128> isn't lpi installed on that box?
[10:13] <pitti> ooh
[10:13] <seb128> no it's not
[10:13] <pitti> seb128: you probably need to call it in dchroot
[10:13] <seb128> should I file a rt?
[10:13] <pitti> all the retracer stuff runs in dchroot -c oneiric
[10:14] <seb128> pitti, ok, that works
[10:14] <pitti> it's installed there, and in the dchroot you can do "sudo apt-get install" yourself
[10:14] <pitti> seb128: ok, doing the change to the other scripts
[10:15] <seb128> \o/ my natty script still works
[10:16] <pitti> wow, so I didn't break the log format even? :-)
[10:16] <pitti> seb128: all scripts fixified
[10:18] <tkamppeter> seb128, I have found out the cause of my online account problem, bug 869341, and given suggestions to solve the problem.
[10:18] <ubot2> Launchpad bug 869341 in gnome-online-accounts ""Online Accounts" icon and UI appears in g-c-c when gnome-online-accounts package is not installed, ignoring user's registration input." [High,Confirmed] https://launchpad.net/bugs/869341
[10:18] <seb128> tkamppeter, thanks
[10:19] <seb128> didrocks, pitti: ok, my script gives that output: http://pastebin.ubuntu.com/703867/
[10:19] <seb128> just for info
[10:19] <seb128> that's bugs with ndup >= 2
[10:19] <pitti> nice
[10:19] <seb128> on the log from yesterday
[10:19] <didrocks> seb128: great! and for lazy people, can you add the link to the bug?
[10:19] <seb128> didrocks, yeah
[10:20] <didrocks> \o/
[10:20] <didrocks> :)
[10:20] <seb128> now I need to figure a way to get things published from the retracer to people
[10:20] <seb128> or somewhere else
[10:20] <pitti> I wonder if jibel has something similar (working directly on LP); every release meeting he gives the "most active bugs" stats
[10:20] <pitti> seb128: it's roughly like this:
[10:20] <seb128> jibel, ^
[10:21] <pitti> seb128: on lillypilly (people.c.c), create a ssh key which only allows an rsync call
[10:21] <pitti> seb128: on porter, create a ssh key called "retracer" without a password, and install it on lillypilly
[10:21] <pitti> then set up a cronjob to rsync the logs every 10 minutes
[10:22] <seb128> pitti, I will have a go to it, thanks
[10:22] <pitti> seb128: check ubuntu-archive@lillypilly:.ssh/authorized_keys
[10:22] <pitti> seb128: it does that very thing for a lot of other reports, such as component-mismatches and the like
[10:22] <pitti> with that you can limit the damage that the passwordless ssh key can do
[10:24] <seb128> pitti, thanks
[10:25] <pitti> cyphermox: any progress on bug 805311? last dupe is from September 30, I wonder if it was magically fixed then?
[10:25] <ubot2> Launchpad bug 805311 in gnome-bluetooth "gnome-control-center crashed with SIGSEGV in g_type_instance_get_private() (device_services_changed)" [High,Triaged] https://launchpad.net/bugs/805311
[10:56] <BigWhale> It is frustrating that network mounts are not accessible from command line... or are they?
[10:57] <BigWhale> network mounts made in nautilus
[11:23] <jibel> seb128, I use something close. I've a script that extract data from LP, the output is there http://paste.ubuntu.com/703895/ it also generate a json file
[11:24] <jibel> seb128, then another script process the json file to create statistics
[11:25] <mvo> seb128: if nautilus tells me it can't mount my external devices with "not authorized", what can I do?
[11:34] <seb128> mvo, is gnome polkit daemon running?
[11:36] <seb128> jibel, what is the logic of your script? is it slow to run?
[11:36] <seb128> jibel, logic, i.e what bugs does it consider?
[11:41] <mvo> seb128: the agent you mean? yes, polkitd as well
[11:42] <seb128> mvo, what error do you get?
[11:43] <mvo> seb128: Unable to mount kindle\nNot Authorized. is there a chance that there is anything somewhere else?
[11:44] <seb128> mvo, ps aux | grep kit-gnome?
[11:44] <seb128> mvo, can you i.e unlock the g-c-c user account panel
[11:44] <seb128> i.e is polkit working in other desktop components?
[11:45]  * mvo checks
[11:45] <jibel> seb128, it takes everything with an ubuntu task and tagged "oneiric" reported over the last 3 days or week. following this logic reports submitted without apport are not caught.
[11:46] <jibel> seb128, and it is as fast as a remote access to the lp api can do.
[11:46] <mvo> seb128: update-manager works, but its asking me for a password on check, normally we allow that for admin users
[11:46] <mvo> seb128: somehting odd is going on
[11:46] <seb128> mvo, ck-list-session?
[11:47] <seb128> mvo, is your session an active admin one?
[11:48] <seb128> pitti, still around or at lunch?
[11:48] <mvo> seb128: oh, that is interessting, it showns me a whole bunch (about 10) for some I am marked active and local, for others I'm not
[11:49] <seb128> mvo, do you have that number of active sessions in vts, etc?
[11:50] <mvo> seb128: no, just one open terminal with a signle tab and no users on the console (but I was logged into that before)
[11:50] <seb128> mvo, ok, weird
[11:50] <mvo> seb128: all sessions have the same session-id it seems
[11:50] <seb128> you should have only one active session
[11:50] <pitti> seb128: back now
[11:51] <seb128> pitti, kamstrup got a candidate patch for the lightdm ck issue: https://code.launchpad.net/~kamstrup/lightdm/fix-gvariant-refs/+merge/78574
[11:51] <seb128> pitti, I'm about to upload to the ubuntu-desktop ppa, do you think we should try to get it in oneiric now as well?
[11:52] <kamstrup> seb128, pitti: at worst it can cause a leak if you log in and out a lot. Not add more crashing :-)
[11:52] <kamstrup> (although I am pretty sure it's correct)
[11:52] <pitti> seb128: oh, so it lost the ref and crashed due to accessing an already freed object/
[11:52] <pitti> yes, I think leak is better than a lost ref
[11:53] <pitti> seb128: fine for me to put it into final, this looks harmless enough
[11:53] <kamstrup> pitti: but I actually don't think it's leaking when we sink the ref. All callers I could grep passed in a g_variant_new_*() directly in the method params
[11:54] <mvo> seb128: rebooting fixed it, I think it was a .Xauthority that had wrong permissions that lead me to not be able to log in, but  apparently that did not close the CK sessions and that mightly confused the poor polkit
[11:54] <pitti> kamstrup: great job!
[11:54] <seb128> mvo, ok
[11:54] <seb128> pitti, should I upload to Oneiric then?
[11:54] <seb128> on it
[11:54] <pitti> seb128: please go ahead
[12:03] <seb128> doh, who changed dch in oneiric to stop setting oneiric :p
[12:03] <pitti> annoying that
[12:03] <seb128> pitti, ok, reuploaded with an oneiric target this time
[12:03] <pitti> cheers
[12:09] <pitti> seb128: so how do you figure out the duplicate date without the timestamp?
[12:10] <seb128> pitti, I don't, I rotate manually log every day and run my script on the whole current log :p
[12:10] <pitti> ah
[12:10] <seb128> every day or every couple of days
[12:10] <seb128> or I tail it
[12:10] <seb128> i.e I hack around ;-)
[12:30] <seb128> re
[12:30] <seb128> pitti, well done, I confirm that the guest account block the home access now ;-)
[12:30] <pitti> yay
[12:34] <pitti> seb128: from now on retracer logs will have timestamps
[12:35] <pitti> seb128: this might break your scripts?
[12:35] <seb128> \o/
[12:35] <pitti> seb128: shall I wipe the logs again, to have one format in a file?
[12:35] <seb128> pitti, yes please
[12:36] <pitti> seb128: doesn't affect dupcheck.txt, so I'll leave that
[12:36] <seb128> right
[12:36] <seb128> thanks
[12:36] <pitti> done, appended to existing 2011107 logs
[12:36] <seb128> I will clean a bit my script and they try to automate it
[12:36] <seb128> pitti, thanks!
[12:36] <pitti> de rien
[12:37]  * pitti having time to do such changes to apport <-- GOOD sign!
[12:37] <seb128> ;-)
[12:37] <seb128> pitti, I've some retracers wishlists for next cycle btw
[12:37] <seb128> do you want bug reports?
[12:37] <pitti> seb128: please
[12:38] <seb128> 1- update the title after retracing to use the correct function name
[12:38] <pitti> usually works better than separate todo lists; I look at +assignedbugs rather often
[12:38] <seb128> it picks the name from the submit time nowadays but that's often not accurate
[12:38] <pitti> oh, I thought we already do that
[12:38] <pitti> but +1
[12:38] <pedro_> update the backtrace of the master bug is there's a dup with a new version ? :-)
[12:39] <seb128> that would be nice as well
[12:39] <pitti> in addition?
[12:39] <seb128> or at least "don't clean regression bugs"
[12:39] <pitti> that's more complex, but bug please
[12:39] <seb128> i.e bug that are detected duplicates of closed bugs
[12:39] <pitti> seb128: "clean regression bugs"?
[12:39] <pitti> they shouldn't be duped in teh first place
[12:39] <pitti> i. e. if a duplicate comes in if the master bug is "fix released"
[12:40] <pitti> it should go to a new bug
[12:40] <pitti> that hasn't worked for a while
[12:40] <pitti> but a few weeks ago I fixed this consolidation thing
[12:40] <seb128> pitti, if I submit a duplicate of a known bug that is ought to be fixed it will mark "that is a duplicate of that bug", tag regression but not attach the retraced stacktrace
[12:40] <seb128> pitti, the new bug doesn't get the retracing attachments though
[12:40] <pitti> seb128: oh, wow; that ought to be simple to fix indeed, bug please and +1 from me for fixing
[12:40] <seb128> it just get "it's a duplicate of that closed bug"
[12:40] <seb128> pitti, well, let me file a few bugs and give you the numbers
[12:40] <pitti> I want to add that to the test sutie
[12:41] <seb128> rather than describe over IRC ;-)
[12:41] <pitti> seb128: everything that is retracing, please file it against upstream
[12:41] <pitti> as we are running trunk in the DX
[12:41] <pitti> DC
[12:41] <pitti> (which makes things a lot easier)
[12:41] <seb128> pitti, ok
[12:50] <seb128> \o/
[12:50] <seb128> the deb from bug #550625 makes my touchpad work in g-c-c
[12:50] <ubot2> Launchpad bug 550625 in linux "Alps touchpad is recognized but synaptics clients and scrolling do not work" [Medium,Confirmed] https://launchpad.net/bugs/550625
[12:51] <seb128> I can disable the pad while typing now!
[13:10] <seb128> pitti, bug #869970
[13:10] <ubot2> Launchpad bug 869970 in apport "it would be nice to update the function name in the title after retracing" [Undecided,New] https://launchpad.net/bugs/869970
[13:14] <tkamppeter> pitti, I got a patch from Tim Waugh to fix the bugs of the cupsd-crashes-shortly-after start class, like bug 860498 or bug 860691 should this go as direct Oneiric upload or as 0-day SRU?
[13:14] <ubot2> Launchpad bug 860498 in cups "cupsd crashed with SIGSEGV in main() : cannot access memory at address 0x7ffffff7" [Medium,New] https://launchpad.net/bugs/860498
[13:14] <ubot2> Launchpad bug 860691 in cups "cupsd crashed with SIGSEGV in main() straight after boot and then periodically." [Medium,Confirmed] https://launchpad.net/bugs/860691
[13:14] <pitti> tkamppeter: what's the patch?
[13:14] <tkamppeter> pitti, diffstat is 1 file changed, 22 insertions(+), 2 deletions(-)
[13:15] <pitti> hm, sounds like SRU to me, I think
[13:16] <tkamppeter> pitti, for some users (see bugs) CUPS crashes shortly after it starts, making printing not working and causing crash reports. The crash is caused by a bug in Tim's Avahi support patch. Tim has provided a simple patch today.
[13:17] <pitti> tkamppeter: can you please commit the patch to debian bzr? I'll have a look at it there
[13:19] <seb128> pitti, bug #869974
[13:19] <ubot2> Launchpad bug 869974 in apport "Would be nice to have the "session started" time" [Undecided,New] https://launchpad.net/bugs/869974
[13:19] <tkamppeter> pitti, will do.
[13:24] <pitti> seb128: responded to 869974
[13:27] <dobey> seb128: claim what is dobey's bug?
[13:27] <seb128> pitti, thanks
[13:28] <seb128> ups, focus issue
[13:28] <seb128> pitti, ok, bug #869982 and I'm done for today
[13:28] <ubot2> Launchpad bug 869982 in apport "Should be easier for the maintainer to get updated stacktraces for a known bug" [Undecided,New] https://launchpad.net/bugs/869982
[13:28] <seb128> pitti, I'm really interested by this one
[13:29] <seb128> pitti, I've tried to expose the issue rather than suggest a solution though I gave some ideas about what I think could work
[13:33] <seb128> pitti, ok, replied to the other one
[13:36] <didrocks> dobey: bug #865115, see the last comments (I confirmed it's the case)
[13:36] <ubot2> Launchpad bug 865115 in ubuntuone-client-gnome "nautilus crashed with SIGSEGV in gconf_client_get(), if both nautilus-open-terminal and ubuntuone-client-gnome are installed" [High,Confirmed] https://launchpad.net/bugs/865115
[13:38] <dobey> didrocks: illogical
[13:39] <didrocks> dobey: what is illogical? can be gsettings and gconf mixing and creating issue, but I bet nautilus itself is using gsettings already
[13:40] <dobey> nautilus is using gsettings, yes; but it shouldn't matter what the plug-in uses
[13:40] <didrocks> dobey: I confirm that mixing the two plugins crashes though
[13:40] <dobey> didrocks: is there a complete stack trace anywhere? that bug seems to not have any apport retraces
[13:41] <didrocks> I guess I saw one in the dup, anyway, it's pretty easy to reproduce
[13:45] <pitti> seb128: replied to 869982
[13:45] <dobey> gdb won't let Us attach to the nautilus process
[13:45] <seb128> dobey, sudo ?
[13:45] <seb128> pitti, danke
[13:47] <seb128> pitti, replied ;-)
[13:47] <seb128> pitti, we can discuss it over IRC if you prefer btw then update the bug
[13:48] <pitti> seb128: replied to 869974
[13:48] <didrocks> #3  nautilus_open_terminal_get_file_items (provider=0x829d630, window=0x82de078, files=0x0) at nautilus-open-terminal.c:550
[13:48] <didrocks>         items = 0x0
[13:49] <didrocks> dobey: this seems wrong ^
[13:49] <pitti> seb128: it's actually nice to have the discussion on the bug, otherwise I'll ask all over again later on when I get to this :)
[13:49] <didrocks> let me install more dbgsym
[13:49] <dobey> yeah that seems wrong
[13:49] <seb128> pitti, ok ;-)
[13:50] <pitti> seb128: ok, bug 869982 settled
[13:50] <ubot2> Launchpad bug 869982 in apport "Should be easier for the maintainer to get updated stacktraces for a known bug" [Undecided,New] https://launchpad.net/bugs/869982
[13:50] <pitti> need to run out for a bit, back at release meeting
[13:50] <seb128> pitti, thanks ;-)
[13:53] <didrocks> dobey: http://paste.ubuntu.com/703972/
[13:53] <didrocks> I guess it's the best backtrace I can get
[13:53] <didrocks> dobey: do you create a dummy file or something like that that nautilus-open-terminal is picking?
[13:54] <dobey> didrocks: can you p *err in frame 0?
[13:54] <dobey> no
[13:56] <didrocks> dobey: $1 = (GError *) 0x0
[13:56] <didrocks> doesn't really help :)
[13:59] <dobey> that doesn't match your backtrace
[13:59] <dobey> gconf_client_get (client=0x82b0730, key=0x1e102f4 "/desktop/gnome/lockdown/disable_command_line", err=0xbfffee4c)
[13:59] <dobey> that is not 0x0 :)
[13:59] <didrocks> dobey: indeed, I relaunched it, let me see if this time the bt is different
[14:00] <dobey> maybe you need to print the local version instead, not sure what it is though
[14:00] <didrocks> (gdb) p err
[14:00] <didrocks> $5 = (GError **) 0xbfffee4c
[14:00] <didrocks> (gdb) p *err
[14:00] <didrocks> $6 = (GError *) 0x0
[14:00] <didrocks> with this time: #0  0x01a96f99 in gconf_client_get (client=0x82b9af8, key=0x1e102f4 "/desktop/gnome/lockdown/disable_command_line", err=0xbfffee4c) at gconf-client.c:1593
[14:01] <didrocks> it's a GError **, that's why we were puzzled :)
[14:02] <dobey> oh
[14:03] <dobey> right
[14:03] <dobey> p **err :)
[14:05] <didrocks> well, unsurprinsingly: (gdb) p **err
[14:05] <didrocks> Cannot access memory at address 0x0
[14:05] <didrocks> :)
[14:05] <dobey> hmm
[14:05] <dobey> oh well
[14:06] <dobey> the crash We are getting on natty is different :-/
[14:07] <didrocks> oh really?
[14:07] <tkamppeter> pitti, patched cups built, started, clicked around in s-c-p, printed test page, keeps running, patch committed/pushed to Debian BZR.
[14:15] <dobey> didrocks: yeah, debugging it
[14:15] <didrocks> dobey: great, thanks! :)
[14:24] <mvo> dpm: meh, do you have a moment to help me with LP? I'm unable to find the right knob to configure it to export the updated translations into a branch that is mergable from software-center trunk
[14:25] <dpm> mvo, sure
[14:25] <dpm> let me load the sc LP page...
[14:27] <dobey> didrocks: fixing
[14:28] <didrocks> dobey: oh you found the issue? Nice!
[14:28] <dobey> yes, i think so
[14:28] <dobey> need to test on oneiric
[14:29] <dobey> but am pretty sure it is it
[14:29] <dpm> mvo, that's the page you need: https://translations.launchpad.net/software-center/trunk/+translations - do you want to merge the rosetta-i18n-export branch to trunk?
[14:30] <mvo> dpm: yeah, that is what I would like to do
[14:31] <dpm> mvo, ok, so does that answer the question? Or were you trying to do something else as well?
[14:31] <mvo> dpm: thanks, I think I find my way aroudn now, I have no idea why I ended up on https://translations.launchpad.net/software-center where there is no sync setup
[14:31] <didrocks> dpm: send me the patch if you need oneiric testing
[14:32] <dpm> mvo, cool. Yeah, that's a bit confusing in the UI - you can only configure translations sync in branches, but not from the project's main page
[14:32] <mvo> yeah, I htink that was the missing info I needed, thanks again :)
[14:32] <dpm> didrocks, perhaps you meant dobey ^ ;)
[14:33] <didrocks> yeah dobey ^ ;)
[14:33] <didrocks> dpm: silly too smart weechat :-)
[14:35] <dobey> didrocks: testing on Our laptop
[14:35] <dobey> oh look, no unity
[14:38] <didrocks> dobey: can you look at your .xsession-errors?
[14:38] <didrocks> dobey: do you have console-kit message?
[14:39] <chrisccoulson> good afternoon everyone
[14:39] <dobey> didrocks: https://chinstrap.canonical.com/~dobey/xsession-errors
[14:39] <didrocks> hey chrisccoulson
[14:39] <chrisccoulson> hey didrocks, how are you?
[14:39] <dobey> gnome-session[1692]: WARNING: App 'compiz.desktop' respawning too quickly
[14:40] <didrocks> dobey: yeah, it's the lightdm issue with console-kit that hopefully kamstrup just fixed
[14:41] <seb128> dobey, try updating lightdm with the current version
[14:41] <pitti> tkamppeter: hm, this isn't immediately obvious to me -- it falls back to comparing pointer values if the timeval comparison says that it's different timestamps?
[14:41] <pitti> tkamppeter: it's less obvious than a simpler null pointer access fix or the like, so I think this should become an SRU
[14:41] <pitti> tkamppeter: please feel free to upload current bzr head to oneiric-proposed (or wait until next week, in case there are more fixes piling up)
[14:42] <pitti> tkamppeter: please just don't commit/tag the upload to debian bzr
[14:50] <tkamppeter> pitti, the problem hewre is that the array can contain two elements which are absolutely equal by content. To assure that the correct one gets deleted, the compare function uses the pointer values if the two entries are equal content-wise. This way the sort function can never consider two entries equal if the tywo are not the same entry.
[14:50] <tkamppeter> pitti, I will check whether Tim did not mess up ...
[14:51] <pitti> tkamppeter: ah, I see, thanks
[14:51] <pitti> tkamppeter: so the workaround with linear search that you did back then was something else then?
[14:52] <tkamppeter> pitti, yes, it was another bug.
[14:54] <tkamppeter> pitti, it seems that the CUPS arrays work only if the sort functions only return 0 if the two array elements are the same array element. The sort functions should never return zero if the elements are different elements with only the sort key fields being different. Even Mike Sweet did sometimes wrong on this.
[14:55] <tkamppeter> pitti, if a CUPS array is small, then it is better to not use a sort function and stay with linear search.
[14:55] <pitti> tkamppeter: ok, that makes more sense now, thanks for the heads-up
[14:55] <pitti> tkamppeter: so, I'm ok with an upload to oneiric if you want to do it now
[14:56] <tkamppeter> pitti, OK, should I do it or should you do it (you have to approve it anyway)?
[14:57] <tkamppeter> pitti, I have no other CUPS bug in the queue, especially no crasher.
[14:57] <pitti> tkamppeter: please do (meeting now); just upload current bzr, without committing the upload to bzr
[14:57] <tkamppeter> pitti, so taking your last AppArmor fix with it?
[14:57] <pitti> tkamppeter: yes, that's harmless
[14:58] <dobey> seb128: seems to have logged in properly the first time after boot now, at least
[14:58] <tkamppeter> pitti, OK, you only need to approve as soon as it is up.
[15:00] <dobey> didrocks: how is this crash reproduced btw?
[15:01] <seb128> dobey, great
[15:01] <didrocks> dobey: hum, just killall nautilus and launch it again, there is a 70% of the crash there
[15:02] <pitti> tkamppeter: hm, seems we are already testing images and Kate wants a hard freeze, so it's SRU after all
[15:02] <pitti> tkamppeter: sorry (but early SRU should be just as good)
[15:02] <pitti> tkamppeter: you can already upload to oneiric-proposed, BTW
[15:05] <tkamppeter> pitti, already uploade, so reject it and I will upload the package marked -proposed. Should the version number be -0ubuntu1 or -0ubuntu0.1 then?
[15:05] <pitti> tkamppeter: -9ubuntu1 will do fine
[15:05] <pitti> tkamppeter: rejected
[15:06] <mhr3> mterry, btw i checked the leaks and yea, it's much better now
[15:07] <mterry> mhr3, awesome
[15:07] <mhr3> mterry, the only thing i see is a couple of GtkLabels leaking per each app
[15:07] <mhr3> but really just a few
[15:07] <mhr3> like 6 per app
[15:07] <mterry> Interesting.  Sounds like the indicator-appmenu fix I pushed.  But that went through too, so this must be something new
[15:09] <mhr3> i should finally finish my awesome tool to be able to see who created the instance at least :)
[15:10] <mhr3> the backtrace is already there... just needs ui work
[15:11] <mhr3> but pygtk... eek :P
[15:13] <dobey> didrocks: yep, seems to fix it
[15:13] <didrocks> dobey: awesome \o/ seems a nice SRU candidate then
[15:15] <dobey> didrocks: yeah, nautilus-open-terminal is in universe right?
[15:15] <didrocks> dobey: oh, the fix is in nautilus-open-terminal?
[15:15] <didrocks> dobey: if so, we can upload :)
[15:15] <dobey> no
[15:15] <didrocks> ok, so SRU for ubuntuone
[15:15] <dobey> it is in ubuntuone-client-gnome
[15:16] <didrocks> dobey: and yeah, as it's in universe, it's not installed by default
[15:16] <dobey> but nautilus-open-terminal is in universe, so not an installed by default thing :)
[15:16] <didrocks> so 0-day SRU for upgrade is fine
[15:16] <dobey> yep
[15:16] <kenvandine> dobey, i am piloting, so send me the SRU branch an i can upload :)
[15:16] <kenvandine> s/an/and
[15:18] <dobey> when We make one We will do that. We are fixing in trunk first. And getting lunch. :)
[15:18] <kenvandine> lunch is good
[15:18] <kenvandine> :)
[15:22] <pitti> seb128: meh, another "500: Internal Server Error" crash
[15:22] <seb128> pitti, ;-(
[15:22] <pitti> seb128: I'll have a look at making this transient
[15:22] <pitti> this happens so often these days, also for our SRU scripts
[15:22] <pitti> annoying
[15:24] <kenvandine> dobey, is "We" kind of like "Dobey, dobster and the dobmaster"?
[15:24] <pitti> seb128: btw, do you still need these files in ~? list, debug, bug
[15:24] <seb128> pitti, no, sorry, that was earlier testing
[15:24] <pitti> no problem, just asking
[15:24] <seb128> pitti, I should do that in a testing dir ;-)
[15:25] <pitti> it doesn't hurt, I just wondered
[15:25] <pitti> crashes in lp_save() through close_duplicate(); erk
[15:26] <pitti> if I do the dup in the web UI, it says
[15:26] <pitti> The following errors were encountered:
[15:26] <pitti>     AttributeError
[15:26] <pitti> probably too many dupes
[15:33] <pitti> seb128: so, I think I better leave it crashing, so that we can clean those dupes manually; it's not crashing too often, and ignoring it leads to open bugs which are dupes; ok?
[15:33] <pitti> restarted
[15:34] <seb128> pitti, works for me yes
[16:00] <tkamppeter> pitti, CUPS uploaded to -proposed.
[16:00] <tkamppeter> pitti, do I need to do something else?
[16:00] <pitti> tkamppeter: nope, that's fine; thanks
[16:05] <tkamppeter> pitti, can you approve it now?
[16:06] <dobey> kenvandine: it is the Royal We
[16:06] <pitti> tkamppeter: will do on Monday, when we freeze really really hard
[16:08] <tkamppeter> pitti, OK, I only thought to let the bug-reporting users test this already on the weekend ...
[16:14] <pitti> tkamppeter: (asking in release meeting)
[16:18] <pitti> tkamppeter: ok, Monday it is
[16:18] <tkamppeter> pitti, OK.
[16:31]  * popey hugs pitti 
[16:32] <pitti> popey: I wish I had seem that earlier, then we could have fixed it months ago :(
[16:32] <popey> meh. it's a very small subset of the world that a) run the developer edition of iOS, and b) run Ubuntu, and c) plug device A into computer B :D
[16:32] <popey> still, I'm happy ☺
[16:36] <seb128> ok, time for some sport, I will be back in ~45 minutes to read the backlog and emails and then call it a week
[16:36] <seb128> have a nice w.e for those who will call it a week before I'm back ;-)
[16:37] <pitti> seb128: bye
[16:38] <didrocks> see you seb128
[16:50] <micahg> seb128: any chance you can fix the desktop team owner before eow?
[16:50] <asac> hmm
[16:51] <asac> i unmaximized firefox on up to date oneiric
[16:51] <asac> and the window decoration disappeared :)
[16:51] <asac> but only for firefox :/
[16:54] <dobey> asac: same here
[16:55] <asac> dobey: oh ... at same time :)?
[16:55] <asac> seb128: didrocks: interested in any info i could gather now?
[16:55] <asac> otherwise i will killall firefox :-P
[16:55] <dobey> asac: no, We saw this behavior last night
[16:55] <dobey> asac: restarting firefox didn't help :)
[16:55] <asac> didnt?
[16:56] <asac> dobey: wm restart required?
[16:56] <dobey> not for Us
[16:56] <dobey> don't know if it is fixed at all yet :)
[16:56] <dobey> let's see
[16:56] <asac> oh your ffox is now with decoration forever ?
[16:56] <asac> wow
[16:56] <didrocks> asac: only for firefox, you still have decoration on the other apps?
[16:56] <asac> i wished i hadnt unmaximized it ... want to maximize it again
[16:56] <asac> didrocks: exactly
[16:56] <dobey> oh it is working now on Our laptop
[16:56] <asac> i unmaximized firefox because i wanted to move it to different desktop
[16:57] <didrocks> asac: if you can reproduce, I think smspillaz would be interested in the "damage" plugin
[16:57] <asac> suddenly it was on a different desktop ... when i looked i figured it was sitting there without decoration
[16:57] <didrocks> if you can enable it (it should be in -extra plugins)
[16:57] <asac> didrocks: ok so nothing i can do with this state
[16:57] <asac> let me try to kill and see if it happens again
[16:57] <didrocks> asac: unfortunately, no
[16:57] <didrocks> yeah
[16:57] <dobey> asac: so log out/in might fix it
[16:58] <asac> not easily reproducable
[16:58] <asac> restarting helped
[16:58] <dobey> asac: We have installed new updates since, so no guarantees :)
[16:58] <asac> let me dist-upgrade one more time
[17:18] <pitti> good night everyone!
[17:18] <didrocks> ok, time for week-end then!
[17:18] <pitti> have a nice weekend
[17:18] <didrocks> thanks, you too pitti :)
[17:30] <jbicha> I think cheese and gnome-sushi will build on ARM if someone wants to retry those builds
[17:32] <seb128> asac, when that happens you can alt-click-dnd to the top, the grib will snap it
[17:32] <seb128> jbicha, ok
[17:33] <asac> seb128: smart. i should have remembered that
[17:33] <asac> but i think without window decoration you cannot move at all?
[17:33] <asac> hmm
[17:33] <asac> next time
[17:34] <seb128> asac, no, that works, been there, done that ... ;-)
[17:34] <asac> thats awesome ... how can i disable window decorations alltogether :)?
[17:34] <asac> seems i dont need that feature :)
[17:34] <asac> weekend fun
[17:39] <jbicha> I've seen a few reports that Firefox search plugins still go missing for upgrades from Natty to Oneiric
[17:39] <seb128> jbicha, I think it's on chrisccoulson's list for next week
[17:39] <seb128> they agree it's ok for a SRU since it doesn't affect new installs
[17:40] <chrisccoulson> yep
[17:40] <chrisccoulson> :)
[18:13] <micahg> anyone care about epiphany-extensions-more or can I remove from oneiric?
[18:14] <micahg> Bug #870187 if anyone has a good reason to not remove
[18:14] <ubot2> Launchpad bug 870187 in epiphany-extensions-more "Please remove epiphany-extensions-more source and binaries from oneiric" [Wishlist,Confirmed] https://launchpad.net/bugs/870187
[21:29] <bjf> i just copied two pictures from my cell phone onto the desktop, the files were there for a second and then vanished
[21:30] <bjf> the files themselves are in ~/Desktop just don't show up
[21:30] <bjf> does unity not like files on the desktop ?
[21:30] <bjf> this is oneiric amd64 unity 3D
[21:35] <bjf> the desktop icons seem to come and go, i'm trying to determine the pattern
[21:36] <bjf> if I move the mouse over the icons they appear, if i move away from them they disappear
[22:06] <bjf> bug #870343
[22:06] <ubot2> Launchpad bug 870343 in unity "The icons associated with files copied to the desktop appear and disappear as the mouse moves across the desktop" [Undecided,New] https://launchpad.net/bugs/870343