[00:46] <Ampelbein> seb128: added debdiff to bug 338963
[01:03] <seb128> Ampelbein: thank you, uploaded
[02:36] <doctormo> bryce: I'm trying to tell the computer to use a higher resolution on an external monitor, but xrandr doesn't list higher modes. Is 800x600 likely to be a limitation in the video card (intel) or is it that it can't find more useful information about available modes (for instance it knows it's a Dell monitor so i2c must work)
[02:41] <bryce> doctormo: cloned or extended?
[02:41] <bryce> doctormo: if extended, is your Virtual set correctly in your xorg.conf?
[02:45] <doctormo> bryce: I'd rather have it only on the external, but cloned seems to limit the resolution to that of the Asus Eeeps 800x480, and the virtual set was set automatically by the new jaunty screen resolution tool (to 800x1080)
[02:45] <bryce> that's your problem
[02:45] <bryce> you are getting 800x600 because that's the max that fits into 800x1080
[02:46] <bryce> what's the max resolution of your external monitor?
[02:47] <bryce> doctormo: if you only care about cloned mode, set Virtual to 2048x2048, that should suffice
[02:47] <bryce> if you want extended, you may need more
[02:47] <bryce> and report your bug to 'screen-resolution-extra'
[02:49] <doctormo> I'll try it,
[02:52] <doctormo> http://www0.dealtime.com/xPF-Dell-E173FPB-Charcoal-Gray FYI
[02:58] <doctormo> That worked for extended mode, but not for cloned, interesting
[02:59] <doctormo> And it broke the gnome bar (at the top and bottom) heh
[03:02] <doctormo> Bummer "Screen Resolution Extra does not use Launchpad as its bug tracker. "
[03:03] <bryce> sure it does
[03:04] <bryce> (was just looking at its bugs this morning)
[03:04] <bryce> here you go - https://bugs.edge.launchpad.net/ubuntu/+source/screen-resolution-extra/
[03:11] <doctormo> https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/358147
[03:12] <doctormo> Yes I was looking at the none ubuntu package, hmm
[03:13] <doctormo> Thanks for your help bryce, I owe you another
[03:13] <bryce> :-)
[03:24] <tedg> Hey bryce, is there time for sponsorships left before freeze?
[03:25] <tedg> If so, can I bug you for one?  bug 356132
[03:27] <bryce> tedg: negotiating with wife (she's hankering for going out to dinner)
[03:29] <bryce> ok, you owe her a $beverage ;-)
[03:30] <doctormo> Oh god, those confirmations dialogs have been driving me insane, I hope I figure out how to switch them off. I don't expect my computer to question me.
[03:30] <tedg> doctormo: There's a preference for it, open the preference dialog :)
[03:30] <tedg> bryce, sounds good to me.  But she'll have to sing kareoke for me ;)
[03:31] <doctormo> tedg: Performous?
[03:31]  * tedg needs to go to Portland sometime bryce is actually in town.
[03:32] <bryce> tedg: hmmm, the GUI string change breaks string freeze
[03:32] <tedg> bryce, yes.  I know.  I wouldn't have changed it had the requester been anyone else :)
[03:32] <bryce> fair enough
[03:33] <tedg> davidbarth is going to work with the translation teams next week to try and get all of the last minute strings figured out.  :-/
[03:36] <tedg> bryce, thanks for sponsoring.  Send my apologies to the hungry wife.
[03:36] <bryce> will do :-)
[03:37] <bryce> just verifying it builds first...
[03:38] <bryce> uploaded.
[03:38]  * tedg hugs bryce, and his wife :)
[07:23] <asac> hmm ... not yet frozen?
[08:20] <asac> Nafallo: gajim somewhat doesnt work right with  latest indicate-python
[08:20] <asac> Nafallo: well. at least it doesnt indicate new messages
[08:21] <asac> just appears in the indicator applet (as an app) ... but no special bells and whistles when new messages arrive
[08:34] <seb128> bryce_, ted: are you joking with this fusa string change now? string freeze was over a month ago and that breaks translations
[08:34]  * seb128 reverts the fusa change
[08:37] <asac> lol
[08:37] <seb128> asac: hey, already awake? ;-)
[08:37] <asac> seb128: yeah ;) ... new approach is: wake up early and wake long :)
[08:37] <asac> work long
[08:37] <seb128> asac: "lol" ... sort of, we should force everybody to use a non english locale
[08:38] <asac> right. i completely agree
[08:38] <asac> was that uploaded? or just proposed for sponsorship?
[08:39] <seb128> uploaded
[08:39] <seb128> asac: http://launchpadlibrarian.net/25091153/fast-user-switch-applet_2.24.0-0ubuntu10_2.24.0-0ubuntu11.diff.gz
[08:39] <seb128> -+			  <property name="label" translatable="yes">Show _confirm dialogs for logout, restart and shutdown</property>
[08:39] <seb128> ++			  <property name="label" translatable="yes">_Confirm logout, restart and shutdown</property>
[08:40] <seb128> "+    * Changing GUI string to make shorter to make dialog a better
[08:40] <seb128> +      size.
[08:40] <seb128> "
[08:40] <seb128> good that I'm watching -changes
[08:40] <asac> so its not that this slipped in by accident
[08:40] <seb128> no, it's just that english speaker have little considerations for translations ;-)
[08:41] <asac> yeah. but anyone should be able to remember that changing strings isnt good after string freeze ;)
[08:42] <chrisccoulson> anyone know what time does final freeze begin today?
[08:42] <asac> seb128: is rosetta smart enough to reinstantiate the old strings if the template gets reverted?
[08:42] <bryce> asac, scroll up
[08:42] <seb128> asac: dunno
[08:43] <asac> hmm
[08:43] <asac> bryce: you should be harder ;)
[08:43] <seb128> I've no scrollup, I close IRC during nights
[08:44] <seb128> but I did undo the string change now
[08:44] <seb128> chrisccoulson: no, european afternoon I would expect
[08:44] <asac> 04:32 < bryce> tedg: hmmm, the GUI string change breaks string freeze
[08:44] <asac> 04:32 < tedg> bryce, yes.  I know.  I wouldn't have changed it had the requester been anyone else :)
[08:44] <asac> 04:32 < bryce> fair enough
[08:44] <asac> seb128: ^^
[08:44] <asac> 04:33 < tedg> davidbarth is going to work with the translation teams next week to try and get all of the last minute strings figured out.  :-/
[08:44] <chrisccoulson> seb128 - thanks
[08:45] <asac> i am quite sure that "davidbarth is going to work with the translation teams" is really a risky assumption.
[08:45] <bryce> asac: why?
[08:46] <asac> bryce: i tried that once and found that translation teams have a latency of weeks rather than day to react
[08:46] <bryce> anyway, I don't care one way or another, sounded like this was ruled from on high
[08:46] <asac> some do it quick ... others dont do.
[08:46] <asac> ;)
[08:46] <seb128> bryce: there is just no way that we get translations for next week
[08:46] <seb128> string freeze was weeks ago
[08:46] <seb128> if somebody is unhappy send him my way, I did undo the change now
[08:47] <asac> seb128: tell that dbarth. he thinks he will be able to do that for a bunch of strings :)
[08:47] <asac> ok breakfast
[08:47] <seb128> it takes days for rosetta to import new templates and do exports
[08:48] <seb128> chrisccoulson: hum, they already froze jaunty apparently
[08:50] <chrisccoulson> thanks - i was wondering. i haven't seen an e-mail yet though
[08:50] <chrisccoulson> i was still working on some fusa changes ;)
[08:51] <seb128> chrisccoulson: I will try to get that in when you are ready
[08:52] <chrisccoulson> thanks. it should be ready early this evening when i get back from work
[08:52] <seb128> excellent
[08:54] <chrisccoulson> seb128 - did you see cody-somerville's e-mail to ubuntu-devel about the gnome-session change?
[08:55] <seb128> chrisccoulson: just did
[08:56] <Nafallo> asac: lovely
[08:58] <chrisccoulson> seb128 - i sent a reply explaining the change, but i'm moderated on that list ;)
[08:59] <seb128> chrisccoulson: I did quickly reply too
[08:59] <chrisccoulson> thanks
[09:02] <asac> Nafallo: lovely? ;)
[09:02] <Nafallo> asac: called sarcasm ;-)
[09:02] <asac> Nafallo: does it work for you?
[09:03] <Nafallo> asac: I should know by now it doesn't work on IRC..
[09:04] <Nafallo> meh.
[09:04] <Nafallo> asac: is it in binary new or something?
[09:05] <asac> Nafallo: python indicate? not yet. i wanted to test gajim with it and ended up wondering what its supposed to do
[09:05] <asac> Nafallo: wonder if it has something to do with libindicate .15
[09:06] <Nafallo> asac: hehe. have to ask kenvandine_wk I guess. I only took the patch ;-)
[09:06] <Nafallo> asac: (and upstream did as well)
[09:07] <asac> Nafallo: the patch looks ok for gajim. only thing i find a bit obscure is that the indication seems only to be done when gajim is set to "popups" for notifications
[09:07] <asac> and of course that i dont get it to work ;)
[09:07] <Nafallo> hehe
[09:09] <davidbarth> asac: i'm already in touch with Arne and David Planella
[09:10] <davidbarth> asac: i've checked that all strings introduce at the time of the UIF are in the rosetta templates
[09:10] <davidbarth> asac: however some of them are not translated in all languages
[09:10] <seb128> davidbarth: there was a string change this night, I did undo it now
[09:10] <davidbarth> asac: Arne has helped raise the priority in rosetta
[09:10] <davidbarth> seb128: which one?
[09:10] <seb128> read log
[09:11] <seb128> that was discussed on this channel less than one hour ago
[09:11] <asac> davidbarth: ok. raising priorities should help a bit ... lets see how well that works out
[09:12] <asac> but changing string today is really, really late
[09:12] <asac> i think final export is next week
[09:12] <seb128> there is just no way that changing a string today will work
[09:13] <seb128> jaunty will not get that translated
[09:13] <seb128> and we will make the translators community angry at us for doing such late change
[09:13] <davidbarth> seb128: ok, spotted
[09:14] <davidbarth> seb128: I already refused a change in the gnome-mount dialog
[09:14] <davidbarth> seb128: I was not aware of this one
[09:14] <davidbarth> seb128: you did well; i cannot understand that it was ever committed; apologies
[09:14] <seb128> that's alright
 tedg: hmmm, the GUI string change breaks string freeze
 bryce, yes.  I know.  I wouldn't have changed it had the requester been anyone else :)
 fair enough
 davidbarth is going to work with the translation teams next week to try and get all of the last minute strings figured out.  :-/
 bryce, thanks for sponsoring.
