[00:28] <rickspencer3> RAOF, are you going to pick off that mga thing today by any chance?
[00:32] <RAOF> rickspencer3: If I get through gnome-keyring-sharp, yes.  Having seen it and read the patch I just wanted to make other people feel safer about picking it up.
[00:32] <RAOF> I'll need bryce to upload for me anyway :)
[00:33] <rickspencer3> RAOF, make sense
[00:33] <rickspencer3> thanks man
[00:35] <robert_ancell> chrisccoulson, do you know where the new system-tools-backends tarballs are coming from?
[00:36] <chrisccoulson> robert_ancell<EMAIL_ADDRESS>[00:37] <robert_ancell> chrisccoulson, so they're given up of fdo then :)
[00:37] <RAOF> Hey!  When did notify-osd messages lose their click-through magic?
[00:39] <chrisccoulson> robert_ancell, yeah, i think it's because it has a different maintainer now
[00:39] <chrisccoulson> RAOF, have they?
[00:39] <robert_ancell> chrisccoulson, well, makes my life easier.  Updated the versions script
[00:40] <chrisccoulson> robert_ancell, cool!
[00:40] <RAOF> chrisccoulson: Song change coming up... let me test again :)
[00:40] <chrisccoulson> RAOF - you're right
[00:41] <chrisccoulson> i can't click through them either
[00:41] <chrisccoulson> that sucks
[00:41] <RAOF> It does somewhat defeat the purpose, yes.
[00:41]  * chrisccoulson checks lucid-changes for when it might have broken
[00:42]  * RAOF fires up ubuntu-bug
[00:44] <RAOF> I think bug #546659 is our winner.
[00:45] <RAOF> Ahem. bug #546650
[00:47] <chrisccoulson> RAOF - thanks
[00:47] <chrisccoulson> hmmm, notify-osd didn't change since 9th march
[00:48] <RAOF> And none of the last couple of uploads seem to contain a “break click through” message, surprisingly enough :)
[00:48] <chrisccoulson> heh
[00:48] <chrisccoulson> and i can't get xtrace to work :-/
[01:15] <rickspencer3> RAOF, I'm wondering bug #546650 should rather be assigned to Dx team
[01:15] <rickspencer3> do you mind if I reassign, or were you planning to look at it
[01:15] <rickspencer3> ?
[01:16] <RAOF> rickspencer3: I'd be happy for you to reassign to Dx.
[01:17] <rickspencer3> RAOF, ok, I accepted it for Lucid too
[01:19] <rickspencer3> RAOF, robert_ancell quick question, either of you guys see anything strange in your messaging menu?
[01:19] <chrisccoulson> rickspencer3, truncated icons?
[01:19] <chrisccoulson> (as a guess)
[01:20] <rickspencer3> chrisccoulson, hi
[01:20] <RAOF> A radiobox control for statuses?
[01:20] <RAOF> That looks pretty weird.
[01:20] <rickspencer3> RAOF, that's your Me Menu, actually
[01:20] <rickspencer3> :)
[01:20] <chrisccoulson> the icons in the messaging menu get cut off now
[01:20] <RAOF> Bah!  Terminology!
[01:20] <rickspencer3> jono_,  is seeing Set up Mail ...
[01:20] <rickspencer3> set up chat ...
[01:20] <rickspencer3> but they are already configured
[01:21] <RAOF> I don't think I've restarted since that change.
[01:21] <chrisccoulson> oh, i'm not seeing that
[01:21] <rickspencer3> did you guys dist-upgrade recently?
[01:21] <chrisccoulson> but my menu looks weird
[01:21] <rickspencer3> like since kenvandine did the Dx release
[01:21] <chrisccoulson> ah, not just yet
[01:21] <rickspencer3> ok
[01:21] <rickspencer3> here's why I hate OOo
[01:22] <rickspencer3> I hardly use it, but I have to wait for calc to update
[01:22] <rickspencer3> ccheney, looks like I'm getting your theme fixes
[01:23] <chrisccoulson> RAOF - the notify-osd bug is a gtk regression
[01:23] <chrisccoulson> i just tried LD_PRELOADing the old version
[01:23] <RAOF> Ah.
[01:23] <chrisccoulson> and it works again
[01:23] <chrisccoulson> i will reassign
[01:24] <robert_ancell> rickspencer3, the babel fish?
[01:24] <rickspencer3> babel fish?
[01:24] <robert_ancell> rickspencer3, Thats what the broadcast icon looks like to me :)
[01:24] <rickspencer3> robert_ancell, is that what the icon for broadcast accounts is
[01:25] <rickspencer3> I thought it was a opium poppy
[01:25] <robert_ancell> lol
[01:25] <RAOF> Man, I love it when unexpected test successes teach you something.
[01:25] <chrisccoulson> so, i wonder what changed in gtk
[01:25] <RAOF> I thought that was a little bird - you know, like the twitter iconography.
[01:25] <chrisccoulson> i might bisect that in the morning
[01:25] <rickspencer3> chrisccoulson, you say it's been fixed?
[01:26] <rickspencer3> in gtk?
[01:26] <chrisccoulson> rickspencer3, it seems to be gtk which has broken it
[01:26] <rickspencer3> when you say "was"
[01:26] <rickspencer3> you mean ... ?
[01:26] <chrisccoulson> if i run notify-osd with the previous version of gtk, then it works again
[01:26] <chrisccoulson> with the current version in the archive, it doesn't work anymore
[01:26] <rickspencer3> so by "was" you mean "is"?
[01:26] <rickspencer3> :)
[01:27] <chrisccoulson> oh, did i say "was"?
[01:27] <chrisccoulson> heh
[01:27] <robert_ancell> rickspencer3, hey, did anyone suggest to mvo to remove eclipse from the featured apps?
[01:27] <rickspencer3> I thought I did, yes
[01:27] <rickspencer3> robert_ancell, does our version of it still suck?
[01:27] <robert_ancell> rickspencer3, I think so
[01:27] <rickspencer3> hmmm, maybe I never did
[01:27] <robert_ancell> rickspencer3, it was when I last tried it
[01:27] <rickspencer3> let me log a bug
[01:28] <robert_ancell> rickspencer3, we should add tuxpaint too as that's a good app for kids
[01:28] <rickspencer3> hmm
[01:28] <rickspencer3> better not log a bug until anyone tries it
[01:28] <rickspencer3> robert_ancell, could you pleaseL
[01:28] <rickspencer3> 1. confirm the suckiness of eclipse
[01:28] <rickspencer3> 2. confirm the awesomeness of tuxpain
[01:28] <rickspencer3> tuxpaint, even
[01:28] <rickspencer3> and ask mvo to do the change?
[01:29] <rickspencer3> a bug report maybe be appropriate, but maybe just ask him tonight
[01:29] <chrisccoulson> hmmm, i'm not sure how to run xprop on a click-through notification bubble
[01:29] <chrisccoulson> RAOF, any ideas? ;)
[01:29] <chrisccoulson> i just get the properties of the window below...
[01:30] <RAOF> There's got to be some way to pass in a pid, right?
[01:30] <chrisccoulson> RAOF - you can pass the window ID, but i don't know what that is
[01:31] <chrisccoulson> i'm not sure how to get it
[01:31] <chrisccoulson> and it's not around for very long either
[01:31] <RAOF> xwininfo -name might be what you're after.
[01:32] <RAOF> I'm not sure what the name of the notify-osd windows is without source digging, but “notify-osd” should be a reasonable guess.
[01:33] <RAOF> xwininfo will give you the ID, then you can xprop
[01:34] <chrisccoulson> it seems there is a permanent offscreen window with the name "notify-osd"
[01:34] <robert_ancell> rickspencer3, hmm, can't even install eclipse at the moment
[01:34] <rickspencer3> that's not real confidence inducing
[01:35] <robert_ancell> :)_
[01:36] <robert_ancell> rickspencer3, not sure if you edit a lot of older glade files but I just uploaded the brand new upstream to make the vboxes stop reverting to being horizontal
[01:36] <ccheney> rickspencer3: hmm i didn't upload it yet
[01:36] <rickspencer3> robert_ancell, I don't recall having this issue
[01:36] <rickspencer3> ccheney, oh, well I'm getting a lot of new OOo
[01:36] <ccheney> rickspencer3: committed it to ooo-build git though and will be uploading it once i find out from rene if he is going to upload -5 to debian in the next day
[01:36] <rickspencer3> k
[01:37] <ccheney> rickspencer3: hmm i think that would have been from monday's upload
[01:37] <rickspencer3> prolly
[01:37] <robert_ancell> rickspencer3, you'd remember it if you'd had it.  Drives a lot of people insane
[01:37] <rickspencer3> I guess it's been a couple of days
[01:37] <rickspencer3> robert_ancell, the glade guys are cool, and work so hard
[01:37] <ccheney> i think i have all the OOo rc bugs fixed now, just have to the upload :)
[01:37] <rickspencer3> but glade needs a lot more love
[01:37] <rickspencer3> before it'll be really easy to use
[01:38] <rickspencer3> a lot of people get blocked by not being able to figure it out
[01:38] <rickspencer3> ccheney, nice!
[01:38] <rickspencer3> ccheney, please upload asap, let's knock these bugs out
[01:39] <ccheney> ok, i'll upload it as 4ubuntu2 if rene isn't going to upload -5 today
[01:39] <ccheney> there are quite a few other fixes in -5 that would be easier to sync by just taking his changes
[01:40] <robert_ancell> rickspencer3, yeah, I'd love to have to time to help them out.  Been using it for so many years.  It's tough being a dev tool as apps get all the developer time
[01:41] <ccheney> apparently debian ftp-master is broken so i'll just do a 4ubuntu2 for now and catch -5 once he can get it uploaded
[01:42]  * ccheney checks current bug list for any other bugs to fix :)
[01:44] <rickspencer3> simple scan .9.1.0? robert_ancell, I thought it was 1.0 time?
[01:44] <rickspencer3> :)
[01:44] <robert_ancell> rickspencer3, yeah, as soon as people stop finding bugs with their obscure scanners
[01:44] <robert_ancell> by obscure I mean scanners I don't own btw
[01:44] <rickspencer3> ccheney, yeah, get some bugs closed! go go go
[01:44] <rickspencer3> right, is there another definition?
[01:45] <rickspencer3> robert_ancell, I used it the other day, and it was a blessed relief
[01:45] <rickspencer3> I want to hold it up as the standard that our software aspires to (well default install apps)
[01:45] <robert_ancell> rickspencer3, that's what I like to hear!
[01:45] <rickspencer3> I'd like to give the whole image managment scenario the same treatment in 10.10
[01:46] <rickspencer3> oops distupgrade, done rb
[01:46] <rickspencer3> brb
[01:47] <ccheney> oh yea i need to fix F11 bug :)
[01:50] <TheMuso> rickspencer3: Yeah I have used simple-scan a few times now, and its great. No screwing with xsane settings to get what you want. :)
[01:52] <rickspencer3> *sigh*
[01:53] <rickspencer3> gwibber an desktopcouch immediately crashed after I started  gwibber
[02:08] <kenvandine> rickspencer3, can you get a traceback?
[02:08] <kenvandine> grab me a log
[02:08] <rickspencer3> https://bugs.launchpad.net/bugs/548514
[02:08] <rickspencer3> https://bugs.launchpad.net/bugs/548515
[02:08] <rickspencer3> suck
[02:08] <rickspencer3> https://bugs.launchpad.net/bugs/548515
[02:08] <rickspencer3> oh well
[02:08] <rickspencer3> kenvandine, ^
[02:09] <rickspencer3> need anything else?
[02:09] <kenvandine> the first one looks like maybe keyring related
[02:10] <kenvandine> and gwibber nor desktopcouch has changed
[02:10] <kenvandine> so something lower in the stack
[02:10] <kenvandine> can you make bug 548515 public?
[02:11] <rickspencer3> I thought I did make it public
[02:11] <rickspencer3> hold on
[02:11] <rickspencer3> kenvandine, puplic now
[02:11] <rickspencer3> lol
[02:11] <rickspencer3> working too long today
[02:12] <rickspencer3> I least I didn't leave out the "l"
[02:12] <kenvandine> damn
[02:12] <kenvandine> that one should get caught at least
[02:12] <kenvandine> oh it's in gwui.py... humm
[02:13] <rickspencer3> kenvandine, so it's just an uncaught exception for a service time out?
[02:14] <kenvandine> well... yes
[02:14] <kenvandine> but that isn't the bug :)
[02:14] <kenvandine> desktopcouch crashing is the bug
[02:14] <rickspencer3> that is *a* bug
[02:14] <kenvandine> yeah... i know :)
[02:14] <rickspencer3> desktopcouch crashing is another bug
[02:14] <rickspencer3> heh
[02:14] <kenvandine> desktopcouch crashing is interesting there... it is like python dumped
[02:14] <rickspencer3> I asked because it seems the uncaught exception will not bother users in for reals
[02:14] <kenvandine> had you rebooted?
[02:15] <rickspencer3> kenvandine, yes
[02:15] <rickspencer3> dist-upgrade, reboot, first thing I saw
[02:15] <kenvandine> rickspencer3, after release users will not see the error
[02:15] <rickspencer3> that's my point, yes
[02:15] <kenvandine> they just won't see anything
[02:15] <kenvandine> we need to handle that
[02:15] <rickspencer3> so we should fix it, but it's not release critical or anything
[02:15] <rickspencer3> we can fix it in 10.10
[02:15] <kenvandine> :)
[02:16] <rickspencer3> I assumed that the two bugs I logged were two apps responding to the same event
[02:16] <kenvandine> i have a way to display it to the users now... :)
[02:16] <TheMuso> argh! I think we have a race condition with desktop startup and at-spi.
[02:16] <kenvandine> just need to wire it up
[02:16] <rickspencer3> the desktopcouch one is more worisome
[02:16] <kenvandine> rickspencer3, yeah.. indeed
[02:17] <rickspencer3> TheMuso, that bites
[02:17] <TheMuso> rickspencer3: a little. Nautilus, and panels are not accessible for me. The only apps that have accessibility are those that I start once in my session.
[02:17] <kenvandine> rickspencer3, when was your last dist-upgrade?
[02:17] <TheMuso> However sometimes they are accessible, hense the race.
[02:17] <rickspencer3> kenvandine, yes
[02:18] <kenvandine> rickspencer3, *when* :)
[02:18] <rickspencer3> TheMuso, hmmm, so desktop starts up to fast now, huh?
[02:18] <rickspencer3> kenvandine, like 30 minutes ago
[02:18] <TheMuso> rickspencer3: Well things start up before at-spi gets a chance to plant its accessibility properties on the root window.
[02:18] <kenvandine> previous one?
[02:18] <rickspencer3> kenvandine, don't recall
[02:18] <rickspencer3> but days
[02:18] <kenvandine> ok
[02:18] <rickspencer3> do you think these could be false positives?
[02:19] <TheMuso> So once at-spi starts, only new apps that are started see these properties, and since, according to .xsession-errors, nautilus, gnome-panel, and some applets start before at-spi, they miss out on accessibility goodness.
[02:19] <rickspencer3> TheMuso, right
[02:19] <kenvandine> rickspencer3, does it fail again?
[02:19] <rickspencer3> seems this needs fixing for sures
[02:19] <rickspencer3> kenvandine, no ... it worked the second time
[02:19]  * TheMuso is now pondering how we can fix it.
[02:19] <kenvandine> rickspencer3, i hate that!
[02:19] <rickspencer3> kenvandine, shall I reboot?
[02:19] <TheMuso> I might have to talk to Seb or Martin.
[02:20] <kenvandine> rickspencer3, nah
[02:20] <kenvandine> i am sure it was some weird condition that is a pain to repro :/
[02:20] <rickspencer3> kenvandine, you think?
[02:20] <rickspencer3> it seems pretty consistent for me
[02:20] <kenvandine> oh... it happened more than once?
[02:20] <rickspencer3> let me reboot and see
[02:20] <rickspencer3> kenvandine, every time I restart
[02:20] <kenvandine> interesting
[02:24] <rickspencer3> kenvandine, back
[02:24]  * rickspencer3 runs gwibber
[02:25]  * rickspencer3 drums fingers
[02:25] <kenvandine> is this on your eeepc?
[02:25] <rickspencer3> kenvandine, no
[02:25] <rickspencer3> oh
[02:25] <rickspencer3> there;s the gwibber crash
[02:26] <rickspencer3> or *a* gwibber crash, anyway
[02:26] <rickspencer3> notify-osd messages are coming in
[02:27] <kenvandine> so gwibber-service and desktopcouch started fine
[02:27] <kenvandine> but the client crashed
[02:27] <rickspencer3> I guess so
[02:27] <kenvandine> so lets see the crash
[02:27] <rickspencer3> kenvandine, what can I get to help you look into this tomorrow?
[02:27] <rickspencer3> ok
[02:27] <kenvandine> just get me the log
[02:27] <kenvandine> should be enough
[02:28] <kenvandine>  ~/.cache/gwibber/gwibber.log
[02:29] <rickspencer3> kenvandine,
[02:29] <rickspencer3> 2010-03-25 18:55:03,438 - Gwibber GNOME Client - INFO - Running from the system path
[02:29] <rickspencer3> 2010-03-25 18:55:28,292 - Gwibber Dispatcher - ERROR - Failed to raise client (DBusException(dbus.String(u'Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.'),),)
[02:29] <rickspencer3> 2010-03-25 18:58:08,401 - Gwibber Dispatcher - ERROR - Message updated: 550630860_411542430860-4063ce6d845f566097470340186e124b-receive, failed
[02:29] <rickspencer3> 2010-03-25 18:59:12,031 - Gwibber Dispatcher - INFO - Loading complete: 1 - ['Success', 'Success', 'Success', 'Success', 'Success', 'Success', 'Success', 'Success', 'Success', 'Success', 'Success', 'Success', 'Success', 'Success', 'Success']
[02:30] <rickspencer3> 2010-03-25 19:03:50,522 - Gwibber Dispatcher - ERROR - Failed to communicate with https://api.facebook.com/restserver.php?api_key=71b85c6d8cb5bbb9f1a3f8bbdcdd4b05&v=1.0&sig=f0e0f484d7942eadc62fe7d35cecd3f2&format=json&query=%0A++++++SELECT+id%2C+post_id%2C+time%2C+fromid%2C+text%2C+object_id+FROM+comment+WHERE+post_id+IN%0A++++++++%28SELECT+post_id+FROM+stream+WHERE+source_id+%3D+626676204%29+AND%0A++++++++fromid+%3C%3E+626676204
[02:30] <rickspencer3> +ORDER+BY+time+DESC+LIMIT+1%2C100%0A++++++&session_key=d3f38185efec2c363dc3559f-626676204&method=facebook.fql.query&call_id=1269569022000
[02:30] <rickspencer3> 2010-03-25 19:03:50,522 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
[02:30] <rickspencer3> 2010-03-25 19:03:51,912 - Gwibber Dispatcher - ERROR - <facebook:responses> Operation failed
[02:30] <rickspencer3> 2010-03-25 19:04:27,588 - Gwibber Dispatcher - ERROR - Loading failed:  - Traceback (most recent call last):
[02:30] <rickspencer3>   File "/usr/lib/python2.6/dist-packages/gwibber/microblog/dispatcher.py", line 327, in run
[02:30] <rickspencer3>     pool.map_async(self.func, self.iterable, callback=self.callback).get(self.timeout)
[02:30] <rickspencer3>   File "/usr/lib/python2.6/multiprocessing/pool.py", line 418, in get
[02:30] <rickspencer3>     raise TimeoutError
[02:30] <rickspencer3> TimeoutError
[02:30] <rickspencer3> 2010-03-25 19:07:49,892 - Gwibber GNOME Client - INFO - Gwibber Client closed
[02:30] <rickspencer3> 2010-03-25 19:08:13,750 - Gwibber Dispatcher - ERROR - Failed to communicate with https://api.facebook.com/restserver.php?api_key=71b85c6d8cb5bbb9f1a3f8bbdcdd4b05&format=json&call_id=1269569285000&viewer_id=626676204&limit=80&v=1.0&sig=a687da7898a9dbabe8b07e1ec1833a8a&session_key=d3f38185efec2c363dc3559f-626676204&method=facebook.stream.get
[02:30] <rickspencer3> 2010-03-25 19:08:13,750 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
[02:30] <rickspencer3> 2010-03-25 19:08:13,751 - Gwibber Dispatcher - ERROR - <facebook:receive> Operation failed
[02:30] <rickspencer3> 2010-03-25 19:09:18,162 - Gwibber Dispatcher - INFO - Loading complete: 2 - ['Success', 'Success', 'Success', 'Success', 'Failure', 'Success', 'Success', 'Success', 'Success', 'Success', 'Success', 'Success', 'Success', 'Success', 'Success']
[02:30] <rickspencer3> 2010-03-25 19:13:17,735 - Gwibber Dispatcher - ERROR - Failed to communicate with https://api.facebook.com/restserver.php?api_key=71b85c6d8cb5bbb9f1a3f8bbdcdd4b05&format=json&call_id=1269569582000&viewer_id=626676204&limit=80&v=1.0&sig=9b38081b80bc4118d4b1bd68b9fcf7b1&session_key=d3f38185efec2c363dc3559f-626676204&method=facebook.stream.get
[02:30] <rickspencer3> 2010-03-25 19:13:17,738 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
[02:30] <rickspencer3> 2010-03-25 19:13:17,738 - Gwibber Dispatcher - ERROR - <facebook:receive> Operation failed
[02:30] <rickspencer3> 2010-03-25 19:14:07,937 - Gwibber Dispatcher - INFO - Loading complete: 3 - ['Success', 'Success', 'Success', 'Success', 'Failure', 'Success', 'Success', 'Success', 'Success', 'Success', 'Success', 'Success', 'Success', 'Success', 'Success']
[02:31] <rickspencer3> 2010-03-25 19:18:13,747 - Gwibber Dispatcher - ERROR - Message updated: 626676204_103704822998277-4063ce6d845f566097470340186e124b-receive, failed
[02:31] <rickspencer3> 2010-03-25 19:19:04,433 - Gwibber Dispatcher - INFO - Loading complete: 4 - ['Success', 'Success', 'Success', 'Success', 'Success', 'Success', 'Success', 'Success', 'Success', 'Success', 'Success', 'Success', 'Success', 'Success', 'Success']
[02:31] <rickspencer3> 2010-03-25 19:24:32,815 - Gwibber GNOME Client - INFO - Running from the system path
[02:31] <rickspencer3> 2010-03-25 19:24:42,946 - Gwibber Service - INFO - Running from the system path
[02:31] <rickspencer3> 2010-03-25 19:26:25,113 - Gwibber Dispatcher - ERROR - Failed to communicate with https://api.facebook.com/restserver.php?api_key=71b85c6d8cb5bbb9f1a3f8bbdcdd4b05&format=json&call_id=1269570369000&viewer_id=626676204&limit=80&v=1.0&sig=1094750bd2c2a89033298487787f9f39&session_key=d3f38185efec2c363dc3559f-626676204&method=facebook.stream.get
[02:31] <rickspencer3> 2010-03-25 19:26:25,116 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
[02:31] <rickspencer3> 2010-03-25 19:26:25,116 - Gwibber Dispatcher - ERROR - <facebook:receive> Operation failed
[02:31] <rickspencer3> 2010-03-25 19:26:50,664 - Gwibber Dispatcher - ERROR - Failed to communicate with https://api.facebook.com/restserver.php?api_key=71b85c6d8cb5bbb9f1a3f8bbdcdd4b05&v=1.0&sig=b9084a77e6d8f8841ccd87cc00cd2dad&format=json&query=%0A++++++SELECT+id%2C+post_id%2C+time%2C+fromid%2C+text%2C+object_id+FROM+comment+WHERE+post_id+IN%0A++++++++%28SELECT+post_id+FROM+stream+WHERE+source_id+%3D+626676204%29+AND%0A++++++++fromid+%3C%3E+626676204
[02:31] <rickspencer3> +ORDER+BY+time+DESC+LIMIT+1%2C100%0A++++++&session_key=d3f38185efec2c363dc3559f-626676204&method=facebook.fql.query&call_id=1269570394000
[02:31] <rickspencer3> 2010-03-25 19:26:50,664 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
[02:31] <rickspencer3> 2010-03-25 19:26:52,020 - Gwibber Dispatcher - ERROR - <facebook:responses> Operation failed
[02:31] <rickspencer3> 2010-03-25 19:27:14,576 - Gwibber Dispatcher - INFO - Loading complete: 1 - ['Success', 'Success', 'Success', 'Success', 'Failure', 'Failure', 'Success', 'Success', 'Success', 'Success', 'Success', 'Success', 'Success', 'Success', 'Success']
[02:31] <rickspencer3> dang it!
[02:31] <rickspencer3> that was supposed to be a pastbin url :/
[02:31] <rickspencer3> http://pastebin.ubuntu.com/401520/
[02:31]  * rickspencer3 blush
[02:32] <kenvandine> hehe
[02:32] <LaserJock> rickspencer3: now we can all debug together :-)
[02:32] <rickspencer3> yeah
[02:32] <rickspencer3> and decode my social networking credentials too
[02:32] <TheMuso> wooo
[02:33] <TheMuso> pastebin probably would have been better...
[02:33]  * rickspencer3 changes all passwords
[02:33] <rickspencer3> TheMuso, yeah, it was an accident
[02:33] <LaserJock> yeah ... cause I don't have enough peeps on *my* facebook to keep up, I gotta steal yours too
[02:33] <TheMuso> lol
[02:33] <rickspencer3> I pasted into pastebin, then selected the URL, and pasted into there thinking I was copying, then pasted into here
[02:34] <LaserJock> rickspencer3: I find pastebinit is useful for that, I've had similar issues
[02:34] <rickspencer3> hehe
[02:34] <rickspencer3> oh well
[02:34] <LaserJock> as long as seb's asleep you're probably ok
[02:34] <LaserJock> ;-)
[02:34] <rickspencer3> it's not like this gets logged for eternity and then searchable in google cache forever
[02:34] <rickspencer3> hehe
[02:34] <rickspencer3> I was wondering why I didn't get kicked
[02:42] <rickspencer3> kenvandine, is it possible that i am trying to start the UI while the daemon is loading
[02:42] <rickspencer3> and so GetServices() blows up because the daemon is not ready?
[02:46]  * RAOF likes Do's “send to pastebin” action for this sort of thing.
[02:48] <kenvandine> rickspencer3, that shouldn't matter
[02:48] <kenvandine> rickspencer3, that is how gwibber is designed to start... the UI starts the service
[02:48] <kenvandine> except in the autostart scenario
[02:48] <kenvandine> but that doesn't matter either
[02:49] <kenvandine> rickspencer3, but... some of my startup related bug fixes might have been after the last upload
[02:50] <rickspencer3> kenvandine, it looks like all that GetServices does is dump a Python list to JSON
[02:51] <kenvandine> yes
[02:51] <kenvandine> but it requires the daemon to respond
[02:51] <rickspencer3> right
[02:51] <rickspencer3> so looking at the stack trace, it implies that the daemon is not there
[02:52] <kenvandine> i wonder if the service is starting twice
[02:52] <rickspencer3> kenvandine, could me starting manually confict with the autostarting?
[02:52] <kenvandine> and when you hit the service, it is getting the wrong one
[02:52] <kenvandine> there was a problem with that which has been fixed
[02:53] <rickspencer3> kenvandine, I saw there was a related bug that was fix released
[02:53] <rickspencer3> should I try again tomorrow?
[02:53] <kenvandine> if the service wasn't completely up and you started the client it would fire up a second service
[02:53] <rickspencer3> hmmm
[02:53] <kenvandine> which would then figut for the name on dbus
[02:53] <rickspencer3> I see
[02:53] <rickspencer3> so the client crashes
[02:53] <kenvandine> let me see if that was fixed before the last release
[02:53] <kenvandine> yes
[02:53] <rickspencer3> but then the service stands up
[02:53] <rickspencer3> and start ripping to notify-osd
[02:54] <rickspencer3> I try again, and the service is there, works
[02:54] <rickspencer3> so it seems that starting manually before the autostart kicks in will be quite common
[02:54] <rickspencer3> is there a way to set a "starting" flag for the daemon, and wait for it to clear before the client makes calls on it?
[02:55] <rickspencer3> kenvandine, I'll see if there are updates tomorrow and poke at it some more
[02:55] <kenvandine> well that should be fixed though
[02:55] <rickspencer3> ok
[02:55] <kenvandine> rickspencer3, i might not get a release out until the weekend
[02:55] <kenvandine> but we are overdue
[02:56] <rickspencer3> kenvandine, so you think the fix is uploaded but not released?
[02:56] <kenvandine> i am looking
[02:56] <rickspencer3> Version: <IP_ADDRESS>-0ubuntu1
[02:57] <kenvandine> yeah... the fix is in that
[02:57] <kenvandine> hummm
[02:57] <kenvandine> i haven't witnessed it, and been testing it daily in kvm and on the livecd
[02:57]  * kenvandine boots one
[02:58] <rickspencer3> bummer
[02:58] <rickspencer3> kenvandine, maybe time to go to sleep, and take a fresh start tomorrow?
[02:58] <rickspencer3> the solution will come to you in a dream
[02:59] <rickspencer3> and you will be pissed you let me waste all your time tonight ;)
[03:09] <Sarvatt> so it looks like this huge number of bugs about gnome-screensaver-gl-helper crashing with proprietary drivers are all from when it activates after installation before the person reboots. anyone know a way around that? disabling the screensaver until reboot possible?
[03:10] <Sarvatt> activate proprietary graphics drivers in jockey > idle for 5 minutes > screensaver kicks in and a crash report comes up
[03:12] <RAOF> Sarvatt: Well, we'll be disabling apport soon... is that entirely a false-positive?
[03:19] <Sarvatt> yep doesn't actually hurt anything, theres just a large number of bugs under the last few releases about it
[03:20] <RAOF> I guess the other option is to drop the nvidia & fglrx drivers entirely and just ship nouveau's 3d & radeon ;)
[03:21] <Sarvatt> haha funny joke :)
[03:23] <robert_ancell> rickspencer3, just saw your featured IDE response. Am interested on you feedback on the mail I just sent
[03:23] <rickspencer3> what huh?
[03:23] <kenvandine> rickspencer3, well i can't repro in  a VM :/
[03:23] <rickspencer3> robert_ancell, I skipped to the top
[03:23] <rickspencer3> fudge
[03:25] <kenvandine> rickspencer3, i'll try again tomorrow
[03:26] <rickspencer3> kenvandine, ack
[03:26] <rickspencer3> maybe I can set up some debugging hooks here
[03:26] <kenvandine> yeah
[03:26] <kenvandine> lets do that tomorrow
[03:32] <chrisccoulson> Sarvatt, I get the gnome-screensaver-gl-helper crash on my NVIDIA machine quite frequently
[03:32] <chrisccoulson> (or one of them)
[03:33] <rickspencer3> robert_ancell, what do you want me to comment on exactly?
[03:33] <rickspencer3> I thought I was agreeing with you ;)
[03:34] <robert_ancell> rickspencer3, oh, just you've had the experience of doing focus groups with developers etc.  You might actually know how people learn programming :)
[03:35] <rickspencer3> robert_ancell, I commented on the bug
[03:35] <rickspencer3> robert_ancell, i have run hundreds of usability studies on developers
[03:35] <rickspencer3> well, hundreds?
[03:36] <rickspencer3> that would be 10 per year
[03:36] <robert_ancell> rickspencer3, yeah, a lot more than my 0!!
[03:36] <rickspencer3> okay. maybe 50, but watches 100s of developers
[03:39] <rickspencer3> anyway, what was my point?
[03:39]  * rickspencer3 too late ...
[03:42] <robert_ancell> damn sydney people keep talking :)
[03:47] <lifeless> robert_ancell: oh hai
[03:47] <robert_ancell> lifeless, hey
[03:54] <rickspencer3> yo sydney peeps!
[03:54] <rickspencer3> g'night mates
[03:55] <rickspencer3> :)
[03:55] <kenvandine> good night
[03:56] <ccheney> heh i love 8GB ram, plenty to disk cache the entire OOo source tree, so grep returns instantly
[04:13]  * ccheney testing the F11 patch now :)
[04:45] <RAOF> Mmm.  GAPI, I like the cut of your jib!
[04:50] <ccheney> hmm the patch doesn't work, wtf
[04:51]  * ccheney thinks he must not have the proper stuff installed or something else weird
[04:53] <ccheney> the accelerator settings are there but it seems to not be using them, gah
[05:10]  * ccheney thinks he found the place the real settings were hiding
[05:41] <robert_ancell> didrocks, has the gdmsetup patch dropped the session selector somewhere?
[05:52] <robert_ancell> pitti, can you look at bug 445123 and release it if OK.  Patch on my branch, I've tested it and it works
[06:03]  * RAOF seems to have confused gnome-keyring-daemon
[06:37] <pitti> Good morning
[06:37] <pitti> robert_ancell: how are you?
[06:37] <robert_ancell> pitti, hey, good
[06:38] <robert_ancell> pitti, gtg, could you also take a look at feature freeze request for bug 548589
[06:38] <pitti> robert_ancell: I'll look at both
[06:39] <pitti> robert_ancell: gdm> that should be relatively easy, now that we have the gconf mechanism?
[06:39] <pitti> so please feel free to merge
[06:39] <robert_ancell> pitti, yeah for gdm just copied the sound path - so ok to upload?
[06:39] <pitti> I wish we had generalized the d-bus interface for setGconfBoolean(), setGconfString(), etc.
[06:40] <pitti> repeating that code is ugly
[06:40] <pitti> but sure, "good enough" for now
[06:40] <robert_ancell> pitti, yeah, I didn't want to do that because I wasn't sure what information is stored in gconf and then everything would be user readable
[06:40] <pitti> robert_ancell: well, it's just gdm, and you need polkit privs to read/write it anyway?
[06:41] <robert_ancell> pitti, I'm hoping somehow in 10.10 we can reduce the huge pile of patches
[06:41] <pitti> but nevermind for now
[06:41] <pitti> let's not redesign it yet again for lucid
[06:41] <pitti> robert_ancell: right, or perhaps there's a better alternative for our gdmsetup by then
[06:41] <robert_ancell> pitti, well, there's all the other patches too :)
[06:41] <pitti> right, but those are the most painful
[06:44] <robert_ancell> pitti, see you next week!
[06:44] <pitti> robert_ancell: have a good weekend!
[07:00] <TheMuso> pitti: It seems we have a race condition with desktop startup. When accessibility is enabled, sometimes at-spi starts after nautilus/gnome-panel and applets get started, causing only applications loaded after/in the session to be accessible.
[07:00] <TheMuso> pitti: I am pretty sure you could confirm this using accerciser with accessibility turned on.
[07:00] <TheMuso> pitti: My questino is, how do we fix this? :)
[07:01] <TheMuso> question even
[07:02] <pitti> TheMuso: is that dg/autostart/at-spi-registryd.desktop ?
[07:02] <TheMuso> pitti: yes
[07:02] <pitti> TheMuso: hm, that already has X-GNOME-Autostart-Phase=Initialization
[07:02] <pitti> which is as early as it can get
[07:02] <TheMuso> pitti: Yes.
[07:02] <pitti> everything else starts later than that
[07:03] <TheMuso> Well something is not right somewhere. When at-spi loads, it adds accessibility properties to the root window. If GTK sees these properties, it loads accessibility bits. at-spi is obvisouly not ready for nautilus etc when they start, causing them to be inaccessible.
[07:08] <pitti> TheMuso: ah, that's plausible -- it might set the properties later than the other apps start
[07:08] <TheMuso> pitti: I'd say so.
[07:08] <pitti> hm, I thought programs have to register to the GNOME session to signal that they are ready
[07:09] <pitti> but I'd guess that a-s-r would only do so after setting the properties?
[07:09] <pitti> TheMuso: it might be worth adding a sleep(3) after setting the properties and checking with bootchart whether the other stuff is properly delayed
[07:09] <TheMuso> Very likely, yes. Haven't looked at the code myself to be sure. WIll take a look on Monday. I just noticed this race when attempting to use nautilus today.
[07:10] <TheMuso> pitti: do you mean in at-spi-registryd code?
[07:10] <pitti> TheMuso: yes
[07:11] <TheMuso> pitti: Ok, as above, I'll lok Monday. I'm at the end of my week, but came back to try and sort this out. I'll probably need someone else to interpret the boot chart, as graphs/graphics mean little to me. :)
[07:11] <TheMuso> look
[07:11] <pitti> TheMuso: yes, I'm happy to interpret them for you
[07:11] <TheMuso> pitti: ok thanks, will get back to you once I make the above change.
[07:11] <pitti> TheMuso: enjoy your weekend then!
[07:11] <TheMuso> pitti: Will do, thanks.
[07:12]  * pitti goes back enjoying debugging scsi ioctls on remote machines for bug 445852
[07:13] <RAOF> Hm.  What has possessed pulseaudio to consume 700MB of memory?
[07:30] <baptistemm> Hi there
[07:30] <dholbach> didrocks, pitti: I have the same alt-1 problem again, also I configured ctrl-< (convenient on a german keyboard) to fire up a terminal - this doesn't work either
[07:31] <dholbach> hi baptistemm
[07:31] <baptistemm> pitti, do you know bpython interpreter, that awesome
[07:37] <didrocks> good morning
[07:37] <didrocks> baptistemm: hey o/ what's the difference with ipython?
[07:38] <didrocks> dholbach: hi, did you look at the accelerator about groupe window that I mentionned yesteday?
[07:39] <baptistemm> didrocks, apt-get install it
[07:39] <baptistemm> you'll see some neat features
[07:40] <baptistemm> immediatly
[07:40] <dholbach> didrocks: erm
[07:40] <baptistemm> you have completion, you can post code to a pastebin, save the code
[07:40] <dholbach> hi didrocks
[07:41] <didrocks> baptistemm: ipython can do that too (not sure about copying to a pastebin), but the 2 others, right. You can also paste your code
[07:41] <baptistemm> if you have time, give a try anyway
[07:41] <didrocks> ok
[07:42] <dholbach> didrocks: http://paste.ubuntu.com/401641 what you're looking for?
[07:45] <didrocks> dholbach: yeah, not seing anything interesting there. You can maybe unset now as you've done yesterday, and redump the result to make a diff?
[07:47] <dholbach> it seems to think that ">" is "\" or something
[07:50] <TeTeT> asac: morning, another network-manager question: how can I build a specific git version, e.g. commit 6773cc6a639e6698d19b8b6bc91cc6bfa2a1d26e
[07:50] <dholbach> didrocks: paste.ubuntu.com/401647 made alt-1, etc. work again - now I need to figure out why '>' is '\'
[07:51] <dholbach> ok, fixed again - that was a mistake on my part
[07:51] <didrocks> dholbach: ah?
[07:52] <dholbach> didrocks: resetting /apps/metacity made alt-1 work again
[07:52] <didrocks> dholbach: right, but you don't know which on is the guilty one :)
[07:53] <dholbach> yeah
[07:57] <didrocks> pitti: do you have still the select default session in gdmsetup?
[07:58] <pitti> didrocks: hm, apparently that got lost
[07:58] <didrocks> I guess robert removed it in the merge :/
[07:58] <dholbach> thanks didrocks
[08:04] <didrocks> ok, he didn't take the whole file, hence the issue
[08:27] <seb128> hello there!
[08:27] <pitti> hi seb128
[08:27] <sabdfl> howdy seb128
[08:27] <pitti> good morning sabdfl
[08:28] <sabdfl> and to you :-)
[08:28] <seb128> hey pitti sabdfl
[08:28] <seb128> how are you?
[08:29] <sabdfl> doing great thanks. good cloud sprint this week, and some fun stuff in prep for UDS :-)
[08:30] <didrocks> hey seb128
[08:30] <didrocks> good morning sabdfl
[08:30] <sabdfl> howdy
[08:32] <seb128> salut didrocks
[08:37] <aquarius> seb128, https://bugs.edge.launchpad.net/ubuntu/+source/rhythmbox/+bug/538416 is about not being able to drag files between libraries in rhythmbox -- I seem to have set its importance in rhythmbox which I shouldn't have done. Sorry about that.
[08:41] <seb128> aquarius, hey, don't worry that's not an issue
[08:41] <seb128> is the ability to do that important for the store users?
[08:42] <seb128> which leads to an interesting question I have on the rhythmbox topic, do you guys hack on rhythmbox too? ie will you fix rhythmbox issues to make the store work better?
[08:42] <seb128> or help upstreaming those and working on those?
[08:43] <seb128> when I say "guys" it might be you only, I don't know how you team is organized and how many people work on the desktop side or on the server one
[08:44] <aquarius> it would be very nice, yes. At the moment, if you want to move a song from the music store library to your ordinary library (say, because you've filled up your 2GB storage in Ubuntu One), you've got to drag the song out to a folder in Nautilus and then back into the main Music library; you can't just drag it between the two
[08:44] <aquarius> working on the music store on the desktop: me and rodrigo_. Hacking on rhythmbox itself: in theory, sure. Me personally, my C isn't good enough :(
[08:44] <seb128> session restart brb
[08:47] <seb128> re
[08:47] <seb128> sorry about that
[08:47] <seb128> aquarius, I see
[08:48] <aquarius> rodrigo_'s is though ;)
[08:48] <seb128> right
[08:48] <seb128> not sure how busy he is
[08:48] <seb128> but I think it would benefit rhythmbox, our relationship with upstream and store users to improve rhythmbox there
[08:48] <didrocks> seb128: I saw you spoke with robert yesterday about the gdm change, do you know if he has a branch somewhere? (he didn't push and my changes was rejected)
[08:49] <aquarius> very, at the moment, but then so's everybody else :) If we hit a problem which we want fixed in the store and which needs a fix in RB, then we'll certainly look at fixing that problem in RB.
[08:49] <seb128> didrocks, which ones?
[08:49] <rodrigo_> seb128, yes, I wouldn't mind working on it, just that until now, we didn't have the need to fix anything in rhythmbox
[08:49] <seb128> hey rodrigo_
[08:49] <rodrigo_> seb128, until that bug about moving msongs from one lib to the other came
[08:49] <didrocks> seb128: the face browser he uploaded 2 hours ago
[08:49] <seb128> how are you?
[08:49] <seb128> didrocks, I did talk with robert about it?
[08:50] <seb128> didrocks, I'm very tired I think, I don't remember that at all today
[08:50] <didrocks> oh, it was pitti, sorry seb128 :)
[08:50] <seb128> ok
[08:50] <rodrigo_> seb128, fine, and you? :-)
[08:50] <didrocks> just backlogged a lot of things this morning ^^
[08:51] <seb128> didrocks, ~robert-ancell/gdm/bug-445123
[08:51] <seb128> says the bug
[08:51] <seb128> dunno why he didn't push to gdm bzr though
[08:51] <didrocks> seb128: ok, I'll integrate that he redo my changes
[08:51] <seb128> didrocks, he dropped your change?
[08:52] <seb128> didrocks, which one?
[08:52] <didrocks> seb128: right, about the session
[08:52] <seb128> rodrigo_, quite good thanks!
[08:52] <seb128> didrocks, :-(
[08:52] <seb128> didrocks, thanks for spotting
[08:52] <didrocks> seb128: so, I've reintegrated them, pushed and get a not so nice "already uploaded version" :/
[08:53] <didrocks> seb128: in fact, it was spotted in bug #548417
[08:53] <didrocks> I launched gdmsetup and "OMG where is the option?" ;)
[08:54] <seb128> lol
[08:54] <seb128> I though too it looks different before
[08:54] <seb128> but it's not the upload from today
[08:54] <seb128> the issue was there when I tried the sound change
[08:55] <didrocks> seb128: right, that version contained the merged. I didn't notice that the merge was wrong :)
[09:10] <seb128> pitti, how busy are you today?
[09:11] <pitti> seb128: I'm just done with debugging 445852
[09:11] <pitti> (ugh, that took a while)
[09:11] <pitti> seb128: need to leave for 45 mins now for a doctor appointment
[09:12] <pitti> and then I need to review/update our release status; things pile up
[09:12] <seb128> aquarius, rodrigo_: btw for such rhyrhtmbox issues could you open bugzilla bugs at least and try to see on #rhythmbox if they could give hints to solve the issue too
[09:12] <pitti> seb128: I can probably squeeze in some stuff in the afternoon, what's up?
[09:12] <seb128> pitti, hum, ok, no hurry, see you later!
[09:12] <seb128> pitti, retracers
[09:12] <pitti> yes, apparently they need some solid debugging
[09:12] <seb128> we need that
[09:13] <seb128> would be nice to have crashes showing up in launchpad
[09:14] <pitti> I'll try to do that ASAP
[09:14] <seb128> thanks
[09:14] <pitti> we just got staging LP fixed for apport
[09:14] <pitti> so I can at least run the test suite again
[09:14] <pitti> and reproduce stuff there, etc.
[09:14] <dholbach> hi guys
[09:15] <seb128> having a rough idea if the store is stable or not would be useful
[09:15] <dholbach> I have the problem of alt+1 on another machine now :)
[09:15] <dholbach> hello sabdfl
[09:15] <seb128> but without apport crashes being retraceds it's hard to tell
[09:15] <seb128> hey dholbach
[09:15] <seb128> use compiz! ;-)
[09:15] <dholbach> not sure compiz is the answer to that problem ;-)
[09:16] <seb128> ok, so copy your gconf config and unset things until fixing the issue
[09:16] <seb128> and diff
[09:16] <seb128> and figure what setting is to blame
[09:16] <mvo> compiz!
[09:16] <didrocks> 3 times in less than 24 hours, dholbach is a rockstar with alt + 1 :)
[09:16] <dholbach> I like using tabs
[09:18] <seb128> dholbach, do what you did yesterday but with copying before
[09:18] <seb128> so you can diff afterwards and tell us
[09:18]  * mvo uploads r666 of software-center
[09:20] <didrocks> seb128: dholbach tried that this morning: http://paste.ubuntu.com/401647
[09:20] <didrocks> (well, I suggested the same thing of course ;))
[09:21] <seb128> didrocks, ok, you didn't figure which key does that exactly?
[09:21] <seb128> could be in an another gconf subdir
[09:21] <seb128> like g-s-d keybdings
[09:22] <baptistemm> heya
[09:22] <didrocks> seb128: he reset only what is in the diff and it fixed that (he got the same on another machine lately)
[09:23] <baptistemm> To whom can I ask a decision for bug 534702
[09:23] <seb128> didrocks, did unsetting the ctrl-alt-t thing is enough to get it working?
[09:23] <didrocks> dholbach: ? ^
[09:24] <seb128> could be the keybinding he's using
[09:24] <dholbach> seb128: I'm using ctrl-alt-t now
[09:24] <baptistemm> I would like to have it + some patches in 4.63 or 4.63 even if possible
[09:24] <dholbach> I unset /apps/metacity
[09:24] <dholbach> and lots of other stuff already
[09:24] <didrocks> seb128: apart from that, I don't see any other key that can be relevent, weird :/
[09:25] <seb128> dholbach, dunno then
[09:25] <seb128> didrocks, ^
[09:25] <seb128> baptistemm, try subscribing ubuntu-release
[09:25] <seb128> or ask pitti
[09:25] <seb128> or asac
[09:25] <dholbach> http://paste.ubuntu.com/401680/
[09:26] <seb128> dholbach, it's working now?
[09:26] <dholbach> no
[09:27] <seb128> k, I really don't know
[09:27] <seb128> you seem to be the only one to get the issue
[09:27] <dholbach> yeah
[09:27] <seb128> think about what you changes on all your boxes
[09:27] <dholbach> I changed stuff over years :)
[09:27] <dholbach> but I reset a lot already
[09:27] <seb128> it's happening in a guest session?
[09:28] <dholbach> no
[09:28] <seb128> k, so I can't really help you there
[09:28] <dholbach> I hate it when stuff breaks because of "old settings that used to work before" :-(
[09:28] <seb128> backup .gconf
[09:28] <dholbach> yeah, I'll see what I can do
[09:28] <seb128> and delete things until finding where the issue is
[09:28] <dholbach> thanks a bunch everybody
[09:28] <seb128> then diff and find the key
[09:28] <dholbach> yep
[09:28] <dholbach> is there anything other than gconf I should have a look at?
[09:28] <seb128> you can put back the buggy config and try cleaning until part until you find the exact one
[09:29] <seb128> well I would start by moving .gconf on the side
[09:29] <seb128> and see if that fixes it
[09:30] <seb128> if it does you know it comes from there
[09:30] <seb128> then put the dir back and try without the desktop subdir
[09:30] <seb128> and see if that fixes the issue
[09:30] <seb128> etc
[09:30] <dholbach> brb
[09:30] <dholbach> thanks seb128
[09:30] <seb128> you're welcome
[09:31] <seb128> ok, another session restart, brb
[09:32] <dholbach> man, it works now, after I relogged in
[09:47] <baptistemm> thanks seb128
[10:01] <asac> TeTeT: you need to encode the git url in the changelog version. then run ./debian/rules get-current-source
[10:02] <seb128> oh, asac there
[10:02] <asac> hi nse
[10:02] <asac> seb128:
[10:02] <seb128> hey asac
[10:02] <asac> i am sure i didnt do a few things ;)
[10:02] <seb128> asac: there is no chance we get that nm-applet upload in is it?
[10:02] <asac> seb128: yes.
[10:02] <seb128> asac: dx is harazing us about it
[10:02] <seb128> asac: it's due for weeks now
[10:02] <asac> ok
[10:03] <seb128> asac: thanks!
[10:03] <asac> TeTeT: 0.8~rc4~git.20100218t181708.fa9e9b4-0ubuntu1~nmt1  is one example
[10:03] <asac> TeTeT: just use 0.8+git.....
[10:03] <asac> if its after 0.8
[10:03] <asac> if its before 0.8 you can just use the version from above and change the git id (fa9e9b4)
[10:31] <TeTeT> asac: thanks a lot, easier than I thought!
[10:33] <asac> np
[10:35] <pitti> hm, no Chris Coulson today?
[10:37] <seb128> pitti, dunno, he has been joining late recently though, not sure if that's because he shifted time wise, he works late in nights too or if he tries to get work done without irc...
[10:43] <pitti> mvo, seb128: I wonder about bug 150702 - alt+shift-tab works fine here..
[10:44] <mvo> pitti: work for me too, I can have a look after lunch
[10:45] <seb128> pitti, works for me
[10:45] <pitti> ok, that's enough for me; closing :)
[10:45] <pitti> mvo, seb128: thanks
[10:45] <seb128> pitti, look to the upload didrocks did 2 days ago I think I've read something about that one
[10:46] <pitti> ah
[10:46] <mvo> yes, it got only recently uploaded
[10:46] <mvo> I think I commited it a while ago but did not upload myself
[10:47] <seb128> mvo, hey, well done on categories translations, they work now
[10:47] <seb128> in s-c
[10:47] <mvo> seb128: sweet
[10:48] <didrocks> right, it's working for me as well with mvo's changes
[10:49] <mvo> cool
[10:49]  * mvo goes for lunch
[10:54] <pitti> bryceh, tjaalton: for bug 539473, can we drop the b-dep to utempter? Or do we need to fix the package?
[10:56] <seb128> hey pedro_
[10:58] <pedro_> bonjour seb128!
[11:02] <tgpraveen12> is there anything that i can do in this situation:- at spi crashes i click on report problem
[11:02] <tgpraveen12> The problem cannot be reported:
[11:02] <tgpraveen12> The program crashed on an assertion failure, but the message could not be retrieved. Apport does not support reporting these crashes.
[11:03] <tgpraveen12> and the thing is that mouse accessibility hasnt been working since several days in lucid.
[11:06] <pitti> chrisccoulson: good morning, how are you?
[11:06] <chrisccoulson> hey pitti, i'm good thanks, but still quite tired again
[11:06] <chrisccoulson> how are you?
[11:06] <seb128> hey chrisccoulson
[11:07] <chrisccoulson> hey seb128
[11:09] <pitti> chrisccoulson: still no sleep? I'm quite well, thanks; I'm happy that I tracked down this "libatasmart kills SSDs" bug..
[11:10] <chrisccoulson> yay\o/
[11:10] <chrisccoulson> thats good :-)
[11:10] <chrisccoulson> yeah, i didn't get much sleep again last night
[11:10] <seb128> pitti, does it affect lot of disk models on karmic?
[11:11] <seb128> pitti, ie should I recommend people I know to never install karmic on a ssd?
[11:12] <popey> kenvandine: does gwibber work behind a proxy?
[11:12] <pitti> I can't say; the bug has 5 dupes, but quite some subscribers
[11:12] <pitti> seb128: ^
[11:12] <pitti> seb128: karmic-proposed has a workaround now
[11:13] <seb128> ok
[11:13] <pitti> seb128: it easily survives a couple of (or even 50) of those bugs, but it seems to have some long-term effect
[11:13] <pitti> seb128: you can rescue the disk by dd'ing zeros over it, though
[11:13] <seb128> ok
[11:14] <popey> kenvandine: i think 'no' might be the answer after I just tested it
[11:16] <seb128> pedro_, hey
[11:16] <seb128> pedro_, could you get the debug log for this butterfly crash you get?
[11:17] <pedro_> seb128, yep, as soon as i get it again i'll attach the log file to the report
[11:17] <seb128> pedro_, thanks
[11:18] <pedro_> seb128, my pleasure ;-)
[11:28] <tjaalton> pitti: commented on the bug
[11:29] <pitti> tjaalton: thanks
[11:33] <tjaalton> pitti: so it's possible to revert the change, or to fix libutempter
[11:38] <pitti> tseliot, Riddell: can you please give me a quick status about bug 540177? is that blocked by anything, too hard to do, or on the way for b2?
[11:41] <tseliot> pitti: I have a patch that needs some testing. I have just rebuilt kdebase-workspace
[11:42] <tseliot> pitti: and, unless we want plymouth to prevent failsafe x from showing up, we need a new upload of plymouth (Keybuk will deal with it)
[11:43] <pitti> tseliot: thank you
[11:44] <tseliot> np
[11:59] <Ng> asac: are you still mr ubufox? :)
[12:00] <asac> Ng: most likely unfortunately, yes. there are a few bugs, yes.
[12:00] <asac> Ng: anything particular?
[12:01] <pitti> Riddell, kenvandine: can you please update https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus for Kubuntu/DX?
[12:15] <kenvandine> pitti, will do
[12:43] <kwwii> asac: hey, where are the network manager icons these days?
[12:43] <kwwii> asac: trying to figure out the name of the bars which show up for 3g connections
[12:45] <asac> kwwii: i think we dont have a dynamic 3g signal strenght experience yet. dpkg -L network-manager-gnome | grep wwan
[12:45] <asac> /usr/share/icons/hicolor/22x22/apps/nm-device-wwan.png
[12:45] <asac> ?
[12:45] <asac> that one is probably the one
[12:45] <asac> oh
[12:45] <kwwii> asac: but that doesn't have the states
[12:46] <asac> kwwii: yes, 3g doesnt have states atm
[12:46] <asac> wasnt finished upstream for 0.8
[12:46] <asac> unless we have a patch i dont remember
[12:46] <asac> chrisccoulson: wanna check out?
[12:46] <asac> ;)
[12:46] <kwwii> asac: hrm, it seems that when you plug one in blue bars appear
[12:46] <kwwii> asac: and they are not in the Humanity set, so they must come from network manager itself
[12:47] <kwwii> blue bars in the panel is bad :)
[12:47] <asac> hmm. can you send a screen?
[12:47] <asac> i dont have a 3g modem atm
[12:47] <kwwii> asac: nope, I don't have one either
[12:47] <kwwii> asac: sabdfl has one and is experiencing the problem
[12:49] <asac> kwwii: how does the wwan look like?
[12:50] <asac> kwwii: whats our default theme atm?
[12:50] <asac> is the link blue thing in firefox in our default theme?
[12:50] <asac> kwwii: in code i dont see it using anything but the nm-device-wwan for 3g
[12:50] <kwwii> asac: hrm, ok I will try that and see if it fixes the problem
[12:51] <kwwii> asac: yes, the blue link color is a problem with any mixed dark/light theme
[12:51] <kwwii> asac: so yes, it is in our defualt theme
[12:52] <didrocks> seb128: I had a couple of hours and worked on the g-c-c change for button layout. Do you have a bug number handy?
[12:53] <seb128> didrocks, oh nice, wait
[12:53] <didrocks> I need a string freeze exception too as I enable people to revert the change automatically applied
[12:55] <seb128> didrocks, you mean there?
[12:57] <didrocks> seb128: if the theme provide a button layout which is different from your current selection, it applies it (as we talk yesterday), and there is a revert button if people wants to keep his configuration
[12:57] <seb128> pedro_, could you try if you confirm bug #543892?
[12:58] <chrisccoulson> hi asac - sorry, i didn't realise anybody had tried to message me ;)
[12:58] <seb128> didrocks, bug 535322 is your issue
[12:58] <didrocks> seb128: sweet! thanks :)
[12:58] <chrisccoulson> asac - ok, i will look at that
[12:59] <seb128> didrocks, hum, I'm not sure we want that
[12:59] <pedro_> seb128, will have a look
[12:59] <asac> chrisccoulson: heh. np
[12:59] <seb128> didrocks, is that what is done for ie fonts too?
[12:59] <didrocks> seb128: fonts is quite different: font changes aren't applied automatically, you have to select the apply button
[13:00] <chrisccoulson> asac - i'm just about to build firefox locally with the cairo patch
[13:00] <seb128> didrocks, k, I'm not sure I like having a question there
[13:00] <chrisccoulson> hopefully it works ok :)
[13:00] <didrocks> seb128: it's not a question, it's applied automatically
[13:00] <seb128> didrocks, I don't get where is the new string though
[13:01] <didrocks> seb128: the goal is to have that accepted upstream and they won't if we change automatically the user config. Here, we change it and there is the extra pan (like for the font) saying "the theme applied a new layout button, you can revert it"
[13:02] <seb128> didrocks, hum, k, I'm not convinced about that dialog to be honest
[13:03] <seb128> seems to be a question confusing users and getting in the way when changing themes
[13:03] <didrocks> seb128: it's just to avoid the corner case we talked about yesterday, the "you screwed up my home baked configuration"
[13:03] <didrocks> seb128: do you want to give it a try? (pitti too maybe?)
[13:04] <seb128> so when do you display the question? I guess we should do it only when the current configuration is not the default one
[13:04] <seb128> or the one which matches the theme which was selected
[13:05] <kki> hi folks, i'm writing something on policykit for Ubuntu User and I have a short question. Will polkit-gnome-authorization appear in Lucid? It was supposed to be in beta 1: https://bugs.launchpad.net/ubuntu/+source/policykit-gnome/+bug/530829 but I couldn't find it.
[13:05] <seb128> ie it should be displayed if you changed gconf manually before and not if you just use the configuration dialog the normal way
[13:05] <didrocks> seb128: it's only the second atm, it's when the configuration doesn't matches the theme which was selected
[13:06] <pedro_> seb128, yes i can reproduce it, i'm adding the debugging log and comment on the upstream bug
[13:06] <seb128> pedro_, thank you
[13:06] <pitti> didrocks: try what?
[13:07] <didrocks> pitti: the g-c-c changes with the layout button change (but maybe, let's finish to discuss with seb128 first about the change)
[13:07] <seb128> I want other people opinion on that
[13:07] <seb128> I think the dialog will add confusion to solve a corner case
[13:07] <seb128> 99% of users never touch this key
[13:07] <seb128> and will just want the theme to be the one they select
[13:08] <seb128> not have a weird question every time they select a theme to try
[13:08] <didrocks> seb128: it's only when the theme has a layout which differs to want is currently selected
[13:08] <seb128> right, which means every time you switch between our theme an any other one
[13:09] <didrocks> so, it's not something that happends relatively often
[13:09] <didrocks> right
[13:09] <seb128> well seems the basis usecase
[13:09] <seb128> the first time an user will switch theme the question will be there
[13:09] <seb128> since our theme is the only one setting the order
[13:09] <seb128> so it's basically 99% of users who will get it
[13:09] <pitti> kki: we explicitly disabled it, because it's mostly useless these days
[13:09] <didrocks> it's not really a question, just an notice
[13:10] <pitti> seb128, didrocks: oh, *this* kind of layout -- I was thinking too much about keyboard layouts recently
[13:10] <seb128> I think the question should be there only if the user layout doesn't match the previous theme one
[13:10] <didrocks> pitti: sorry that you are haunted by keyboard layout ;)
[13:10] <seb128> ie if the user tweaked the key by hand to really be custom
[13:10] <seb128> does it make sense to you?
[13:10] <didrocks> seb128: right, make sense, I can give it a try
[13:11] <seb128> thanks
[13:11] <seb128> either that or don't display anything
[13:11] <didrocks> (let's try, not sure how we can do that)
[13:11] <seb128> that's like using the effects capplet
[13:11] <seb128> if you use the ui you deal with having values set by it
[13:11] <seb128> if you don't want that you can change the theme in gconf-editor
[13:11] <seb128> well I would not bother
[13:11] <seb128> just declare that the capplet set themes are they are designed
[13:12] <seb128> if you want something else don't use the capplet
[13:12] <didrocks> seb128: I'll just have a look if that can be easily done first, as the logic is almost there
[13:12] <seb128> it's the same for custom gtk colors
[13:12] <kki> pitti: thx, are you going to replace it by some other graphical solution?
[13:12] <seb128> those will be dropped on theme change
[13:12] <pitti> kki: no, there is none ATM
[13:13] <didrocks> seb128: it's gconf value too?
[13:13] <seb128> didrocks, not sure
[13:14] <seb128> didrocks, it's in the detailled option, second tab
[13:14] <didrocks> seb128: for all gconf value that are changed I saw on this window, it's 1. keep gconf value 2. propose user to take the theme one (if 2.) -> 3. propose user to revert last applied one
[13:15] <didrocks> here, I have skipped the 2nd part (which wasn't natural at first in the code)
[13:15] <didrocks> to have it apply from the theme selection
[13:15] <seb128> didrocks, ok, I would just drop the question but it's up to you
[13:15] <didrocks> I guess your proposal about looking if gconf_key != previous theme is a good idea
[13:15] <seb128> I fear we get a pushback from design
[13:16] <didrocks> well, gconf_key != previous theme is for 1% of people
[13:16] <seb128> right
[13:16] <didrocks> if we can please them easily, I give a timeline of 10 min :)
[13:16] <seb128> do that if it's easy
[13:16] <seb128> or drop the question
[13:17] <seb128> sorry but I think there is a good chance design don't like us suggesting applying the ubuntu theme without the button order we decided on there...
[13:17] <seb128> ie if you switch from human to light themes after upgrading for example you should get the new experience
[13:17] <pitti> seb128: are you currently working on the retracers?
[13:18] <pitti> 1000     32671  0.0  0.2  39044  8024 ?        S    00:47   0:00 www-browser https://edge.launchpad.net/+authorize-token?oauth_token=XjcGb1bh38FtZKp2kktH&allow_permission=WRITE_PRIVATE
[13:18] <seb128> not a question you don't really know about
[13:18] <seb128> pitti, no, I tried to subscribe the team to a bug yesterday using the script
[13:18] <kki> pitti: but polkit-1 is still a part of 10.04 since you ported a few apps to it, no? Only commandline...
[13:18] <seb128> pitti, and it screwed, seems to start some text web browser but without content displayed
[13:18] <pitti> seb128: I guess I can kill that one?
[13:19] <pitti> kki: it's been in Ubuntu since 9.10, yes
[13:19] <seb128> pitti, yes
[13:19] <kki> pitti: ok, thanks :)
[13:19] <pitti> seb128: ah, I just saw that I have a launchpad.py bug fix shelved
[13:19] <seb128> pitti, I trying to get out as I could and probably let it running
[13:19] <pitti> but I coudl never test it due to staging not working
[13:19] <seb128> tried
[13:19] <seb128> not sure why it didn't just subscribe the team
[13:19] <seb128> token outdated?
[13:21] <seb128> asac, chrisccoulson: is there a bug about firefox not using startup-notification when start from the gnome-panel launcher?
[13:22] <seb128> ie the busy cursor and an extra entry in the task list are displayed for a while
[13:22] <chrisccoulson> i'm not sure about that
[13:23] <seb128> chrisccoulson, do you get the issue too?
[13:24] <chrisccoulson> seb128 - i do if i launch it from the panel menu, but not from the launcher that i normally use on the panel
[13:24] <chrisccoulson> so i never noticed it until now
[13:24] <seb128> weird
[13:24] <seb128> I do get it from the default launcher there
[13:24] <seb128> on 2 boxes
[13:25] <seb128> it does the same if I dnd the firefox entry which is in the internet category there too
[13:25] <chrisccoulson> seb128 - the launcher on my panel must be an old one
[13:26] <chrisccoulson> it doesn't have StartupNotify=true in it
[13:26] <seb128> k
[13:26] <chrisccoulson> which is why i'd never seen it before
[13:26] <seb128> that's maybe correct
[13:26] <seb128> if firefox doesn't handle it
[13:26] <seb128> ie the firefox one maybe shouldn't have it
[13:26] <seb128> I will check for open bugs
[13:27] <seb128> it's quite visible and worth fixing for lucid
[13:31] <chrisccoulson> seb128 - thanks, i'll take a look at that at some point
[13:31] <chrisccoulson> it might be a trivial fix to make it work properly anyway
[13:33] <pitti> seb128: meh; staging isn't really "fixed", it just fails further along :(
[13:34] <asac> seb128: could be that the XWindow name is wrong ... let me check
[13:35] <seb128> chrisccoulson, asac: it's bug #469752
[13:35] <asac> StartupWMClass=Firefox
[13:35] <asac> we should check what the window class is
[13:36] <seb128> the bug has a comment saying 3.7 has the issue solved so maybe worth checking there?
[13:38] <seb128> chrisccoulson, asac: ^
[13:39] <seb128> can you reassing to xulrunner if that's correct?
[13:39] <seb128> it seems the upstream bug has a trivial patch for it
[13:39] <didrocks> ok, got it work :)
[13:39] <seb128> didrocks, excellent
[13:40] <didrocks> seb128: the default I set for other theme (not having the key) is menu:minimize,maximize,close (was the default on karmic, right?)
[13:41] <seb128> didrocks, I think so
[13:41]  * didrocks boot his VM
[13:44] <asac> chrisccoulson: can you check the startup bug? e.g. if its an issue at all etc.?
[13:45] <seb128> asac: it's an issue for sure and fixed in xul hg so we just have to backport changes
[13:47] <asac> hmm. ok. i sent out all change requests today :)
[13:47] <asac> yeah but ok
[13:47] <asac> i will let chris check that
[13:47] <seb128> k
[13:48] <seb128> still no nm-applet upload to lucid? :-)
[13:48] <tjaalton> asac: your mozilla daily builds are taking all the ppa buildd's ;)
[13:48] <asac> seb128: thats scheduled for today ;)
[13:48] <asac> tjaalton: no. the ppa builders are all gone
[13:48] <tjaalton> asac: https://edge.launchpad.net/builders
[13:48] <asac> tjaalton: we thoguth we fixed it, but seems we didnt. and cr3 was sick leave a few days
[13:49] <seb128> asac: k, thanks
[13:49] <asac> tjaalton: kde/landscape ... lots of other stuff is buildingt
[13:50] <tjaalton> asac: I was going to suggest dropping intrepid and maybe jaunty from the releases to build on
[13:53] <didrocks> seb128: ok, confirming that all is working fine now and the defualt is ok. We should maybe wait uploading the theme first which will revert the gconf key setting and add the key in the index file?
[13:54] <didrocks> seb128: other, if we upload g-c-c first, if user change theme, it won't find the key in the theme file and will take the default position
[13:54]  * didrocks expects a lot of "waow, they revert the order position in the theme" buzz if it's the case ;)
[13:56] <seb128> didrocks, upload I would say it only affects people changing and back and will be fixed today
[13:56] <didrocks> seb128: ok :)
[13:56] <dholbach> I moved .gconf away now and restarted the session - alt+1 still doesn't work :)
[13:56] <seb128> didrocks, kwwii will likely give on an ack for the change later on
[13:56] <seb128> didrocks, kwwii will likely give on an ack for the change later on
[13:56] <seb128> ups
[13:57] <seb128> dholbach, weird
[13:57] <seb128> dholbach, does it work using an another layout?
[14:00] <dholbach> nope
[14:03] <seb128> dholbach, k, so I don't know
[14:03] <seb128> sorry
[14:03] <dholbach> no worries
[14:03] <chrisccoulson> seb128 - we're expecting a theme update today then are we?
[14:03] <seb128> chrisccoulson, light-themes?
[14:04] <seb128> check with kwwii
[14:04] <chrisccoulson> seb128 - yeah
[14:04] <seb128> but didrocks needs a change
[14:04] <seb128> so we will do an upload in any case yes
[14:04] <chrisccoulson> i would like my purple terminals to return for the weekend ;)
[14:04] <seb128> we can sneak your change in too
[14:04] <seb128> let's wait for kwwii to reply
[14:04] <seb128> we will either get an update from him or distro change both your changes to lucid
[14:05] <seb128> works for you?
[14:05] <chrisccoulson> yeah, that should be fine
[14:05] <seb128> cool
[14:05] <seb128> chrisccoulson, did you read the comments I did about xulrunner before?
[14:05] <seb128> the startup notification issue and the upstream change to investigate
[14:05] <chrisccoulson> seb128 - yeah, i did
[14:06] <chrisccoulson> the bug should remain targetted against firefox for now though, as it uses its own local xulrunner
[14:06] <seb128> oh, right
[14:07] <seb128> is the assignee right?
[14:07] <seb128> I don't know him
[14:08] <chrisccoulson> seb128 - yeah, micahg is quite active on the mozillateam
[14:14] <rickspencer3> good morning all
[14:14] <rickspencer3> seb128, pitti hi
[14:14] <pitti> hey rickspencer3
[14:15] <rickspencer3> pitti, just in case there is any ambiguity ...
[14:15] <rickspencer3> no more features for Lucid!
[14:15] <rickspencer3> I won't fixed bug #445123
[14:15] <rickspencer3> this is not a bug, this is a feature request
[14:15] <chrisccoulson> didn't a fix already get uploaded for that?
[14:15] <rickspencer3> chrisccoulson, the new feature did, yes
[14:16] <pitti> yes, Robert fixed it with a hip shot
[14:16] <pitti> rickspencer3: you want it rolled back?
[14:16] <rickspencer3> but who is going to test, translate, and document it?
[14:16] <rickspencer3> and then who is going to respond to the requests to make it work differently
[14:16] <rickspencer3> and what of the regressions or breakages it could introduce
[14:16] <rickspencer3> pitti, I'm a bit confused, I thought we were well past visual freeze, why did the release team ok this?
[14:16] <chrisccoulson> rickspencer3, you don't need to convince me that adding new features now is a bad idea ;)
[14:17] <chrisccoulson> i thought exactly the same thing when i saw the comment last night that it must be  fixed in lucid
[14:17] <pitti> rickspencer3: it wasn't really explicitly requested
[14:17] <rickspencer3> ok
[14:17] <rickspencer3> *isgh*
[14:17] <rickspencer3> sorry
[14:17] <rickspencer3> it seems that each release our users and the engineers ask for better quality as the single most important request
[14:17] <seb128> rickspencer3, hey
[14:18] <rickspencer3> hi seb128
[14:18] <chrisccoulson> it's not like this feature hasn't been missing for many months already
[14:18] <seb128> right I was a bit surprised
[14:18] <rickspencer3> so I think we should roll this back rather than springing it on our translators, documentors, qa team, etcs...
[14:18] <seb128> well
[14:18] <seb128> we added the sound one 2 days ago though
[14:18] <seb128> so it's going through translators anyway
[14:19] <seb128> so depends how we fell about it now
[14:19] <seb128> we can go either way
[14:19] <seb128> + didrocks brough back the une one today
[14:19] <rickspencer3> seb128, that's a good argument for rolling back that change too!
[14:19] <pitti> the default session one has been there for ages
[14:19] <pitti> it was just accidentaly dropped a few days back
[14:19] <rickspencer3> please, for the love of all the is clean and pure ...
[14:20] <rickspencer3> stop changing Lucid
[14:20] <rickspencer3> :)
[14:20] <seb128> pitti, I think he was suggesting that for the sound one
[14:20] <pitti> eww
[14:20] <seb128> rickspencer3, ok, let's do that
[14:20] <seb128> so we keep what we have now?
[14:20]  * pitti clings to the sound checkbox
[14:20] <pitti> [ ] Embarass me
[14:21] <chrisccoulson> is that the german translation? ;)
[14:21] <pitti> it's my mental translation
[14:23] <rickspencer3> seb128, can we propose robert_ancell's gdm patch upstream and see if we can just pick it up in 10.10 in a sync?
[14:23] <didrocks> rickspencer3: the previous gdmsetup patch is in upstream bugtracker for month…
[14:23] <seb128> rickspencer3, the gdmsetup one?
[14:23] <seb128> it's sitting there for one cycle
[14:24] <seb128> they don't seem to be interested
[14:24] <rickspencer3> seb128, yes
[14:24] <rickspencer3> ok
[14:24] <seb128> I think they don't invision it this way
[14:25] <seb128> they want those options in the normal desktop config dialogs
[14:25] <seb128> i.e the sound one would be a "set system default" in the sound capplet
[14:26] <rickspencer3> seb128, ack
[14:26] <rickspencer3> well, we should at least offer, I suppose
[14:26] <seb128> we did
[14:26] <rickspencer3> but that's for after April 15th
[14:26] <rickspencer3> right now ..
[14:26] <seb128> well gdmsetup is waiting for comments for a cycle
[14:26] <tseliot> Riddell, Keybuk: my transition patch for kdm seems to work well and, even though it doesn't have a fade effect like gdm, it makes the transition much smoother. If it passes my local tests with failsafe X and Keybuk's plymouth branch, where can I commit my patch (until a new plymouth is uploaded)? Shall I create my own branch?
[14:27] <Keybuk> is there any reason not to upload it now?
[14:27] <Keybuk> there's nothing in my plymouth update that you need
[14:27] <Keybuk> it will work with the current plymouth
[14:32] <tseliot> Keybuk: well, deactivate + quit doesn't really work well and we do that for failsafe X
[14:33] <tseliot> actually it works, in the sense that plymouth exits and the splash remains on the screen leaving the vt in KD_GRAPHICS mode, therefore you can't see failsafe X
[14:34] <baptistemm> asac, hi
[14:37] <tseliot> Keybuk: I've just noticed this commit: http://bazaar.launchpad.net/~plymouth-dev/plymouth/trunk/revision/1169
[14:37] <tseliot> Keybuk: shall I call reactivate and then quit?
[14:37] <bigon> http://bugs.freedesktop.org/show_bug.cgi?id=26394 << I think I'm hit by that bug on lucid :/
[14:38] <tseliot> bigon: in #ubuntu-x maybe?
[14:38] <Keybuk> tseliot: NO!
[14:38] <bigon> tseliot: thx
[14:38] <Keybuk> tseliot: deactivate + quit doesn't work well for gdm either
[14:38] <Keybuk> tseliot: there's no reason to delay the kdm upload for the plymouth fix for that
[14:39] <tseliot> Keybuk: even if it deliberately breaks failsafe X?
[14:39] <Keybuk> tseliot: why hold off uploading kdm?
[14:40] <tseliot> Keybuk: my question is the answer to your question, unless there's something that I'm missing
[14:40] <Keybuk> tseliot: nothing about your patch changes
[14:40] <Keybuk> if you upload it today, or next week
[14:40] <Keybuk> if you upload it today, and I upload plymouth next week, you don't need to upload again
[14:40] <Keybuk> so why not upload today?
[14:41] <tseliot> Keybuk: yes, in this sense, you're right. There's no real dependency
[14:44] <pitti> seb128: FYI, amd64 retracer crashed on an outdated linux crash (couldn't find the .ddeb for old kernel); fixed in bzr trunk
[14:46] <seb128> pitti, thanks
[14:46] <pitti> seb128: i386 just keeps crashing with a 500 Internal Server Error, I just untag the bug
[14:47] <seb128> pitti, I noticed the error in the log but couldn't browse the bug
[14:47] <seb128> we should try to change that at some stage
[14:47] <seb128> not being able to browse those bugs in launchpad
[14:47] <seb128> ok, thank you
[14:48] <pitti> seb128: in fact, I just fixed another bug in trunk which might be responsible for this (although previous Launchpad versions were much more explicit about it)
[14:48] <pitti> it sometimes tried to reassign an upstream task to a new package
[14:49] <pitti> but anyway, /me merges to ubuntu, updates chroots, and let them go on
[14:49] <seb128> pitti, thanks a lot
[14:51] <superm1> pitti, tseliot mentioned he's working on a few changes to jockey's fglrx handler, and i had mentioned to him that there are a few commits from jockey trunk that should probably be cherry picked too for bugs that they are fixing in ubuntu (and marked as such)
[14:52] <pitti> superm1: I know, I'm on them
[14:52] <pitti> superm1: I want to fix one more bug, then I'll do a new upload
[14:53] <superm1> pitti, cool.  i'm not sure where tseliot is on the fglrx handler changes. i didn't realize more was necessary other than s/xorg-driver-fglrx/fglrx/
[14:54] <tseliot> superm1, pitti: yes, there is also something more that I need to do for nvidia
[14:56] <chrisccoulson> hmmm, weird
[14:56] <superm1> oh, nvidia? so is the fglrx handler ok then?
[14:56] <chrisccoulson> pitti - i built firefox with the cairo patch, and it looks even worse now :-/
[14:57] <pitti> chrisccoulson: uh.. mind putting it into a PPA? might be worth asking slangasek to test it, since he's heavily affected by this
[14:57] <chrisccoulson> i'll try and figure out why it's worse first
[14:57] <pitti> ok
[14:57] <chrisccoulson> it's not following my font settings at all
[15:00] <tseliot> superm1: no, the fglrx handler is disabled while the nvidia still has a few problems
[15:01] <tseliot> nvidia should work fine in most cases
[15:43] <pitti> asac: do you know who is responsible for the mozilla-daily chromium-browser builds?
[15:46] <ogra> pitti, fta i think
[15:46] <pitti> ogra: thanks
[15:47] <pitti> fta: any chance that we could stop the intrepid daily builds? at this point of intrepid's life cycle they are just wasting buildd power, I think; also, perhaps the jaunty ones could move to weekly?
[15:57] <ronoc> pitti: just going to take a closer look at this mute bug - going to log in now to your machine if taht is okay
[15:57] <rodrigo_> jono, heh, facebook doesn't like you neither? :D
[15:57] <jono> rodrigo_, indeed
[15:57] <jono> it seems we are hated by the might book right now
[15:57] <rodrigo_> jono, I guess they've added some non-working, ultra-paranoid filter
[15:57] <rodrigo_> jono, were you writing about telescopes also? :)
[15:57] <pitti> ronoc: sure, go ahead
[15:57] <ronoc> pitti: ta
[15:58] <pitti> ronoc: applet is acting up again right now, if you want to peek into my session
[15:58] <pitti> ronoc: oh, wait; I need a reboot, brb
[15:58] <ronoc> ok cool
[15:59] <jono> rodrigo_, haha
[15:59] <jono> not telescope
[15:59] <jono> telescopes
[15:59] <jono> I may have been penalized for "over evangelizing" if anything, Guy Kawazaki had the same issue
[15:59] <asac> pitti: yes. i agree that we can drop the intrepid builds. i think fta is fine with that. the real problem is that many ppa builders were down for a while this week as cr3 was out of office :)
[16:00] <rodrigo_> jono, :)
[16:01] <jono> rodrigo_, I guess we are officially "The Facebook Two"
[16:02] <rodrigo_> jono, maybe an oportunity to write our own, yeah :D
[16:02] <fta> pitti, asac: yep, no problem to drop intrepid. i wanted to do that once it's officially EOS, which is supposed to be soon (iirc)
[16:02] <kwwii> asac: the awesome bar link color is fixed in the latest theme package
[16:03] <jono> rodrigo_, hehe
[16:03] <fta> pitti, asac: as for jaunty, it's possible to move it to weekly assuming some minor work on drobotik
[16:04] <pitti> ronoc: I rebooted, but it's fine right now; Heisenbug
[16:05] <ronoc> pitti: its an odd one alright. I cannot reproduce it here
[16:05] <ronoc> on my 64bit or 32bit
[16:09] <tseliot> pitti, Keybuk: I've uploaded my fix for bug #540177 (just FYI)
[16:10] <asac> kwwii: sorry. so that upstream bug is a non issue?
[16:10] <asac> fta: jaunty - everyting to weekly (chromium/firefox etc.9?
[16:10] <asac> that would be ok i think
[16:10] <asac> or two per week
[16:11]  * kenvandine -> lunch
[16:11] <rickspencer3> bug #477226
[16:11] <seb128> chrisccoulson, didrocks: light-themes changes uploaded
[16:12] <chrisccoulson> seb128 - awesome, thanks
[16:12] <chrisccoulson> so, purple terminal again later :)
[16:12]  * didrocks hugs seb128
[16:12] <kwwii> asac: well, I fear this bug will make some web pages look bad but until it is tested I can't really know
[16:12] <kwwii> asac: by monday we will know what it breaks or doesn't
[16:14] <seb128> pitti, you can assign the appindicator bug to a contractor too, ie Nafai or jsmith
[16:14] <pitti> seb128: for g-p-m?
[16:14] <seb128> yes
[16:14] <seb128> or any bug with those changes
[16:14] <Nafai> Yeah, I can look at it today
[16:14] <pitti> seb128: too late, I fixed it
[16:14] <Nafai> or even better :)
[16:14] <asac> kwwii: so you changed link color on web as well?
[16:15] <asac> i see. lets keep the pressure up upstream
[16:15] <pitti> it was simple, one minute to look at the code to understand the problem, 5 s to fix the patch, three minutes testing :)
[16:15] <asac> kwwii: please dont post in that bug that all is ok now
[16:15] <seb128> pitti, ok
[16:26] <vuntz> :l
[16:26] <seb128> hey vuntz
[16:30] <rickspencer3> pitti, hi, when you get a chance, could you please look at bug #477226
[16:31] <rickspencer3> make a judgement if it is really an RC bug, and if so, perhaps see if TheMuso and/or crimsun might benefit from some assistance or what not?
[16:37] <crimsun> ugh, there really has to be a better way than trawling through dozens of bug attachments for codec info
[16:37] <crimsun> rickspencer3: I haven't even read that bug report until now
[16:37] <nigelb> crimsun: tweak the hook?
[16:38] <crimsun> nigelb: well, everything that we break ought into separate attachments via the hook is actually combined in upstream's script
[16:38] <crimsun> break out*
[16:39] <nigelb> crimsun: ah
[16:41] <crimsun> rickspencer3: that bug is fixed upstream but requires a backport of the Conexant HDA codec (sound/pci/hda/patch_conexant.c) from linux-2.6.34
[16:42] <crimsun> granted, half the people in that bug report are just saying "me, too" without providing any useful machine info
[16:45] <chrisccoulson> pitti - are you in the release meeting too?
[16:45] <pitti> chrisccoulson: yes
[16:45] <chrisccoulson> ah, ok. i won't bother you for a little while then ;)
[16:49] <rickspencer3> crimsun, do you think it's feasible to fix?
[16:49] <rickspencer3> if it's too risky, just "won't fix" it for Lucid and we'll provide a PPA or something
[17:22] <ronoc> pitti: i don't know what to do with this bug on your machine. I checked your dependencies and all seems fine
[17:22] <pitti> ronoc: do you have more than one soundcard? it might be related to that? (although neither of them is muted)
[17:23] <ronoc> pitti: it appears to be a regression of a bug in libindicate/indicator-sound re image loading that was 'fixed' a week ago
[17:23] <pitti> ronoc: how does it decide which icon to show?
[17:23] <pitti> same thing that determines the slider position?
[17:23] <pitti> since if I just touch that by a bit, it starts working correctly
[17:23] <ronoc> pitti: on my desktop I have an pci outboard and the usual intel on board
[17:24] <ronoc> pitti, yes the volume should set the image aswell as the slider
[17:24] <pitti> ronoc: can I run this in debug mode somehow? that it's verbose about which image it picks, and why?
[17:25] <ronoc> pitti, when the indicator is ready fetches the volume, mute status and device availability
[17:25] <ronoc> pitti
[17:25] <ronoc> pitti: of course - the best thing is to install libindicator-tools
[17:25] <ronoc> apt-get source indicator-sound
[17:26] <ronoc> and the depends
[17:26] <ronoc> make
[17:26] <ronoc> the cd to the src dir
[17:26] <ronoc> unload the indicators from the panel
[17:26] <ronoc> killall indicator-sound-service
[17:27] <ronoc> make sure there is no service running
[17:27] <ronoc> then kick off your own from the src dir ./indicator-sound-service
[17:28] <ronoc> pitti: then you need to run the .so in with the loader -
[17:28]  * kenvandine wishes debugging indicators was a bit simpler :/
[17:30] <pitti> ronoc: (sorry, I'm lagging; still in meeting)
[17:30] <ronoc> pitti: /usr/lib/libindicator/indicator-loader src/.libs/libsoundmenu.so
[17:30] <ronoc> pitti, np
[17:30] <pitti> ronoc: "unload the indicators from the panel"?
[17:30] <ronoc> pitti: right click - 'remove from panel'
[17:30] <pitti> is that "killall indicator-applet"?
[17:31] <pitti> ah, ok
[17:31] <ronoc> pitti: or ^ :)
[17:31] <ronoc> kenvandine: tell me about it :)
[17:31] <pitti> althought that gives you the nice "do you want to restart?" dialog which you can use to restart the d-bus services underneath
[17:32] <ronoc> pitti: but you don't want to do that do you? you want to run it manually and monitor trace ?
[17:32] <pitti> ronoc: dpeends; is the bug in the -service or in indicator-applet process?
[17:32] <pitti> ronoc: ok, I guess I need to do that exercise on Monday
[17:33] <ronoc> pitti: will i think its in libindicator - if you can reproduce this with the loader then it is easy to fix from my end -
[17:33] <ronoc> -i +e
[17:33] <pitti> ronoc: problem is, if I restart the applet manually, it always works
[17:33] <pitti> it only seems to go wrong during session star
[17:33] <pitti> t
[17:33] <pitti> ronoc: could the problem be that the indicator starts earlier than pulseaudio is ready?
[17:34] <ronoc> pitti, yeah this is the exact same as before - no the indicator can handle pulseaudio not being around when starting or flapping
[17:35] <ronoc> pitti: I have 64bit lucid on my desktop now - will try to reproduce this here (10 restarts so far no sign :(
[17:35] <ronoc> very annoying bug
[17:38] <ronoc> pitti, basically we changed the image loading code to handle the theming problems - now image loading is done via libindicator - imagehelper
[17:38] <ronoc> pitti - so this is where this bug started to appear
[17:38] <pitti> ronoc: well, it's not that the image looks broken or anything -- it's just the wrong one
[17:39] <ronoc> pitti: its like the volume update never gets to update the image
[17:52] <chrisccoulson> pitti - the cairo patch makes the firefox fonts worse due to bug 379761
[17:52] <chrisccoulson> and they aren't just a little bit worse...
[17:52] <pitti> chrisccoulson: hm, how did that work with the system cairo?
[17:52] <pitti> chrisccoulson: (and didn't we have two cairo patches?)
[17:53] <chrisccoulson> asac thinks the issue is that it's using 2 copies of cairo (the internal one, plus the system one which gtk links to)
[18:00] <asac> yeah. i am quite sure because i did some deep digging on that
[18:00] <asac> however, from the feedback i got most really complain about the lcd patch
[18:01] <chrisccoulson> asac - do you mean they complain about the lack of the lcd patch?
[18:01] <asac> yes
[18:01] <asac> well. i never mangaed to explain to them that there are two bugs
[18:01] <chrisccoulson> i think they would complain even more if they saw it with the lcd patch ;)
[18:01] <asac> chrisccoulson: only thing we can know is to add the patch ... wait till our dailies pick it up and ask if its good now
[18:01] <asac> chrisccoulson: hah. thats bad
[18:02] <asac> chrisccoulson: so there is no hinting at all? i thought i used the fontconfig default hinting
[18:02] <asac> rather than the gnome-setting
[18:02] <chrisccoulson> hmmm, i'm not sure it's worth even doing that. the fonts are truly horriffic on my laptop since i applied the patch
[18:02] <asac> chrisccoulson: have a screen of that?
[18:03] <chrisccoulson> yeah, one second
[18:04] <pitti> good night everyone
[18:05] <ronoc> later pitti, will try to reproduce over the w.end
[18:05] <ronoc> have a good one
[18:07] <seb128_> 'night pitti
[18:07] <chrisccoulson> asac - http://people.canonical.com/~chrisccoulson/Screenshot-Bug%20%23379761%20in%20firefox%20%28Ubuntu%29:%20%E2%80%9CMASTER%20-%20FF%203.5%20font%20hinting%20does%20not%20honour%20gnome-settings%E2%80%9D%20-%20Mozilla%20Firefox.png
[18:07] <chrisccoulson> oops
[18:07] <chrisccoulson> should have shortened the link
[18:08] <asac> chrisccoulson: can you fix it in fontconfig?
[18:08] <chrisccoulson> i'm not sure if i know enough about fontconfig to do that yet ;)
[18:09] <asac> chrisccoulson: http://paste.ubuntu.com/
[18:09] <asac> chrisccoulson: use that for .fonts.conf
[18:09] <asac> then restart ffox
[18:11] <chrisccoulson> asac - did you mean to post a link with some content? ;)
[18:12] <asac> chrisccoulson: oh
[18:13] <asac> chrisccoulson: pastebin claimed its "insecure content" and refused to submit it ;)
[18:13] <asac> chrisccoulson: here it is: http://paste.ubuntu.com/401941/
[18:13] <asac> it starts with <?xml ...
[18:13] <asac> ;)
[18:13] <asac> the rest was to trick paste.ubuntu.com
[18:13] <chrisccoulson> ok, just trying now
[18:13] <asac> chrisccoulson: if that isnt good, try hintfull rather than slight
[18:21] <chrisccoulson> asac - hintslight doesn't make much difference, but hintfull seems to make the fonts look better, but very skinny
[18:21] <asac> chrisccoulson: yes so for you it seems that our default in ubuntu is wrong
[18:22] <asac> i wanted to go to hintfull in general, but got pushback
[18:22] <chrisccoulson> hmmm, but now is probably not a good time to change that
[18:25]  * ccheney wanders off to find lunch, bbs
[18:35] <chrisccoulson> asac - hintmedium seems to be a reasonable compromise
[18:39] <asac> chrisccoulson: yes. problem is that depends on the font you are using and the screen. there is no golden rule unfortunately
[18:40] <chrisccoulson> asac - i'm slightly confused about how all the different font components fit together (eg, fontconfig, freetype etc)
[18:40] <asac> chrisccoulson: its a mess ;)
[18:40] <chrisccoulson> you seem to be quite knowledgeable about fonts ;)
[18:40] <asac> chrisccoulson: yes, i ended up in that trap at some point ;)
[18:40] <mdeslaur> chrisccoulson: the screenshot you just pasted does not have a working lcd filtering patch
[18:40] <chrisccoulson> and also why changing .fonts.conf changes firefox but not anything else ;)
[18:41] <asac> chrisccoulson: right. thats becase gnome-settings win over fontconfig
[18:41] <chrisccoulson> mdeslaur, i'm just about to try yours
[18:41] <asac> the only solution is to make gnome frontend to configure using fonts.conf
[18:41] <chrisccoulson> ah, ok, that makes more sense
[18:41] <chrisccoulson> so, g-s-d is setting X properties which are picked up by gtk isn' it?
[18:41] <asac> there was some effort in the past, but thats difficult
[18:42] <asac> chrisccoulson: yes. but thats not optimal. problem is that different fonts have different perfect settings on different dpi
[18:42] <asac> so chinese fonts often dont need same hinting as latin fonts etc.
[18:42] <chrisccoulson> ah, ok
[18:42] <chrisccoulson> and i assume that fontconfig is more flexible here?
[18:42] <asac> one solution is to add a virtual config for fontconfig imo
[18:43] <asac> that loads the xsettings at level 50
[18:43] <asac> and then make cairo only obey fontconfig
[18:43] <asac> in that way we could overload the xsettings for special fonts still
[18:43] <asac> so e.g. /etc/fonts.d/50-x-settings.conf
[19:26] <jjardon>  Hello, Could somebody take a look to this bug: https://bugs.launchpad.net/ubuntu/+source/gtk-doc/+bug/526794
[19:27] <jjardon> I have installed 1.11 in my lucid, but 1.13 seems to be available in launchpad
[19:27] <jjardon> strange
[19:30] <mdeslaur> jjardon: it FTBFS: E: Couldn't find package highlight
[19:31] <jjardon> mdeslaur, install highlight
[19:33] <jjardon> here the version is 1.13: https://launchpad.net/ubuntu/lucid/+source/gtk-doc
[19:33] <mdeslaur> jjardon: gtk-doc depends on highlight, and highlight is in universe, so it failed to build
[19:33] <jjardon> am
[19:34] <jjardon> I see the problem now, how can be this fixed? (gtk-doc is part of GNOME release)
[19:35] <james_w> either highlight should be approved for main, or gtk-doc should be changed to disable highlighting again
[19:35] <mdeslaur> jjardon: it's probably too late for lucid, but you could either see if gtk-doc can be built without highlight, or get highlight approved for main with a MIR
[19:38]  * jjardon checkin gtk-doc code
[19:39] <didrocks> time to enjoy the week-end. See you everyone :)
[19:40] <jjardon> gtk-doc can be compiled without  highlight installed
[19:40] <jjardon> you only need vim
[19:42] <chrisccoulson> have a good weekend didrocks
[19:43] <jjardon> mdeslaur, should I file a bug?
[19:44] <mdeslaur> jjardon: you need to file a FFe if you want it to go in lucid
[19:46] <jjardon> mdeslaur, Could you point me to some documentation to how make that?
[19:53] <mdeslaur> jjardon: https://wiki.ubuntu.com/FreezeExceptionProcess and then https://wiki.ubuntu.com/SponsorshipProcess
[19:53] <jjardon> mdeslaur, thank you
[19:57] <seb128> there is no need of a ffe to fix a source not building
[19:58] <mdeslaur> oh, cool, I wasn't 100% sure on that point
[19:58] <mdeslaur> jjardon: ^
[19:58] <seb128> it's rather a rc bug to have the lucid version not building
[20:01] <jjardon> seb128, sorry, Should I have to do "anything" then? ;) I already filled this bug: https://bugs.launchpad.net/ubuntu/+source/gtk-doc/+bug/526794
[20:02] <jjardon> oh, seems to be fixed
[20:03] <jjardon> thanks james_w ;)
[20:03] <seb128> jjardon, we have the new version for weeks, it didn't build because highlight is in universe
[20:04] <seb128> we either need to make it build without it
[20:04] <seb128> or get highlight promoted in lucid
[20:04] <jjardon> seb128, I don't have highlight in my machine and I can compile gtk-doc without problems (no extra option passed)
[20:05] <seb128> so somebody needs to open a bug on the debian bts about dropping the build-depends
[20:05] <jjardon> seb128, git version here, maybe the requirement was relaxed in some commit
[20:05] <seb128> so we need to backport this commit
[20:06] <seb128> http://packages.qa.debian.org/g/gtk-doc/news/20100114T092125Z.html
[20:06] <seb128> "Enable syntax highlighting for source code."
[20:06] <seb128> guess that's the reason
[20:07] <jjardon> viewing configure.ac, you can enable it with a recent version of vim
[20:07] <jjardon> seb128, http://git.gnome.org/browse/gtk-doc/tree/configure.ac#n99
[20:08] <seb128> we either need to turn that off or see if we can get it to build without universe components
[20:11] <jjardon> seb128, I tried here: if you don't have vim ot highligh instaled, you still can make ./autogen.sh && make without any problems (autotools auto disable the feature)
[20:11] <seb128> right
[20:11] <chrisccoulson> excellent, my gf has gone out for the evening. time for me to order some unhealthy food
[20:12] <seb128> chrisccoulson, lol
[20:12] <mdeslaur> lol
[20:12] <mvo> *yumm*
[20:12] <seb128> jjardon, the build-depends is probably no required
[20:12] <seb128> mvo, it's probably not vegetarian food either :p
[20:13] <mvo> french fries, very unhealty, still yummy :)
[20:13] <seb128> ;-)
[20:13]  * seb128 hugs mvo
[20:14]  * mvo hugs seb128
[20:15] <fta> could someone have a look at bug 539246?
[20:22] <jjardon> have to go, thank you for your support :)
[20:24] <kenvandine> my laptop is seriously about to start smoking
[20:24] <kenvandine> gwibber has my CPU pegged... and trying to debug :)
[20:25] <bencc> where can I report a bug in gedit?
[20:30] <kenvandine> bencc, run "ubuntu-bug gedit"
[20:37] <bencc> kenvandine: didn't know about that. thanks
[20:39] <kenvandine> bencc, np... thanks for filing bugs!
[21:00] <Nafai> hrm, gwibber doesn't seem to be posting
[21:00] <Nafai> kenvandine: any logs or such I should look at?
[21:01] <kenvandine>  ~/.cache/gwibber/gwibber.log
[21:02] <kenvandine> Nafai, i heading out right now though... but should be around later tonight if you want me to look
[21:02] <kenvandine> or file a bug
[21:02] <Nafai> sure thing, thanks
[21:02] <kenvandine> hopefully it will be obvious :)
[21:02] <Nafai> yeah
[21:06] <Nafai> kenvandine: Simple, for some reason friendfeed was selected as the only one to send messages, instead of Twitter :)