[01:21] <bcurtiswx> Reinstallation of telepathy-haze is not possible, it cannot be downloaded.
[01:21] <bcurtiswx> in natty, afaik it can be :-\
[01:25] <psusi> while testing an unrelated patch to nautilus, I find that my system menu is back and the minimize/maximize/close icons are back on the right side of the window.  This is still the case after downgrading packages.  The menus are normal if I log in as another user.  What about my profile got screwed up to cause this?
[06:06] <pitti> Good morning
[06:09] <pitti> dobey: ah, I never noticed that; yes, it adds the .bzr-builddeb/ dir, as this is not part of debian/, but also not part of upstream
[06:09] <pitti> dobey: kind of a shortcoming of bzr-bd
[06:18] <robert_ancell> hey pitti - the langpack stuff doesn't work with dh7 does it?
[06:19] <pitti> hey robert_ancell
[06:19] <pitti> robert_ancell: not yet, no; we didn't yet create a dh_langpack for the magic, it's all in the cdbs langpack.mk so far
[06:19] <robert_ancell> pitti, ok, cheers
[06:21] <robert_ancell> pitti, actually you might be able to help me with this one.  You seem to be a regular uploader to aptdaemon, is it OK to change it to cdbs so it uses langpack.mk?
[06:22] <pitti> robert_ancell: which parts do we need from it actually? just pot file building?
[06:22] <robert_ancell> pitti, the .policy file conversion to using gettext-domain and stripping the xml translations
[06:22] <robert_ancell> bug 690270
[06:22] <ubot2> Launchpad bug 690270 in ubuntu-translations "Translated String (zh_TW) Not Showed within aptdaemon" [Medium,Triaged] https://launchpad.net/bugs/690270
[06:24] <pitti> robert_ancell: so, not sure whether glatzor/mvo would mind a cdbs conversion; TBH I'd rather ask them first
[06:24] <robert_ancell> pitti, ok np, I'll flick them the bug
[06:24] <pitti> robert_ancell: we haven't had the problem so far, but as we do now I can also look into creating a dh_langpacks
[06:24] <robert_ancell> pitti, can we do it without duplicating the code?
[06:25] <pitti> robert_ancell: the code would move to dh_langpacks, and cdbs langpack.mk would then just call that
[06:25] <robert_ancell> oh that's good - that sounds like the best solution
[06:26] <pitti> main question is in which package to ship it
[06:26] <pitti> I guess I could build it from pkgbinarymangler
[06:26] <pitti> and produce a new dh-langpack package
[06:26] <pitti> which cdbs would then depend on
[06:27] <pitti> then it would be seamless for cdbs
[06:30] <robert_ancell> seamless always sounds good :)
[06:50] <Amaranth> robert_ancell: I just made compiz depend on cdbs for langpack stuff even though it uses a dh7-style build system
[06:50] <robert_ancell> Amaranth, so you can get around it?  Thanks
[06:51] <Amaranth> Hmm, actually I'm not even sure where this code came from
[06:52] <Amaranth> But yeah, there is code in the compiz debian/rules for calling out to cdbs stuff for handling .desktop and .schema files for language packs
[06:52] <Amaranth> I must have copied it from another package in Ubuntu, either that or didrocks did it
[06:55] <pitti> Amaranth: so it seems it gets high time for dh --with=langpack
[06:56]  * mvo hugs glatzor
[06:56] <pitti> hey glatzor, hey mvo, guten Morgen
[06:57] <mvo> hey pitti, guten morgen!
[06:59] <didrocks> good morning
[07:00] <Amaranth> morning didrocks
[07:00] <didrocks> hey Amaranth
[07:00] <Amaranth> didrocks: hey, did you add the code in the compiz debian/rules for using cdbs stuff for langpacks?
[07:00] <Amaranth> I suppose I could just bzr blame but this seems easier
[07:00] <didrocks> Amaranth: IIRC, I did port that
[07:00] <didrocks> why?
[07:01] <pitti> robert_ancell, Amaranth: bug 735934 FYI, feel free to subscribe
[07:01] <ubot2> Launchpad bug 735934 in pkgbinarymangler "Build dh_langpack" [Medium,In progress] https://launchpad.net/bugs/735934
[07:01] <pitti> didrocks: ^ I think you were interested in that as well
[07:01] <Amaranth> I remember having issues building it on a PPA that I didn't locally because I had cdbs already so I thought I copied it from somewhere
[07:01] <didrocks> Amaranth: I don't use cdbs, it's all dhè
[07:02] <Amaranth> didrocks: Oh, we were just talking about that bug and I started thinking about it
[07:02] <didrocks> 7*
[07:02] <Amaranth> didrocks: But you call out to perl scripts installed by cdbs
[07:02] <didrocks> /usr/lib/cdbs/strip-schema.pl
[07:02] <didrocks> right
[07:03] <didrocks> pitti: yeah, that's part of I wanted to do
[07:03] <didrocks> what*
[07:03] <didrocks> still have the task, working on more urgent stuff, right now, though
[07:03] <pitti> didrocks: I'll work on it
[07:03] <didrocks> ok :)
[07:03] <pitti> didrocks: just want to point it out because I remembered that you were interested in using it
[07:04] <didrocks> pitti: btw, is the gnome-session stuff still scheduled?
[07:04] <didrocks> yeah
[07:04] <pitti> didrocks: I have kept getting RCish bugs to work on so far :/
[07:05] <didrocks> pitti: not only for you, I would think that the whole team was concerned about gnome-session :)
[07:07] <mvo> thanks robert_ancell for the analysis on 690270
[07:07] <didrocks> pitti: I'll try to get some time this evening to work on it
[07:07] <robert_ancell> mvo, np
[07:58] <rodrigo_> morning
[08:14] <evilvish>  anyone heard of mousetweaks segfaulting in maverick?
[08:45] <seb128> hey
[08:47] <pitti> bonjour seb128
[08:47] <seb128> hello pitti
[08:47] <seb128> how are you?
[08:48] <pitti> seb128: I'm great, thanks!
[08:49] <pitti> was nice last night, had both our parents over, made pizza, and had some sparkling wine :)
[08:49] <rodrigo_> hi seb128, pitti
[08:49] <pitti> hey rodrigo_, how are you?
[08:49] <rodrigo_> pitti, I'm fine, thanks
[08:50] <seb128> hey rodrigo_
[08:50] <seb128> pitti, great!
[08:50] <seb128> pitti, so you drink wine now? ;-)
[08:50] <pitti> seb128: well, we call that "Sekt", it's similar to champagner
[08:50] <pitti> I do drink that, yes
[08:50] <rodrigo_> :)
[08:51] <pitti> I don't drink red wine at all, but recently I started to try some light white wine
[08:51] <pitti> (oh, and wine isn't off-topic here! ask YokoZar!)
[08:52] <rodrigo_> there is an ubuntu package for wine, so no, not off-topic here :)
[08:52] <pitti> rodrigo_: yeah, YokoZar is the maintainer
[08:52] <rodrigo_> ah :)
[08:53]  * pitti CPRs seb128 - are you back yet?
[08:56] <seb128> urg, internet went flacky and back
[08:57] <pitti> *phew*, he's back
[08:57] <seb128> pitti, hey again ;-)
[08:57]  * pitti hugs seb128
[08:57] <seb128> bah, seems the gdm update fails to start for some users
[08:57]  * seb128 hugs pitti
[08:57] <seb128> hate gdm!
[08:57] <pitti> my fault?
[08:58] <seb128> nfc
[08:58] <seb128> there are  changes in it
[08:58] <seb128> one ipv xdmcp git backport which I doubt would break things
[08:58] <seb128> jhunt's upstart tweaking
[08:58] <seb128> your's git backport for this login crash thing
[08:58] <pitti> doesn't start at all, or crashes? In the former case, I'd blame the upstart changes
[08:58] <seb128> I don't see anything obviously wrong
[08:59] <seb128> could be the upstart one?
[08:59] <pitti> I haven't rebooted since this morning's updates yet
[08:59] <seb128> they say it randomly doesn't start
[08:59] <pitti> seb128: depends on the symptoms -- crash or not start
[08:59] <pitti> but my backported login crash is fairly obvious
[08:59] <seb128> bug #735805
[08:59] <ubot2> Launchpad bug 735805 in gdm "GDM fails to start" [Undecided,Confirmed] https://launchpad.net/bugs/735805
[08:59] <pitti> it just hides a widget under some condition which we don't have by default
[08:59] <seb128> bdrung, ^ do you have specifics?
[09:06] <pitti> seb128: hm, can't see anything obviously broken in the upstart changes either
[09:06] <pitti> unless "runlevel PREVLEVEL=S" is true very early in the boot, in which case it would fail to start
[09:06] <pitti> or calling runlevel fails
[09:09] <pitti> seb128: replied to the bug
[09:09] <seb128> pitti, thanks
[10:11] <didrocks> pitti: good news, the gnome-session change isn't needed anymore. Now unity will disable itself if it launched and can't run
[10:12] <pitti> didrocks: oh, that's great!
[10:27] <seb128> hum, dear update-manager stop freezing and triggering apport if someone dismiss the password dialog by error
[10:30] <cdbs> seb128: yes, just noticed
[10:30] <cdbs> that
[10:31] <seb128> hey cdbs ;-)
[10:31] <cdbs> seb128: hi, how are you doing?
[10:32] <cdbs> seb128: my 4 month long study leave just ended, unfortunately I was not very active in this cycle because of exam
[10:32] <cdbs> s
[10:32] <seb128> cdbs, I'm fine thanks, how are you?
[10:32] <cdbs> rockin'
[11:18] <ogra_> seb128, why did you drop the armel workaround from telepathy-glib
[11:19] <seb128> ogra_, because I hate freedom and armel as well ;-)
[11:19] <ogra_> haha
[11:19] <didrocks> quoted
[11:19] <didrocks> :)
[11:19] <seb128> ogra_, joke aside what workaround?
[11:19] <seb128> ogra_, https://launchpad.net/ubuntu/+source/telepathy-glib/+changelog
[11:20] <ogra_> looks screwed up to me
[11:20] <seb128> ogra_, we are on sync for a while
[11:20] <ogra_> telepathy-glib (0.11.13-1ubuntu2) maverick; urgency=low
[11:20] <ogra_>   * use -O0 on armel builds to work around FTBFS due to failing selftests
[11:20] <ogra_>     issue is described in launchpad bug 623979, failing buildlog is attached
[11:20] <ogra_>     to that bug.
[11:20] <ubot2> Launchpad bug 623979 in telepathy-glib "telepathy-glib fails to build on armel due to two unsuccessfull selftests" [Undecided,Fix released] https://launchpad.net/bugs/623979
[11:21] <ogra_> apt-get soruce telepath-glib gets me a pretty different changelog btw
[11:22] <seb128> ogra_, right, it gives you the debian one since we synced
[11:22] <ogra_> without any ubuntu entries
[11:22] <seb128> ogra_, right, it's coming from debian
[11:22] <seb128> ogra_, why would they have ubuntu entries?
[11:22] <ogra_> hmm
[11:23] <seb128> ogra_, on why we dropped the -O0 because I had no clue if that was still an issue with the new gcc, telepathy stack, etc
[11:23] <seb128> and it's easier to sync with debian during the unstable cycle
[11:23] <ogra_> dunno why *they* would have them, but it would be good to not lose our entries for being able to look stuff up
[11:23] <seb128> ogra_, https://launchpad.net/ubuntu/+source/telepathy-glib/+changelog is what you are looking for
[11:23] <seb128> ogra_, we will not start merging every package that had ubuntu uploads rather than sync just for the changelog
[11:23] <ogra_> sure ...
[11:24] <seb128> that wouldn't make sense
[11:24] <ogra_> well, it was a bit irritating
[11:24] <seb128> ogra_, to start why nobody sent the workaround to debian?
[11:25] <ogra_> debian doesnt need it, they dont use our optimization levels
[11:25] <ogra_> (they build for armv5 etc etc)
[11:25] <seb128> could we be smart and only turn it on where needed?
[11:26] <ogra_> tricky
[11:26] <seb128> so we could keep the source without diff over debian
[11:26] <seb128> well, we could send them a patch with a dpkg-vendor call
[11:26] <seb128> i.e just enable it on Ubuntu
[11:26] <pitti> ... and make sure that we have a gcc bug filed for this
[11:27] <ogra_> its definitely a but that we need it at all, someone should fix it in the code i guess
[11:27] <ogra_> s/but/bug/
[11:29] <ogra_> for now i would just like to have images again though
[11:31] <seb128> ogra_, then get someone from linaro to work on the gcc issue?
[11:31] <ogra_> seb128, well, that will take weeks (by experience) gcc uploads dont just happen every day
[11:31] <seb128> well it's over a cycle
[11:31] <ogra_> i will have to apply the workaround anyway to get images back i fear
[11:32] <seb128> ogra_, ok, that's fine, it just made our job easier to sync during the unstable cycle, but I will drop it again next cycle
[11:32] <ogra_> k
[11:33] <seb128> ogra_, you should really open a gcc bug and maybe makes a patch that debian could take meanwhile, like using dpkg-vendor and set the workaround on Ubuntu
[11:33] <ogra_> well, first lets see if it fixes it still ;)
[11:33] <ogra_> yes, i will talk to linaro and open a bug
[11:33] <seb128> thanks
[11:33] <bdrung> seb128: i confirm that it's a breakage in the upstart job (bug #735805).
[11:33] <ubot2> Launchpad bug 735805 in gdm "GDM fails to start" [High,Confirmed] https://launchpad.net/bugs/735805
[11:34] <seb128> bdrung, thanks
[11:34] <bdrung> seb128: anything else you want to know?
[11:34] <seb128> bdrung, can you maybe ping jhunt on #ubuntu-devel?
[11:34] <seb128> bdrung, he's the one who did the change and he's investigating the breakage now but he doesn't get the issue
[11:35] <chrisccoulson> kklimonda, did you have any luck getting mongodb working with the latest mozjs?
[11:43] <kklimonda> chrisccoulson: no, I did fix some issues but I hit weird errors like http://pastebin.com/Pn4udv5z - I've commented on the upstream ticket, and I will probably give it another shoot next week, but now I'm swamped with work (both Ubuntu-related and not) so I can't tell if I'll get it into any shape before beta.
[11:43] <seb128> rodrigo_, do you think you could upstream the patch from bug #736042?
[11:43] <ubot2> Launchpad bug 736042 in gnome-media "add "PULSE_PROP_media.role" to gnome-sound-recorder" [Wishlist,Confirmed] https://launchpad.net/bugs/736042
[11:44] <rodrigo_> seb128, looking
[11:44] <chrisccoulson> kklimonda, thanks. where is the upstream ticket?
[11:44] <seb128> rodrigo_, hum, that's probably still in gnome-media which you don't maintain upstream, I guess we better git format that and send the bugzilla rather
[11:44] <kklimonda> chrisccoulson: http://jira.mongodb.org/browse/SERVER-2683
[11:44] <rodrigo_> seb128, that's what I was going to do
[11:45] <chrisccoulson> thanks
[11:45] <seb128> rodrigo_, if you want to do it please do ;-)
[11:45] <seb128> rodrigo_, thanks
[11:45] <rodrigo_> seb128, ok
[11:47] <rodrigo_> seb128, hmm, where else do we use that PULSE_PROP thing?
[11:47] <seb128> rodrigo_, http://pulseaudio.org/wiki/ApplicationProperties
[11:48] <seb128> rodrigo_, in ubuntu it's useful for the indicator sound
[11:48] <seb128> rodrigo_, it will show input sliders when you start an application which set it to phone or production see bug #736049
[11:48] <ubot2> Launchpad bug 736049 in indicator-sound "show record level control on PULSE_PROP_media.role=production" [Low,In progress] https://launchpad.net/bugs/736049
[11:49] <rodrigo_> ok
[11:49] <chrisccoulson> kklimonda, is the WIP patch anywhere?
[11:51] <Sweetshark> pitti: https://bugs.launchpad.net/bugs/712725 could you give the merge another try?
[11:51] <ubot2> Launchpad bug 712725 in nlpsolver "[MIR] libreoffice-nlpsolver" [Medium,Confirmed]
[11:51] <kklimonda> seb128: looks like the new glibmm release build-depends on mm-common for building documentation and mm-common is in universe.
[11:52] <Sweetshark> (see the latest comment on the issue)
[11:53] <kklimonda> chrisccoulson: no, but I can push what I wrote to github.. actually, there isn't much so I can just git you a diff itself ;)
[11:54] <chrisccoulson> kklimonda, yes please. i'll take a look later on
[11:55] <kklimonda> chrisccoulson: http://paste.ubuntu.com/581055/
[11:55] <chrisccoulson> thanks
[11:55] <didrocks> hum, we need to do a fake upload to pull in a package which is in debian NEW? we can't get the dsc file from it?
[11:55] <Laney> no you can't
[11:56] <didrocks> ok, thanks Laney :)
[11:56] <Laney> :-)
[11:57] <Laney> grab it from $VCS and upload, then sync when it's uploaded
[12:04] <didrocks> Laney: yeah, I'm asking to the maintainer to do it if possible, then I will NEW it :)
[12:04] <Laney> woo
[12:07] <chrisccoulson> kklimonda, oh, i didn't realise that mongodb's malloc override was declared inline. that might be the real issue with assigning it to a pointer
[12:12] <kklimonda> chrisccoulson: afair the problem I was trying to solve wasn't about it being assigned to pointer, but about malloc being expanded to mongo::ourmalloc in some xulrunner header, but I will happily agree with you - I'm much more of a C coder, than the C++ one. If you can describe it in detail I'd be thankful.
[12:14] <didrocks> seb128: IIRC, you were talking about some gdm issue this morning?
[12:14] <didrocks> seb128: seems people on the french forum get a black screen at start since then
[12:23] <seb128> didrocks, right, there is an issue with jhunt's upstart job tweaks
[12:23] <didrocks> ok, it's upstart then
[12:23] <seb128> didrocks, they can switch to a vt and start gdm there
[12:24] <seb128> didrocks, no, it's the gdm job
[12:24] <didrocks> oh? ok
[12:24] <didrocks> seb128: yeah, they already found the vt tweak :)
[12:24] <seb128> didrocks, bug #735805
[12:24] <ubot2> Launchpad bug 735805 in gdm "GDM fails to start" [High,Confirmed] https://launchpad.net/bugs/735805
[12:26] <didrocks> seb128: ok, reading, thanks :)
[12:27] <seb128> didrocks, see that's when I'm happy about my no upload on friday rule ;-)
[12:27] <seb128> didrocks, I was pondering uploading that or not ;-)
[12:27] <didrocks> seb128: oh, you already know I totally agree with this rule :-)
[12:27] <didrocks> oh really?
[12:27] <didrocks> heh ;)
[12:27] <didrocks> like "uploaded kthxbye"
[12:28] <seb128> well that's rather that I merged jhunt's fix and there was a crash fix pending
[12:28] <seb128> so I pondered uploading with those or not
[12:28] <didrocks> yeah
[12:28] <didrocks> well, stick to this rule :)
[12:28] <seb128> ;-)
[12:28] <didrocks> (I still think Friday morning is okayish)
[12:28] <didrocks> as long as it hits the repo before lunch :)
[12:48] <seb128> hey mterry
[12:48] <seb128> is your recent merge request fixing bug #730976
[12:48] <seb128> ?
[12:48] <ubot2> Launchpad bug 730976 in libdbusmenu "LIBDBUSMENU-GTK-DEBUG: Could not handle image type 0" [Low,New] https://launchpad.net/bugs/730976
[12:49] <mterry> seb128, ah, yes!
[12:49] <mterry> seb128, didn't think to look for a bug
[12:50] <mterry> seb128, do you know of a bug for the "dbusmenu_gtk_parse_get_cached_item: assertion `GTK_IS_MENU_ITEM(widget)' failed" message?
[12:51] <seb128> mterry, ted did a merge request for it yesterday
[12:52] <mterry> seb128, oh, swell
[12:52] <seb128> mterry, see https://code.edge.launchpad.net/dbusmenu/+activereviews
[12:52] <seb128> if you want to review and ack it ;-)
[12:53] <seb128> mterry, it's the no spam for seb one
[12:53] <mterry> yup
[12:53] <seb128> mterry, btw ted's tarball are due today
[12:53] <seb128> if you have things to get in
[12:54] <mterry> seb128, naw
[12:54] <mterry> seb128, my empathy menu fix is empathy-side
[12:55] <mterry> seb128, just realized I have the ability to review dbusmenu branches.  Do you know policy?  Should I merge it myself?
[12:56] <mterry> (i mean, for ted's branches that I approve)
[12:56] <seb128> mterry, not sure, check with ted, usually other dx-ers ack it but don't merge but I guess that's because they don't have a local checkout handy etc
[12:56] <seb128> i.e it's easier for them to just ack and ted handle the merge
[12:56] <mterry> k
[12:57] <seb128> the unity team tends to let whoever did the request merge his work it seems
[12:57] <seb128> then they do a review of approved things not merged once a week before rolling tarballs
[12:58] <seb128> didrocks can probably confirm that or not ;-)
[12:59] <didrocks> seb128: yeah, when you have commit right, it's better you merge it
[12:59] <didrocks> seb128: I think you are in ~unity-team, isn't it?
[12:59] <didrocks> oupss
[12:59] <didrocks> mterry: ^^
[12:59] <didrocks> mterry: you have one pending merge :)
[13:00] <mterry> didrocks, so I should be merging branches of mine that get approved?  But not branches that I approve?
[13:01] <didrocks> mterry: right
[13:01] <didrocks> for unity at least :)
[13:01] <mterry> yar
[13:23] <kenvandine> mterry, woot, you fixed empathy's contact menu!
[13:23]  * kenvandine high fives mterry
[13:24] <bcurtiswx> what was wrong with it?
[13:25] <bcurtiswx> oh right, it didn't show..correct?
[13:26] <mterry> bcurtiswx, no, this one showed, but didn't do anything when clicked
[13:26] <mterry> a race condition
[13:26] <bcurtiswx> mterry, wow, great then :)
[13:27] <kenvandine> bcurtiswx, the not showing part was fixed in dbusmenu last week
[13:27] <bcurtiswx> well, i must be captain oblivious this past weekend :-\
[13:27] <bcurtiswx> have been*
[13:30] <dobey> pitti: hrmm, are you going to do a new upload of distutils-extra with mandel's patch? i've been trying to make a .deb, but quilt hates me :(
[13:32] <dobey> ah, stupid patch levels
[13:42] <bcurtiswx> pedro_, did you get my ping from last night?
[13:46] <pedro_> bcurtiswx, yes, i was going to point you to bug 731708 , is that the same you're facing?
[13:46] <ubot2> Launchpad bug 731708 in nautilus "nautilus doesn't run, Unique-DBus-WARNING, assertion 'watcher_id > 0' failed" [Low,Confirmed] https://launchpad.net/bugs/731708
[13:47] <bcurtiswx> pedro_, yes that would be it, thx
[13:48] <pedro_> bcurtiswx, you're welcome, please follow up there ;-)
[13:48] <bcurtiswx> pedro_, i figured a killall nautilus would help, except it just keeps respwaning
[13:48] <bcurtiswx> quite annoying
[13:48] <seb128> pedro_, hey, that bug got fixed yesterday
[13:49] <bcurtiswx> seb128, is it in the repos yet?
[13:49] <seb128> bcurtiswx, yes, since yesterday
[13:49] <seb128> bcurtiswx, what issue do you get?
[13:50] <bcurtiswx> hrmm, i had this bug last night.  I can't access the machine right now (it's my desktop at home) but nautilus would just hang, heating up my system with CPU usage.  I can't killall nautilus because it respawns, so I did it by terminal and got the same warning as that bug
[13:51] <bcurtiswx> it was right after a dist-upgrade from M-->N
[13:52] <seb128> could be a different issue than the warning
[13:52] <seb128> but without details or a stacktrace not easy to say
[13:53] <bcurtiswx> i can see what info i can grab when I get home later this evening GMT-4 (Eastern)
[14:43] <mterry> seb128, OK, I started my CoreDev application page.  If you want to help me along, leave an endorsement!  https://wiki.ubuntu.com/mterry/CoreDev
[14:46] <mterry> That goes for anyone else too.  I like all endorsements
[14:46] <seb128> mterry, \o/
[14:46] <pitti> mterry: oh, great! will add my praise as well
[14:47] <mterry> yay
[14:50] <pitti> dobey: are you blocked on the new p-d-e? I can upload today if you need it, but it seemed to be a corner case
[14:51] <dobey> pitti: i got an upload into our nightlies ppa to fix it there, but we will need it in 11.04 also at some point soon i suspect, but not super urgent
[14:52] <pitti> Sweetshark: replied in 712725
[14:52] <pitti> dobey: you have windows builds there?
[14:53] <pitti> dobey: we are talking about the ValueError crash when scanning over ctypes imports, right?
[14:54] <dobey> pitti: yes because ctypes.wintypes exists on linux, though it fails with the valueerror. which is why this is a problem at all
[14:55] <pitti> ah, ok
[14:59] <pitti> dobey: uploaded
[15:00] <dobey> pitti: cool, thanks
[15:01] <jibel> seb128, there's a bug with a patch proposed upstream that we need in natty for automated testing.
[15:01] <jibel> seb128, bug 690657
[15:01] <ubot2> Launchpad bug 690657 in gnome-utils "Text Widget under combo box is not exposing accessibility" [Medium,Confirmed] https://launchpad.net/bugs/690657
[15:02] <jibel> seb128, how to proceed to have it included in natty, is subscribing the desktop team ok and enough ?
[15:03] <seb128> jibel: ubuntu-sponsors usually
[15:03] <seb128> jibel: I noticed it but I was waiting for an upstream review
[15:07] <jibel> seb128, okay, I'll wait for a review but target it to natty b1 to not forget it.
[15:08] <Sweetshark> pitti: re replied in 712725. It would be a FFE.
[15:10] <seb128> jibel: I will try to get it in today or tomorrow
[15:25] <mvo> pitti: is jockey driving dpkg/python-apt in a way that makes it not write logs to /var/log/apt/term.log ? I am triaging a bunch of package install failures and a lot of nvidia, b43 releated ones have failures but empty logs. any idea about this?
[15:28] <pitti> mvo: it's basically using apt.Cache()[pkg].markInstall(), and cache.commit()
[15:28] <pitti> mvo: all the apt code is in jockey/oslib.py, do you see anything wrong with it?
[15:28] <pitti> mvo: I don't deliberately disable logging
[15:29] <pitti> mvo: (off to long phone call now)
[15:31] <mvo> pitti: thanks, I have a look (I have a call now as well). the above should be fine but I will double check
[15:34] <jibel> seb128, great! thanks
[15:43] <seb128> jibel: yw
[15:44] <seb128> mterry, ok, unity doesn't like your indicator-datetime-preferences desktop for some reason
[15:44] <mterry> seb128, probably just too awesome for unity
[15:44] <mterry> seb128, how doesn't it like it?
[15:45] <seb128> mterry, it doesn't match indicator-datetime-preferences to it
[15:45] <seb128> like the launcher doesn't get the right title etc
[15:45] <mterry> guh
[15:46] <seb128> it gives an empty launcher title here with a fuzzy icon
[15:46] <seb128> mterry, does it work for you?
[15:47] <seb128> mterry, I'm trying indicator-datetime trunk with karl's pending work
[15:47] <mterry> seb128, does it show in the applications place?
[15:48] <seb128> mterry, yes and it in gnome-panel menus
[15:48] <seb128> I've tried running in on a command line, from the indicator or from gnome-panel
[15:48] <mterry> seb128, you installed it via a deb, right?
[15:48] <seb128> yes
[15:49] <seb128> I did bzr merge lp:indicator-datetime in the current packaging vcs and bzr bd that
[15:49] <seb128> indicator-datetime-preferences.desktop	indicator-datetime-preferences
[15:49] <seb128> it's correctly listed in the index
[15:50] <seb128> well I should restart my session to be sure I guess
[15:50] <seb128> brb
[15:54] <kenvandine> uh oh... log session restart
[15:55] <kenvandine> hope he isn't busted :)
[16:08] <bcurtiswx> mterry killed seb128 this time, not me :P
[16:08]  * kenvandine runs out for a bit, bbl
[16:11] <seb128> re
[16:11] <seb128> ok, restarting was not the best idea, disk check and then gdm upstart issues
[16:11] <seb128> mterry, I'm back ;-)
[16:11] <mterry> seb128, :)
[16:11] <seb128> mterry, still the same after a restart, empty title and fuzzy icon
[16:11] <mterry> :(  OK, looking into it
[16:12] <seb128> mterry, do you get it as well?
[16:12] <mterry> seb128, I have to build trunk, I'm not running it right now
[16:13] <seb128> mterry, don't bother
[16:14] <mterry> seb128, ?
[16:14] <seb128> mterry, it's a cosmetic issue, it can wait today's tarball and tomorrow to be debugged
[16:15] <seb128> mterry, I though you had the .desktop installed locally since you worked on it
[16:15] <mterry> I did but via a deb, so when I switched debs...
[16:15] <seb128> doesn't seem an indicator issue anyway
[16:16] <seb128> the .desktop is installed and listed correctly by the places and menus etc
[16:19] <kklimonda> seb128: do you have a moment? new glibmm release requires updated mm-common (and it's in universe for now) to build documentation. How should I proceed on gettinng it into main?
[16:20] <seb128> kklimonda, the wiki has mir requirements details
[16:20] <seb128> you need to file a bug asking for promotion with some details
[16:21] <mterry> kklimonda, https://wiki.ubuntu.com/UbuntuMainInclusionRequirements
[16:23] <kklimonda> thanks. Should I first update it to the new version, and then request MIR?
[16:23] <seb128> mterry, ok, I've the feeling it doesn't like the "&" in the Name=
[16:24] <seb128> mterry, if I replace it then it works
[16:24] <seb128> mterry, sorry for the noise, not your fault
[16:24] <seb128> it's DBO's fault
[16:24] <seb128> or didrocks's ;-)
[16:24] <didrocks> hum?
[16:24] <DBO> hum?
[16:25] <seb128> didrocks, unity launcher displays and empty title when there is a "&" in the name
[16:25] <seb128> indicator-datetime-preferences.desktop:Name=Time & Date
[16:25] <seb128> removing the & makes it work
[16:25] <didrocks> seb128: already fixed by a kind contributor :)
[16:25] <didrocks> not in trunk though
[16:26] <seb128> so now wth is it displaying a blurry icon when there is a 48x48 svg
[16:27] <seb128> in fact it's not
[16:27] <seb128> mterry, ok, sorry for the noise, everything is ok
[16:27] <seb128> or will be when didrocks's merge the contributor patch in trunk ;-)
[16:29] <bcurtiswx> seb128, in your GDM upstart, did you see any plymouth errors?
[16:30] <seb128> bcurtiswx, no
[16:31] <bcurtiswx> seb128, 'more /var/log/syslog | grep plymouth'
[16:32] <seb128> no error
[16:32] <bcurtiswx> seb128, Ok thx
[16:32] <seb128> btw you can "grep plymouth syslog"
[16:32] <seb128> it's less to type ;-)
[16:32] <bcurtiswx> im too lazy... wait... :P
[16:33] <bcurtiswx> i think i had too much fun with pipes and thats why i keep doing that..
[16:34] <bcurtiswx> and this is where linux turns away from PG rating to R... totally hit enter before reading that one :-\
[16:39] <dobey> pitti: why does new distutils-extra rewuire various python3 bits for build-depends?
[16:39] <pitti> dobey: because it runs the self tests for both python 2 and 3, and I needed some example libraries to run them against
[16:39] <pitti> so I took the smallest ones I could find which had the necessary properties (multiple modules, etc.)
[16:40] <dobey> oh :-/
[16:41] <dobey> guess i will have to disable that for our PPA backport for lucid
[16:45] <mterry> seb128, oh, missed your messages.  Yay!  \o/
[16:46] <pitti> dobey: you basically need to drop all but the first two lines in the override_dh_auto_install: rule in debian/rules, and drop the py3 build depends; then it should be fine
[16:46] <pitti> dobey: (oh, and drop the p3 package from debian/control, of course)
[16:46] <pitti> dobey: if you are just needing that one ctypes fix, we can also SRU this
[16:49] <dobey> pitti: don't need an sru. we only need the fix in our nightlies. it is easier to just have the new version in our PPA
[16:49] <pitti> dobey: ack
[17:27]  * mterry goes afk, errand
[17:30] <seb128> rodrigo_, seems you forget the actual patch on https://bugzilla.gnome.org/show_bug.cgi?id=644560?
[17:31] <ubot2> Gnome bug 644560 in Gal "Can't set an account password" [Normal,Needinfo]
[17:34] <kenvandine> seb128, what was the gdm upstart issue?
[17:34] <kenvandine> i have a box here that isn't starting gdm at boot... but looks like it is because plymouth is failing
[17:34] <seb128> kenvandine, dunno, jhunt is still working it out
[17:35] <seb128> kenvandine, no, it's likely the upstart job fault
[17:35] <seb128> kenvandine, try using http://launchpadlibrarian.net/66503336/gdm.conf
[17:35] <seb128> kenvandine, or downgrade
[17:35] <seb128> kenvandine, or wait for the new one to build ;-)
[17:36] <kenvandine> i'll try it
[17:36] <kenvandine> weird thing is if i boot an older kernel it works
[17:37] <kenvandine> but with the latest kernel, if i drop to a VT and start gdm it works too
[17:37] <kenvandine> seems weird kernel versions would make a difference
[17:37] <kenvandine> oh
[17:37] <kenvandine> <         if [ "$curr" = S -o "$prev" = unknown ]
[17:38] <kenvandine> so maybe it doesn't know the previous one
[17:40] <kenvandine> seb128, yup... that fixed it
[17:40] <kenvandine> :)
[17:41] <seb128> kenvandine, ;-)
[17:41] <kenvandine> thx
[17:41] <kenvandine> right before lunch i was searching for an existing bug on that
[18:23]  * mterry is back
[18:23] <seb128> tedg, is http://paste.ubuntu.com/581238/ known?
[18:24] <seb128> tedg, I get it running indicator-datetime in valgrind and restarting unity-panel-service
[18:24] <seb128> tedg, is that a libindicator issue?
[18:25] <tedg> seb128, Yeah, it would be a libindicator issue.  I think I've seen that trace before, but I could have sworn it was fixed :-/
[18:25] <seb128> tedg, still happening in natty
[18:25] <tedg> But yeah, definitely libindicator
[18:25] <seb128> tedg, https://bugs.launchpad.net/ubuntu/+source/libindicator/+bug/719457
[18:25] <ubot2> Launchpad bug 719457 in libindicator "valgrind invalid reads error on unloading" [Low,Fix released]
[18:25] <seb128> seems similar
[18:26] <seb128> bah, I closed it because it seemed fixed
[18:26] <seb128> let's reopened
[18:26] <tedg> seb128, See I knew someone fixed it. ;-)
[18:26] <seb128> lol
[18:27] <seb128> tedg, I'm sure that's what you want, you ignore bug reports until the submitter gets confused and close it himself because there is no activity on the bug ;-)
[18:27] <tedg> seb128, SHHH!!! It's a secret strategy.
[18:31] <kenvandine> tedg, still can't upload?
[18:32] <tedg> kenvandine, No, got chrome... ido is up.  libindicator is on it's way.
[18:32] <kenvandine> oh, cool
[18:33] <kenvandine> i guess i should have actually clicked on the link you sent
[18:33] <kenvandine> :-D
[18:33] <tedg> Yes, that's generally what they're for ;-)
[18:35] <chrisccoulson> kklimonda, down to half a screen of compiler errors with mongodb now ;)
[18:35] <vish> anyone up for sponsoring branch on bug 736250 ? :)
[18:35] <ubot2> Launchpad bug 736250 in cheese "Update oldish looking icons in cheese effects" [Wishlist,Triaged] https://launchpad.net/bugs/736250
[18:35] <kklimonda> chrisccoulson: you rock :)
[18:38] <tedg> seb128, So mterry fixed bug 569273 but I'm not sure how to mark the various distro tasks.
[18:38] <ubot2> Launchpad bug 569273 in indicator-application "memory leak in gnome-power-manager" [Medium,Confirmed] https://launchpad.net/bugs/569273
[18:39] <tedg> seb128, Also, annoyingly.  It's in libappindicator in Natty, but indicator-application in all the other distro series.
[18:39] <mterry> tedg, plus, mine was just the last nail in the coffin (hopefully)
[18:40] <mterry> tedg, some of those other tasks were arguably valid in the past but got reopened
[18:40] <tedg> mterry, Yeah.  It makes marking the bug correctly difficult.
[18:57] <seb128> tedg, set it invalid for the others lines
[18:57] <seb128> tedg, we can do an also affect distribution, indicator-application, invalid natty and add stable series if we want
[18:57] <seb128> is that an issue in lucid?
[19:02] <tedg> seb128, Was libappindicator in Lucid?  If it was, it could have been.
[19:03] <tedg> seb128, I think we should definitely backport to Maverick.
[19:03] <tedg> seb128, It's literally a 5 character fix :)
[19:03] <seb128> tedg, guess not, I think those issues started being raised in 10.10
[19:04] <seb128> tedg, https://launchpad.net/ubuntu/+source/indicator-application
[19:07]  * tedg should probably be more familiar with the exact dates of all of libappindicator as they're blogged about daily.
[19:08] <seb128> tedg, it's likely nothing was using it enough in lucid that it was an issue
[19:08] <tedg> seb128, Yeah, or nothing was completely replacing the menu everytime like g-p-m
[19:09] <seb128> tedg, right
[19:09] <seb128> mterry, do you want to sru you leak fix for maverick btw?
[19:09] <seb128> mterry, we should probably sru the theme_cb crash one as well
[19:11] <mterry> seb128, i can do the leak, sure.  which was the theme_cb?
[19:13] <seb128> https://code.launchpad.net/~mterry/libappindicator/fix-crash-708188/+merge/51356
[19:13] <seb128> mterry, ^
[19:14] <mterry> so tiny.  I am succinct.  OK.  I can prep an SRU for 10.10
[19:16] <seb128> mterry, thanks
[19:25] <mterry> tedg, you swear that sinking the ref won't cause problems with anyone?  Or put another way, you don't think any consumers corrected for the leak?
[19:25] <psusi> I somehow managed to get my min/max/close buttons back on the right and the system menu on the left.  Is there a gconf key or something that controls this?
[19:26] <seb128> mterry, let's get the other fix in and wait a bit to get natty feedbackon the ref thing
[19:26] <tedg> mterry, I don't know of anyone that did.  I would have hoped they would have noted it to us...
[19:26] <vish> psusi: /apps/metacity/general/button_layout
[19:26] <vish> psusi: thats in the gconf^
[19:27] <mterry> seb128, you mean do the theme_change separately?
[19:27] <seb128> mterry, well the theme_change one seems safe and gnome-bt upstream specifically asked if we could fix that in stable since they keep receive crash bug upstream about it
[19:28] <mterry> k
[19:28] <seb128> mterry, it's harder to say if the ref one will impact on applications, so better to wait a bit and see if any issue is raised in natty before backporting it
[19:29] <mterry> seb128, there is a safer fix we could apply just to g-p-m for 10.10
[19:29] <mterry> other apps would leak, but I don't think any of them are nearly as bad
[19:29] <seb128> mterry, if you want to do that go for it
[19:29] <psusi> vish: ahh, thanks... I kept looking for it in nautilus keys since it somehow got screwed up when I installed a new nautilius package...
[19:29] <seb128> it seems to be the only real complain
[19:30] <seb128> so should be enough for a non lts version
[19:30]  * mvo grumbles about the second compiz freeze of the day
[19:30] <mvo> or unity
[19:31] <seb128> mvo, it's frozen? or it's crashing and apport freezes it while it's getting infos?
[19:32] <mvo> good question, unity --reset killed the whole X
[19:32] <mvo> joy!
[19:32] <didrocks> mvo: screen freeze? there is a known Xorg freeze AFAIK
[19:32] <didrocks> but no compiz
[19:32] <seb128> didrocks, yeah, blame it on the x guys
[19:33] <didrocks> totally :)
[19:35] <pitti> chrisccoulson: hey, how are you?
[19:35] <chrisccoulson> pitti - good thanks, how are you?
[19:35] <pitti> chrisccoulson: I wondered, did you hear about cases where flash videos in mozilla/chromium/etc. turned "red" recently?
[19:35] <pitti> chrisccoulson: I'm great, thanks!
[19:35] <seb128> chrisccoulson, run away, pitti saying hello in the evening is a trap, he will give you work!
[19:36] <chrisccoulson> pitti - yeah, i've seen it discussed a little bit. i can't recreate it, but i think someone already forwarded a bug to adobe
[19:36] <pitti> chrisccoulson: I seem to get this with the second video I play in firefox, until I purge the cookies; a friend of mine also noticed that after a maverick update, so I blame the flash plugin
[19:36] <kklimonda> hmm..  any idea what's happening: symbol lookup error: /usr/bin/unity-2d-places: undefined symbol: _ZN12Unity2dDebug15installHandlersEv ?
[19:36] <pitti> chrisccoulson: no, I don't want to give you actual work :)
[19:36] <chrisccoulson> pitti - https://bugs.adobe.com/jira/browse/FP-6327
[19:36] <pitti> chrisccoulson: I just wondered whether you happened to know a better workaround than "disable cookies"
[19:36] <pitti> chrisccoulson: ah, thanks muchly for the pointer
[19:36] <kenvandine> seb128, can you get libfolks out of binNEW?
[19:37] <kenvandine> it's holding up empathy
[19:37] <kenvandine> seb128, please :)
[19:37] <seb128> didrocks, pitti: ^
[19:37] <seb128> I don't have access from that box
[19:37] <seb128> I'm just doing IRC right now from this box ;-)
[19:37] <chrisccoulson> pitti - the last comment suggests that downgrading flash fixes it
[19:37] <pitti> kenvandine: yep, looking
[19:37] <seb128> pitti, thanks
[19:37] <pitti> seb128: oh, poor man's proxy?
[19:37] <kenvandine> pitti, thx
[19:38] <didrocks> seb128: you mean, you are just slacking? :p
[19:38] <pitti> seb128: or rather, rich man's? (buying a second laptop instead of installing bip?) :-P
[19:38] <seb128> kenvandine, btw sjoerd pointed early that we should get farsight synced on debian, it seems we don't install some files in there
[19:38] <kenvandine> haha
[19:38] <kklimonda> ok, my bad
[19:38] <kenvandine> seb128, yeah, he told me you were doing it
[19:38] <seb128> pitti, rather having an old one which is used for testing and other things ;-)
[19:38] <seb128> pitti, lol
[19:39] <seb128> kenvandine, well "synced" is merged we have a recommends diff there
[19:39] <didrocks> ok, time for dinner and evening, see you tomorrow!
[19:40] <kenvandine> seb128, ok
[19:40] <seb128> kenvandine, well I failed to do it today so if you want feel free, otherwise I will try tomorrow
[19:40] <seb128> 'night didrocks
[19:40] <didrocks> bonne nuit seb128 ;)
[19:40] <kenvandine> i should be able to do it
[19:40] <kenvandine> i think tedg is almost done abusing me for today :)
[19:41]  * tedg creates a libindicated quickly
[19:42]  * kenvandine hides 
[19:43] <mxpxpod> is this the correct place to ask about things in the gnome 3 ppa?
[19:43] <pitti> kenvandine: libfolks nudged
[19:43] <kenvandine> pitti, thx!
[19:44] <cdbs> mxpxpod: fire away!
[19:45] <mxpxpod> I'm running gnome-shell from the gnome 3 ppa and the gtk theme looks wrong
[19:45] <mxpxpod> also, when I run a program like gnome-control-center from the command line, it tells me it can't find the named theme Adwaita
[19:46] <mxpxpod> I figure that the two are related
[19:46] <cdbs> mxpxpod: you need to have adwaita installed, looks like it isn't in the PPA yet
[19:46] <mxpxpod> really? I thought it was part of gnome-themes-standard
[19:46] <cdbs> mxpxpod: wait for someone to add it there first
[19:47] <mxpxpod> I know that there's a /usr/share/themes/Adwaita on my box
[19:47] <cdbs> oh wait, there IS gnome-themes in the PPA
[19:47] <cdbs> I dunno then, rodrigo_ ? ^^
[19:49] <mxpxpod> I noticed kenvandine mentioned something about libfolks and empathy, and I'm guessing that will answer my question about the empathy package
[19:50] <mxpxpod> however, it seems that gucharmap still depends on libgtk3.0-0 and it's creating a conflict in apt-get dist-upgrade
[19:54] <seb128> kklimonda, check with Kaleo maybe about the symbols error
[19:54] <seb128> or try ogra
[19:55] <bdrung> did someone already complained about http://www.omgubuntu.co.uk/2011/03/ubuntu-natty-adds-control-centre-entry-to-session-menu/ ?
[19:55] <bdrung> is there a bug report against this change?
[19:55] <seb128> no
[19:55] <bdrung> this change is similar to putting "shutdown" under "start"
[19:56] <bdrung> seb128: in which package was this change made?
[19:57] <kklimonda> seb128: figured it out, a perfect pebkac case :)
[19:57] <seb128> bdrung, indicator-session
[19:58] <seb128> bdrung, bug #727823
[19:58] <ubot2> Launchpad bug 727823 in ayatana-design "Enable Gnome-Control-Center in Unity, and add "System Settings" link to the session indicator menu" [Critical,Fix released] https://launchpad.net/bugs/727823
[19:58] <chrisccoulson> looks like all you natty users are now using firefox 4 final ;)
[19:58] <seb128> chrisccoulson, no change between rc and stable?
[19:58] <chrisccoulson> seb128 - there's no plan for another RC now, which means that what we have now is what will be released on 22nd
[19:59] <bdrung> seb128: should i comment that bug or open a new one?
[20:00] <seb128> bdrung, open a new one and comment to give the number
[20:02] <seb128> bdrung, btw if you read the bug the indicator used was already being argued there
[20:03] <chrisccoulson> kklimonda, what are you building to give you that error btw?
[20:03] <chrisccoulson> oh
[20:04] <chrisccoulson> actually, you said in your message ;)
[20:06] <mterry> seb128, bug 708188 and bug 569273 are ready for SRU
[20:06] <ubot2> Launchpad bug 708188 in libappindicator "softwares using libappindicator crash with SIGSEGV in theme_changed_cb()" [High,Fix released] https://launchpad.net/bugs/708188
[20:06] <ubot2> Launchpad bug 569273 in indicator-application "memory leak in gnome-power-manager" [Medium,Confirmed] https://launchpad.net/bugs/569273
[20:07] <seb128> mterry, well done ;-)
[20:23] <mxpxpod> how do I keep nautilus from running when gnome starts with gnome-shell?
[20:34] <pitti> good night everyone
[21:42] <seb128> re
[21:42] <seb128> tedg, did you roll indicator-dt yet?
[21:43] <tedg> seb128, Yup
[21:43] <seb128> hum, ok
[21:43] <seb128> tedg, you can clean the g-s-t requirements from the configure and the remaining include
[21:43] <seb128> it has been switched to the use g-s-d
[21:44] <seb128> well that will be for the next update
[21:44] <tedg> seb128, Are you saying no oobs for me?
[21:44] <seb128> it works fine without those, I built trunk with those dropped today
[21:45] <seb128> tedg, no, not for you ;-)
[21:48] <tedg> seb128, done
[22:22] <seb128> tedg, hum, bug #729150
[22:22] <ubot2> Launchpad bug 729150 in libappindicator "nm-applet crashed with SIGSEGV" [High,Triaged] https://launchpad.net/bugs/729150
[22:22] <seb128> which is mterry?
[22:23] <bcurtiswx> kenvandine, are you still here?
[22:23] <tedg> seb128, We're discussing the fix on the merge request
[22:23] <seb128> tedg, ok, just got that
[22:23] <seb128> is bug #708118 fixed or not?
[22:24] <ubot2> Launchpad bug 708118 in libappindicator "nm-applet crashes with SIGSEGV in icon_name_hash()" [Medium,Confirmed] https://launchpad.net/bugs/708118
[22:24] <seb128> cyphermox, ^
[22:24] <seb128> it didn't get recent duplicates
[22:24] <seb128> nor comment
[22:24] <cyphermox> right
[22:25] <cyphermox> I think that's because it has all the bugs at the moment when the retracers didn't work correctly two weeks ago
[22:25] <cyphermox> it's not fixed, we should talk about how to set use-fallback on the GtkImage used by the GtkStatusIcon created by libappindicator
[22:26] <seb128> cyphermox, what do you mean about the retracers?
[22:26] <cyphermox> nevermind, I was talking about something else
[22:26] <cyphermox> yeah, if I try to duplicate it I'd get an error
[22:27] <seb128> oh you think it's the same issue than the other one?
[22:27] <cyphermox> yes, same issue as the bug number in the last comment: 729150
[22:28] <cyphermox> seb128, have you looked at the merge request too?
[22:29] <seb128> ok
[22:29] <seb128> it's but it's not clear to me what the issue is or why that fixes it
[22:31] <seb128> it's -> yes
[22:31] <cyphermox> seb128, afaict while the icon gets created the gicon is unref'ed before the icon is done -- or while icons are being changed due to an update of the cache
[22:32] <cyphermox> using icon names bypass this completely
[22:32] <seb128> seems a bug in gtk then?
[22:32] <cyphermox> I also found that not unrefing themed_icon doesn't cause this crash
[22:32] <seb128> but that would create some leaks
[22:33] <cyphermox> right
[22:34] <cyphermox> I thought keeping it as a member of whatever structure appindicators have an unref'ing just before creating a new one would work, but I haven't tested it
[22:34] <cyphermox> seb128, also, see https://bugzilla.gnome.org/show_bug.cgi?id=614800
[22:34] <ubot2> Gnome bug 614800 in gtk "Crash in find_image_offset()" [Critical,Unconfirmed]
[22:35] <seb128> where did ted go?
[22:35] <seb128> cyphermox, yeah, I'm just trying to see how we get it fixed for this cycle
[22:35] <seb128> seems there is a gtk issue that you try to workaround there
[22:37] <cyphermox> seb128, I tend to agree with milanbv 's analysis though that it's really in libappindicator more than gtk... although gtk should be able to sustain the cache being rebuilt anytime
[22:38] <seb128> is that crash only happening when the cache is being rebuilt?
[22:38] <cyphermox> yeah
[22:39] <cyphermox> see my last comment in the gnome bug, that's how I was able to reproduce it consistently
[22:39] <seb128> is nm reconnecting on upgrade?
[22:39] <seb128> it seems weird that users run that often in nm reconnecting while the icon cache is rebuilt
[22:40] <cyphermox> it doesn't reconnect but icons are being updated regularly for wifi signal strength
[22:41] <cyphermox> seb128, note this only crashes when using the fallback more to the notification area
[22:41] <seb128> cyphermox, but how can the gicon been unrefed while in use?
[22:42] <cyphermox> seb128, don't know. my guess is that the icon/theme change signal sent when the cache is updated is received from both the appindicator stuff and the underlying gtkstatusicon, and they both fight to update the icon
[22:45] <seb128> cyphermox, you are sure it's the same issue?
[22:45] <seb128> cyphermox, seems the new bug is due to http://bazaar.launchpad.net/~indicator-applet-developers/libappindicator/trunk/revision/195
[22:45] <seb128> it's the fix for bug #708188
[22:45] <ubot2> Launchpad bug 708188 in libappindicator "softwares using libappindicator crash with SIGSEGV in theme_changed_cb()" [High,Fix released] https://launchpad.net/bugs/708188
[22:46] <seb128> cyphermox, the bugs started the day after the commit landed in natty
[22:47] <cyphermox> seb128, it's the same stack trace.
[22:47] <cyphermox> unless you see something different that I missed?
[22:47] <kenvandine> seb128, indicator-datetime uploaded... lets hope the bugs stop coming in :)
[22:48] <cyphermox> seb128, I also looked at it with Q-FUNK to confirmed it came from the same set of circumstances
[22:49] <seb128> cyphermox, ok, so those users are not running unity nor GNOME with indicators?
[22:49] <cyphermox> (Q-FUNK reported a duplicate of bug 729150
[22:49] <ubot2> Launchpad bug 729150 in libappindicator "nm-applet crashed with SIGSEGV" [High,Triaged] https://launchpad.net/bugs/729150
[22:49] <seb128> interesting to see that we get that number of users using the fallback there
[22:50] <seb128> or do they run other desktops, i;e xfce or something?
[22:50] <cyphermox> yeah
[22:50] <cyphermox> seb128, I don't think xfce is affected, micahg told me something about blacklisting libs
[22:50] <cyphermox> but these users use whatever DE with a notification area, not indicators
[22:51] <seb128> well you can have both
[22:52] <seb128> ie that's what classic GNOME has
[22:52] <cyphermox> well, yes
[22:52] <cyphermox> but if indicator-application is running, it will catch nm-applet. AFAICT then nm-applet doesn't crash
[22:52] <cyphermox> though I could have just not been able to reproduce it in that case
[22:53] <seb128> bug #725417
[22:53] <ubot2> Launchpad bug 725417 in notify-osd "notify-osd crashed with signal 7 in find_image_offset()" [Medium,New] https://launchpad.net/bugs/725417
[22:53] <seb128> seems a similar crash but notify-osd doesn't use libappindicator
[22:53] <cyphermox> sure looks the same
[22:54] <cyphermox> fair enough, I'm convinced it's a gtk issue... but I have no clue how to fix it
[22:54] <cyphermox> oh wait no, that's not the same thing
[22:55] <cyphermox> notice how the icon_name is set there?
[22:57] <cyphermox> it also seems to be a notification generated by nm-applet :'(
[22:59] <seb128> cyphermox, right
[22:59] <seb128> ok, not sure what is causing the issue either bug seems something that be handled for natty
[23:04] <cyphermox> yeah
[23:05] <seb128> the update you suggest could work but it would still be nice to understand the issue
[23:05] <seb128> it's frustrating to not having an explanation ;-)
[23:06] <cyphermox> yeah
[23:06] <cyphermox> it's also frustrating that this is the last reported crasher for nm-applet ;)
[23:07] <seb128> seems a common one though
[23:07] <cyphermox> yeah... scary how many users seems to have it... and seem to use classic gnome
[23:07] <seb128> would be interesting to know what desktop those users are running, especially if that's GNOME but without the indicator applet configured
[23:07] <cyphermox> I know for sure that's the case for Q-FUNK
[23:07] <seb128> it seems weird that they drop the indicator-applet
[23:07] <cyphermox> I should ask sebner too
[23:07] <seb128> he dropped the indicator? do you know why?
[23:08] <cyphermox> "hardcore gnome2 user"
[23:08] <seb128> it seemed that users got used to it nowadays are are mostly fine with it
[23:08] <cyphermox> yeah
[23:09] <cyphermox> well I see the main bug for 729150 is running unity-2d
[23:09] <seb128> that's a misleading tag
[23:09] <cyphermox> ah
[23:09] <seb128> it means unity-2d is installed
[23:10] <cyphermox> oh
[23:10] <seb128> none has the running-unity tag
[23:11] <seb128> well in the recent bug duplicates
[23:11] <seb128> so it's not likely an issue under unity
[23:11] <seb128> which would confirm that it's only in fallbacking code
[23:11] <cyphermox> I'm fairly confident it's when not running unity or indicator applets
[23:11] <seb128> still surprising that GNOME classic users still drop the indicator-applet nowadays
[23:12] <cyphermox> seb128, could be others though -- xubuntu, and all
[23:12] <seb128> if you run into some maybe ask them why ;-)
[23:12] <seb128> right.
[23:12] <cyphermox> any idea how this could be broken in gtk?
[23:13] <seb128> no, I fail to understand the issue still
[23:13] <cyphermox> then no wonder I also don't understand it :)
[23:13] <seb128> the gicon can't really go away under the code feet in the middle of a call
[23:14] <seb128> but I'm not really familiar with that code and some other people have debugged it for a while so I don't expect I would find something obvious
[23:14] <cyphermox> I couldn't find a place where the gicon was ref'ed by the gtkstatusicon or gtkiconcache code
[23:15] <cyphermox> but my understanding of gtk is still pretty limited
[23:15] <seb128> let's see if we can get someone in dx helping there, I will ask them tomorrow
[23:15] <cyphermox> ok
[23:15] <seb128> hum, I'm was checking fix commited bugs on launchpad
[23:16] <seb128> the alsa-drivers source has like 15% of those
[23:16] <seb128> do they stack years of fix or just never clean the bugs that are fixed? ;-)
[23:16] <cyphermox> even if I'm silent in the channel, I'm there around 7h30am to 8am my time
[23:17] <cyphermox> heh
[23:17] <seb128> was that for here or a channel error? ;-)
[23:17] <seb128> (just curious seemed out of context)
[23:17] <cyphermox> no it was for here
[23:17] <cyphermox> you said you'd ask dx tomorrow
[23:17] <cyphermox> let me know early ;)
[23:18] <seb128> ok
[23:18] <seb128> desrt, there?
[23:20] <seb128> robert_ancell, howdy
[23:20] <robert_ancell> seb128, hello
[23:20] <seb128> robert_ancell, how are you?
[23:20] <robert_ancell> good, what are you doing here at this time :)
[23:20] <seb128> robert_ancell, don't worry I don't have work for you (yet), just saying hello ;-)
[23:21] <seb128> robert_ancell, checking also how much work you have and if you want some desktopish bugs assigned when I run into so or if you are set
[23:21] <seb128> so -> some
[23:22] <robert_ancell> seb128, I'm mostly busy, but send me some suggestions - if they're in my knowledge set I'll grab them
[23:22] <seb128> robert_ancell, well, tv is boring and I'm sitting in front of it with the laptop on and I had IRC running because I was following some discussions ;-)
[23:23] <seb128> robert_ancell, I've nothing specific, the only one I can think of right now is get gnome-display-properties to not display it's hint in the screen corner when not focussed which seems a frequent complain of people doing presentation on beamers and such
[23:24] <robert_ancell> seb128, sounds interesting, bug number?
[23:26] <seb128> robert_ancell, bug #403840 seems close enough
[23:26] <ubot2> Launchpad bug 403840 in gnome-control-center "Display Preferences Monitor identification should be optional" [Wishlist,Confirmed] https://launchpad.net/bugs/403840
[23:26] <seb128> but I might open a new one, I know it's something people often complain about at conferences or UDS and that was raised as hundredpapercut issue
[23:28] <robert_ancell> should be easy, that's a fun looking bug :)
[23:30] <seb128> robert_ancell, great! ;-)
[23:30] <seb128> robert_ancell, oh, there also a gdm one
[23:30] <robert_ancell> yeah, busy *mumble mumble*
[23:30] <seb128> since we know how you love gdm right ;-)
[23:31] <seb128> robert_ancell, well, bug #696038 if you feel like taking it
[23:31] <ubot2> Launchpad bug 696038 in gdm "system user appears in login list of users" [Low,Confirmed] https://launchpad.net/bugs/696038
[23:31] <robert_ancell> yeah, we do need to fix that one.  I'll take a look
[23:31] <seb128> robert_ancell, it shouldn't be one of those bugs where you need to fight with the code layers etc
[23:32] <seb128> so it might be okish ;-)
[23:32] <robert_ancell> don't count on it
[23:32] <robert_ancell> it will be something stupid
[23:32] <seb128> ok, famous last word right?
[23:32] <robert_ancell> it's probably buried deep in console kit somewhere
[23:32] <seb128> should know better than commenting on gdm bugs being easy ;-)
[23:33] <seb128> robert_ancell, well, ck-history list those but that might be ok since they really logged in
[23:33] <seb128> robert_ancell, it's the uid filtering gdm is doing that seems to not work, or not apply to ck lists
[23:33] <seb128> I don't think we should aim at making ck not list those
[23:34] <seb128> robert_ancell, I will sync libwnck3
[23:34] <seb128> robert_ancell, just saw the #debian-gnome mention
[23:34] <robert_ancell> ah, thanks :)
[23:34] <seb128> robert_ancell, the empty line is annoying me on versions ;-)
[23:34] <robert_ancell> heh, that's why I put it there!
[23:35] <seb128> ;-)
[23:35] <seb128> robert_ancell, bug #610802
[23:35] <seb128> ok found it
[23:35] <ubot2> Launchpad bug 610802 in hundredpapercuts "'Mirror Screens' often seen on projectors during presentations." [Low,Triaged] https://launchpad.net/bugs/610802
[23:35] <robert_ancell> seb128, what do you think about this - when we get near final freeze the packages that are synced with debian but not up to date we make -ubuntu versions of them, then sync them for Oneiric?
[23:35] <seb128> robert_ancell, I've assigned it to you
[23:36] <seb128> robert_ancell, seems fine to me, though I don't think we will have much to update this cycle since we are mostly uptodate on GNOME 2.32
[23:36] <seb128> but for GNOME3 packages sure
[23:36] <robert_ancell> yup
[23:37] <seb128> robert_ancell, ignore the email about bug #216144 I wrote your name in the wrong tag
[23:37] <ubot2> Launchpad bug 216144 in gnome-control-center "gnome-display-properties should allow the primary screen to be chosen" [Medium,Fix released] https://launchpad.net/bugs/216144
[23:37] <seb128> tab
[23:50] <seb128> if someone cares about anjuta it seems it might need a rebuilt with a newer vala to fix a crash on start
[23:50] <seb128> upstream thinks it's could be due to vala abi breaks
[23:50] <seb128> bug #722079 as well
[23:50] <ubot2> Launchpad bug 722079 in libgda4 "When installing Anjuta in Natty Alpha libsqlite3.so is missing" [Low,Confirmed] https://launchpad.net/bugs/722079
[23:51] <seb128> ted: you won bug #726005 btw
[23:51] <ubot2> Launchpad bug 726005 in indicator-applet "indicator-applet crashed with SIGSEGV in g_cclosure_marshal_VOID__POINTER()" [Medium,Confirmed] https://launchpad.net/bugs/726005
[23:51] <seb128> ups, he's not there
[23:51] <seb128> ok, enough computer for today
[23:52] <seb128> 'night everybody
[23:56] <psusi> is this channel logged?  someone told me what gconf key controlled whether the min/max/close buttons are on the right or left earlier, and I forgot what it was...