[09:15] <seb128> no need to apologies, your team is new to the ubuntu process, string freezes, etc
[09:16] <davidbarth> bryce: ah... that's different kind of problem, thanks for the pointer
[09:16] <bryce> davidbarth: from that exchange I gathered you had directed this particular change be done, and figured I could help your team in a pinch
[09:17] <davidbarth> bryce: i was not that requester; that's why i'm concerned
[09:18] <seb128> davidbarth: anyway sort that with ted when he's aorund and  I ping me back if there is an issue
[09:18] <davidbarth> seb128: will do
[09:19] <seb128> thanks
[09:19] <didrocks> hi there o/
[09:19] <seb128> lut didrocks
[09:19] <didrocks> seb128: I hope you crashed gracefully in your bed :)
[09:20] <seb128> didrocks: yeah, I'm looking forward to have a weekend and some extra sleep too though ;-)
[09:20] <didrocks> :-)
[09:20] <dpm> hi all, regarding the string changes, yes, davidbarth talked to me, but I directed him to ArneGoetje, since I'm still settling in. What I think we should do at some point is to better document the string freeze process and find a good way to let translators know about string freeze breaks.
[09:21] <davidbarth> dpm: yeah, but this one (fusa) was a rogue last minute change, nothing we had discussed previously
[09:22] <seb128> brb
[09:23] <bryce> davidbarth: there is confirmation from you on the bug itself - bug 356132
[09:24] <davidbarth> bryce: er?!
[09:24] <bryce> https://bugs.edge.launchpad.net/ubuntu/+source/fast-user-switch-applet/+bug/356132/comments/2
[09:24] <davidbarth> bryce: right, on the minimize button issue, not about the string change
[09:25] <lool> seb128: GNOME #575247
[09:25] <lool> seb128: I've just pushed a gnome-keyring workarounding seemingly the same bug on armel
[09:25] <seb128> lool: yes?
[09:25] <seb128> lool: should be fixed in 0ubuntu6 I uploaded yesterday
[09:25] <lool> Crap
[09:25] <lool> seb128: Ok; thanks, we should try it out
[09:25] <seb128> lool: see bug #328167
[09:26] <seb128> lool: http://svn.gnome.org/viewvc/gnome-keyring/trunk/egg/egg-secure-memory.c?r1=1706&r2=1705&pathrev=1706
[09:26] <seb128> lool: ups, bug #338158 I meant
[09:26] <lool> seb128: Just too bad I didn't notice you included the patch before adding the -O1 myself
[09:26] <seb128> Ng: ^ did you try the keyring update?
[09:26] <lool> seb128: Ah, that was your bug; thanks
 bryce: i was not that requester; that's why i'm concerned   <-- according to bug 356132 you were indeed the requester, so if not you, who was the requester ted referred to above?
