[01:43] <jbicha> finally managed to get my Unity 3D working for the first time in almost a week, I think clearing ~/.cache was the trick
[01:51] <kenvandine> jbicha, that is weird
[01:51] <jbicha> yeah, too bad I used rm -r and not just mv
[01:52] <jbicha> kenvandine: resurrected your contacts mir
[01:53] <kenvandine> thx!
[02:36] <jbicha> TheMuso: are you around?
[03:01] <RAOF> jbicha: Luke tells me that the answer is “no” :)
[03:02] <RAOF> Apparently Telstra's decided that it doesn't want to provide internet, even from a mobile.
[03:19] <jbicha> oh ok, I was just looking for someone interested in uploading vte3
[03:20] <TheMuso> Ok I have limited connectivity now.
[03:21] <TheMuso> jbicha: I am around now.
[05:11] <pitti> Good morning
[05:12] <pitti> chrisccoulson: awesome!
[05:12] <pitti> chrisccoulson: does the same apply to Tbird as well?
[05:21] <pitti> dobey: bug 939173 - looks like sso-client is now trying to use qt?
[05:21] <ubot2`> Launchpad bug 939173 in ubuntu-sso-client "ubuntu-sso-login crashed with ImportError in start_setup(): No module named qt" [High,Confirmed] https://launchpad.net/bugs/939173
[05:21] <pitti> I thought that only affected the control center
[05:27] <jasoncwarner_> DBO thumper hey guys... this bug here: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/936818 ROAF saw this same thing on Intel, I saw it on nvidia...looks like it isn't just nvidia driver thing... any other thoughts?
[05:27] <ubot2`> Launchpad bug 936818 in compiz "Visual Corruption on Desktop" [High,New]
[05:30] <TheMuso> jasoncwarner_: Good afternoon... Hope you weren't kep offline too long today, and I hope you didn't miss anything important. :)
[05:31] <jasoncwarner_> TheMuso: telstra down? I ended up tethering for a bit today...wondered what was up
[05:31] <TheMuso> jasoncwarner_: So you are not on Telstra for mobile? Yes, down so badly that it took out a large chunk of internet usage around the country.
[05:32] <jasoncwarner_> TheMuso: I am on telstra mobile...weird...
[05:32] <jasoncwarner_> I'm back up now with both....how long were you down?
[05:33] <TheMuso> jasoncwarner_: About 40 minutes or there abouts, couldn't even get a connectin on my mobile... Adn the closest place where I could have used wifi was using Telstra also...
[05:41] <thumper> jasoncwarner_: I wish we had more info on it
[05:42] <jasoncwarner_> thumper: I think we were hoping ti was driver related, but clearly not anymore. So probably somewhere in nux/unity/compiz? (manager steps out now ;) ) DBO mentioned something about FBO but I'll let him speak to that.
[05:42] <thumper> jasoncwarner_: is it exactly the same behaviour?
[05:42] <thumper> I'm on intel and not seen any corruption
[05:43]  * thumper goes to make dinner
[05:43] <jasoncwarner_> thumper: RAOF says it even has the same black defect in the white bar...so I would say yeah, close enough for government work
[05:43] <thumper> bbl
[05:43] <thumper> :)
[05:44] <RAOF> thumper: I've seen it exactly once - yesterday.  It went away with a restart.  I've not seen it before or since.  It does look very much like that effect, though.
[07:13] <didrocks> good morning
[07:13] <pitti> bonjour didrocks
[07:14] <rickspencer3> good morning pitti, didrocks, jasoncwarner_
[07:14] <pitti> hey rickspencer3 q
[07:14] <didrocks> hey pitti, rickspencer3
[07:15] <rickspencer3> hey pitti, sure, shoot
[07:15] <jasoncwarner_> hey rickspencer3
[07:15] <didrocks> good morning jasoncwarner_
[07:15] <jasoncwarner_> morning didrocks
[07:16] <jasoncwarner_> didrocks: hey, you get my emails (don't you love waking up to me in your inbox? )
[07:17] <didrocks> jasoncwarner_: one sec, just connecting and already 3 PM :/
[07:21] <didrocks> jasoncwarner_: so, on bug #926859
[07:21] <ubot2`> Launchpad bug 926859 in nux "llvmpipe software rendering needs blacklisting in unity-support-test" [High,Triaged] https://launchpad.net/bugs/926859
[07:21] <didrocks> jasoncwarner_: I can do it
[07:23] <didrocks> jasoncwarner_: for bug #936818, I added the tag
[07:23] <ubot2`> Launchpad bug 936818 in compiz-core "Visual Corruption on Desktop" [High,Fix committed] https://launchpad.net/bugs/936818
[07:23] <didrocks> jasoncwarner_: I can add it to the spreadsheet in a new section for the priority
[07:24] <jasoncwarner_> thanks, didrocks !
[07:25] <didrocks> yw :)
[07:27] <bschaefer> didrocks, hey
[07:28] <bschaefer> didrocks, I was just merging the new ibus support code into unity, and it cant found 'ibus-1.0'
[07:29] <didrocks> good morning bschaefer
[07:29] <bschaefer> didrocks, I thought "libibus-1.0-dev" had been added
[07:29] <didrocks> bschaefer: nux or unity?
[07:29] <bschaefer> they both need it
[07:29] <didrocks> for the "it"
[07:29] <didrocks> ah
[07:29] <didrocks> jay told me only nux will need it
[07:29] <bschaefer> https://code.launchpad.net/~unity-team/unity/unity.text-entry-im/+merge/94305
[07:29] <didrocks> and that the API isn't leaked
[07:29] <didrocks> in unity
[07:30] <bschaefer> hmm well unity will need it until we redo TextEntry using the pimpl idiom
[07:31] <didrocks> bschaefer: it shouldn't work like that then
[07:31] <didrocks> bschaefer: nux .pc file should require ibus in that case
[07:31] <didrocks> and remove the dep check in unity
[07:31] <didrocks> then, with that, I'll make the nux -dev to ibus -dev
[07:32] <didrocks> I spent 1h to explain that to your team last week :/
[07:32] <bschaefer> didrocks, it didn't seem to get back to me :(
[07:33] <thumper> bschaefer: I'm fixing nux a little
[07:33] <didrocks> bschaefer: no worry, as thumper is making is to no leak, you will need to remove the ibus check on unity and be done once nux is merged
[07:34] <bschaefer> didrocks, right now the TextEntry.h is including the ibus.h which is why the dep check was there for unity
[07:34] <didrocks> it*
[07:34] <bschaefer> didrocks, the nux part just merged a little bit ago
[07:35] <didrocks> bschaefer: TextEntry.h is part of nux, isn't it?
[07:35] <bschaefer> didrocks, yeah
[07:35] <didrocks> bschaefer: so yeah, it's not how you do it in that case
[07:35] <didrocks> (if thumper wasn't fixing the leak)
[07:35] <didrocks> what you do in that case, is:
[07:35] <didrocks> your nux.pc file is requiring ibus-1.0
[07:36] <bschaefer> yes
[07:36] <didrocks> then, seeing that, the nux-dev package will dep on the ibus-dev package
[07:36] <didrocks> so, when you include nux from unity
[07:36] <didrocks> you don't need to check for ibus
[07:36] <bschaefer> hmm I thought I had tried that, then it complained about no ibus.h found
[07:36] <didrocks> as the nux.pc check will make unity checking for ibus.pc
[07:37] <didrocks> bschaefer: it's how it works for all FLOSS project, so you probably did something wrong :
[07:37] <didrocks> :)
[07:37] <bschaefer> didrocks, most likely ;)
[07:37] <didrocks> but yeah, the reason here is "there is no magical reason unity dev should read the nux .h files to know that a dep is missing" ;)
[07:37] <didrocks> so Tim is fixing the leak, you don't need to do that
[07:38] <bschaefer> didrocks, it is still good to learn!
[07:38] <didrocks> you can push an additional revision that removes the ibus check in unity though
[07:38] <didrocks> bschaefer: yeah, it's pretty simple once you know it :)
[07:40] <bschaefer> didrocks, thanks!
[07:40] <bschaefer> thumper, thank you too, for being up and working still
[08:31] <chrisccoulson> good morning everyone
[08:33] <bryceh> chrisccoulson, g'day
[08:33] <chrisccoulson> hi bryceh, how are you?
[08:33] <bryceh> chrisccoulson, good, you?
[08:34] <chrisccoulson> bryceh, yeah, not too bad thanks. i feel like this week has been much more productive than last :)
[08:35] <bryceh> good, yeah been crazy amounts of bugs here on the X side, but got through a ton
[08:43] <chrisccoulson> pitti - when does the freeze come in to effect?
[08:43] <pitti> chrisccoulson: I think today at 2100 UTC
[08:44] <kenvandine> the last mad dash :)
[08:44] <chrisccoulson> pitti - ah, cool. thanks. i've got new builds of firefox and thunderbird, but i'm trying to hold out until i've got mozilla approval for making the changes for hyphenation
[08:44] <chrisccoulson> and i don't want to do 2 uploads :)
[08:58] <seb128> hey
[08:59] <pitti> bonjour seb128
[08:59] <seb128> hey pitti, wie gehts?
[08:59] <pitti> gut, danke!
[09:00] <seb128> kenvandine, go to bed!
[09:01] <kenvandine> seb128, soon:)
[09:01] <seb128> it's not a proper hour to upload video lenses :p
[09:01] <seb128> or anything else ;-)
[09:01] <kenvandine> seb128, damn your quick :)
[09:01] <seb128> kenvandine, tb is efficient
[09:01]  * kenvandine ignores that
[09:01] <seb128> kenvandine, joke aside I was just opening my mailed and looking at -changes, good timing ;-)
[09:01]  * kenvandine also really dislikes evolution now too
[09:05] <jasoncwarner_> wow kenvandine me thinks you should be sleeping
[09:05] <didrocks> salut seb128
[09:05] <kenvandine> jasoncwarner_, i did tell you i was going to be like an hour ago :)
[09:05] <seb128> lut didrocks, ca va
[09:05] <seb128> hey jasoncwarner_
[09:05] <kenvandine> i had two more things to finish... done now though
[09:05]  * jasoncwarner_ notes how often I see someone saying "good night" and "good morning"
[09:06] <jasoncwarner_> kenvandine: ah...well, get to sleep ;)
[09:06] <kenvandine> video lens updated, time to crash :)
[09:06] <kenvandine> see you guys in a couple hours!
[09:06] <seb128> kenvandine, 'night
[09:07] <didrocks> seb128: ça va, le rush dès la première minute, mais ça va :)
[09:08] <bryceh> jasoncwarner_, good night.  And good morning!
[09:08] <seb128> didrocks, there is a reason I don't start my IRC first thing in the morning ;-)
[09:08] <jasoncwarner_> bryceh: seriously! you too!
[09:08] <didrocks> seb128: yeah, I tried to get that too, but was trapped this morning :)
[09:09] <seb128> didrocks, ;-)
[09:09] <chrisccoulson> wow, it's busy in here this morning
[09:09] <seb128> that happens even to the bests!
[09:09] <seb128> chrisccoulson, hey, how are you?
[09:10] <chrisccoulson> seb128, yeah, pretty good thanks. and you?
[09:10] <seb128> chrisccoulson, smashed a plug first thing this morning? ;-)
[09:10] <seb128> I'm good thanks
[09:10] <chrisccoulson> seb128, oh, not this morning. my foot is still throbbing though
[09:10] <chrisccoulson> and i still have a hole in my toe :(
[09:10] <seb128> :-(
[09:12] <pitti> chrisccoulson: the doctor didn't stitch the toe together?
[09:13] <chrisccoulson> pitti - oh, i've not been to see a doctor. they wouldn't do that anyway, they'd just send me to an A+E department
[09:13] <chrisccoulson> i'm sure it'll heal :)
[09:13] <pitti> uh?
[09:14] <bryceh> A+E?
[09:14] <pitti> aren't you worried about infections?
[09:14] <chrisccoulson> heh, i hadn't thought of that ;)
[09:16] <bryceh> chrisccoulson, what happened?
[09:16] <chrisccoulson> bryceh, i stepped on to the pins of an electrical plug on the floor, when i got out of bed a couple of mornings ago
[09:16] <chrisccoulson> and one of them penetrated my foot ;)
[09:16] <chrisccoulson> but i also broke the plug
[09:17] <bryceh> ah, ouch.  yeah, tetanus shot time
[09:22] <bryceh> sorry, didn't mean to kill the conversation, so to speak.
[09:25] <pitti> bryceh: I hope he's running head over heels to a doctor!
[09:26] <bryceh> indeed!
[09:29] <seb128> lol
[09:30] <seb128> not sure a doctor would do much for a cut
[09:31] <seb128> you can clean that with antiseptics yourself
[09:31] <seb128> well I guess different people have different habits, I would probably not run to a doctor either for that ;-)
[09:33] <bryceh> seb128, suppose it matters how deep it is
[09:33] <pitti> I probably would when I coudl see my foot's inside from a larger hole
[09:33] <pitti> and GB power plugs are insanely big
[09:33] <bryceh> seb128, still throbbing after 3-4 days might suggest infection
[09:34] <pitti> /join #ubuntu-doctors
[09:34] <seb128> well it matters if they need to close it and clean it in a better way yeah
[09:34] <seb128> pitti, or -> move to actual work :p
[09:34] <seb128> pitti, thanks again for the help on updates btw
[09:34] <pitti> seb128: I am currently uploading 821 packages; how many do you? :-)
[09:35] <seb128> pitti, I'm not going to pick that gauntlet
[09:35] <seb128> ;-)
[09:35]  * pitti hugs seb128, my pleasure
[09:35]  * seb128 hugs pitti
[09:35] <seb128> damn
[09:35] <seb128> you are 1 bug ahead again
[09:35] <pitti> hehe
[09:35] <pitti> go, seb128, go!
[09:35] <seb128> ;-)
[09:35] <didrocks> I know why seb128 wanted to do the GNOME's update completly himself :)
[09:35] <pitti> my goal was to break the 200 mark this cycle
[09:36] <pitti> that would be a new personal record
[09:36] <pitti> I know, didrocks can only laugh at trivial numbers like this
[09:36]  * didrocks has an army to work for him :)
[09:36] <seb128> oh, nice, Debian updated libgphoto2 yesterday, I just wanted to do that myself
[09:37] <seb128> didrocks, in fact I think pitti scored more bug closing from that GNOME update round than me :p
[09:37] <pitti> didrocks: and yet the hud keeps popping up when I don't want it :)
[09:37] <seb128> but it's only fair from the stack of updates he did ;-)
[09:37] <pitti> seb128: oh? I think it was about 5 or so
[09:37] <didrocks> seb128: damn! :)
[09:37] <didrocks> pitti: yeah, I just want to have enough people opening duplicate
[09:38] <didrocks> and closing them all, so that I can +100 on the bug number
[09:38] <seb128> pitti, yeah, I think I got between 3 and 5, g-c-c and g-s-d took me a whole afternoon to rebase and clean our patches and closed 1 bug we had

