[08:02] <pitti> Good morning
[08:02] <pitti> crimsun: oh, sorry; well, let's just drop or lower the delay then
[08:03] <RAOF> Good afternoon pitti :)
[08:04] <pitti> didrocks, desrt: valac is in main; shouldn't it be?
[08:04] <pitti> hey RAOF, had a good weekend?
[08:04] <RAOF> Pretty good, yaeh.
[08:04] <seb128> pitti, it is, indicator build-depends on it
[08:04] <seb128> to build the gir binary
[08:04] <pitti> am I just not fully awake yet, or do fonts look very ugly since today?
[08:05] <RAOF> I got me a shiny new camera for my birthday :)
[08:05] <seb128> pitti, I didn't upgrade yet but I upgraded on saturday
[08:05] <seb128> looks fine there
[08:07] <seb128> pitti, the retracers emailing every hour is that to say they are running? ;-)
[08:07] <slomo> pitti, didrocks, desrt: also you should really get vala 0.8.0, it fixes *many* bugs and is the start of a stable release series (while 0.7) wasn't
[08:07]  * seb128 cleans some 118 retracer emails
[08:07] <pitti> seb128: sorry about that; no clue why this now happens, but I'll look into this today
[08:07] <seb128> hey slomo
[08:08] <slomo> hi seb128 :)
[08:08] <seb128> slomo, it's month after new source freeze I think buzztard can wait next cycle
[08:08] <slomo> ok, that's fine :)
[08:08] <seb128> slomo, we have higher importance things to work on one week before lucid freeze than getting new untested sources and making sure they do something useful ;-)
[08:09] <pitti> seb128: I was barely at home during WE, so I couldn't fix it in the last two days
[08:09] <seb128> pitti, yeah that's ok, I'm just teasing you, easy enough to filter out
[08:09] <seb128> pitti, if you really want to spam you are not trying enough, you should change some letters in the title at least ;-)
[08:10] <seb128> re*t*racer rEtraccer etc
[08:10] <seb128> ;-)
[08:10] <pitti> d3AR Sebastien, R E Tr4cers are 80% off noW !!!11!!
[08:14] <didrocks> good morning
[08:16] <pitti> bonjour didrocks
[08:16] <didrocks> Guten Morgen pitti, how was your week-end?
[08:16] <pitti> we spent all Saturday driving around, to Munich and back
[08:17] <seb128> lut didrocks
[08:17] <didrocks> pitti: have you been able to move everything you wanted to Munich?
[08:17] <pitti> my wife will be doing an internship there over the summer, so we moved over some of her stuff and already went to the work place to see where it is
[08:17] <didrocks> salut seb128 ;)
[08:18] <pitti> didrocks: yes; wasn't all that much, but we filled up the car quite well
[08:18] <pitti> didrocks: (Renault Kangoo delivery car)
[08:19] <didrocks> oh :)  yeah, remember about here moving to Munich for an internship, and that you will live in the two places in the meanwhile.
[08:20] <RAOF> Living in two places at once sounds tiring. :)
[08:21] <didrocks> hey RAOF
[08:21] <RAOF> Hey ho, didrocks
[08:22] <pitti> RAOF: yeah, I'll have to switch places several times during summer
[08:31] <cassidy> seb128, morning! Would it be possible to fix https://bugs.edge.launchpad.net/ubuntu/+source/hellanzb/+bug/549234 ? Current package is unusable and a sync should fix it
[08:33] <seb128> cassidy, hey, adding to my list of things to look at today
[08:34] <cassidy> cool; thanks!
[09:20] <pitti> seb128: ok, warning fixed
[09:22] <seb128> pitti, danke
[09:22] <pitti> seb128: it's a silly warning from python-pkgresources, FYI
[09:22] <pitti> seb128: I dropped our local launchpadlib from PYTHONPATH in "environ"
[09:22] <pitti> so that it's using the system packages
[09:22] <pitti> should do for now
[09:24] <baptistemm> hello
[09:36] <nigelb> didrocks, done!  New debdiff attached :)
[09:36] <didrocks> nigelb: thanks, adding to my TODO list :)
[09:37] <nigelb> didrocks, thank you :)
[09:43] <seb128> robert_ancell, hey
[09:44] <robert_ancell> seb128, hery
[09:44] <robert_ancell> hey
[09:44] <czajkowski> ara: who should I poke re my comment on bug 109156
[09:44] <seb128> robert_ancell, how are you?
[09:45] <robert_ancell> seb128, good, just arrived in Taipei this morning
[09:45]  * ara opens the bug report
[09:45] <seb128> robert_ancell, oh? what are you doing there?
[09:45]  * czajkowski has had a weekend of a broken lucid and buttons hiding till jcastro told me how to get them to reappear
[09:45] <robert_ancell> seb128, working out of the office here for a week
[09:46] <ara> czajkowski, your comment should be another bug report
[09:46] <czajkowski> ara: wasn't sure as the error is the same
[09:46] <ara> czajkowski, specifically about the error message
[09:47] <czajkowski> ok
[09:47] <ara> czajkowski, you are complaining about the error message not being appropriate, aren't you?
[09:47] <czajkowski> yes
[09:47] <czajkowski> and also still getting the error.
[09:47] <seb128> robert_ancell, oh ok, how is Taipei and the office ?
[09:48] <robert_ancell> seb128, a very nice view :)  much more fun flying north-south too so not jetlagged
[09:48] <chrisccoulson> hello everyone
[09:48] <ara> czajkowski, sure, that's why you should be opening a new one only about the error message
[09:48] <seb128> robert_ancell, hehe
[09:49] <seb128> robert_ancell, is the view better than in London?
[09:49] <czajkowski> ara: ok
[09:49] <robert_ancell> the view is less interesting than london but Taipei 101 is a cooler building.  And a _lot_ further up :)
[09:49] <czajkowski> ara: what package should I add it to ?
[09:49] <robert_ancell> Level 46
[09:50] <ara> czajkowski, metacity, I think
[09:50] <ara> seb128, ^, you agree?
[09:50] <seb128> ara, about?
[09:50] <seb128> what error?
[09:50] <ara> seb128, see czajkowski's comment on bug 109156
[09:50] <seb128> I'm not sure
[09:51] <seb128> would require debugging
[09:51] <seb128> just pick one ;-)
[09:51] <seb128> that seems a low importance issue to me, I've other things I want to look at before lucid so I will let this one for triagers ;-)
[09:51] <ara> seb128, :D
[09:51] <czajkowski> ara: cheers for the help 561294
[09:52] <czajkowski> seb128: I'm sure it's low, just for a new end user to see the message that something sucks really isn't at all helpful :)
[09:53] <seb128> never saw that error on any install I did
[09:54] <czajkowski> yeah I find annoying errors :(
[09:54] <czajkowski> usually just me who has them too
[09:59] <chrisccoulson> hey seb128 - do you want to sponsor g-c-c for me? :)
[09:59] <didrocks> nigelb: you didn't debdiff against the last version. Not a big deal there (only adapting debian/changelog), but always ensure you have the latest version :)
[10:00] <nigelb> didrocks, ouch.  I didn't know there was another upload
[10:00] <didrocks> nigelb: apt-cache show/policy is your friend :)
[10:00] <didrocks> nigelb: no pb, testing it now
[10:00] <nigelb> didrocks, oh thanks :)
[10:02] <seb128> chrisccoulson: hey
[10:02] <chrisccoulson> hey seb128, how are you?
[10:02] <seb128> chrisccoulson: sure, thanks a lot for fixing this issue, what is taking locking there just for learning?
[10:02] <seb128> chrisccoulson: I'm good thank you, you?
[10:03] <didrocks> hey chrisccoulson, you rock ;)
[10:03] <pitti> hey chrisccoulson, good morning
[10:03] <chrisccoulson> seb128 - the issue is that gtk_dialog_run takes the lock when exiting from the recursive main loop, and then it gets taken again when dispatching another event from the main loop
[10:04] <didrocks> chrisccoulson: I don't undestand how g_timeout calling a function take the lock and not gdk_threads_add_timeout
[10:04] <nigelb> pitti, will you be SRU-ing bug 532852 ? (you fixed it last week, I just closed it for lucid)
[10:04] <chrisccoulson> so, using gtk_threads_add_timeout rather than g_timeout_add guards the whole callback with gdk_threads_enter/gdk_threads_leave, and makes sure it ends up in a consistent state
[10:04] <seb128> chrisccoulson: oh, I see
[10:04] <pitti> nigelb: I wasn't going to (I closed the karmic task); is there a pressing reason for this?
[10:05] <pitti> nigelb: oh, right, that's the other bug, sorry
[10:05] <pitti> nigelb: I thought about the crash on invalid pid
[10:05] <nigelb> hehe :)
[10:07] <didrocks> chrisccoulson: so, the gdk_threads_enter was called twice? (didn't noticed that when adding some printf). Not sure to follow you there between the different between g_add_timeout and gdk_threads_add_timeout
[10:07] <chrisccoulson> didrocks - events dispatched from g_timeout_add don't have the GDK global lock (ie, gdk_threads_enter hasn't been called)
[10:08] <chrisccoulson> whereas gdk_threads_add_timeout gives you the global lock
[10:09] <didrocks> chrisccoulson: oh ok, so, the callback function as discaring in the first case the global lock. Understood
[10:09] <didrocks> thanks :)
[10:09] <chrisccoulson> yw
[10:10] <chrisccoulson> didrocks - this explains some of it i think: http://library.gnome.org/devel/gtk-faq/stable/x481.html
[10:10] <didrocks> chrisccoulson: thanks, will have a look
[10:10] <seb128> chrisccoulson: did you have a chance to look at the dnd crasher too will you were at it?
[10:11] <chrisccoulson> seb128 - i didn't get a chance. i finished quite late on friday in the end ;)
[10:11] <seb128> chrisccoulson: no problem, I will sponsor that already for now ;-)
[10:11] <chrisccoulson> thanks
[10:12] <seb128> thank *you*
[10:13] <baptistemm> Hi there
[10:15] <chrisccoulson> hey pitti, how are you btw?  (sorry, i missed your comment above) ;)
[10:15] <pitti> chrisccoulson: I'm good, thanks!
[10:16] <pitti> how about you?
[10:16] <seb128> lut baptistemm
[10:16] <chrisccoulson> pitti - quite tired. i had to work a bit at the weekend, as the NSS security update in karmic caused 2 regressions
[10:16] <pitti> urgh
[10:16] <pitti> chrisccoulson: perhaps take off the afternoon to get some rest?
[10:16] <asac> yes. we all suffered that way ;)
[10:17] <asac> (once)
[10:17]  * pitti hugs asac and chrisccoulson
[10:17] <asac> hehe
[10:17] <chrisccoulson> but they're both fixed now thanks to jdstrand and asac :)
[10:17]  * chrisccoulson hugs pitti
[10:17] <baptistemm> hello seb128
[10:17]  * asac hugs pitti and chrisccoulson .... and seb128 ;)
[10:17]  * chrisccoulson hugs asac and seb128 too
[10:17]  * seb128 hugs asac
[10:17]  * seb128 hugs chris
[10:17]  * seb128 hugs chrisccoulson
[10:18] <seb128> bah, namespace conflicts on this channel :p
[10:18] <seb128> pitti, "usb 5-2: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 1024 ret -84"
[10:18] <chrisccoulson> lol
[10:18] <seb128> do you know what those USBDEVFS_CONTROL failed are?
[10:18] <chrisccoulson> -ETOOMANYCHRIS
[10:18] <pitti> seb128: I've never seen those, I'm afraid; is that libmtp?
[10:18] <seb128> bug #559892
[10:19] <pitti> seb128: usbdevfs is /dev/bus/usb/
[10:19] <pitti> lol
[10:19] <seb128> pitti, another of those "rhythmbox hijack what is should not"
[10:19] <seb128> is -> it
[10:20] <seb128> combined with bug #557623 the new mtp code creates trouble
[10:20] <seb128> I'm pondering turning mtp off by default in rhythmbox for lucid
[10:20] <pitti> seb128: udevadm info --exportdb output might be useful
[10:20] <seb128> pitti, I've asked that on the bug, thanks
[10:20] <seb128> not to mention that we use an ages old libusb
[10:21] <pitti> seb128: hmm, that'd be a pity.. it'd be worth checking if there's a /dev/libmtp* link for it
[10:21] <seb128> so nobody is going to fix it for us
[10:21] <pitti> seb128: i. e. if it's libmtp recognizing too many devices, or Rhythmbox tryign to grab non-MTP devices (which I suspect)
[10:21] <seb128> pitti, what does create the entry?
[10:21] <pitti> the latter is the same problem with gphoto cams
[10:21] <pitti> seb128: /lib/udev/rules.d/45-libmtp8.rules
[10:21] <seb128> well
[10:21] <pitti> SYMLINK+="libmtp-%k"
[10:22] <seb128> one issue is that libmtp crashes in libusb
[10:22] <seb128> cf the bug I just pointed
[10:22] <seb128> I'm not sure how to deal with that but it crashes rhythmbox for lot of users
[10:22] <seb128> since rhythmbox does a libmtp_detect at init
[10:23] <seb128> the second issue is that it hijack some non mtp devices which I don't understand
[10:23] <seb128> the cameras case is special since those a ptp devices which is sort or mtp-ish too
[10:23] <seb128> still a bug
[10:23] <pitti> right, but they don't generate a libmtp dev symlink
[10:23] <pitti> at least not for mine
[10:23] <seb128> but I don't get how it hijack usb key mounting or mouse for some users
[10:23] <pitti> and yet RB tries to grab it
[10:24] <seb128> right, mtp-detect returns things for those though
[10:24] <pitti> I have a feeling that RB iterates over all RB devices and does some not-tight-enough checks
[10:24] <seb128> which rhythmbox doesn't handle correctly
[10:24] <seb128> right
[10:24] <seb128> I will look to that today
[10:25] <seb128> still it will not fix the crasher
[10:25] <pitti> the crasher is with real MTP devices?
[10:26] <seb128> no
[10:27] <seb128> I get the invalid read on my d630 with no device attached to the computer
[10:27] <seb128> just calling the libmtp detect function is tnough
[10:29] <pitti> seb128: so RB crashes right away on your system?
[10:29] <seb128> pitti, no, it's an invalid read, it's like lottery
[10:30] <seb128> depends what you hit with your pointer, it might just not crash
[10:31] <seb128> I do get the invalid read under valgrind though and crash report we get indicates it's one of the most common lucid crashes for rhythmbox
[10:31]  * pitti tries the reproducer
[10:33] <pitti> seb128: hm, I ran that with "valgrind testmtp", and no errors
[10:33] <pitti> seb128: do I need any option?
[10:33] <seb128> no
[10:34] <seb128> $ valgrind ./device
[10:34] <seb128> ==8536== Memcheck, a memory error detector
[10:34] <seb128> ...
[10:34] <seb128> ==8536== Invalid read of size 1
[10:34] <seb128> ==8536==    at 0x4085E08: usb_parse_descriptor (descriptors.c:42)
[10:34] <seb128> ==8536==    by 0x40860BF: usb_parse_configuration (descriptors.c:238)
[10:34] <pitti> hm, then I can't reproduce this, I'm afraid
[10:34] <seb128> it might well be hardware specific
[10:34] <seb128> looking to the libusb code it seems case where it fails to parse to usb infos
[10:36] <pitti> seb128: would it help at all to build RB and/or libmtp against libusb-1.0?
[10:36] <seb128> I can try if libusb1 has this bug
[10:36] <seb128> but it seems late for a such change
[10:36] <pitti> they seem to have a different API, though
[10:36] <seb128> teuf said libusb1 has a compat layer
[10:36] <pitti> seb128: right, but if -1.0 works, we might backport a fix from upstream
[10:37] <seb128> we maybe don't build the compat lib though
[10:41] <ara> seb128, if you have time, could you please add an endorsement to my application at https://wiki.ubuntu.com/AraPulido/PerPackageUploadApplication
[10:41] <ara> seb128, comments are also welcome
[10:41] <seb128> ara, ok, will do!
[10:41] <ara> seb128, thanks!
[10:41] <seb128> you're welcome
[10:43] <baptistemm> ah, persia has suggested that I could have endorsement for bluetooth related packages
[10:44] <baptistemm> he told that he will endorse but I wonder if I needed someone else?
[10:44] <baptistemm> perhaps someone here could do that?
[10:46] <seb128> I'm not sure, I didn't sponsor enough of your updates to say
[10:46] <baptistemm> at least you fixed some garbage of mine :)
[10:47] <seb128> right, which make me think you are sometime not careful enough ;-)
[10:47] <seb128> let's maybe wait next cycle
[11:13] <pitti> seb128: thanks for subscribing me to all the volume handling bugs (in nautilus, etc.)
[11:13]  * pitti can leech from seb128's awesome bug triaging and concentrate on the ones that he can help with
[11:13] <seb128> pitti, is that really welcome or do you want me to stop doing that? ;-)
[11:13] <pitti> seb128: no, I'm serious
[11:13] <seb128> good
[11:13]  * seb128 hugs pitti
[11:13] <pitti> I don't find enough time to read all the gvfs etc. bugs myself
[11:14]  * pitti hugs seb128
[11:22] <seb128> ok, I finished email backlog before lunch today
[11:29] <seb128> pitti, I didn't see your new comment on bug #559723 and reassign to udisks, do you want me to reassign it back?
[11:30] <seb128> pitti, the udisks log seems boggus some thousand tracks and 96 audio ones too
[11:30] <pitti> seb128: it's probably udev, let me look
[11:31] <pitti> seb128: ah; I'll wait for his udev log and cdrom_id output, and reassign to udev if appropriate
[11:31] <pitti> udisks is fine for now
[11:31] <seb128> ok good
[11:31]  * pitti -> doctor and lunch, bbl
[11:31] <seb128> hum, lunch!
[11:33] <baptistemm> chrisccoulson: do you have some progress on bug 536766?
[11:33] <didrocks> pitti: see you
[11:33] <didrocks> seb128: enjoy
[12:28] <vish> didrocks: hi , re: the cheese apport hook. the log file now attaches as a .log or still a .log.gz ?  [last i heard nigel was having trouble getting that done..]
[12:30] <didrocks> vish: hey, from the source it's a .log now, but I'll have to check again once the crash will be fixed :)
[12:31] <vish> didrocks: ah, then probably not , lp does the compression :(   iirc , he mentioned he would work on it again to fix that part for Maverick
[12:32] <didrocks> vish: ok, maybe we can keep it that way for lucid, even if it's not nice for us to get that and see for maverick with LP guys (having an apport hook is still better than nothing)
[12:32] <vish> yup :)
[12:49] <ia> hello. maybe could anyone take a look, please, at #524938 and at some rationale, why this package should be fixed, not removed - https://bugs.launchpad.net/ubuntu/+source/libopensync-plugin-syncml/+bug/524938/comments/10
[13:23] <gicmo> seb128: hi hi
[13:24] <seb128> hey gicmo!
[13:24] <seb128> how are you?
[13:25] <gicmo> pretty good
[13:25] <gicmo> in Munich at the University
[13:25] <gicmo> you will be pleased to know that everybody here uses ubuntu
[13:25] <gicmo> ;-)
[13:27] <seb128> gicmo, waouh!
[13:27] <seb128> gicmo, when is the gsetting hackfest?
[13:29] <gicmo> seb128, this week, coulnd't make it, but will be helping out remotely on Wed, Thur, Fr.
[13:29] <seb128> gicmo, oh ok
[13:33] <gicmo> seb128: I hope lucid comes out on time, here everything is on hardy and is eager to upgrade to next LTS
[13:33] <seb128> gicmo, Ubuntu is like GNOME, it's always out on time ;-)
[13:34] <ogra> now why did i read "of" instead of "on" above
[13:35] <gicmo> seb128: hehe ;-)
[13:35] <gicmo> ogra: heh freudian reading error?
[13:35] <gicmo> (-:
[14:06] <seb128> gicmo, Ubuntu is like GNOME, it's always out on time ;-)
[14:06] <seb128> ups
[14:06] <seb128> gicmo, sorry, focus issue
[14:31] <seb128> rickspencer3, hey
[14:33] <rickspencer3> hi seb128
[14:33] <kenvandine> pitti, seb128: a recommends should be enough to pull something onto the CD right?
[14:33] <rickspencer3> kenvandine, hi
[14:33] <kenvandine> and good morning
[14:33] <pitti> kenvandine: yes
[14:33] <kenvandine> :)
[14:33] <seb128> kenvandine, yes
[14:33] <pitti> hey rickspencer3, hey kenvandine
[14:34] <kenvandine> pitti, python-indicate isn't on the CD but is a recommends
[14:34] <seb128> if the something is not in universe...
[14:34] <kenvandine> un oh
[14:34] <kenvandine> damn
[14:34] <kenvandine> pitti, can that get promoted?
[14:35] <pitti> kenvandine: technically yes; practically, why?
[14:35]  * pitti waves with FF
[14:35] <kenvandine> cause the "setup broadcast accounts" in the message menu never goes away
[14:35] <kenvandine> unless that gets installed
[14:35]  * kenvandine doesn't know how nobody (including me) noticed this yet!
[14:36] <rickspencer3> kenvandine, perhaps because desktopcouch has never succeeded in synching your gwibber account data without crashing
[14:36] <kenvandine> hahaha
[14:36] <kenvandine> true that
[14:36] <rickspencer3> so no one has been able to test the SFTS experience
[14:36] <rickspencer3> ^not kidding actually
[14:36] <rickspencer3> I wanted to talk about this today
[14:36] <kenvandine> now that desktopcouch actually works out of the box :)
[14:37] <pitti> kenvandine: perhaps it should be a depends then?
[14:37] <rickspencer3> over the whole weekend on my netbook, desktopcouch never succeeded in copying down all of my databases
[14:37] <kenvandine> pitti, i guess your right
[14:37] <kenvandine> since the messaging indicator kind  of goes screwy without it
[14:37] <kenvandine> rickspencer3, eek
[14:37] <kenvandine> got logs?
[14:37] <rickspencer3> https://bugs.launchpad.net/bugs/530541
[14:38] <rickspencer3> kenvandine, this seems rather widespread
[14:38] <kenvandine> ~/.cache/desktop-couch/log/desktop-couch-replication.log
[14:38] <kenvandine> yeah, that one
[14:38] <rickspencer3> is there a way for me to see what couch databases are in the cloud atm?
[14:38] <kenvandine> humm
[14:38] <kenvandine> rickspencer3, sort of
[14:39] <rickspencer3> anyway, SFTS will never work if the desktopcouch just crashes after it starts up
[14:39] <kenvandine> http://www.freedesktop.org/wiki/Specifications/desktopcouch/Documentation/Troubleshooting?action=AttachFile&do=view&target=ubuntuone-couchdb-query
[14:39] <kenvandine> download that script
[14:39] <kenvandine> you can query your dbs directly in the cloud with that
[14:40] <kenvandine> but... it currently doesn't list your dbs
[14:40] <kenvandine> if you know the names, you can just hit each one
[14:40] <kenvandine> also look at your replication log
[14:40] <rickspencer3> bug #528728
[14:41] <huats> hello everyone
[14:41] <rickspencer3> kenvandine, ok, I'll look into that later today
[14:41] <rickspencer3> in the meantime, what is the status of getting run_couchdb fixed before we, you know, release?
[14:42] <kenvandine> i think that is one of the bugs chad thinks is fixed and is looking for testers for
[14:42] <kenvandine> rickspencer3, willing to test from a ppa?
[14:42] <rickspencer3> kenvandine, sure
[14:42] <kenvandine> let me get the details and confirm he thinks this is related
[14:42]  * kenvandine thinks he should comment to that affect on the bug
[14:42] <rickspencer3> did pitti ack adding python-indicate as a depends?
[14:43] <pitti> it needs a MIR first
[14:43] <kenvandine> i think since he suggested it :)
[14:43] <kenvandine> pitti, the source is already main
[14:43] <pitti> but if it's really necessary for correct funcionality, it should be a depends, yes
[14:43] <kenvandine> it comes from libindicate
[14:43] <pitti> ah
[14:43]  * pitti promotes then
[14:43] <kenvandine> so no MIR
[14:43] <kenvandine> thx
[14:43] <kenvandine> i'll add as a depends anyway
[14:43] <kenvandine> technically gwibber works, but it breaks the experience for messaging menu
[14:43] <pitti> kenvandine: no, the source is indicate-python
[14:44] <kenvandine> oh?
[14:44] <kenvandine> damn
[14:44]  * kenvandine thought that was built from the same source
[14:44] <kenvandine> ok, i'll get an MIR together
[14:45] <kenvandine> next cycle we should merge that inline with libindicate :)
[14:45] <kenvandine> then tedg doesn't forget about it... and learns to love python
[14:45] <tedg> kenvandine: If you can fix indicator-application so it builds twice from the same build, I'd love python more :)
[14:46] <tedg> For Maverick will we be able to just use the GIR file for Python?
[14:47] <kenvandine> dunno
[14:47] <kenvandine> anything that uses GIR doesn't build for me now... :)
[14:47]  * tedg wants that so bad.  This building multiple Python versions stuff is *so* stupid.
[14:51] <kenvandine> pitti, bug 561508
[14:52] <coffeedude> Hey pitti.  Is there anyway to manage bugs assigned to a package (i.e. likewise-open) without joining bug squad?  Things like importance, won't fix, etc...  no rush.  Just curious,
[14:52] <kenvandine> tedg, in reality we can drop that for now
[14:52] <kenvandine> since we only care for one version... it was an issue in karmic for some reason
[14:52]  * kenvandine can't recall
[14:52] <kenvandine> tedg, but yes, if we can get GIR stuff instead... yay!
[14:53] <tedg> kenvandine: I think we can.  The Python GIR hackfest is this week, eh?
[14:54] <pitti> coffeedude: for upstream tasks you should already be able to; but for Ubuntnu packages you need to be in bug squad, I think; can you please talk to bdmurray or pedro to add you?
[14:54] <coffeedude> pitti, Will do.  Thanks.
[15:00] <popey> kenvandine: are you working on proxy support for gwibber for lucid?
[15:00] <kenvandine> popey, no :(
[15:00] <popey> :(
[15:00] <kenvandine> we have a patch adding libproxy support, but it requires a newer libproxy that is in lucid
[15:00] <kenvandine> and it is too late to update something like that
[15:00] <popey> when I start gwibber behind a proxy I get apport crashes for gwibber, gwibber-service and desktop-couch immediately
[15:00] <kenvandine> popey, it will go in real soon though for lucid+1
[15:01] <kenvandine> popey, humm... crashes?
[15:01] <popey> not even an SRU?
[15:01] <popey> yup
[15:01] <popey> barfaroony
[15:01] <kenvandine> popey, it is a pretty big jump, libproxy 0.2.3 to 0.4.0
[15:01] <kenvandine> should break anything, but might require some rebuilds
[15:01] <kenvandine> popey, we will upload the newer libproxy to the gwibber ppa though for folks using the newer gwibber
[15:02] <seb128> we might want to consider the new libproxy
[15:02] <kenvandine> seb128, oh?
[15:02] <seb128> it's late but not used by a lot of things
[15:02] <kenvandine> i would love to update it
[15:02] <seb128> telepathy guys raised the issue
[15:02] <seb128> the version we have is year old and buggy
[15:02] <kenvandine> libsoup-gnome2.4-1
[15:02] <seb128> I wanted to maybe raise it tomorrow in the meeting or discuss it with pitti later when he's done dealing with lucid breakages
[15:02] <kenvandine> is the only thing that concerned me
[15:03] <seb128> right
[15:03] <kenvandine> seb128, if you can get that updated... i'll fix the proxy issue and make a ton of people happy :)
[15:03] <popey> +1 :)
[15:03] <seb128> the proxy part is probably not used frequently in normal desktop use
[15:05] <kenvandine> seb128, yeah, and the developers said there is no real api breakages, just additions
[15:05] <kenvandine> with one exception, i think something no longer returns NULL when it used to
[15:05] <seb128> kenvandine, is the proxy code used transparently by any libsoup client or is that something you need to use specifically?
[15:06] <kenvandine> i need specifically
[15:06] <kenvandine> for gwibber
[15:06] <kenvandine> to do anything useful for proxy support in gwibber, we need 0.4.x
[15:06] <seb128> well the context was rather to evaluate how much impact it can have on libsoup users
[15:07] <seb128> ie if it's an opt in and gvfs etc don't use it it has pretty low chance to break anything
[15:07] <seb128> it = the update
[15:14] <nigelb> pitti, is there something wrong with the apport.hookutils.attach_hardware code?  I get a traceback while running a hook
[15:14] <nigelb> didrocks, looking at your comments.  It has something to do with ^
[15:18] <pitti> nigelb: I need some more details about that (like the backtrace) before I can answer. It generally works fine
[15:18] <nigelb> pitti, https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/542091/comments/15
[15:19] <nigelb> I did see it when I tested my self, but ignored it then
[15:20] <pitti> nigelb: ah, you aren't supposed to use the return value (it's None)
[15:20] <pitti> nigelb: just call attach_hardware(repoert)
[15:20] <pitti> it modifies report in-place
[15:21] <nigelb> ah, my mistake then, sorry :)
[15:21]  * pitti sighs -- 4:30 PM, and I still didn't catch up on mail
[15:22] <rickspencer3> pitti, cntrl-A, Delete
[15:22] <rickspencer3> ;)
[15:22] <nigelb> rickspencer3, that works sometimes :D
[15:22] <pitti> rickspencer3: you mean T . <CR> d  ? :-)
[15:23] <nigelb> pitti, sigh, i'm still doing something wrong.  another traceback http://paste.ubuntu.com/413148/
[15:24] <pitti> nigelb: symb['add_info'](self)
[15:24] <pitti> ?
[15:24] <pitti> nigelb: what's that supposed to do? can you please show me the entire code?
[15:24] <nigelb> yup
[15:24] <pitti> oh, hang on
[15:24] <pitti> that's apport's code, nevermind
[15:25] <nigelb> well, the hook is this http://paste.ubuntu.com/413150/
[15:25] <pitti> nigelb: your add_info() function needs to take one or two arguments
[15:25] <pitti> nigelb: that looks alright, hmm
[15:26] <pitti> apport.hookutils.attach_hardware("HardwareInformation")
[15:26] <pitti> nigelb: the argument needs to be report, not a string
[15:26] <nigelb> just say (report)?
[15:26] <pitti> yes
[15:26] <nigelb> oh
[15:27]  * nigelb hugs pitti 
[15:27] <nigelb> thank you, it works fine now :)
[15:27] <pitti> \o/
[15:35] <seb128> dpm, hey there
[15:35] <seb128> dpm, could you look at bug #561535 and see if we need to email translators, how many strings that will break, if we can get the karmic ones used again there?
[15:36] <dpm> heya seb128, looking...
[15:36] <seb128> dpm, gcalctool went back to the karmic version
[15:36] <seb128> dpm, the new rewrite one was not ready on time for lucid
[15:47] <dpm> seb128, I think we should be fine: the template and translations were imported 2 days ago, many languages are already translated from upstream and some others were completed on the day of the upload or shortly after. I'll send a quick heads up e-mail to translators, but I think the only issue here is that the language packs with the karmic strings have not yet been released
[15:48] <seb128> dpm, ok excellent, thanks for checking!
[16:00] <nigelb> didrocks, got the new debdiff in, should fix all issues :)
[16:00] <didrocks> nigelb: I just need the new apport hook as I've integrated the .install and changelog file, but I can extract it from the debdiff
[16:01] <nigelb> didrocks, arg.  I seem to do all sorts of wrong stuff today :(
[16:09] <Nafai> good morning
[16:18] <seb128> does anybody know how the default dictionnary to use is set?
[16:18] <seb128> dpm, ^?
[16:19] <dpm> seb128, I'm afraid I don't, but I could investigate.
[16:20] <seb128> I would be curious if it's buggy for other people too
[16:20] <seb128> I get english selected there on new french installs
[16:20] <seb128> in empathy or evolution for example
[17:00] <milanbv> would anybody be OK to prepare a SRU to Karmic at some point to fix bug 490093?
[17:00] <milanbv> I don't think the fix would be hard, I can provide a patch
[17:41] <czajkowski> seb128: any idea why when i start my machine up, all main header bars are missing from any application or terminal and i need to run compiz --remove to get things back
[18:16] <chrisccoulson> pitti - would you mind removing mozilla-noscript from the archive?
[18:16] <pitti> not at all
[18:16] <pitti> chrisccoulson: blacklist as well, I suppose?
[18:17] <chrisccoulson> pitti - yes, please
[18:17]  * pitti slaughers
[18:17] <pitti> "slaughters"
[18:17] <pitti> chrisccoulson: Qapla'
[18:20] <kklimonda> chrisccoulson: are you going to remove greasemonkey too? :)
[18:22] <pitti> argh, so much trouble with CDs
[18:39] <chrisccoulson> pitti - thanks
[18:41] <chrisccoulson> i had to google what "Qapla'" meant there ;)
[18:42] <nigelbabu> chrisccoulson, tsk tsk, you dont speak klingon?
[18:42] <chrisccoulson> nigelbabu, clearly not ;)
[18:42] <chrisccoulson> kklimonda, there are no plans to remove greasemonkey, how come?
[18:42] <Nafai> chrisccoulson: I had to google it the other day when pitti used the word as well :)
[18:42] <kklimonda> chrisccoulson: I got scared - noscript was yet another big extension :)
[18:44] <kklimonda> chrisccoulson: btw. could you take a look at bug 538580 when you have some spare time, before the final freeze? last time I've asked you to do that hopefully ;)
[18:57] <Nafai> lunching
[19:01] <rickspencer3> Nafai any news on that Bluetooth indicator bug?
[19:20] <Sarvatt> anyone familiar with compiz that has an idea why this might be happening? there is a check for the max texture size on startup, and for people with a 2048x2048 max that are using one 2048xwhatever monitor it is starting with a black screen unless they reduce the size to 2047. people with 2 monitors aren't affected and a 2048 virtual works in that case but of course we just changed compiz so it wont start with if the requested texture size
[19:20] <Sarvatt> is >= the max instead of just > because of the single monitor people being unable to even start up so 2 1024x768 monitors doesn't work anymore
[19:23] <Sarvatt> it's like something is padding the size by 1 pixel just in the single monitor case
[19:34] <didrocks> seb128: for the "Using space key…" in gnome-keyboard-properties, the setting is common to any keyboard layout. It's just a gconf key (/desktop/gnome/peripherals/keyboard/kbd/options). I think we should add the default in the installer if keyboard layout == oss, sounds right?
[19:40] <didrocks> seb128: not really sure how to deal with that properly as I guess we want that gconf option (set /desktop/gnome/peripherals/keyboard/kbd/options to [nbsp nbsp:none]) only with oss layout to avoid regression?
[20:04] <didrocks> seb128: I have maybe another way to obtain the same result, but only for oss layout. I'll give it a test tomorrow. Don't bother right now :)
[20:58] <seb128> didrocks, re, ok, let's talk about that tomorrow but no gconf tweaking for this one ;-)
[20:59] <seb128> didrocks, new installs only will do or let's change the oss definition
[20:59] <didrocks> seb128: yeah, there is another solution changing the oss layout… but upstream don't want to change it
[21:00] <seb128> didrocks, well upstream is upstream, they might have different opinions or consider different userbases ;-)
[21:01] <didrocks> seb128: I'm still finishing the whole reading to ensure I understand to pros and the cons and will give you a summary tomorrow :)
[21:01] <seb128> didrocks, ok, I think I would look for the bugs about switching to oss by default too on launchpad
[21:01] <seb128> and maybe comment on this one about the issue and asking for opinion
[21:02] <didrocks> seb128: "to oss" to other layout than oss, you mean?
[21:02] <seb128> seems some people knew about layouts and cared about the change they might have an useful opinion on how to get what we want
[21:02] <seb128> oss is the default now no?
[21:02] <didrocks> right
[21:02] <seb128> ok, so "to oss"
[21:02] <seb128> we add some discussion over what should be default for french, it used to be non-oss
[21:03] <seb128> we did switch because some people argued for a while on it and cared about the change
[21:03] <seb128> there is a bug which has been marked fixed on xkeyboard-config I think
[21:03] <seb128> the bug is on launchpad for sure, I'm not sure about xkeyboard-config
[21:03] <didrocks> I remember it wasn't oss at some point. I was thinking you told that there were a bug about choosing another layout than oss by default right now
[21:04] <seb128> I think the discussion was about having access to non secable spaces by default
[21:04] <seb128> oh no
[21:04] <seb128> I say let's comment on the bug where people arguing that we should have oss by then
[21:04] <seb128> they might still read comments on the bug
[21:04] <didrocks> good idea
[21:04] <seb128> let's tell them that we consider switching back or doing changes because of this issue
[21:05] <didrocks> layout are hell. I just use … and €, but nothing more :)
[21:05] <seb128> I know there was people on this bug which fixed issue with oss to unblock the change
[21:05] <seb128> they might have an idea on what are nice options to fix this space issue
[21:05] <didrocks> they switch include "nbsp(level4nl)" to include "nbsp(level4n)"
[21:06] <didrocks> I tried and it works
[21:06] <didrocks> it's related to a change in 2008 by cjwatson
[21:06] <seb128> could be a good idea to ping Colin tomorrow too
[21:06] <didrocks> because non breakable space was available at that time at runlevel 5 (Right Ctrl)
[21:06] <seb128> just to know if he has an opinion on the topic
[21:06] <didrocks> it broke a lot of apps like virtualbox
[21:07] <didrocks> sure
[21:07] <didrocks> and that's when upstream change it because of this to level4nl
[21:07] <didrocks> (cf https://bugs.freedesktop.org/show_bug.cgi?id=9529#c27)
[21:08] <seb128> could be a good idea to speak to Sergey about the issue too
[21:08] <seb128> he's svu on the GNOME IRC
[21:08] <didrocks> oh ok, so, let's take care about that tomorrow?
[21:09] <didrocks> I'll finish to understand exactly the difference between level4n and level4nl first
[21:12] <seb128> yes
[21:12] <seb128> you should call it a day
[21:12] <seb128> (I'm just back from sport, good to have a break, I hope you got one as well ;-)
[21:15] <kenvandine> rickspencer3, get a chance to test desktopcouch from that ppa?
[21:15] <didrocks> sure, I'm sure triaging bugs, reading email, and some bug report hunting for this keyboard mess :)
[21:15] <didrocks> just doing one restart and then, it'll be enough for today
[21:15] <didrocks> seb128: enjoy your shower/dinner if you didn't have it yet
[21:16] <didrocks> ok, restarting now and test. Won't reconnect before tomorrow, enjoy your evening everyone
[21:22] <seb128> 'night didrocks
[21:23] <seb128> kenvandine, we have a bug in the empathy ubuntu theme which makes texts with new lines to not be displayed, have you seen it?
[21:23] <kenvandine> no... /me tests
[21:23] <seb128> kenvandine, who is working on the theme and can it be fixed for lucid?
[21:23] <kenvandine> i can track him down
[21:23] <seb128> thanks
[21:24] <kenvandine> so i can just a return in the message?
[21:24] <kenvandine> like shift-enter or something?
[21:24] <seb128> right, shift-enter
[21:25] <kenvandine> seb128, is there a bug filed?
[21:25] <seb128> bug #
[21:25] <seb128> bug #546338
[21:25] <seb128> 546338
[21:25] <seb128> gra, sorry
[21:26] <seb128> kenvandine, ^
[21:26] <kenvandine> showing up for me
[21:26] <seb128> it's happening in all protocols apparently and in the notification bubble
[21:26] <seb128> but not in the discussion log
[21:27] <seb128> the bug has screenshots
[21:28] <kenvandine> humm.... looked fine for me in notify-osd and in the chat
[21:28] <kenvandine> oh... he said it works for him in gtalk
[21:28] <kenvandine> but doesn't work in MSN
[21:28] <seb128> nor yahoo
[21:28] <seb128> nor googletalk
[21:29] <kenvandine> look at comment #4
[21:30] <kenvandine> yeah... clearly working for me with jabber and gtalk
[21:30]  * kenvandine tries msn
[21:33] <kenvandine> seb128, do you have a MSN account?
[21:33]  * kenvandine has no contacts online in MSN and only one MSN account :)
[21:33] <kenvandine> makes it hard to test
[21:35] <Nafai> rickspencer3: Sorry I missed you earlier.  I think I may pull ted in for help in a bit because it seems to be related to the app indicator libraries
[21:36] <seb128> kenvandine, nop
[21:36] <kenvandine> nm... i found a test account i had
[21:36] <seb128> cool
[21:36] <Nafai> kenvandine: I have a MSN account if you need help as well
[21:37] <kenvandine> working for me with msn as well
[21:37] <kenvandine> Nafai, can you try to reproduce bug 546338
[21:37] <kenvandine> ?
[21:37] <Nafai> sure, let me look
[21:44] <Nafai> kenvandine: If I understand correctly, I need to have the "Ubuntu" theme selected in Empathy?
[21:53] <kenvandine> Nafai, yes
[21:53] <kenvandine> and hit shift-enter to insert a new line
[21:54] <Nafai> ok, trying
[21:55] <kenvandine> i just commented and posted a screenshot
[21:55] <kenvandine> maybe i am miss-understanding the problem... it seems to work fine to me
[21:56] <Nafai> yeah, me either, between two google talk accounts
[21:58] <kenvandine> ok
[21:58] <kenvandine> can you comment on the bug as well?
[21:58] <seb128> Nafai, google talk was listed as working on the bug though?
[21:58] <seb128> kenvandine, Nafai: thanks for trying, good to see it's not happening to every user
[21:58]  * Nafai rereads
[21:59] <Nafai> ah, I didn't read the whole comment thread
[21:59] <kenvandine> in one comment... but i tested with MSN as well and it worked
[21:59]  * kenvandine tries using the same characters they used in the screenshot
[22:01] <seb128> ccheney, no, this font issue is not a gnome-control-center bug, g-c-c only writes a gconf key it doesn't apply any settings
[22:01] <kenvandine> ok, that worked too
[22:01] <seb128> ccheney, gnome-settings-daemon is what apply the xsettings if that's what you meant there, and gtk software react to the change correctly which means the setting is set
[22:03] <ccheney> seb128: yea must be g-s-d but at least with respect to font filtering g-s-d was not setting it properly, the rest of gnome worked right but anything relying on it setting it in xsettings did not work, including OOo
[22:04] <ccheney> seb128: the part about font filtering last year i verified myself
[22:04] <ccheney> with debugging set for g-s-d etc
[22:04] <seb128> ccheney, did you open a bug about this issue with your debugging infos?
[22:04] <ccheney> i just forgot what part of gnome to reassign it to so set it back to what it was before being assigned to OOo
[22:05] <seb128> ccheney, is that a dynamic update issue or still wrong after restart openoffice or the session?
[22:05] <ccheney> seb128: yea should still be in launchpad somewhere, and if i remember correctly was opened upstream as well, i was working with asac about it at the time
[22:05] <ccheney> it was an issue with the filtering that it would set the right option in xsettings and then set the old setting back again as some sort of weird race, i don't remember the exact details now
[22:05] <seb128> we have a patch from asac for fixing filtering not working in openoffice
[22:05] <ccheney> after restarting gnome it would work
[22:05] <seb128> it's still in lucid
[22:06]  * kenvandine has to head out... good night all !
[22:06] <seb128> 'night kenvandine
[22:06] <ccheney> seb128: iirc there were two separate issues
[22:06] <seb128> right, there was the filtering one that asac fixed
[22:06] <chrisccoulson> seb128 - want me to disable the gnome-user-share nautilus bar? i'm not going to have time to fix it so that it hides when there are no bluetooth devices
[22:06] <ccheney> seb128: the thing asac fixed in the patch afaicr was something different than the race
[22:06] <seb128> and I think you said by then that g-s-d was applying several times the settings
[22:06] <seb128> chrisccoulson: what do you think?
[22:07] <ccheney> seb128: yea it would apply settings several times but would generally end up with the last setting being the wrong one, if you restarted gnome it would work ok as long as you didn't try changing it again
[22:07] <ccheney> seb128: which was what i was referring to, as to not being sure if the font selection issue might be the same thing
[22:07] <chrisccoulson> seb128 - i'm not too bothered either way, but i suppose it's confusing for users that have no bluetooth hardware
[22:07] <chrisccoulson> i'm just not sure i'll have time to fix it properly before final freeze ;)
[22:07] <ccheney> seb128: the user said it was happening in more than just OOo which was why i thought it might be related to the race
[22:09] <seb128> k
[22:09] <seb128> ccheney, thanks
[22:09] <seb128> chrisccoulson: you think the bar is useful?
[22:09] <seb128> chrisccoulson: (I would vote for just not shipping it in lucid but I don't want to force my opinion)
[22:09] <chrisccoulson> seb128 - it's useful for discovering that bluetooth sharing exists
[22:10] <chrisccoulson> but it wouldn't be a regression in functionality if we didn't ship it
[22:10] <seb128> I think it has potential to be confusing over useful
[22:10] <chrisccoulson> seb128 - ok, i will disable that for lucid later then
[22:10] <seb128> seems the sort of feature which can wait next cycle
[22:10] <chrisccoulson> and fix it properly next cycle :)
[22:10] <seb128> right
[22:10] <seb128> that would be my opinion
[22:11] <seb128> to discover the feature is one thing
[22:11] <seb128> having to have a buggy bar staying after you discovered it is another ;-)
[22:11] <seb128> ie it will be a bit harder to find the option but I think people can figure from internet documentation or the capplet
[22:11] <chrisccoulson> yeah, hopefully
[22:12] <chrisccoulson> ok, i will sort that later. thanks
[22:12] <ccheney> seb128: probably setting the xsetting by hand (not sure how to do that myself) would reveal if the problem is in the apps or in g-s-d
[22:12] <seb128> chrisccoulson: thanks
[22:12] <ccheney> seb128: iirc that was how we found the issue with the filtering not getting set right
[22:12] <seb128> ccheney, do you know a way to set xsettings by hand?
[22:12] <ccheney> seb128: iirc there was some way but i forgot how
[22:13] <ccheney> seb128: iirc its a command line app you can make adjustments with
[22:13] <ccheney> seb128: probably bryceh would know :)
[22:13] <seb128> I've asked details on the bug to know if it works after restarting the software or the session
[22:13] <ccheney> ok
[22:13] <seb128> I don't really care about things not working dynamically if they work after restart
[22:13] <ccheney> seb128: yea reassign back to me if it still is broken after restarting gnome
[22:13] <seb128> it's still a bug but not one which should annoy users every day
[22:14] <ccheney> i can dig into it further if that is the caes
[22:14] <ccheney> er case
[22:14] <seb128> ok
[22:21] <bryceh> xsettings?  dunno what that is
[22:25] <chrisccoulson> i don't think you can make adjustments to xsettings by hand (not whilst g-s-d is running anyway)
[22:25] <chrisccoulson> only one app can own the selection
[22:31] <ccheney> chrisccoulson: i used something to view the settings and iirc changed them using it too
[22:32] <chrisccoulson> hmmm, strange. g-s-d exits when it loses the selection
[22:32] <ccheney> chrisccoulson: well changed them in a terminal and then launched OOo from that and iirc it inherited it
[22:32] <chrisccoulson> are you sure that's xsettings and not xrdb?
[22:32] <ccheney> oh yea i forgot what i used
[22:32] <ccheney> it was xrdb
[22:33] <ccheney> sorry for the confusion on my part
[22:33] <chrisccoulson> yeah, that's possible :)
[22:33] <ccheney> so is there something else that sets options like that called xsettings also?
[22:34] <ccheney> the bug report was about setting the font in g-c-c and it not being used by OOo and several other non-gnome apps
[23:30] <TheMuso> Good morning.
[23:39] <RAOF> Goood morning.
[23:40] <Nafai> morning guys
[23:41] <RAOF> And a fine afternoon to you too, I trust.
[23:41] <RAOF> :)
[23:41] <Nafai> yes, not too bad
[23:46]  * TheMuso is loving this morning, coolest one we have had in a while. :)
[23:52] <rickspencer3> Hi RAOF
[23:52] <RAOF> rickspencer3: Good morning!