[09:27] <lool> Didn't see it in the GNOME one
[09:27] <seb128> lool: you know about https://launchpad.net/bugs/bugtrackers/gnome-bugs/nnnnnn?
[09:27] <seb128> lool: reverse mapping, give you the launchpad bugs which point on GNOME nnnnnn
[09:27] <lool> seb128: No
[09:27] <lool> seb128: Thanks for telling me about it!
[09:27] <seb128> that can be handy ;-)
[09:27] <lool> Indeed
[09:28] <seb128> I've a smart bookmark on that
[09:28] <seb128> and a script which get all the ChangeLog #nnnnn so I can know what bugs to close with an update
[09:28] <lool> Eh I'm creating a smart bookmark as we speak :)
[09:28] <seb128> I just open a tab for each bugs and see which ones have matchin launchpad entries
[09:28] <lool> hehe
[09:28] <lool> Nice
[09:29] <didrocks> lool: I have done the same when seb128 told me about this :)
[09:29] <seb128> I should clean that and put it online
[09:29] <davidbarth> bryce: read the bug report
[09:29] <davidbarth> bryce: the bug was about the minimize button, *not* about making a string change
[09:52] <lool> seb128: Turns out we still the gkd issue with your patch
[09:52] <lool> So I'll keep the -O1
[09:53] <seb128> ok
[09:53] <seb128> there is some other svn changes apparently so I'm not sure this one is enough
[10:01] <Ng> seb128: just checked that I'm up to date, will reboot and give it a go
[10:02] <seb128> Ng: ok thanks
[10:22] <lool> seb128: coherence > I've not been following the specifics and don't think I'll look into it, feel free to push a patch if you have one
[10:23] <seb128> lool: some motus are on it apparently so I will let them handle that one
[10:23] <lool> Great
[10:24] <Ng> seb128: well I just did a loop of 153 ssh's and it seems fine :)
[10:24] <seb128> Ng: excellent!
[10:24] <Ng> indeed :)
[10:24] <seb128> Ng: thanks for testing
[10:24] <Ng> np
[11:21] <Ampelbein> seb128: sorry about breaking totem update.
[11:24] <seb128> Ampelbein: that's ok, I fixed it, that's what you get for doing review after 1oclock ;-)
[12:08] <davidbarth> seb128: ping? i've spotted two regressions, and one is a pidgin crasher
[12:08] <seb128> davidbarth: hello, which ones?
[12:08] <davidbarth> seb128: sabdfl's pidgin session keeps crashing
[12:08] <davidbarth> seb128: it's ok on my desktop but mirco sees that too
[12:09] <seb128> davidbarth: that's bug #357949
[12:09] <davidbarth> seb128: second, the volume notifications are not sent anymore (nothing in n-osd debug log), so there must be something wrong with the patch not being applied anymore, or so?
[12:09] <seb128> davidbarth: they can unset their buddy custom icon as workaround
[12:09] <seb128> davidbarth: g-s-d didn't change for several days, are you sure it's not on your side?
[12:10] <davidbarth> seb128: will double check and report in a few minutes
[12:59] <lool> seb128: The vfp stuff is merged in gtk+ as well in Debian; like pango, it will be 3 lines to uncomment or so until the change is merged in debian glibc
[12:59] <seb128> lool: ok thanks
[12:59] <seb128> lool: you uploaded the change to jaunty?
[13:00] <lool> seb128: I'm about to
[13:00] <lool> seb128: I was about to ask you whether it was ok to upload pango and gtk
[13:00] <seb128> lool: I update gtk this morning be sure to get the current version
[13:00] <seb128> updated
[13:00] <seb128> lool: yes
[13:00] <lool> Ok, thanks
[13:06] <lool> seb128: 2.16.0-1ubuntu3?
[13:06]  * lool goes checking unapproved
[13:06] <seb128> lool: no 1ubuntu4
[13:06] <lool> Ok
[13:06] <seb128> lool: it has been approved an hour ago
[13:06] <lool> aha
[13:07] <seb128> we need to put everything under bzr ;-)
[13:07]  * didrocks logs this :-)
[13:07] <seb128> didrocks: hey
[13:08] <seb128> didrocks: there is still a pidgin crash btw
[13:08] <didrocks> seb128: oh, really? It didn't crashed yesterday with the updated libxml package
[13:08] <didrocks> seb128: do you have a bug number with a procedure explaining how to crash it?
[13:08] <seb128> didrocks: it crashes when you have a custom buddy image for your jabber account or try to add one
[13:09] <seb128> didrocks: still the same bug number, it has been updated
[13:09] <didrocks> seb128: ok, if nothing changes, I will try to give a look tonight (but surely not before 8-9 PM). I can't access to jabber in my company
[13:12] <didrocks> seb128: I just don't understand exactly why pidgin interacts with gstreamer-plugins-bad (I can understand for usual gstreamer plugins, but why bad ones can be used too?)
[13:14] <seb128> didrocks: did you read the debian bug I pointed yesterday?
[13:17] <seb128> didrocks: sorry I was distracted again
[13:17] <seb128> didrocks: gstreamer installs a libxml error handler or something which conflicts with the libxml one
[13:17] <lool> seb128: I don't think you want the latest changes in gtk+2.0 in Debian as some seem intrusive (symbols and icon-cache changes)
[13:17] <lool> seb128: However you could sync the next experimental uploads if you wanted
[13:18] <seb128> lool: jaunty is frozen now, I'm in favor of not touched anything until karmic now
[13:18] <seb128> lool: but thanks for the notice
[13:18] <lool> seb128: Yup, we agree
[13:19] <seb128> touched -> touching
[13:19] <seb128> lool: thanks for syncing the ubuntu changes, I've been worked with kov to get in sync again but he missed some of the changes
[13:21] <lool> kov does a lot of typos / simple mistakes etc.
[13:21] <lool> I prefer checking what he changes too
[13:21] <didrocks> seb128: ok, so the error comes from the gstreamer way of handling libxml errors. Hum, not sure to be awaken when you provided the debian bug reference :)
[13:22] <seb128> didrocks: you replied after I gave the number
[13:22] <seb128> didrocks: there is a bug watch to the debian and gnome bug on launchpad too
[13:22] <seb128> didrocks: bug #357949
[13:23] <seb128> didrocks: no, the issue is a libxml one apparently, it doesn't let other software do things they should be able to do
[13:23] <seb128> didrocks: but I might be wrong, I will try to sort that with upstream when they are around
[13:23] <didrocks> seb128: ok, let me read the debian bug
[13:27] <lool> seb128: I'm preparing ubuntu6 with the VFP pass and an autotools-dev bdep; will push to our ARM ppa first to try it on armel.
[13:27] <lool> Err ubuntu5
[13:27] <seb128> lool: what about ubuntu5?
[13:27] <seb128> ok ;-)
[13:28] <seb128> didrocks: one course of action would be to disable the new error handle in gstreamer
[13:29] <didrocks> seb128: so, libxml triggers on errors any registered application and gstreamer is one of this, but the previous version of libxml was erasing schannel value even if it was not NULL, which is no more the case and make pigdin crashes, right?
[13:29] <lool> seb128: (and pango1.0 1.24.0-3ubuntu1)
[13:30] <seb128> didrocks: dunno about the previous libxml version, the bug is there for a while but nothing else was setting conflict hanlders before
[13:30] <seb128> lool: ok thanks
[13:30] <didrocks> seb128: ok, right, keep me in touch if I can be helpful (or if we use something like --gst-disable-segtrap)
[13:30] <didrocks> as a workaround
[13:31] <seb128> didrocks: if you have some time with it I would appreciate if you can give a try to the gst workaround
[13:31] <seb128> it try setting a custom icon for jabber
[13:31] <seb128> it will crash for pretty sure
[13:31] <asac> Nafallo: does gajim work for you at all? it doesnt open any chat for me anymore :(
[13:31] <seb128> and then try the gst change, if it fixes it upload
[13:32] <didrocks> seb128: I will try, but I can't before 8 PM
[13:34] <seb128> didrocks: that's ok, no hurry
[13:34] <seb128> thanks
[13:34] <didrocks> seb128: you will thank me if I can do something for it :)
[13:35] <seb128> ;-)
[13:37] <asac> Nafallo: gajim.py:3386: Warning: /build/buildd/glib2.0-2.20.0/gobject/gsignal.c:3075: signal name `selection_changed' is invalid for instance `0x27bd690'
[13:37] <asac> those look suspicious
[13:38] <asac> Nafallo: hmm. seems like the "single window for everything" is broken. detaching window helps
[14:16] <Nafallo> asac: are you talking about WITH python-indicate now
[14:16] <Nafallo> ?
[14:22] <asac> Nafallo: no. with and without
[14:23] <asac> single-window mode is broken ;)
[14:23] <Nafallo> asac: JID?
[14:24] <Nafallo> asac: works for me.
[14:24] <Nafallo> up to date jaunty
[14:30] <asac> Nafallo: single window mode?
[14:31] <Nafallo> asac: that's all I'm ever using.
[14:38] <asac> sigh
[14:38] <asac> too bad ;)
[14:38] <asac> so no jabber for me until i figure
[14:46] <walters> does ubuntu use the "console" auth concept?
[14:47] <james_w> yeah
[14:47] <james_w> we're trying to move away from "at_console" though as I understand it
[14:47] <walters> ok thanks, i was really confused about this bug
[14:48] <walters> james_w: is root also at console?
[14:48] <james_w> that I'm not sure about
[14:49] <james_w> can I take a look at the bug?
[14:49] <walters> (it's not on fedora, but is on suse)
[14:49] <walters> james_w: http://bugzilla.gnome.org/show_bug.cgi?id=577122
[14:52] <jcastro> hey seb128, james_w was linking me to this: http://bugzilla.gnome.org/show_bug.cgi?id=578444
[14:53] <jcastro> is that related to this? https://bugs.edge.launchpad.net/ubuntu/+source/gnome-control-center/+bug/207781
[14:54] <seb128> jcastro: that's basically http://bugzilla.gnome.org/show_bug.cgi?id=154029
[14:54] <jcastro> right
[14:54] <jcastro> seb128: so we fixed it sometime between comment 33 and 34?
[14:54] <seb128> jcastro: the patch has been written by matthew garrett
[14:55] <seb128> jcastro: dunno, who did incremental changes
[14:55] <seb128> jcastro: what is the issue?
[14:56] <jcastro> seb128: I am trying to figure out what happened here: http://bugzilla.gnome.org/show_bug.cgi?id=154029#c34
[14:57] <seb128> jcastro: it happened that they never bothered commenting on the patches so we didn't bother updating them either
[14:58] <mclasen> jcastro: I told peter to look at porting the ubuntu patch to device properties
[14:58] <mclasen> but he came back and told me that it was already using properties...
[14:58] <seb128> jcastro: I'm not sure who did the patch update, that's somebody from #ubuntu-x not #ubuntu-desktop I think
[14:58] <james_w> walters: so, we have the root section as well
[14:59] <jcastro> seb128: I think it was wgrant and reviewed by bryce?
[14:59] <mclasen> the patch that we ended up using is a bit different from yours, though. peter added 'disable while typing' support
[14:59] <jcastro> mclasen: ok I am just trying to figure out why no one raised their hand when they felt the patch was ready for upstreaming
[14:59] <seb128> jcastro: right
[14:59] <mclasen> jcastro: its time to finally get this all upstream
[14:59] <jcastro> if it ever got to that point
[15:00] <james_w> walters: kees's suggestion just duplicates the root parts to an at_console. Is there something running as the user when it should be root?
[15:00] <jcastro> mclasen: nod
[15:00] <mclasen> jcastro: I'm not blaming anyone, really. I'm just happy that peter got this working for us very quickly...
[15:00] <walters> james_w: doesn't look like it, both the send and recieve side are uid=0 in the log
[15:01] <seb128> jcastro: I think that one is a case where different people touched the thing, the original author (matthew) didn't upstream it and nobody cared to update the upstream bug when fixing issues
[15:01] <jcastro> mclasen: yeah that's ok, we used to get alot of flak about this kind of thing and we've made alot of progress to fix it so I just wanted to make sure
[15:01]  * jcastro isn't looking to assign blame or anything like that
[15:01] <jcastro> seb128: ok so we can all agree to blame garrett, sounds fine to me. :p
[15:02] <seb128> jcastro: ;-)
[15:05] <mclasen> peter also fixed the dontzap fiasco, good guy...
[15:06] <jcastro> mclasen: I "collect" bugs about patch issues, so feel free to ping me when things like this happen
[15:18] <myrandomstuff> hello all
[15:20] <tseliot> mclasen: when will those patches be included in Gnome? In which version of Gnome?
[15:21] <mclasen> tseliot: not my call, but I hope to see them in 2.28
[15:21] <tseliot> mclasen: ok
[15:35] <myrandomstuff> would this be a good place to get some assistance with Audacity?
[15:37] <kenvandine_wk> asac: i have an update to indicate-python... bug 358483, can you give it an ack?
[15:38] <kenvandine_wk> asac: it includes better fixes than we had yesterday :)
[15:38] <kenvandine_wk> james_w: can you do the same please?
[15:39] <asac> kenvandine_wk: did they fix the licensing?
[15:39] <asac> ;)
[15:39] <asac> sorry if i sound like a broken record
[15:39] <kenvandine_wk> yes
[15:39] <kenvandine_wk> they merged my branch :)
[15:39] <asac> ok looking ;)
[15:39] <asac> kenvandine_wk: err. the tests/
[15:39] <asac> those i care most about ;)
[15:39] <kenvandine_wk> well... i know
[15:40] <kenvandine_wk> i told them
[15:40] <asac> kenvandine_wk: you could hav esuggested a similar merge
[15:40] <kenvandine_wk> but it is better than yesterda :)
[15:40] <james_w> they are done
[15:41] <kenvandine_wk> i need 2 ubuntu-dev acks right?
[15:42] <james_w> nope, that's just for new packages
[15:42] <kenvandine_wk> ah
[15:42] <kenvandine_wk> ok
[15:42] <kenvandine_wk> good :)
[15:42] <james_w> you now need motu-release ACK, and one dev to upload
[15:42] <kenvandine_wk> ok
[15:43] <james_w> looks fine to me
[15:43] <kenvandine_wk> great
[15:43] <james_w> how does this stand with 0.1.5 compatibility
[15:43] <james_w> anything to be aware of?
[15:44] <kenvandine_wk> better than yesterday
[15:44] <kenvandine_wk> there is one bug
[15:44] <kenvandine_wk> but doesn't affect anything yet
[15:44] <kenvandine_wk> but that bug existed yesterday as well
[15:44] <kenvandine_wk> this is basically a better fix than what tedg had yesterday
[15:44] <asac> kenvandine_wk: they are fixed ;)
[15:45] <asac> kenvandine_wk: how about shipping them in examples?
[15:45] <kenvandine_wk> from eeejay
[15:45] <kenvandine_wk> asac: i would rather have the makefile do that in make install
[15:45] <kenvandine_wk> but i guess i could just do that in the packaging
[15:45] <asac> right
[15:45] <asac> just a suggestion
[15:45] <asac> definitly nothing essential
[15:46] <kenvandine_wk> just feels ugly to me... :)
[15:46] <james_w> kenvandine_wk: so you can't write a listener in python currently?
[15:46] <kenvandine_wk> james_w: right
[15:46] <james_w> I don't think that's an issue really
[15:47] <kenvandine_wk> asac: so /usr/share/doc/python-indicate/tests
[15:47] <kenvandine_wk> ?
[15:47] <kenvandine_wk> james_w: right... not urgent atm
[15:48] <asac> kenvandine_wk: yeah. thats a possibility
[15:49] <james_w> kenvandine_wk: make it /usr/share/doc/python-indicate/examples I guess
[15:49] <eeejay> kenvandine_wk: oops, i forgot to include the tests in the dist
[15:49] <asac> +                                     (guint) indicator,
[15:49] <asac> isnt that a pointer? ;)
[15:49] <asac> GPOINTER_TO_UINT (indicator) ;)
[15:49] <dobey> james_w: btw, any luck with a bzr 1.13.2 release including that patch?
[15:49] <kenvandine_wk> eeejay: can you respin the tarball?
[15:49] <eeejay> asac: it isn't in 0.1.5 anymore
[15:49] <james_w> dobey: I enquired about it yet, but I imagine 1.13.2 will be after 1.14
[15:50] <asac> eeejay: what isnt in 0.1.5?
[15:50] <james_w> dobey: also there is another bug they are chasing that will be fixed in 1.13.2 as well, and I'm not sure they've nailed it yet
[15:50] <asac> eeejay: you mean:
[15:50] <asac> -                                     (guint) *indicator,
[15:50] <asac> +                                     (guint) indicator,
[15:50] <eeejay> asac: IndicateListenerIndicator is not an int/pointer anymore
[15:50] <asac> ?
[15:50] <eeejay> asac: yup
[15:51] <dobey> james_w: ah
[15:51] <asac> eeejay: stilly you cast the pointer to guint ;)
[15:51] <asac> still
[15:51] <eeejay> asac where are you pulling those lines from?
[15:51] <kenvandine_wk> asac: ok, i pushed the packaging branch again... installs the examples
[15:51] <asac> eeejay: bzr diff
[15:51] <asac> kenvandine_wk: greawt
[15:52] <eeejay> asac: exactly, that is why it is broken ;)
[15:54] <asac> eeejay: hmm. so its even broken in 0.0.3?
[15:54] <eeejay> asac: yes
[15:54] <asac> eeejay: is there a fix somewhere?
[15:55] <eeejay> asac: i have a branch for libindicate and indicate-python that fixes this
[15:55] <eeejay> asac: but we are running late, and it requires libindicate  changes too
[15:56] <eeejay> asac: here is my conversation with tedg regarding it:
[15:56] <tedg> asac: This is in the listener interface that does not work in the python bindings.
[15:56] <asac> tedg: ok.
[15:56] <eeejay> asac: https://code.launchpad.net/~ted-gould/indicator-applet/python-bindings-dont-know-what-im-doing/+merge/5366
[15:56] <tedg> asac: So in 0.0.3 it doesn't work differently :)
[15:56] <asac> tedg: so do you have any clue why gajim doesnt work? it doesnt change state of the indicator when message notify happens
[15:57] <asac> kenvandine_wk: may i suggest to use dh_install -p... ? instead of move?
[15:57] <kenvandine_wk> sure
[15:57] <Nafallo> asac: so the binary passed binary new now?
[15:57] <tedg> asac: No, I do not.  kenvandine_wk thought it was something to do with them modifying his patch.
[15:57] <asac> Nafallo: not sure ;)
[15:57] <asac> Nafallo: havent checked
[15:58] <Nafallo> asac: wouldn't it be hard for me to reproduce something without having all the parts you reckon?
[15:58] <asac> tedg: hmm. its odd .. the code is the same as the example im client
[15:58] <asac> tedg: and i added print and it definitly gets to indicator.show
[15:58] <kenvandine_wk> asac: you looked at gajim?
[15:58] <asac> Nafallo: you know how to build a package, right ;)?
[15:58] <tedg> asac: Hmm, can you run "/usr/lib/indicator-applet/listen-and-print" in a terminal and see what gajim is sending?
[15:58] <Nafallo> asac: I'm at work. if it's not quick I can't prioritise it.
[15:59] <asac> kenvandine_wk: i wanted to look at gajim, but then i found that my single-window-mode is completely borked and stopped looking further on top of a flaky base ;)
[15:59] <asac> e.g. my single-chat window doesnt even open here
[15:59] <asac> kenvandine_wk: do you see the same behaviour that i described above in gajim (e.g. no change of status in indicator)?
[15:59] <asac> Nafallo: that package is tiny ;)
[16:00] <Nafallo> asac: I haven't got a build environment except PPAs...
[16:00] <asac> Nafallo: dget https://edge.launchpad.net/ubuntu/jaunty/+source/indicate-python/0.0.2-0ubuntu1/+files/indicate-python_0.0.2-0ubuntu1.dsc; dpkg-source -x *.dsc; cd indicate-pyth*/; dpkg-buildpackage -rfakeroot ;)
[16:00] <asac> Nafallo: ok
[16:00] <kenvandine_wk> asac: yeah... which is weird
[16:00] <kenvandine_wk> it worked before
[16:01] <kenvandine_wk> the im-client example still works
[16:01] <kenvandine_wk> gwibber still work
[16:01] <kenvandine_wk> s
[16:03] <eeejay> kenvandine_wk: re-uploading tarball now
[16:04] <kenvandine_wk> thx
[16:05] <eeejay> done
[16:15] <asac> reuploading tarball?
[16:15] <asac> is there a new release?
[16:15] <kenvandine_wk> asac: no... just added the tests dir to the dist target
[16:15] <kenvandine_wk> they weren't included
[16:18] <kenvandine_wk> asac: i pushed a change to use dh_install
[16:19] <asac> kenvandine_wk: ok. through a new tarball?
[16:20] <asac> e.g. do i need to update the tarball?=
[16:20] <kenvandine_wk> yeah :/
[16:20] <kenvandine_wk> the tests were missing in the tarball
[16:21] <asac> kenvandine_wk: err. you also need to do a new merge in bzr i guess
[16:21] <asac> otherwise it will show up in diff.gz as a negative diff i would think
[16:21] <kenvandine_wk> oh right... damn
[16:21] <kenvandine_wk> yeah
[16:21]  * kenvandine_wk does that
[16:22] <kenvandine_wk> asac: done... thx!
[16:22] <eeejay> ok, i am off for a while
[16:22] <kenvandine_wk> later eeejay
[16:22] <kenvandine_wk> thx
[16:22] <eeejay> kenvandine_wk: no, thank you :)
[16:56] <kenvandine_wk> so i appear to have been hit by the pidgin crashes when connecting to jabber bug :)
[16:59] <seb128> yeah, it's a popular one today
[17:02] <kenvandine_wk> asac: i got an ack for indicate-python, can you upload it?
[17:04] <asac> kenvandine_wk: yeah
[17:05] <kenvandine_wk> asac: thx
[17:07] <asac> argh. so i managed to upload the previous tarball. too bad. but well. at least the diff is in the right direction
[17:09] <asac> got struck by new bzr bd behaviour (preferring builds/ tarball over tarballs)
[17:18] <pitti> Good morning
[17:18] <pitti> how's things?
[17:19]  * pitti hugs the channel
[17:19] <asac> pitti: all good. i am in easter mode, but still working :)
[17:20] <kenvandine_wk> pitti!
[17:20] <kenvandine_wk> pitti: got a few minutes to look at something?
[17:20] <seb128> hey hey pitti
[17:21] <asac> kenvandine_wk: ok i reuploded it with a new tarball version
[17:21] <seb128> pitti: I'm looking forwarding the weekend and getting some sleep but otherwise good
[17:21] <pitti> kenvandine_wk: hey, what's up?
[17:21] <kenvandine_wk> bug 353768
[17:21] <asac> kenvandine_wk: you can bzr merge lp:~asac/indicator-applet/0.0.3+1
[17:21] <kenvandine_wk> mvo uploaded a fix to his ppa for testing
[17:21] <kenvandine_wk> asac: will do
[17:21] <seb128> pitti: I did the notify-osd update btw
[17:22] <kenvandine_wk> pitti: but... ekiga is still held back in update-manager
[17:22] <kenvandine_wk> pitti: but not with dist-upgrade
[17:22] <kenvandine_wk> pitti: does that make any sense?
[17:23] <asac> kenvandine_wk: does dist-upgrade install NEW packages?
[17:23] <asac> or remove packages?
[17:23] <kenvandine_wk> yeah
[17:23] <asac> if so, its expected
[17:23] <asac> oh update-manager
[17:23] <kenvandine_wk> i would expect the same behavior
[17:23] <asac> thought it would install NEW packages
[17:24] <seb128> update-manager doesn't do that if you don't use the dist-upgrade mode
[17:24] <kenvandine_wk> oh
[17:24] <asac> seb128: update-manager doesnt install NEW packages?
[17:24] <asac> ok then it explains my confusion ;)
[17:24] <seb128> asac: not the standard mode, when there is new packages to install it displays an extra dialog which runs the dist-upgrade mode if required
[17:25] <pitti> kenvandine_wk: hang on, talking to sb, back in 5
[17:25] <seb128> ie it ask you on startup if you want to open the dist-upgrader
[17:25] <asac> hmm. maybe is should use update manager more
[17:25] <seb128> is = you?
[17:25] <asac> I ;)
[17:25]  * kenvandine_wk grabs a bite to eat... back soon
[17:33] <pitti_> seb128: I saw, thanks
[17:34] <asac> [ubuntu/jaunty] indicate-python 0.0.3+1-0ubuntu1 (Waiting for approval)
[17:37] <pitti_> kenvandine_wk: ah, that looks like an apt quirk
[17:40] <pitti_> kenvandine_wk: if the number of dependencies to the old package is not significantly smaller than the number of dependencies to the new one, it prefers to hold it back
[17:40] <pitti_> kenvandine_wk: can you please talk to mvo about it? seems he solved it already in his ppa
[17:40]  * pitti_ is just too busy here, hard to find a quiet spot
[17:40] <pitti_> but then again, that's the point of the conf :)
[17:45] <kenvandine_wk> pitti_: mvo
[17:45] <kenvandine_wk> 's fix doesn't work
[17:45] <kenvandine_wk> and now he is on holiday
[17:45] <asac> kenvandine_wk: whats the problem?
[17:46] <kenvandine_wk> asac: ekiga is getting held back
[17:46] <asac> kenvandine_wk: what kind of transition was done with ekiga packaging?
[17:46] <kenvandine_wk> to quote mvo "it is apt being stupid"
[17:46] <kenvandine_wk> dist-upgrade gets it
[17:47] <asac> right. but what are the changes that ekiga got that lead to this?
[17:47] <pitti_> kenvandine_wk: update-manager you mean?
[17:47] <kenvandine_wk> asac that is what he tried in his ppa... but no luck
[17:47] <kenvandine_wk> he said apt
[17:47] <pitti_> kenvandine_wk: why do the libpt2.6* packages conflict to the libpt2.4* ones in the first place? that looks like the root of the problem
[17:47] <kenvandine_wk> asac version bump
[17:47] <pitti_> kenvandine_wk: we give packages different library sonames so that we can avoid those
[17:47] <pitti_> hmm
[17:47] <kenvandine_wk> mvo didn't think so
[17:48] <asac> yeah lib2.6 shoulnt conflict lib2.4
[17:49] <kenvandine_wk> maybe that would fix it... mvo and slangask has discussed this in detail... i'd think they would have tried that
[17:49] <pitti_> Package: libpt2.6.1-plugins-v4l2
[17:49] <pitti_> Conflicts: [...
[17:49] <pitti_> libpt2.4.2-plugins-v4l2
[17:49] <seb128> slangasek and cjwatson were wondering about this conflicts too yesterday I think
[17:50] <pitti_> that looks wrong
[17:50] <kenvandine_wk> ok, i will try to fix that
[17:50] <pitti_> the previous version did it as well, I think, but it's still wrong
[17:50] <kenvandine_wk> pitti_: it did...
[17:50] <pitti_> seb128: do you have some time to help kenvandine_wk with that? I need to go offline again
[17:50] <kenvandine_wk> which is what i followed
[17:51] <kenvandine_wk> i'll get it in my ppa and test
[17:51] <asac> conflicting would require a package removal and that is what update-manager doesnt do
[17:51] <seb128> pitti_: I will try having a look but I'm away for sport soon
[17:51] <seb128> asac: well, when you need a removal it opens this dialog asking if you want to dist-upgrade
[17:51] <seb128> or if you need a new package to be installed
[17:52] <asac> seb128: given that dist-upgrade works i guess its really the removal. i remember that mvo told me at some point that he never removes packages except for dist-upgrades
[17:53] <asac> personally i have never seen the "dist-upgrade" dialog you refer to
[17:53] <seb128> ok, so maybe the dialog is to install new packages only
[17:53] <asac> just what you get when running update-manager -d
[17:53] <asac> seb128: yeah. i think its for new
[17:53] <asac> update-manager installs new, but doesnt remove packages, while apt-get upgrade does neither, and dist-upgrade does both :) ... hope thats correct now ;)
[17:54] <seb128> is the content of those libs actually conflicting?
[17:54] <seb128> why has the conflicts there been used?
[17:54] <asac> if not, just drop the conflicts
[17:54] <asac> ;)
[17:54] <seb128> who did the update?
[17:55] <asac> doesnt look like they conflict
[17:55] <asac> http://paste.ubuntu.com/147765/
[17:55] <asac> unless libpt2.4 shipped 2.6 files :-P
[18:01] <asac> Build conflicts: libpt2.6.1 libpt2.4.2
[18:14] <Ng> ok, so either xul things (FF/TB) can't talk to gnome-vfs anymore, or I'm on crack and they never could
[18:15] <Ng> I just had someone in the office say they can't attach files from an sftp share to email in TB because it's not showing up in the volume list, and they're right, and the same happens on mine, but I can't completely confirm that it ever did work because I've never done it myself
[18:16] <seb128> Ng: the fileselector is using gvfs nowadays so the sftp share is not in gnomevfs
[18:16] <Ng> sorry, my bad, I mean gvfs
[18:16] <seb128> is the share in gedit for example?
[18:17] <Ng> yes
[18:17] <seb128> ok, so talk to asec
[18:17] <seb128> asac
[18:17] <seb128> they might be using the fileselector in local mode
[18:17] <seb128> you can still browse .gvfs but that's not obvious
[18:17] <seb128> or use a GNOME email client ;-)
[18:20] <Ng> seb128: I'll mention the .gvfs workaround and conferr with asac asap (if he has any sense he's already enjoying his easter weekend ;)
[18:20] <seb128> the distro team people don't have any sense usually don't worry ;-)
[18:21] <seb128> or not just on freeze line for a new version ;-)
[18:22] <seb128> that being said time for sport bbl
[18:25] <calc> Ng: it should be fairly easy to get FF/TB to work with gvfs fuse
[18:26] <calc> Ng: if your app has gtk dialog but not gio support you can tell GFile to give you file paths instead of uris
[18:26] <calc> Ng: i changed OOo to doing that for this release since its gnomevfs and gio support was broken
[18:29] <Ng> calc: I'm fairly sure this was working
[19:37] <didrocks> seb128: every stacktraces have no function shown in #0 (I think, the call of gstreamer0.10-plugins-bad function) , people didn't install gstreamer0.10-plugins-bad-dbg?
[19:39] <didrocks> (it seems you said that it's fixed, but my question still exists, btw ;))
[19:40] <didrocks> (and ok, you took the proposed patch in debian BTS for pidgin)
[19:42] <Keybuk_> YOUR POWER IS CRITICALLY LOW AND I'm ABOUT TO HIBER*bzzp*
[19:42] <Keybuk_> Too Late!
[19:42] <hyperair> lolwut
[19:52] <Nafallo> asac: hi
[20:12] <seb128> didrocks: the crash is not in gst but libxml
[20:59] <kenvandine_wk> seb128: i removed the Conflicts and the Replaces... still not fixing the problem