[09:35] <pitti> Good morning
[09:37] <seb128> chrisccoulson, ArneGoetje: hey, how is the langpack changes for the firefox search in .1 going?
[09:37] <chrisccoulson> hi seb128, are you with rick atm?
[09:38] <seb128> chrisccoulson, hey, yes, meeting for lucid .1
[09:38] <seb128> chrisccoulson, do you need something?
[09:39] <chrisccoulson> i was going to suggest that i come and visit ;)
[09:40] <seb128> chrisccoulson, I don't think it's required, we are going through the buglist and iso validations
[09:40] <seb128> chrisccoulson, we are just late and we need that change in today or tomorrow
[09:41] <chrisccoulson> seb128 - the main issue is that we already have the langpacks for .1
[09:41] <seb128> we suggested doing a manual updates to the concerned languages
[09:41] <seb128> not a new export
[09:44] <ArneGoetje> seb128: yep, I just need the data
[09:45] <seb128> chrisccoulson, ^ do you have those datas?
[09:45] <chrisccoulson> seb128 - i do: https://pastebin.canonical.com/34805/
[09:46] <seb128> chrisccoulson, thanks, can you work with ArneGoetje to get that in?
[09:48] <baptistemm> hello
[09:50] <chrisccoulson> seb128 - yeah, sure. i think we're ok now
[09:56] <seb128> chrisccoulson, ok, thanks, let me know when it's uploaded
[09:56] <fta> seb128, the gtk/cairo rendering but i had with chromium, the clokc applet and many other apps is bug 605979
[09:56] <seb128> or ready for upload
[09:56] <ubot2> Launchpad bug 605979 in gtk2-engines-murrine (Ubuntu) "Buttons rendered wrong (with white background) with nvidia-current (affects: 3) (heat: 18)" [Undecided,Confirmed] https://launchpad.net/bugs/605979
[09:56] <seb128> fta, thanks
[09:56] <fta> seb128, the debdiff fixes it all for me
[09:57] <seb128> fta, ok, so it's video driver specific for some reason
[09:57] <seb128> that explains why I didn't get it
[09:58] <fta> but properly closing the surfaces looks like a good idea anyway
[09:58] <fta> as cairo 1.9 is now enforcing it
[10:00] <seb128> fta, right
[10:56] <ArneGoetje> chrisccoulson: language-pack-zh-hans in lucid-proposed
[13:14] <kenvandine> rodrigo_, bummer that you won't be making it to the rally
[13:18] <rodrigo_> kenvandine, yeah, sucks, but going on Wed (arriving at 6PM) and getting back on Friday, just for 1.5 days, was not worthy, so trying to follow it from here
[13:18] <kenvandine> yeah
[13:19] <rodrigo_> kenvandine, just saw you merged my branch, thanks!
[13:19] <kenvandine> np
[13:20] <rodrigo_> kenvandine, btw, for u1-client, dobey told me that he just gets lp:ubuntu/u1-client, does the package from there, dput's the package, and then the branch is merged automatically to lp:ubuntu/u1-client
[13:20] <rodrigo_> kenvandine, should I do the same for couchdb-glib/evo-couchdb, or should I keep using the ubuntu-desktop branch?
[13:20] <kenvandine> rodrigo_, either way...
[13:21] <rodrigo_> so, the ubuntu-desktop branch is merged from the lp:ubuntu... one?
[13:24] <kenvandine> rodrigo_, no
[13:24] <kenvandine> lp:ubuntu/couchdb-glib is from the automatic imports
[13:24] <kenvandine> so no common ancestor
[13:25] <rodrigo_> ok, so if I do it dobey's way, yhe ubuntu-desktop branch will be out of date, right?
[13:25] <kenvandine> yeah
[13:25] <kenvandine> it will be abandoned basically
[13:25] <rodrigo_> ok, will keep using that then
[13:25] <rodrigo_> ah
[13:26] <kenvandine> but either way
[13:36] <TheMuso> robert_ancell: http://live.gnome.org/GAP/AtkGuide
[14:00] <dobey> rodrigo_: i try to avoid maintaining multiple package branches if possible
[14:00] <dobey> or when possible, rather
[14:27] <dobey> kenvandine: do we really need the ~ubuntu-desktop pkg branches for u1?
[14:28] <kenvandine> dobey, no
[14:30] <dobey> kenvandine: should we make them 'disappear' ? :)
[14:31] <seb128> dobey, hey
[14:32] <dobey> seb128: hey dude. how's prague?
[14:32] <seb128> dobey, did you have any bug to track your ubuntuone-client lucid sru?
[14:32] <seb128> dobey, it's going fine so far I think ;-)
[14:32] <seb128> dobey, you got 8 bugs fixed and verified in the previous upload
[14:32] <seb128> but you added an another upload with no bug in the changelog
[14:33] <seb128> which drops patches which should have been dropped in the previous upload?
[14:33] <seb128> (seeing the changelog)
[14:33] <seb128> dobey, the result is that the upload with the 8 bug fixes got stucked and will likely not be on lucid .1
[14:33] <dobey> let me look again, it's been abit since i uploaded it :)
[14:34] <dobey> seb128: the second upload has those bug fixes
[14:34] <seb128> right
[14:34] <seb128> but why did you do a new upload?
[14:34] <dobey> seb128: the second upload removes a patch i forgot to remove with the first upload, and a fix for a lintian error
[14:35] <seb128> there is no bug associated with it explaining what was wrong with the previous one
[14:35] <dobey> because the first upload was FTBFS
[14:35] <seb128> hum
[14:35] <seb128> that's concerning
[14:35] <dobey> because i forgot to remove the patch
[14:38] <seb128> oh ok, the testing was done on the second upload
[14:38] <seb128> you should use -v when doing the source build next time
[14:38] <dobey> -v?
[14:38] <seb128> to include both changelog entries
[14:38] <dobey> ah ok
[14:38] <seb128> debuild -S -v<lucid_updates_version>
[14:39] <seb128> you would have both changelog entries listed
[14:39] <seb128> which wouldn't have confused the sru summary etc
[14:39] <seb128> thanks
[14:42] <dobey> seb128: ok, now i know, and knowing is like 150% of the battle or something :)
[14:42] <seb128> hehe
[14:42] <seb128> I'm trying to get the update in .1
[14:44] <seb128> dobey, also the keyring issue is still there and is a bug in python-gnomekeyring
[14:44] <seb128> I get the same issue when using the gnome-python-desktop examples
[14:44] <seb128> I tried in a guest session
[14:44] <seb128> I can't find the translated name in any source or translation though
[14:44] <dobey> seb128: ok, that's weird
[14:44] <seb128> so I'm puzzled about it
[14:45] <dobey> since python-gnomekeyring is just a very slim wrapper over the C api. I don't think there's any "real" code in it
[14:45] <seb128> right, which is why I'm puzzle
[14:45] <seb128> the name is coming from somewhere though
[14:50] <dobey> what is the french version that's breaking it?
[14:51] <seb128> it's "par_défaut"
[14:51] <seb128> i.e par_défaut.keyring
[14:53] <dobey> oh, wow, i didn't realize that the lp translations ui was this bad
[14:55] <seb128> dobey, /usr/share/doc/python-gnomekeyring/examples/keyring.py
[14:55] <seb128> you can use that as an example to trigger the bug
[14:55] <seb128> or run ubuntuone-preferences
[14:56] <dobey> ok, gnome-python-desktop doesn't have any translations in lp it seems
[14:57] <seb128> it's only bindings
[14:57] <seb128> it doesn't have any upstream either
[14:57] <dobey> yeah
[15:02] <seb128> #. TRANSLATORS: This is the name of an automatically created default keyring.
[15:02] <seb128> msgid "Default"
[15:02] <seb128> msgstr "Par défaut"
[15:03] <seb128> libgnome-keyring
[15:03] <seb128> #: ../library/gnome-keyring.c:2685
[15:03] <dobey> lovely
[15:03] <seb128> so it's a libgnome-keyring issue
[15:03] <dobey> i wonder why that didn't show up in my search
[15:03] <dobey> bad launchpad
[15:03]  * seb128 opens gnome-keyring.c:2685
[15:03] <seb128> ../library/gnome-keyring.c:2685
[15:03] <seb128> ups
[15:03] <dobey> yeah, gnome-keyring bug
[15:13] <RAOF> libgnome-keyring also has some awkward threading issues (ie: it sometimes dies when I try to access it from a thread other than the gtk main thread).  This is annoying.
[15:20] <dobey> RAOF: welcome to gtk+ development.
[15:20] <dobey> RAOF: i think you missed all the fun immediately before the lucid release, with the keyring threading issues.
[15:21] <RAOF> No, I didn't miss that at all.
[15:21] <dobey> ah
[15:22] <RAOF> But libgnome-keyring _used_ to be threadsafe, and then 2.30 broke it.
[15:22] <RAOF> (Which made gnome-keyring-sharp non-threadsafe, and stuff was depending on it)
[15:25] <dobey> oh, i am fully aware
[15:26] <RAOF> And then the secret-store DBus api will eventually happen, and someone will want to just go ahead and implement that in C# rather than wrapping libgnome-keyring.  And the magical ponies will dance on unicorns.
[15:30] <dobey> the secret-store dbus api has happened. gnome-keyring is just the only thing that implements any of it right now
[15:31] <dobey> and using dbus in a gtk+ app without having the dbus stuff in the glib main thread can be quite painful
[15:33] <seb128> slomo, do you know if somebody is packaging libdmapsharing or libpeas in Debian?
[15:33] <seb128> robert_ancell, ^
[15:33] <seb128> those are the ones we would need, first one for rhythmbox daap, the second one for totem
[15:33] <seb128> but the second is probably not an issue for now since we don't update
[15:53] <slomo> seb128: i'm interested in both but don't have the time
[15:53] <slomo> seb128: no idea if someone else is going to package them
[15:53] <seb128> slomo, ok, we might do those
[15:53] <slomo> so you'll have a gtk+3 totem?
[15:53] <seb128> slomo, btw did you see that robert_ancell started on gdk-pixbuf?
[15:54] <slomo> yes
[15:54] <seb128> slomo, no, as said before " but the second is probably not an issue for now since we don't update"
[15:54] <seb128> slomo, libdmapsharing is required in the current rhythmbox
[15:54] <slomo> ah
[15:54] <slomo> good
[15:55] <robert_ancell> ok, I will have do those two
[16:58] <and471> vish, mpt, afternoon
[17:01] <and471> mpt, vish, sorry gents, my graphics card crashed :(   afternoon :-)
[17:03] <mpt> hi and471
[17:04] <mpt> bbl
[17:09] <vish> and471: hey.. :)
[17:10] <vish> and471: are you on maverick , or lucid?  [crash..]
[17:15] <and471> vish, lucid
[17:16] <and471> vish, what is the bug?
[17:16]  * and471 just had an amazing day paintballing
[17:16] <vish> and471: nah , i was wondering about your bug/crash :)
[17:16] <and471> vish, oh ok :)
[17:44] <dobey> james_w: ping?
[17:45] <dobey> james_w: the auto-importer seems to have broken again. new ubuntuone-storage-protocol uploaded last week, but bzr branch still has the previous release
[17:45] <dobey> james_w: do you have any idea what's causing these issues to pop up with the imports?
[17:56] <fagan> whats the package name for the time indicator?
[17:56] <fagan> Its saying friday when its tuesday
[17:56]  * fagan thought he was going crazy
[17:58] <fagan> ah I got it
[17:58] <dobey> fagan: i've had some of the applets in my panel sort of 'freeze' up at times. like the normal clock applet even.
[17:58] <dobey> not sure what is wrong though :(
[17:58] <fagan> dobey: so its a known issue
[17:58] <fagan> hmmmm
[17:59] <jpds> fagan: Surely it being Friday should be a good thing?
[17:59] <fagan> jpds: well am supposed to do something on friday so me thinking its friday kinda wasnt helpful :)
[18:00] <dobey> fagan: the clock applet will stop 'updating' the text for the time, in the panel. but i can click on it and open the calendar, and prefs and stuff. switching to 24h time, and back to 12h 'fixes' the problem for me
[18:00] <dobey> at least, until it happens again
[18:00] <fagan> oh ok
[18:01] <dobey> yesterday, it was showing 11:03 for almost an hour. i looked up and thought "i'm pretty hungry, it's GOTTA be later than that" :)
[18:01] <dobey> and of course, it was noon already :(
[18:01] <fagan> dobey: I suppose its not stable yet for a reason
[18:01] <fagan> the time works fine for me
[18:02] <fagan> its just the date
[18:02] <fagan> and the day
[18:02] <dobey> fagan: i was getting this in lucid.
[18:03] <dobey> fagan: this is with the upstream clock applet. i'm not using the indicator
[18:03] <fagan> wow thats weird
[18:03] <dobey> fagan: but i have no idea why it's breaking
[18:03] <dobey> i thought it was a theme issue, but that doesn't seem to be the case
[18:03] <fagan> does upstream?
[18:03] <fagan> know I mean
[18:08] <dobey> i don't know if it's an upstream issue or an ubuntu issue
[18:08] <dobey> i don't know if there's a bug for it either, i haven't had time to deal with it beyond just changing the pref to poke it back into reality
[18:09] <dobey> err
[18:09] <dobey> i don't know if it's an upstream issue or an ubuntu issue
[18:09] <dobey> since you probably missed that :)
[18:09] <fagan> I just got a nice crash in empathy
[18:09] <fagan> hehe
[18:09] <fagan> empathy + IRC = Bad
[18:10] <dobey> heh
[20:52] <fagan> why is it so quiet in here today
[20:52] <fagan> is it a holiday or something?
[20:53] <dobey> no
[20:53] <dobey> but the platform rally is happening this week
[20:53] <fagan> ah ok
[20:53] <dobey> so maybe it will be a little quieter than normal :)
[20:53] <fagan> I was wondering where everyone was
[20:53] <fagan> I wanted to ping mvo but he wasnt online all day
[20:54] <fagan> Should have finished a patch for him last week but have it more or less finished now for him to have a look at
[20:54] <dobey> ah. i suspect he is having beer now
[20:54] <fagan> lol probably
[20:55] <fagan> :)
[20:55] <dobey> but i am not at the rally, so i don't know anything about what's going on for sure :)
[20:55] <dobey> and if i was there, i'd probably be having beer instead of chatting with you, right now, too :)
[20:55] <fagan> lol
[20:55]  * fagan feels like getting a beer now but has none :(
[20:56] <dobey> i don't have any either :(
[20:57] <fagan> tea will have to do
[20:58] <fagan> you know what would be insane if ubuntu used mumble instead of IRC
[20:58]  * fagan has weird thoughts like this sometimes
[20:59] <fagan> Mumble is voice chat if you didnt know. Imagine #ubuntu in voice chat
[20:59] <fagan> lol
[20:59] <dobey> heh
[20:59] <dobey> yeah i know what mumble is
[20:59] <dobey> yeah, i could see random people joining and speaking russian
[20:59] <fagan> My heroes of newerth clan just got a private server
[21:00] <fagan> and we have no russians
[21:00] <fagan> :)
[21:00] <dobey> well, you aren't #ubuntu :)
[21:00] <fagan> just english speeking
[21:00] <fagan> it crashes empathy IRC
[21:00] <dobey> there's a telepathy plug-in for mumble?
[21:00] <fagan> nope
[21:01] <dobey> or #ubuntu crashes empathy?
[21:01] <fagan> yep
[21:01] <dobey> nice
[21:01] <dobey> good thing i don't use empathy, or go into #ubuntu :)
[21:01] <fagan> When empathy goes onto the room it freezes trying to load the people list
[21:02] <fagan> then it crashes the client when it gets too many messages
[21:02] <fagan> plus it uses a lot of cpu when its on #ubuntu too
[21:02] <fagan> its really busy there
[21:02] <fagan> I think im the only one who uses empathy as an IRC client
[21:02] <fagan> in the world
[21:02] <fagan> :)