[09:38] <didrocks> pitti: more seriously, this is a compiz and unity patch, it's #1 on the priority list
[09:38] <pitti> didrocks: yes, I know; I was just kidding you
[09:38] <didrocks> https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuMtju1x8UoEdDNCT1U5MlVodjIwNGJPdnU5YVltVmc#gid=1
[09:38] <didrocks> see, it's #1, no kidding :)
[09:39] <pitti> didrocks: I guess the real scope of the bug is larger than just alt+f4
[09:39] <seb128> pitti, btw the 200 mark is a joke, you should aim for 300 seeing where we stand with stil like 5 weeks of bug fixing
[09:39] <seb128> we can do it!
[09:39] <didrocks> pitti: yeah, I just didn't change the bug title
[09:39] <seb128> ;-)
[09:39] <pitti> seb128: well, I never got to 200 before, so this was my goal at the start of the cycle
[09:39] <didrocks> pitti: it's basically if you key + something, compiz please please please ignore "key" tap
[09:40] <didrocks> seb128: so, I think we don't need the metacity update, there is the gsettings stuff we don't want and the other fixes are not relevant IMHO
[09:40] <pitti> yes, I often get it with switching workspaces or terminal tabs
[09:40] <seb128> didrocks, ok
[09:40] <didrocks> pitti: so switching ws on the way to change to Shift + Super + arrows
[09:40] <seb128> didrocks, what about the lim merge request from sam, does that needs to land before lim in compiz?
[09:40] <didrocks> seb128: no, both are independant from what I was told
[09:40] <didrocks> it will just be deactivated
[09:41] <pitti> didrocks: sorry, shift+super+something will break my hand
[09:41] <seb128> didrocks, well, for feature parity for 2d I guess we will need to land it?
[09:41] <pitti> didrocks: ctrl+alt is very convenient (keys are next to each other)
[09:41] <didrocks> pitti: agreed, and moving a window will be Super + alt + arrows
[09:41] <seb128> didrocks, is lim planed to land before beta1 still?
[09:41] <didrocks> seb128: no, see the desktop meeting, no release before beta1 :)
[09:41] <bryceh> didrocks, heya good morning!
[09:41] <didrocks> seb128: yeah, they will land at the same time, hopefully (still need work on the 2d side)
[09:42] <didrocks> hey bryceh
[09:42] <didrocks> bryceh: good morn… night! :)
[09:42] <bryceh> didrocks, are you aware of bugs 933322 / 931967?
[09:42] <ubot2`> Launchpad bug 933322 in xserver-xorg-video-ati "LightDM graphic corruption with ati and nvidia" [Undecided,Confirmed] https://launchpad.net/bugs/933322
[09:42] <didrocks> lightdm? :)
[09:43] <didrocks> I don't really work on it, but looking :)
[09:43] <bryceh> didrocks, possibly they're dupes, we're not sure yet.  We *think* they're not unity bugs but not 100% certain.  Also think they're not X or driver bugs, but not 100% certain.  And we're not 100% certain they're lightdm either but that's the best guess so far.
[09:43] <seb128> bryceh, btw, I "like" how you put that wacom g-s-d bug that 1 user with specific hardware ran into on the wiki meeting page and didn't mention any of the xserver bug ten of unity users are running into ;-)
[09:44] <bryceh> can't repro on -intel
[09:44] <seb128> in the "Notable bugs this week:"
[09:44] <seb128> bryceh, I've nothing against being finger pointed for stuff we broke but I think that summary is not fair
[09:44] <bryceh> seb128, yes but were any of those ten of unity users Pete Graner? ;-)
[09:44] <seb128> heh ;-)
[09:45] <didrocks> bryceh: it doesn't seem to be particularly linked to unity as people reports the same in GS, isn't it?
[09:45] <bryceh> seb128, anyway, certainly wasn't trying to point fingers, sorry if it came off that way!  :-(
[09:45] <seb128> bryceh, well I would rank xorg segfault and closing your session several times a time over "g-s-d doesn't start when a specific wacom device is plugged leading to a weird looking but working desktop"
[09:45] <seb128> several times a "day"
[09:46] <seb128> bryceh, no worry, I just think you overranked that wacom issue to be fair, putting it at the top of the weeky is a bit much, it has bitten 1 user and it doesn't break the session just g-s-c
[09:46] <seb128> g-s-d
[09:47] <bryceh> didrocks, right, and I can reproduce the one on -ati logging into gnome classic (no effects) which is why I'm doubting unity.  But kinda running out of ideas so am seeing if anyone has more clue than I on it.
[09:47] <seb128> (anyway, moving on)
[09:47] <bryceh> seb128, sorry it upset you!
[09:48] <didrocks> bryceh: hum, I don't have any ATI around, but gnome classic (no effects) have compisoted enabled, maybe try metacity without any compositing?
[09:48] <seb128> bryceh, oh it doesn't upset me, I just think it has been overanked over other issues, I've a list of bug that collect dups every day though :-(
[09:49] <seb128> bryceh, sorry for complaining, I got back to work (I just noticed that it was on the wiki because didrocks pointed to the page for the "no local menu in beta" info)
[09:49] <bryceh> seb128, to be honest at the time I added it, a couple people had asked about it, and at the time it sounded fairly bad.  But mainly I was just penciling it in hoping you'd notice and follow up on it.
[09:49] <seb128> bryceh, yeah, fair enough, and thanks for making sure it got raised ;-)
[09:49] <bryceh> seb128, also I guess I was thinking maybe the status report would be a good way to track bugs that are known issues but that we're not going to fix ASAP, that non-desktop people might run into
[09:50] <seb128> upstream is looking at it
[09:50] <bryceh> but maybe that's not such a great idea, I dunno
[09:50] <bryceh> I'm certainly full of many not so great ideas
[09:50] <seb128> bryceh, well, I think it's a good idea, but I would think the synaptic, xorg and mesa issue are fairly common and should be there as well then ;-)
[09:50] <bryceh> didrocks, oh I assumed "no effects" implies no compositing?
[09:51] <bryceh> seb128, right  totally agreed, those are well worth adding
[09:51] <didrocks> bryceh: I guess there are some, need to check on gconf, not 100% sure
[09:51] <bryceh> actually, wait, I know the synaptic and mesa issues, what's the xorg issue?
[09:52] <seb128> bryceh, the WriteToClient thing
[09:53] <seb128> bryceh, but I didn't follow much, just read the discussion with the dx guys the other day
[09:53] <bryceh> ah right, that actually turned out to be nvidia 295.10 specific and is already fixed
[09:54] <seb128> oh, good news ;-)
[09:55] <seb128> bryceh, well anyway sorry if that seemed ranting, I find weird to find 2 GNOME bugs there and nobody's else bugs, it filled like a bit people were finger pointing on others issue but not listing theirs ;-)
[09:55] <seb128> filled->felt
[09:56] <bryceh> seb128, really the only reason I listed those two was because they were originally reported against X as X bugs, and they ended up not X bugs but sounded like a lot of people would hit them.  I'll continue listing such bugs but will also try to remember to list the currently hitting X-and-really-is-X bugs as well.  Guess I overlook those since I'm actively working on them.  Would love it if you did similarly on the gnome
[09:56] <bryceh> side.
[09:56] <bryceh> seb128, also you may have better insight into X bugs that people are hitting a lot, so don't be shy about flagging them if you think they're getting hit a lot.  That'll actually help me and chris focus on solving them.
[09:57] <seb128> bryceh, yeah, I like the "list known issue" idea, maybe having a separate section for those would be better though
[10:05] <czajkowski> good morning people :)
[10:05] <pitti> hey czajkowski, how are you?
[10:05] <czajkowski> good thanks getting into this workign from home lark
[10:05] <czajkowski> :)
[10:05] <pitti> you didn't before?
[10:05] <czajkowski> nope never
[10:06] <seb128> hey czajkowski
[10:07] <didrocks> pitti: if you have some minutes, can you please cheat with those build priority: https://launchpad.net/~ubuntu-desktop/+archive/ppa/+packages -> compiz, c-p-m, metacity ?
[10:09] <pitti> didrocks: done
[10:09] <didrocks> pitti: thanks a lot, and sorry to bother you :)
[10:09] <pitti> didrocks: no worries
[10:13] <bryceh> seb128, alright here you go, my quick brain dump - https://wiki.ubuntu.com/DesktopTeam/Meeting/2012-02-28
[10:14] <seb128> bryceh, thanks, will try to do something similar to desktop as well
[10:14] <seb128> bryceh, you put it in "agenda" btw, maybe add a "known issues" section?
[10:16] <bryceh> seb128, feel free to edit
[10:16] <seb128> right, it's a wiki !
[10:16] <seb128> ;-)
[10:17] <bryceh> RAOF, ^^ if I missed any X bugs worth mentioning, please add
[10:30] <ogra_> hmm, with the most recent update all fonts in my panel (unity-2d) got a colour blur around them .... and my notification bg color seems to be a dark green
[10:35] <bryceh> ogra_, I haven't heard of that bug.  Might be something unity2d related.  Check your /var/log/dpkg.log and downgrade as makes sense until you find the faulty component.
[10:36] <ogra_> note that i'm on arm ... and use a tegra2 driver ... i guess i should first disable that bit and see if its the driver
[10:36] <ogra_> i would have guessed for a Qt issue, but that wouldnt explain the green notification bubbles (which look really weird btw)
[10:37] <Sweetshark> pitti: yeha! all reportbuilder deps seem to be there now! MIR galore, brace for impact.
[10:37] <pitti> Sweetshark: yes, I poked them last night/this morning
[10:37] <pitti> Sweetshark: note that most of them were in main before and thus don't need a MIR
[10:38] <pitti> Sweetshark: we only need the libexttextcat thingy you already filied
[10:38] <pitti> Sweetshark: is this related in any way to libtextcat (which is already in main)?
[10:39] <pitti> sorry, it's in universe
[10:39] <pitti> but was in main in natty/oneriric
[10:41] <Sweetshark> there are a ot left for MIR
[10:41] <Sweetshark> if we would upload again today (just for MIRs and reportbuilder) would that abort the running arm builds?
[10:42] <pitti> no, builds are never aborted
[10:42] <pitti> but their builds might fail to upload
[10:42] <pitti> due to the obsolete version
[10:42] <pitti> so I'd rather wait until armhf has built
[10:43] <Sweetshark> yes.
[10:43] <pitti> Sweetshark: does https://launchpad.net/ubuntu/+source/libreoffice/1:3.5.0-1ubuntu2/+build/3230659 provide any indication how far it is?
[10:44] <Sweetshark> pitti: its in sd (star draw=impress, thats rather far up the build)
[10:45] <Sweetshark> but sd/sw (writer)/sc (calc) are the major beasts, so they are still to be done.
[10:46] <Sweetshark> sw alone is ~1/12 of compile time ...
[10:47] <Sweetshark> pitti: is there any way to find out how big the buildlog is on the buildd by now?
[10:47] <pitti> not with mere layman powers
[10:52] <Sweetshark> comparing it to the amd64 log and filtering for compiles, it is roughly at 88% (assuming that the ARM make used the same build order, which it does not have to, but likely does)
[10:53] <Sweetshark> OTOH the sw/sd/sc compiles will take longer because they have bazillion of includes.
[10:53] <Sweetshark> the only way to be sure is once it is finished, we have a log and a total time to comare against.
[10:54] <Sweetshark> :/
[11:39] <didrocks> again, xorg crashing on toomanywrite :/
[11:56] <bryceh> didrocks, ??
[12:06] <didrocks> bryceh: I'm getting the issue since oneiric: when there are too many write on my disk, X crashes
[12:17] <bryceh> didrocks, install my https://launchpad.net/~ubuntu-x-swat/+archive/mesa-8.0.1
[12:17] <didrocks> bryceh: mesa? I have a nvidia card
[12:17] <bryceh> hrm
[12:18] <bryceh> didrocks, 295.20?
[12:18] <didrocks> bryceh: yeah, I got it since oneiric
[12:18] <didrocks> and I'm on the latest
[12:19] <bryceh> odd, dunno.  Filed bug#?
[12:19]  * bryceh EOD + Bed.  g'nite.
[12:20] <pitti> bryceh: sleep well!
[12:20] <didrocks> I think I filed more than once, but can file another one with latest crash :)
[12:28] <ogra_> didrocks, soo ... we need to talk, i got an overview about the gles stuff yesterday ....
[12:28] <ogra_> didrocks, seemingly what linaro produced will be an 1.9MB patch file .... plus 4-500k for compiz-plugins-main
[12:29] <didrocks> ogra_: ok, does it follow the requirement from the email thread?
[12:30] <ogra_> what thread exactly ? (i have like ten open for that topic)
[12:30] <didrocks> same here, and I have 2 people pinging me everyday about it :/
[12:30] <didrocks> it's so confusing
[12:30] <ogra_> i dont think it ships tests etc
[12:30] <didrocks> and I lost so much time on it
[12:31] <ogra_> who pinged you ?
[12:31] <didrocks> jay, david…
[12:31] <ogra_> it should all be run over my table
[12:31] <ogra_> hmm
[12:31] <didrocks> so, the patch which don't ship tests
[12:31] <didrocks> they are in #define armel?
[12:31] <didrocks> #ifdef sorry
[12:31] <ogra_> anyway, i dont think 1.9M is acceptable, but i also dont want to lose the work that was been done over thelast months
[12:32] <didrocks> what's your proposal then?
[12:32] <ogra_> no, thats the compiz part, its a patch that should only be applied if DEB_BUILS_HOST is arm
[12:32] <ogra_> during package build
[12:32] <didrocks> ok, some people come back telling it was finally on #ifdef
[12:32] <ogra_> well, seems they *can* clean it up, they just didnt have the time yet
[12:32]  * didrocks *sigh*
[12:33] <ogra_> the end result should be more like 500k or so
[12:33] <didrocks> ok, and that's the compiz part only applied on armel build, isn't it?
[12:34] <ogra_> the question is, regarding the beta, should we apply it now and wait for getting it updated until release or should we wait for the cleaned up patch and ask for freeze exceptions etc
[12:34] <ogra_> right, that was the plan
[12:34] <ogra_> but it will make your diff-gz horrid for a while if we apply it now ...
[12:34] <didrocks> bryceh: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/939470 when you wake up and it's retraced
[12:34] <ubot2`> didrocks: Error: <Bugtracker.plugin.Launchpad instance at 0xa5ae8cc> bug 939470 not found
[12:34] <ogra_> and indeed it would need your agreement (as well as skaet's)
[12:35] <didrocks> ogra_: well, anyway, there is a FFe request to do, do you have any ETA for them to make the patch cleaned up?
[12:35] <ogra_> they promised me "before release"
[12:35] <ogra_> with me pushing for asap indeed
[12:35] <didrocks> well, "before release" it really vague
[12:35] <didrocks> you can open a FFe
[12:36] <ogra_> alf should be able to give a very rough ETA
[12:36] <didrocks> and discuss with the release team when it's the last dadte
[12:36] <didrocks> date*
[12:36] <ogra_> k
[12:36] <didrocks> ogra_: also, I want to be clear
[12:36] <ogra_> will do (first talking to kate though)
[12:36] <didrocks> if compiz is FTBFS on armel, that won't prevent me to pushing a compiz fix
[12:36] <ogra_> right
[12:36] <didrocks> then, they will have to fix their patch promptly
[12:36] <didrocks> if not done and the armel image is broken for few days
[12:37] <ogra_> just ignore it and blame me or linaro (cant blame ubuntu-arm anymore, it dissolved)
[12:37] <didrocks> I'll revert the patch to make the armel image working
[12:37] <didrocks> ogra_: heh, blaming you? with pleasure :)
[12:37]  * didrocks hugs ogra_
[12:37]  * ogra_ hugs didrocks 
[12:37] <didrocks> ok, seems we are in agreement then :)
[12:37] <didrocks> hope that will lift the confusion on all those threads!
[12:37] <ogra_> right, let me try to catch kate first though
[12:37] <didrocks> yeah, keep me posted
[12:37] <ogra_> yeah, i dislike doing it by mail at all
[12:38] <didrocks> +1
[12:38] <ogra_> we should just have quick ad-hoc IRC meetings so everyone is in the loop and can react immediately
[12:38] <didrocks> agreed, once you discussed it with kate, maybe you can arrange that?
[12:38] <ogra_> but seems thats not how linaro works :)
[12:38] <ogra_> i will try
[12:39] <didrocks> sweet :)
[12:41] <alf> ogra_: didrocks: Keep in mind that, as I mentioned yesterday, even the cleaned up patch is estimated around 400KB for compiz-core and around 300K for compiz-plugins-main
[12:41] <ogra_> yes, buts thats a lot smalled than x.xMB
[12:41] <ogra_> :)
[12:41] <didrocks> yeah :)
[13:00] <Riddell> I'm the beta tech release manager
[13:00] <Riddell> Sweetshark: libreoffice here needs looked into toot sweet
[13:01] <Riddell> hmm, no robert, if anyone sees him tell him the lighdm needs cleaned up there
[13:03] <seb128> Riddell, what is the issue with lightdm?
[13:04] <Riddell> oh sorry, forgot link
[13:04] <Riddell> http://people.canonical.com/~ubuntu-archive/nbs.html
[13:04] <Riddell> NBS is all
[13:04] <seb128> Riddell, no lightdm there
[13:04] <Riddell> seb128: "lightdm-gtk-greeter"
[13:04] <seb128> Riddell, lightdm-gtk-greeter is a standalone source now that needs to be taken care of by the derivatives that need it
[13:05] <seb128> robert_ancell said several time he wrote it as a demo greeter and has no intention to spend efforts on it
[13:05] <seb128> that's why he made a different project,source for it this cycle
[13:05] <Riddell> seb128: that's fine.  I'll just delete it then
[13:05] <seb128> so somebody from xubuntu,lubuntu,ubuntustudio needs to step up
[13:06] <seb128> Riddell, it's the default greeter for several derivatives
[13:06] <seb128> talk to them maye
[13:06] <seb128> talk to them maybe
[13:13] <Sweetshark> Riddell: hmm?
[13:14] <Riddell> Sweetshark: http://people.canonical.com/~ubuntu-archive/nbs.html
[13:15] <Sweetshark> Riddell: hmm, yes.
[13:17] <Sweetshark> reportbuilder needed a few MIRs so we did not build it yet. The stuff is now synced an ready, but the currently building LO package doesnt yet contain it.
[13:17] <seb128> Riddell, well you can't delete "it" in fact, the issue is that the gtk greeter got moved to a new source and nobody packaged the new source, so the derivates depends on a nbs package, if you delete the binaries you just made the derivates uninstallable it doesn't solve the issue
[13:17] <Sweetshark> pitti: opinion about the reportbuilder issue?
[13:18] <Riddell> seb128: ok thanks
[13:18] <Riddell> Sweetshark: will you be ready in time for beta freeze (8 hours)?
[13:19] <Sweetshark> ready in sense of 'fixed package uploaded' or in the sense of 'package finished building on ARM'?
[13:20] <Sweetshark> 1) yes (but then either MIRs would need to pass quickly) 2) no, no matter what I do, building on ARM takes way longer than 8 hours.
[13:20] <Riddell> 1) is fine
[13:21] <Riddell> poke mterry if you need MIRs
[13:21] <mterry> At this point, MIRs likely need FFes too
[13:22] <mterry> Oh, reading scroll back, this is a moved package?  Probably doesn't need an FFe then, but I don't have the whole conversation
[13:22] <Sweetshark> mterry: some more tasty MIRs: bug 938582, bug 938708, bug 938709, bug 938712
[13:23] <ubot2`> Launchpad bug 938582 in libexttextcat "[MIR] libexttextcat" [Undecided,New] https://launchpad.net/bugs/938582
[13:23] <ubot2`> Launchpad bug 938708 in lucene2 "[MIR] lucene2" [Undecided,New] https://launchpad.net/bugs/938708
[13:23] <ubot2`> Launchpad bug 938709 in libcmis "[MIR] libcmis" [Undecided,New] https://launchpad.net/bugs/938709
[13:23] <ubot2`> Launchpad bug 938712 in sampleicc "[MIR] sampleicc" [Undecided,New] https://launchpad.net/bugs/938712
[13:23] <Sweetshark> mterry: all those are a) in universe b) have already compiled in main as part of libreoffice before
[13:24] <mterry> Sweetshark, noted.  I have some UIF stuff to do, but will get to that after
[13:24] <Sweetshark> mterry: (they would just get properly get split out of the LO package into a separate one)
[13:27] <Sweetshark> Riddell: local build with reportbuilder just finished. Alas uploading now would mean that the currently building ARM packages do not get NEW'ed again :(
[13:28] <Riddell> as you wish, freezer is in 8 hours
[13:28] <Riddell> I'm able to do new on request
[13:28] <seb128> mterry, hey
[13:28] <seb128> mterry, how are you?
[13:28] <Sweetshark> mterry: thx
[13:28] <seb128> mterry, did you talk to robert_ancell about getting an unity-greeter update out today?
[13:28] <mterry> seb128, good.  About to push out a couple exciting unity-greeter changes
[13:29] <mterry> seb128, I said that if he didn't do it, I would today.  So I'm about to
[13:29] <seb128> mterry, cool
[13:29] <pitti> seb128, Riddell: I contacted xubuntu etc. leads, they are preparing the new lightdm greeter source package
[13:29] <seb128> mterry, great work on the greeter this cycle, lot of good comments around ;-)
[13:29] <seb128> pitti, great, thanks!
[13:29] <mterry> seb128, yay :)
[13:29] <mterry> pitti, did you do the revamp of the apport dialog?  Looks nice
[13:30] <pitti> mterry: that was ev
[13:30] <pitti> according to specs from mpt
[13:30] <mterry> pitti, ack, redirected my compliment then  :)
[13:35] <Sweetshark> pitti, Riddell: who wants to upload libreoffice MIR-galore-edition?
[13:35] <pitti> Sweetshark: "upload"?
[13:35] <pitti> Sweetshark: oh, a new package; sure; did it finish building on armhf?
[13:36] <Sweetshark> pitti: nope
[13:36] <Sweetshark> pitti: it did neither finish nor fail
[13:36] <Sweetshark> pitti: halting problem ftw
[13:37] <Sweetshark> pitti: but Riddell found we have a dep on reportbuilder from the libreoffice metapackage but no reportbuilder package build.
[13:38] <pitti> Sweetshark: yes, it's NBS
[13:38] <pitti> http://people.canonical.com/~ubuntu-archive/nbs.html
[13:38] <pitti> that's why I asked you about that a few days ago
[13:39] <pitti> Sweetshark: but it's "only" NBS, so it's not so urgent to fix that we should risk more armhf delays
[13:39] <pitti> because that, unlike the NBS, causes serious trouble
[13:39] <pitti> Sweetshark: http://people.canonical.com/~ubuntu-archive/testing/precise_probs.html
[13:39] <pitti> we need to fix those for beta-1
[13:40] <Sweetshark> pitti, Riddell: Fight!
[13:40] <pitti> much of it is buildd lag etc, but yesterday there were 111 uninstallables, and _all_ were due to libo
[13:41] <pitti> not sure what all the other stuff is all about, perhaps we just got a new Qt which just finished building on armhf or so
[13:41] <Sweetshark> I have a 3.5.0-1ubuntu3 package ready here building reportbuilder and having pulling in all the MIR deps. I dont mind waiting for after the beta with that ...
[13:41] <pitti> oh, that woudl be mesa
[13:41] <Riddell> pitti: mm, I'll put that page on the BetaProccess list
[13:42] <pitti> seems mesa didn't have an armhf build, I pinged tjaalton
[13:44] <pitti> nevermind, it's due to the wayland upload apparently
[13:46] <didrocks> seb128: g-c-c trunk is all yours now :)
[13:46] <seb128> didrocks, thanks!
[13:46] <Sweetshark> pitti, Riddell: would it make sense to do a 3.5.0-1ubuntu3 upload with reportbuilder and the MIRs if the current ARM build finish in 3-4 hours (before beta-1)?
[13:46] <jbicha> good morning
[13:47] <pitti> Sweetshark: if it builds in two days or so, it sounds ok
[13:47] <Riddell> yes depends if images are needed before it builds
[13:47] <Riddell> but they should be fine for smoketesting on i386/amd64 before we move onto arm
[13:48]  * Sweetshark feels like doing the timewarp again.
[13:49] <pitti> Riddell: I'm just hesitant to upload it now because LibO _never_ built on armhf before, and causing massive uninstalalbility
[13:49] <pitti> we need this built to succeed
[13:49] <nessita> hello everyone! quick question, I've been having the following for weeks now, is it expected or is something wrong in my setup?
[13:49] <nessita> The following packages have been kept back:
[13:49] <nessita>   nvidia-173
[13:49] <pitti> nessita: no, the 173 driver isn't compatible with our current X.org
[13:49] <pitti> you need to use -current
[13:50] <nessita> pitti: thanks!
[13:51] <jbicha> mterry: would you be interested in uploading the new vte3?
[13:52] <mterry> jbicha, I'm a bit busy, but could try to pick it up after my queue is done
[13:52] <Ursinha> pitti, hello!
[13:52] <pitti> Ursinha: o/
[13:53] <Ursinha> pitti, we need someone to look at bug 827615
[13:53] <ubot2`> Launchpad bug 827615 in software-center "software-center crashed with TypeError in show_available_packages(): this constructor takes no arguments" [High,Confirmed] https://launchpad.net/bugs/827615
[13:53] <Ursinha> it's not possible to install deb files by double clicking them
[13:53] <Ursinha> it's a regression
[13:53] <jbicha> seb128: not sure how busy you are today, but I'd like to see libosinfo make it out of the new queue (for gnome-boxes)
[13:53] <pitti> Ursinha: I assigned it to Gary
[13:54] <seb128> jbicha, quite busy, stuff uploaded before the freeze shouldn't need an exception, I guess the r-t guys will clear the queue
[13:54] <seb128> jbicha, but if they don't I will have a look later
[13:54] <Sweetshark> heh. the armhf buildd not plays catchup with the armel one.
[13:54] <seb128> I think new stuff in universe should be fine to clear from the queue tomorrow
[13:54] <seb128> pitti, Riddell: ^ right?
[13:54] <pitti> sure
[13:55] <seb128> thanks
[13:55] <Ursinha> thanks pitti!
[13:55] <Riddell> seb128: as long as it doesn't go against feature freeze
[13:55] <pitti> most of those were uploaded before FF
[13:55] <pitti> new processing is just a bit on the slow side with everyone working on last-minute things, I guess
[13:57] <Riddell> I might tackle New now
[13:57] <mdeslaur> seb128: hi! Do we have any plans on reverting indicator-session? LP: #939518
[13:57] <pitti> jbicha: need sponsoring?
[13:59] <kiwinote> Ursinha: fwiw mvo has already fixed that s-c bug in trunk, so it'll be working in the next s-c release when he's back from vacation
[14:01] <seb128> mdeslaur, I can do that yes
[14:01] <Ursinha> kiwinote, awesome, I'll add a note in the bug
[14:01] <Ursinha> kiwinote, and when is he back? :)
[14:02] <kiwinote> Ursinha: not sure about that ;)
[14:04] <jbicha> pitti: just https://code.launchpad.net/~ubuntu-desktop/vte/ubuntu-vte3
[14:06] <pitti> jbicha: uploaded, thanks!
[14:14] <desrt_> jbicha: hey
[14:14] <desrt> jbicha: any word on the shell?
[14:20] <jbicha> desrt: only thing I was hesitating on was that g-c-c/g-s-d was patched to not support changing Shell's keyboard shortcuts
[14:20] <desrt> jbicha: i talked to seb about that and it seems like it may be reasonable to have g-c-c/g-s-d update both sets of keys
[14:20] <jbicha> right, just waiting until someone does that
[14:20] <desrt> jbicha: and even if not, i don't consider that to be a blocker
[14:20] <jbicha> also, Shell 3.9 now requires clutter 1.9 which is more work
[14:21] <desrt> tricky.
[14:21] <desrt> 3.9?
[14:21] <desrt> 3.3.90?
[14:21] <jbicha> 3.3.90
[14:21] <desrt> right
[14:22] <didrocks> desrt: hey!
[14:23] <desrt> didrocks: hey :)
[14:23] <didrocks> desrt: small question, when a gsetting schema key has a path, anything special need to be done for the override file?
[14:24] <jbicha> so clutter would need a ffe since it's a library transition, but would Shell?
[14:24] <desrt> didrocks: no.
[14:24] <jbicha> I'm a bit confused about yesterday's decision that there are no standing FFe's
[14:24] <desrt> didrocks: gsettings schemas normally have a path...
[14:25] <seb128> jbicha, what decision is that?
[14:25] <didrocks> desrt: hum, ok :) I need to reread the doc about relocatable path then, I was thinking that you provide a path only in that case, but it's been a long time I didn't play with it :)
[14:26] <didrocks> and also, I need to make more test on why g-s-d doesn't want my override :)
[14:26] <didrocks> desrt: thanks!
[14:26] <desrt> didrocks: gsettings overrides are done at the schema level (ie: oblivious to dconf paths)
[14:26] <jbicha> seb128: https://wiki.ubuntu.com/StandingFeatureFreeze?action=diff&rev2=13&rev1=12
[14:26] <desrt> so if you override a default value there, it should apply to all instances of that schema
[14:26] <Sweetshark> pitti: armel is in install
[14:26] <didrocks> desrt: ok, makes sense then! Thanks :)
[14:26] <pitti> Sweetshark: crossing fingers for armhf :)
[14:27] <seb128> jbicha, I will pretend I didn't see that edit :p
[14:27] <seb128> jbicha, joke aside it makes that that things we didn't update yet to a new serie new a ffe
[14:27] <seb128> jbicha, the GNOME exception makes sense because we usually ship unstable .90 and it makes no sense to no go from there to stable
[14:28] <seb128> jbicha, stuff like a new clutter or a new gnome-shell need a ffe
[14:28] <desrt> particularly clutter is... interesting
[14:28] <desrt> there were some fairly substantial changes there that broke things for a while
[14:28] <seb128> yeah, I really want to stay away from that one
[14:28] <seb128> so much change this cycle
[14:28] <desrt> i think it's ironed out now, but....
[14:28] <ricotz> hi, also having cogl break abi and bump soname with every pre-release doesnt help here either ;)
[14:28] <seb128> hey ricotz, right
[14:28] <ricotz> desrt, hi
[14:28] <desrt> rebuild ALL the things!!
[14:29] <ricotz> seb128, hi
[14:29] <desrt> ricotz: hi :)
[14:29] <ricotz> desrt, exactly ;)
[14:29] <seb128> staying on clutter 1.8 spared us lot of efforts
[14:29] <ricotz> cogl will at least one more time bump it
[14:29] <ricotz> to remove/rename all EXP symbols
[14:30] <ricotz> seb128, for now, yes, but i hope there is the option to ship it when cogl is ready
[14:30] <desrt> seb128: gnome-session has a libunity depend.  what's the story there?
[14:31] <seb128> $ apt-cache show gnome-session | grep unity
[14:31] <seb128> Recommends: unity | unity-2d | gnome-shell (>= 3.0)
[14:31] <seb128> Breaks: bug-buddy (<< 2.20), gnome-power-manager (<< 2.28), unity-2d (<< 5.4~), xserver-xorg (<< 1:7.4)
[14:31] <seb128> desrt, ?
[14:31] <seb128> desrt, where?
[14:31] <m4n1sh> didrocks: ping
[14:31] <desrt> hum.
[14:31] <desrt> i tried to remove libunity9 and it said it wanted to take gnome-session with it
[14:31] <Sweetshark> pitti: armhf is in install
[14:31] <desrt> perhaps it's indirect
[14:32] <seb128> desrt, doesn't happen here
[14:32] <seb128> desrt, can you pastebin your log?
[14:32] <desrt> maybe i have a weird ppa gnome-session installed
[14:32] <didrocks> m4n1sh: hey
[14:32] <desrt> i'm in the middle of a dist-upgrade now.  letsee if that fixes it.
[14:32] <m4n1sh> didrocks: upload? or in queue?
[14:32] <didrocks> m4n1sh: in queue of doing next
[14:32] <desrt> nope...
[14:32] <m4n1sh> great
[14:32] <m4n1sh> stupid me. Forgot to add the mail title :)
[14:32] <didrocks> m4n1sh: dude, I'm taking care of more than just activity-log-manager :)
[14:33] <m4n1sh> didrocks: I know that :)
[14:33] <desrt> seb128: http://fpaste.org/EWX8/
[14:33] <didrocks> and not spot, no break since 7am :p
[14:33] <didrocks> stop*
[14:33] <m4n1sh> didrocks: you handle just too many things :)
[14:33] <didrocks> so, let's be patient, it's on my list, it will be done today
[14:33] <m4n1sh> just too many
[14:33] <didrocks> :)
[14:33] <didrocks> as everyone working on ubuntu I guess :)
[14:33]  * m4n1sh shows respect
[14:34] <pitti> dobey: :( http://cdimage.ubuntu.com/daily-live/20120223.1/
[14:34] <pitti> dobey: that's with fresh langpacks, they only saved some 2 MB, and mostly because we currently don't have ubuntu-docs translations
[14:34] <pitti> (but these will come back)
[14:34] <seb128> desrt, hum, dunno
[14:34] <pitti> dobey: so my hunch that squashfs wouldn't actually have duplicate files was right :/
[14:34] <desrt> seb128: gnome-session depends natuilus
[14:34] <desrt> seb128: nautilus depends libunity
[14:35] <pitti> so it seems we have 8 real MBs to chop off
[14:35] <desrt> seb128: i'm surprised it's not the same for you?
[14:35] <pitti> chrisccoulson: ^ tbird and ffox will regain some 5 together?
[14:36] <seb128> desrt, it is in fact, I didn't spot it in the middle of the list here
[14:36] <desrt> cool.  makes sense.
[14:37] <seb128> desrt, that's because gnome-session depends on nautilus
[14:37] <seb128> and nautilus depends on libunity9
[14:37] <desrt> seb128: yes.  as i said.
[14:37]  * desrt puts killing libunity on his todo list
[14:37] <seb128> desrt, right, sorry I was checking and didn't read IRC ;-)
[14:37] <seb128> desrt, good luck
[14:37] <desrt> a lot of the stuff in here should really be in libgio as part of GApplication
[14:38]  * desrt has no hesitation to steal good ideas :)
[14:38] <desrt> in this case it looks like quicklist support
[14:41] <seb128> desrt, well it's mostly that and progress bars
[14:42] <desrt> yes.  we should support both of those
[14:42] <desrt> maybe also message counts
[14:42] <seb128> that as well
[14:42] <desrt> this is what i mean by getting rid of libunity
[14:43] <desrt> ie: making it no-longer-necessary by catching up with gtk/glib
[14:43] <chrisccoulson> desrt, oh, please do. that might mean we have a stable ABI
[14:43] <seb128> desrt, well you will never surpersed everything in there
[14:43] <seb128> desrt, but yeah, those could go in gtk
[14:43] <desrt> seb128: but probably enough to remove it as a depend of quite a lot of apps
[14:43] <chrisccoulson> please also kill libindicate :)
[14:44] <seb128> chrisccoulson, you hater :p
[14:44] <chrisccoulson> lol
[14:44]  * desrt loves haters
[14:44] <chrisccoulson> seb128, have you tried using libindicate? ;)
[14:45] <desrt> chrisccoulson: i've heard people (at this company) say the same of certain glib apis :)
[14:45] <desrt> *cough*gvariant*cough*
[14:45] <chrisccoulson> desrt, oh, i found gvariant quite easy to use. i even managed to use it from jsctypes ;)
[14:45] <seb128> the issue with gvariant is not it being hard to use
[14:45] <seb128> it's it being easy to misuse
[14:46] <desrt> true.
[14:46] <seb128> or rather to use in a buggy way
[14:46] <desrt> well
[14:46] <desrt> same with printf
[14:46] <seb128> and what you get when you misuse it
[14:46] <desrt> varargs is such a double-edged sword
[14:46] <seb128> right
[14:48]  * desrt resumes hud-hacking
[14:50] <seb128> desrt, yes please, btw what's the story with gmenus and appmenu?
[14:50] <desrt> seb128: working on it...
[14:50] <desrt> well
[14:50] <seb128> desrt, ok, that will fix menus as well, not only the hud
[14:50] <seb128> good
[14:51] <seb128> desrt, robert_ancell was complaining that his games have no menu at all today
[14:51] <desrt> ya... i guess i'm the one working on it :)
[14:51] <chrisccoulson> when you refer to "appmenu", are you referring to the shell menu, or menubars?
[14:51] <desrt> seb128: so let me do a bit of explaining
[14:51] <chrisccoulson> i'm confused now ;)
[14:51] <seb128> chrisccoulson, indicator-appmenu, same stuff we have for years
[14:51] <desrt> there's a difference between "app menu" and "appmenu"
[14:51] <desrt> appmenu is that ^
[14:51] <desrt> "app menu" is gtk_application_set_app_menu
[14:51] <chrisccoulson> yeah, this is getting really confusing nnow
[14:52] <desrt> ie: the gnome-shell menu that all the games are using now
[14:52] <desrt> as well as gnome contacts, documents, epiphany, etc.
[14:52] <seb128> we should call those unity-menubar and shell-appmenu
[14:53] <seb128> issues is that games use no standard menu, just a shell-appmenu
[14:53] <seb128> so under unity they go nothing in the unity-menubar
[14:53] <seb128> nor the in-windows-fallback
[14:53] <desrt> ya... appmenu-indicator has always been a particularly awful name
[14:54] <desrt> particularly considering the existance of the different-again 'app indicators'
[14:54] <seb128> desrt, how do we go solving that issue?
[14:54] <seb128> desrt, teach indicator-appmenu to display menubars and shell-appmenus merged?
[14:54] <desrt> seb128: near as i can tell the plan is something like so:
[14:55] <desrt> right now, we have in the indicator-appmenu source package two binaries: the hud-service binary and the indicator-appmenu module that gets loaded into the panel service
[14:55] <desrt> each of these collect menu data from dbusmenu separately
[14:55] <desrt> ted wants to merge hud-service into the appmenu indicator (ie: running inside of the unity panel service process)
[14:56] <desrt> this would give it a connection to the X server which means that it would be able to pop up the menus on demand from unity
[14:56] <desrt> so only one process communicating to dbusmenu
[14:56] <desrt> that would be the same process that does gmenumodel as well, of course
[14:56] <desrt> so the first step is to teach hud about gmenumodel
[14:56] <desrt> which i've already done, actually
[14:56] <desrt> i just have to make it speak dbusmenu again as well ;)
[14:57] <desrt> then the two processes get merged
[14:57] <desrt> then the appmenu indicator starts taking its menus from the hud code
[14:57] <desrt> tedg: is this accurate?
[14:57] <Sweetshark> pitti: 3.5.0-1ubuntu3 signed and uploaded to chinstrap. still waiting for armel/armhf.
[14:57] <pitti> Sweetshark: thanks; standing by then
[14:58] <pitti> Sweetshark: also, we need mterry or someone else to approve the MIR first
[14:58] <pitti> otherwise it'll just be depwait
[14:58] <seb128> desrt, is all that what you want to land for precise? ;-)
[14:58] <mterry> pitti, these are the LO MIRs?
[14:58] <desrt> seb128: yes
[14:58] <tedg> desrt, Yes, roughly.
[14:58] <pitti> mterry: there should only be one, libexttextcat or so
[14:58] <desrt> seb128: i'm not really sure how the merging of these two proceses fits into the freezes, etc.
[14:58] <seb128> desrt, ok, I better stop talking to you on IRC and let you work :p
[14:58] <desrt> but afaik that's been the plan all along
[14:58]  * Sweetshark -> LibreOffice ESC call
[14:59] <seb128> desrt, well as usual, the sooner it lands the better ;-)
[14:59] <desrt> tedg: any details that need 'fixing', just so we're all on the same page?
[14:59] <mterry> pitti, I see 4 from Sweetshark earlier
[14:59] <pitti> mterry: hang on, a few were in main earlier
[15:00] <mterry> pitti, lucene2 is the only one where Sweetshark doesn't mention it being in main earlier
[15:00] <tedg> desrt, Not really, I just was a bit confused on why you were discussing X connections.  But, I don't think that's a significant detail :-)
[15:00] <desrt> tedg: presently the hud-service doesn't connect to X
[15:00] <tedg> desrt, I mean, hud-service could connect to X without a problem if we wanted.
[15:00] <pitti> mterry: ok, none of them ring a bell
[15:00] <desrt> tedg: which makes it difficult to pop up a menu :)
[15:00] <tedg> desrt, Sure
[15:00] <pitti> mterry: I was thinking of libxml-java, pentaho-reporting-engine and friends; they just dropped out of main because reportbuilder got temporarily dropped
[15:01] <desrt> tedg: btw... wanted to ask you
[15:01] <desrt> what's the deal with the usage tracking?
[15:01] <desrt> you store it in a sqlite database (presumably for persistence)
[15:01] <desrt> but you also clear it out once per day
[15:02] <tedg> desrt, I clear out entries that are older than 30 days once a day.
[15:02] <desrt> gotcha.  thanks for clarifying :)
[15:03] <tedg> I wish there was a way to put jobs like that "when the hard drive is already spinning"
[15:03] <desrt> tedg: is there some sqlite commandline thingy i can type to see the current usage log, btw?
[15:03] <desrt> for debugging
[15:03] <tedg> desrt, There's hud-list-applications and hud-dump-application
[15:04] <desrt> perfect.  thanks.
[15:04] <tedg> desrt, Or you can just select * from usage; in the sqlite command line tool.
[15:04] <desrt> tedg: i'm a very very lazy man
[15:05] <desrt> aka "a good programmer" :)
[15:05] <tedg> desrt, Heh, I look forward to all the tools you're going to write for things you only do once ;-)
[15:06] <desrt> if only i could write a tool to go to my phone meetings for me...
[15:13] <pitti> desrt: cat mystatus.txt | gnome-orca, and put your phone to the speaker? :-)
[15:16] <desrt> hum!
[15:16] <desrt> pitti: i guess the meeting would not work very well if everyone did that
[15:16] <kenvandine> desrt, it would go quickly!
[15:17] <cyphermox> seb128: any counter-indications to making gnome-icon-theme-full replace gnome-icon-theme in evolution's Depends, gnome-icon-theme is missing one or two icons (encrypted emails) that are provided by -full ... I don't see issues with that as nothing seems to explicitly pull in evolution anymore
[15:17] <seb128> cyphermox, works for me
[15:17] <seb128> the -full thing is purely for the CD space
[15:18] <cyphermox> yeah, that's what I thought
[15:18] <cyphermox> just making sure in case reverse-depends would lie for some reason
[15:19] <cyphermox> would be nice to bundle one or two other fixes to evo with that though
[15:19] <chrisccoulson> b'ah, will people please stop emailing me about chromium builds? thank you :)
[15:19] <cyphermox> lol
[15:20] <cyphermox> chrisccoulson: break them long enough and the emails will stop ;)
[15:20] <chrisccoulson> cyphermox, they've not been running for ages
[15:20] <cyphermox> ah
[15:20] <chrisccoulson> lack of disk space on the machine that they build from
[15:21] <chrisccoulson> and lack of motivation to start them again
[15:21] <chrisccoulson> i haven't used chromium in ages now
[15:21] <cyphermox> chrisccoulson: do you mean on the buildds or on whatever machine fta was using to prepare the builds?
[15:21] <chrisccoulson> cyphermox, oh, i was preparing the builds on chinstrap. but it's pretty much out of disk space
[15:21] <cyphermox> oh
[15:22] <cyphermox> thought it was still daily builds with that thingy
[15:22] <chrisccoulson> the chromium repo's were taking up something like 30GB or something ridiculous
[15:22] <cyphermox> yeah
[15:22] <cyphermox> more than half my hard drive!
[15:23] <chrisccoulson> lol
[15:23] <pitti> pitti.bugs_fixed += 7 # take that, seb128
[15:23] <chrisccoulson> i wish i was doing something more productive than trying to make firefox build on powerpc again
[15:24] <chrisccoulson> can we kill it already? :)
[15:24]  * seb128 rolls up sleeves, wait pitti
[15:25] <jbicha> killed a 4-digit bug with the gnome-terminal upload :)
[15:26] <didrocks> pitti: seb128: just a warning, updating compiz will update the default keybindings
[15:27] <didrocks> pitti: seb128: so if you never changed Ctrl + alt + arrows to something else, it will be Super + Shift + arrows
[15:27]  * didrocks prepares to get a ton of pings about "my ws switcher is broken"
[15:27] <pitti> didrocks: thanks; there's a high chance that I didn't, so I'll just set it back then
[15:28] <didrocks> pitti: yeah, I ensured the g-c-c integration is working
[15:28] <didrocks> so no ccsm :p
[15:28] <didrocks> and exposed some additional keys
[15:28] <didrocks> (keeping Super press will also shows the default keys)
[15:28] <seb128> pitti, well I didn't restart my session but I confirm in a guest session :p
[15:28] <Sweetshark> pitti: libreoffice installer finished on armhf, now it only need to package
[15:28] <seb128> ups
[15:28] <seb128> didrocks, ^
[15:28] <seb128> didrocks, confirm that it works
[15:28] <pitti> Sweetshark: nice, so only another hour or so? much better than the 6 days it took on the babbage board :)
[15:29] <didrocks> seb128: thanks! :)
[15:29]  * didrocks pushes the package of packages
[15:41] <mterry> Sweetshark, ping, so those 4 MIRs were all in main before?  This is just package shuffling?
[15:45] <Sweetshark> mterry: in sofar as if they dont get MIRed we are build our own private version of the same lib inside LO. I would have to recheck if all those were in main before.
[15:45]  * Sweetshark is in a ESC call.
[15:45] <mterry> oops, sorry  :)
[15:45] <Sweetshark> np
[15:49] <dobey> pitti: so we'd still need to drop about 18M on the i386 image, right?
[15:50] <pitti> dobey: 10
[15:50] <mterry> jbicha, you just did vte3?  thanks.   I can pick another one up for you in exchange?
[15:51] <dobey> pitti: 10 will make it actually fit on a CD right? we'd need 6-8 more for getting pyqt bits on?
[15:51] <pitti> ah, right
[15:53] <dobey> pitti: and chrisccoulson's fixes for ffox/tbird aren't on the image yet, right?
[15:53] <pitti> right
[15:54] <dobey> that should drop 10M off the size? or less?
[15:55] <dobey> i guess probably less
[15:56] <didrocks> Riddell: hey, compiz FTBFS because it can't install kde-workspace-dev. I see no kde-workspace nor libkwinglesutils1 recent upload. Is the issue more deep in the dep chain? (https://launchpadlibrarian.net/93985206/buildlog_ubuntu-precise-i386.compiz_1%3A0.9.7.0~bzr2995-0ubuntu5_FAILEDTOBUILD.txt.gz)
[15:57] <didrocks> deeper*
[15:58] <jbicha> mterry: I'm good today, thanks!
[15:58] <Riddell> didrocks: hmm installs for me, let me keep looking
[16:03] <mdeslaur> seb128: is this a gtk issue? http://imgpaste.com/D9vA.png
[16:03] <mdeslaur> seb128: I've been getting transparent context menus once every 10-20 times for the past couple of weeks
[16:04] <seb128> mdeslaur, I doubt it, I would rather blame it on the wm or unity or the theme
[16:04] <seb128> or xorg
[16:05] <mdeslaur> seb128: but lowering my pointer makes each entry draw properly...
[16:05] <mdeslaur> seb128: ok, thanks
[16:05] <seb128> I didn't notice it here
[16:05] <Riddell> didrocks: dunno it installs fine in a chroot too
[16:05] <seb128> mdeslaur, do you use unity-3d?
[16:05] <mdeslaur> yes
[16:05] <seb128> mdeslaur, I would blame compiz
[16:05] <seb128> mdeslaur, did that start after we got the new compiz?
[16:05] <Riddell> didrocks: but compiz had another compile error with kde recently and I said it would be fine to drop the kde bits
[16:06] <didrocks> Riddell: yeah, I just didn't drop the build-dep if we want to put it back one day
[16:06] <mdeslaur> seb128: it's possible
[16:06] <didrocks> Riddell: let me try to rebuild, it's fine in a pbuilder here as well
[16:06] <seb128> mdeslaur, well my bet would be compiz in any case
[16:06] <didrocks> Riddell: otherwise, I'll just drop the dep
[16:06] <mdeslaur> seb128: ok, will file against compiz, thanks
[16:06] <seb128> mdeslaur, yw
[16:06] <seb128> mdeslaur, you could try unity-2d for some hours if you can trigger the bug easily
[16:07] <seb128> mdeslaur, and see if that still happens there
[16:07] <didrocks> mdeslaur: seb128: there is already a bug opened against this
[16:07] <seb128> didrocks, compiz bug then?
[16:07] <didrocks> yeah
[16:07] <didrocks> already in the priority lilst
[16:07] <didrocks> list*
[16:09] <didrocks> Riddell: ok, it still can't take it
[16:13] <mdeslaur> thanks didrocks, found it
[16:23] <seb128> pitti, is report['Tags'] a list or a string where tags are separated by spaces?
[16:24] <didrocks> last time I used it, it was a string with tags separated by spaces
[16:24] <seb128> didrocks, ok, what it seemed to be to me as well, thanks
[16:25] <seb128> I just wanted to check
[16:28] <didrocks> waow, was a long time ago I didn't experienced a kernel panic
[16:29] <didrocks> I have thus to restart building compiz without kde-*
[16:37] <didrocks> Riddell: ok, kde-ws-dev is installing now, I'll ask for rebuilds
[16:49] <pitti> seb128: a string
[16:49] <pitti> dobey: ffox/tbird should buy about 4 MB
[16:50] <dobey> :-/
[16:51] <dobey> did a recent update break gtk-doc btw? it seems to be failing to build html docs for me, and when doing ./autogen --enable-gtk-doc, make dist fails as there are no html files output to copy to the dist dir
[16:51] <kenvandine> dobey, not that i noticed
[16:52] <dobey> hrmm
[16:54] <dobey> ah, it's just the same brokenness that gtk-doc has always had i guess
[16:54] <chrisccoulson> m_conley_away, do you plan to add the QF button on to the toolbar in the current beta?
[17:01] <chrisccoulson> m_conley_away, oh, i see it's already been done on the beta :)
[17:02] <chrisccoulson> is there any chance of getting a monochrome icon for that? ;)
[17:02] <Sweetshark> pitti: I just read "build successfully" flying by on the armhf buildd
[17:03] <pitti> !
[17:03] <pitti> Sweetshark: indeed, it's at chroot cleanup
[17:03] <pitti> PARTY!
[17:03] <pitti> armhf: 797
[17:03] <pitti> with libo and mesa this should go down to 1 or even 0 in a few hours
[17:05] <pitti> and armel accepted
[17:06] <didrocks> m4n1sh: so, I need to build with --with_whoopsie and dep on polkit-gobject-1, isn't it?
[17:06] <didrocks> well, --with-whoopsie
[17:06] <m4n1sh> didrocks: yes
[17:07] <m4n1sh> in case you pass that then --with-ccpanel is not not needed
[17:07] <m4n1sh> polkit is added as a dep
[17:07] <didrocks> m4n1sh: ok, we agree then ;)
[17:07] <Sweetshark> pitti: PARTY indeed: \o\ /o/ \o/ /o? big kudos to janimo and doko
[17:07] <m4n1sh> yup
[17:08]  * Sweetshark -> TDF advisory board call now
[17:17] <aleix> hi, I'm working on an implementation of Ubuntu's ratings and reviews API for Kubuntu
[17:18] <aleix> I was wondering if there's any documentation about the rnr service
[17:27] <pitti> Sweetshark: libreoffice_3.5.0-1ubuntu3_source.changes uploaded
[17:28] <Sweetshark> so, by saturday we will have another ARM build finished hopefully ;)
[17:28] <pitti> yeah
[17:29] <Sweetshark> pitti, mterry, Riddell: thanks for bearing with me on timing this!
[17:29] <pitti> no worries :)
[17:29] <pitti> now we start from a clean base, so it doesn't matter if that build takes a bit longer
[17:35] <kiwinote> aleix: you may want to take a look at https://code.launchpad.net/rnr-server - feel free to ask any questions in #software-center
[17:35] <aleix> oh the channel was #software-center, sorry
[17:41] <pitti> didrocks: compiz FTBFS is due to mesa
[17:42] <pitti> didrocks: mesa just built, needs to publish then we can retry this
[17:43] <didrocks> pitti: you mean the kde-workspace-dev? yeah, I redid a build on amd6' and i386 and it works now
[17:43] <didrocks> still need armel
[17:43] <pitti> yes, it's due to mesa/wayland
[17:43] <pitti> didrocks: see http://people.canonical.com/~ubuntu-archive/testing/precise_probs.html
[17:43] <pitti> it's fun, nothing uses wayland, and yet it makes > 800 packages uninstallable when it breaks :)
[17:44] <kenvandine> haha
[17:45] <didrocks> pitti: yeah, I need to take the habit looking at this page when something is weird in the archive, way easier to pinpoint the issue :)
[17:45] <didrocks> pitti: thanks for the notice!
[18:41]  * didrocks waves goodnight
[19:06] <nessita> anyone knows who's maintaining (if someone) aptdaemon?
[19:06] <pitti> nessita: mvo and glatzor
[19:06] <nessita> pitti: thanks! will ping
[19:07]  * nessita git bitten by bug #926340
[19:07] <ubot2`> Launchpad bug 926340 in aptdaemon "aptd crashed with UnicodeDecodeError in _set_error(): 'ascii' codec can't decode byte 0xc3 in position 9: ordinal not in range(128)" [Undecided,Confirmed] https://launchpad.net/bugs/926340
[19:08] <nessita> glatzor: ping, if you're aroung
[19:08] <nessita> around*
[19:24] <chrisccoulson> hmmm, this is quite an interesting read, for anybody using python: http://revista.python.org.ar/2/en/html/memory-fragmentation.html ;)
[19:24] <chrisccoulson> (or any other language for that matter)
[19:34] <jbicha> mterry: are you still interested in doing favors?
[19:34] <mterry> jbicha, :)  sure
[19:35] <jbicha> mterry: looks like shaunm did a bunch of releases today, I'm grabbing gnome-user-docs & devel-docs but I can't upload yelp-tools or yelp-xsl
[19:36] <mterry> jbicha, sure, I got 'em
[19:39] <pitti> good night everyone!
[19:39] <mterry> pitti, night!
[19:44] <desrt> RAOF: boundaries stopped working?
[19:44] <desrt> boundaries -> barriers(?)
[19:55] <micahg> jbicha: bug 939763
[19:55] <ubot2`> Launchpad bug 939763 in cheese "package libcheese-dev 3.3.5-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/include/cheese/cheese-widget.h', which is also in package libcheese-gtk-dev 3.3.90-0ubuntu1" [Undecided,New] https://launchpad.net/bugs/939763
[19:59] <desrt> chrisccoulson: sounds like gslice!
[20:03] <jbicha> micahg: thanks
[20:26] <dobey> feature/ui freeze: when all the regressions pop up.
[20:51] <tedg> chrisccoulson, Heh, you still awake?
[20:51] <tedg> hey
[20:54] <chrisccoulson> tedg, yes, parts of me are still awake :)
[20:54] <tedg> chrisccoulson, Okay, shut of the porn, I need some blood upstairs :-)
[20:55] <chrisccoulson> lol
[20:55] <tedg> chrisccoulson, I'm getting a blank dbusmenu item at the end of the Thunderbird menus.
[20:55] <tedg> chrisccoulson, Have you seen that?
[20:55] <chrisccoulson> i haven't
[20:55]  * chrisccoulson opens dom inspector to see if i can find anything
[20:55] <tedg> chrisccoulson, I fixed a bug to show items with out submenus, and now I'm getting one...
[20:56] <tedg> chrisccoulson, If you do /usr/lib/libdbusmenu/dbusmenu-dumper and click on TB you'll get the dump.
[20:56] <tedg> chrisccoulson, It should be the very last one.
[20:58] <chrisccoulson> tedg, oh, i see that too
[20:58] <chrisccoulson> tedg, should be easy for me to figure out :)
[20:59] <tedg> chrisccoulson, Heh, famous last words ;-)
[21:00] <chrisccoulson> tedg, oh, i see
[21:01] <chrisccoulson> tedg, so, the issue is that we insert dummy nodes for items that can't be represented in the menubar, to keep everything in sync so that we can handle insertions/removals correctly
[21:01] <chrisccoulson> and there is a spacer on the end of the menubar
[21:01] <chrisccoulson> i've been wondering for a while how to get rid of this workaround :/
[21:01] <tedg> chrisccoulson, well, it's not too big a deal if you just set the visibility to false :-)
[21:01] <chrisccoulson> we added it a while back to resolve crashes we were getting when menuitems were being removed
[21:02] <chrisccoulson> oh, are we not setting the visibility?
[21:02] <tedg> No
[21:03] <chrisccoulson> tedg, hmmm: http://bazaar.launchpad.net/~extension-hackers/globalmenu-extension/trunk/view/head:/extensions/globalmenu/components/src/uGlobalMenuDummy.cpp#L53 :/
[21:04] <tedg> chrisccoulson, When I dump it that property isn't set.  Is it different on the root item?
[21:05] <tedg> chrisccoulson, That should be property_set_bool()
[21:05] <chrisccoulson> hah, well spotted :)
[21:06] <tedg> Glad you didn't set it to TRUE anywhere :-)
[21:06] <chrisccoulson> if i set it to true, i might have seen a compiler warning :)
[21:07] <chrisccoulson> or, would i?
[21:07] <chrisccoulson> actually, perhaps not
[21:07] <chrisccoulson> yeah, if i'd set it to true, i guess it would have crashed
[21:07] <chrisccoulson> ok, i'll get that fixed
[21:07] <chrisccoulson> thanks :)
[21:10] <tedg> np
[21:11] <chrisccoulson> ok, hopefully that should work now: http://bazaar.launchpad.net/~extension-hackers/globalmenu-extension/trunk/revision/277
[21:11] <chrisccoulson> :)
[21:11] <tedg> chrisccoulson, ship it!
[21:11] <tedg> :-)
[21:12] <chrisccoulson> i'll make sure it's in the next upload i do, which may be later (hopefully)
[21:47] <kenvandine> seb128, mind doing a quick review of my new farstream package?  i am not quite ready to upload it yet, but always nice to get feedback early
[21:48] <seb128> kenvandine, can do, where is it?
[21:49] <kenvandine> lp:~ken-vandine/+junk/farstream
[21:49] <kenvandine> seb128, it replaces libgstfarsight-0.10-0
[21:49] <RAOF> desrt: What are you seeing?  Yours is the first report of non-barriers (after fixing the nvidia far-left case) I've come across.
[21:50] <kenvandine> no idea why they renamed the project
[21:50] <desrt> RAOF: just not seeing them working in gnome-shell
[21:50] <seb128> kenvandine, ok
[21:50] <desrt> no gnome-shell upgrade, but just upgraded X, so i assume the change was there
[21:53] <RAOF> desrt: I would be really surprised if the latest xorg changes broke shell; I'll test locally, though.
[22:00] <robert_ancell> seb128, still there?
[22:01] <seb128> robert_ancell, hey
[22:01] <seb128> robert_ancell, how are you?
[22:03] <robert_ancell> seb128, good.  After 3 attempts I'm going to hopefully get the lightdm PAM session patch working today.  It's quite invasive but the regression tests (which I am adding more) do pass on it so it gives me some confidence.  It needs a load of testing to be sure of course.  How do you recommend we test it?  Also, is it affected by the freezes?
[22:03] <seb128> robert_ancell, so for the easy one: we are in hard freeze (i.e archive blocked and release team reviewing queue), so yes, it's affect by the freeze
[22:04] <seb128> robert_ancell, not sure it counts as a feature for after beta, but it would still be good to have it reviewed I think
[22:04] <robert_ancell> seb128, yeah, so it's really a big bug fix rather than a feature
[22:04] <seb128> robert_ancell, are you confident enough to push it to people who are brave enough to run the ubuntu-desktop ppa?
[22:05] <seb128> I would recommend putting it there during the beta freeze
[22:05] <seb128> and file a bug for review from pitti and slangasek
[22:05] <robert_ancell> seb128, I think I'll make a separate PPA, and then if you can test it tomorrow we should push it to the desktop PPA quickly if it appears to be working well
[22:05] <seb128> just for sanity check from people who know pam etc
[22:05] <robert_ancell> yes
[22:05] <robert_ancell> I'm going to get the corporate people who are most effected to test it as they have the complex PAM setups for real
[22:06] <seb128> robert_ancell, works for me, just put it in your own ppa if you don't use it for anything else
[22:06] <seb128> for the first testing round
[22:06] <seb128> robert_ancell, or if that's just for me, put it in the vcs I can locally build lightdm
[22:07] <robert_ancell> seb128, it's on lp:~robert-ancell/lightdm/session-refactor3 (but I'm still ironing out final bugs)
[22:07] <seb128> robert_ancell, drop me an email with the vcs or ppa if you get it in a state you are confident enough to get testing today and I will test tomorrow
[22:07] <robert_ancell> ta
[22:07] <seb128> robert_ancell, or do you want a first testing round on the current version?
[22:07] <robert_ancell> no, it still fails 13 regression tests
[22:07] <seb128> ok
[22:08] <robert_ancell> but that does mean it passes 80 :)
[22:08] <seb128> ;-)
[22:08] <seb128> robert_ancell, btw while you are there quick note and one question
[22:08] <seb128> robert_ancell, 1- I reverted the indicator-session "don't lock" commit in our package today since we still had cases were locking was not happening
[22:09] <robert_ancell> sure
[22:09] <seb128> robert_ancell, not sure if I should get it reverted in trunk as well or if that's just "lightdm needs to handle stuff it doesn't yet"
[22:09] <robert_ancell> seb128, yeah, they should probably revert
[22:09] <robert_ancell> we'll have to solve it properly in 12.10
[22:10] <seb128> robert_ancell, and the question was "what happened to lock screen"? you said you would have a go at trying to make g-s be unity-greeter like (and yes I realize weeks have only so many hours ;-)
[22:10] <seb128> just being curious
[22:10] <robert_ancell> seb128, I started looking at it, but it's not simple
[22:10] <seb128> ok, that's what I figured
[22:10] <robert_ancell> I don't think I'll have the time.  This lightdm patch is more important I think so I've been scrambling to get it working before the baby
[22:11] <seb128> I hate our current lock screen and I wonder if we could do better with a bit of work, going the full way seems obviously for next cycle
[22:11] <seb128> robert_ancell, agreed
[22:11] <robert_ancell> seb128, does anyone have the time?
[22:11] <seb128> I was just status checking
[22:11] <seb128> hum
[22:11]  * seb128 looks at mterry
[22:11] <seb128> ;-)
[22:11] <robert_ancell> it's definitely technically feasible, and it would be worth it
[22:11] <mterry> hm?
[22:11] <seb128> mterry, RUN
[22:11] <seb128> ;-)
[22:11] <robert_ancell> mterry, hey, feeling better?
[22:11] <mterry> robert_ancell, better enough
[22:12] <seb128> oh, mterry was not feeling good?
[22:12] <mterry> seb128, yeah I was off yesterday
[22:12] <seb128> mterry, hey, sorry to hear you were not good, but good that you are better ;-)
[22:12] <mterry> bad timing right before a freeze  :)
[22:12] <seb128> mterry, did I tell you how much users like the unity greeter? ;-)
[22:12] <seb128> robert_ancell, ^ as well
[22:12] <robert_ancell> :P
[22:12] <seb128> we got quite some nice user comments on european hours recently
[22:13] <seb128> just sharing the feedback ;-)
[22:13] <seb128> mterry, we were discussing lock screen and how ugly the current one is
[22:13] <mterry> seb128, yar.  We postponed that until 12.10, right robert_ancell?
[22:13] <seb128> mterry, robert_ancell asked if somebody would have any time to maybe improve that, I just throw your name in case
[22:14] <mterry> Ah, I see.  /me glares at seb128
[22:14] <seb128> but I guess you are busy as everybody else
[22:14] <robert_ancell> mterry, yeah we did... :)
[22:14] <seb128> it was worth trying :p
[22:14] <mterry> seb128, you're talking about some half-way step to make it look nicer, even without full unity-greeter interaction?
[22:14] <seb128> mterry, yes
[22:15] <robert_ancell> mterry, yes, patch gnome-screensaver
[22:15] <robert_ancell> to look like unity-greeter
[22:15] <seb128> just doing something better than this solid grey rectangle with weird aligned label
[22:15] <seb128> I would be happier with like a non grey rectangle and some labels alignment etc tweaks I guess
[22:16] <seb128> mterry, the full "use the greeter" stuff is not for this cycle for sure
[22:16] <mterry> seb128, sounds like someone doesn't know that we passed UI Freeze  :)
[22:16] <seb128> DOH
[22:16] <seb128> did we? ;-)
[22:17] <seb128> mterry, yeah, sorry, it's that day of the cycle where you realize that it's uif and that we still have some sucking ui bits :p
[22:17] <seb128> I will get over it tomorrow :p
[22:17] <mterry> seb128, I kind like the gray box  :)
[22:17] <mterry> seb128, reminds me of a simpler time
[22:17] <RAOF> Before we cared about appearance? :)
[22:17] <seb128> when our only users were geeks who don't have any taste? ;-)
[22:18] <mterry> seb128, what does GNOME3 do?  Is it in-shell?
[22:18] <RAOF> Um, why is déjà dup using white text on a light background?
[22:18] <seb128> mterry, no, they plan to use the shell but didn't get to it this cycle
[22:18] <seb128> mterry, so they basically have what we have I think
[22:18] <Sarvatt> nah 10 minutes ago before someone tried to get him to do it :)
[22:20] <mterry> RAOF, GTK bug, but it's worked around in very latest deja-dup uploaded today
[22:20] <RAOF> Hurray!  Now, if the upgrade would kindly not try to remove *:i386... :)
[22:21] <mterry> seb128, I bet Cimi could whip up some CSS to make it look nicer (at least white on black instead of black on white)
[22:21]  * mterry passes buck
[22:21] <seb128> mterry, nice try ;-)
[22:21] <seb128> if Cimi wasn't like 2 weeks behind on uif
[22:22] <mterry> fair
[22:22] <seb128> like he wanted to fix unity ui bugs this week
[22:22] <seb128> do some "unfocussed theme" next week
[22:22] <seb128> then start fixing the theme for the new gtk...
[22:22] <seb128> then look at bugs
[23:03] <RAOF> desrt: Hm, missing barriers confirmed.  Let's see what's a happenin'.
[23:04] <desrt> ahah!
[23:06] <RAOF> mterry: How much effort do you think it'd be to get déjà dup to backup from a btfrs snapshot of $HOME, rather than the live fs?
[23:07] <mterry> RAOF, how are btfrs snapshots exposed to the system?
[23:07] <mterry> RAOF, I'd have to make btrfs calls to get it?
[23:07] <RAOF> mterry: Yeah.  At worst you could fork a call to the btrfs binary.  The snapshots are exposed as regular directories; it's essentially the same as mounting a different device on a directory.
[23:09] <mterry> RAOF, obviously, if you could expose it as a regular dir before deja-dup becomes involved, that's easiest.  But it sounds like you want to be able to tell deja-dup to do that mounting itself?
[23:09] <RAOF> mterry: Yeah, that'd be ideal; take a snapshot, back up from that, and then delete the snapshot.
[23:10] <mterry> RAOF, ah ah, you mean taking snapshots too.  That would be great; makes sure the files are quiescent
[23:10] <RAOF> (This is on the basis that backups to U1 take on the order of days for me; there's plenty of time for the backup to become incoherent due to skew)
[23:11] <RAOF> Right.  That's exactly the problem I'd like to solve :)
[23:12] <RAOF> desrt: There's no change I can see which would obviously cause the lack of gnome-shell barriers.  When did you last update X?
[23:13] <mterry> RAOF, bug 939903
[23:13] <ubot2`> Launchpad bug 939903 in deja-dup "Use btrfs snapshots during backup if possible" [Wishlist,Confirmed] https://launchpad.net/bugs/939903
[23:15] <desrt> RAOF: let me check my apt log
[23:15] <desrt> Start-Date: 2012-02-23  09:31:18
[23:15] <desrt> xserver-xorg-core:amd64 (1.11.4-0ubuntu3, 1.11.4-0ubuntu4)
[23:16] <RAOF> mterry: Sweet.  I may look into implementing that if I have a lazy day and I don't feel like releasing Do :)
[23:16] <Laney> Naughty.
[23:17] <RAOF> :P
[23:17] <desrt> RAOF: last xorg change before that was xserver-xorg-input-synaptics:amd64 (1.5.0+git20120210-0ubuntu2, 1.5.99~git20120220-0ubuntu2) on the 20th
[23:17] <mterry> RAOF, :)
[23:17] <desrt> pretty sure (a) unrelated and (b) was working since then
[23:17] <desrt> so i'm guessing something happened with the xorg-core 0ubuntu3 -> 0ubuntu4 upgrade
[23:18] <RAOF> Ok.  I can't really see how, so it's time for Mr GDB From A Second Machine.
[23:18] <desrt> let me see if i still have the archive around to do a downgrade
[23:18] <RAOF> You could also pick the files from Launchpad if you don't still have them.
[23:18] <desrt> i do.  logging out/in
[23:19] <desrt> downgrading to 0ubuntu3 fixes it
[23:19] <desrt> so there you go
[23:20] <desrt>   * debian/patches/500_pointer_barrier_thresholds.diff:
[23:20] <desrt> oh come on
[23:20] <desrt> nothing obvious that could have caused it? :p
[23:20] <RAOF> I mean, there's nothing obvious in that diff.
[23:20] <desrt> :)
[23:20] <RAOF> I *did* change the implementation slightly, true :P
[23:21] <desrt> gdb time, indeed
[23:35] <RAOF> Ah, my old nemesis, <optimised out>.
[23:38] <Sweetshark> RAOF: still better than the "sexier segfault" from https://bugs.freedesktop.org/show_bug.cgi?id=8622
[23:38] <ubot2`> Freedesktop bug 8622 in Lib/Xlib "libX11/XCB threads: simultaneous event-wait with other Xlib request breaks" [Major,Resolved: fixed]
[23:43] <RAOF> Heh.
[23:44] <broder> RAOF: i *hate* <optimised out>!
[23:46] <bryceh> time for a build with disabled optimizations
[23:46]  * Sweetshark is a bit pumped up still, from two touch and go LibreOffice uploads (read, "armhf is finished, ok, pipe in the next one!". there were no more than 5 minutes between build finished and next upload.
[23:52]  * desrt installs debugging symbols to discover what broder hates
[23:52]  * desrt installs debugging symbols to discover who RAOF's old nemesis is