[00:24] <TheMuso> Eww. How did a previously unreleased Ubuntu version tag make its way into the nautilus packaging branch?
[01:22] <JackyAlcine> Question: Does the kernel calls the VESA driver if the Nouveau driver fails?
[01:29] <RAOF> JackyAlcine: No.  X might, though.
[05:59] <RAOF> Yay.  Turns out 5-7 business days actually meant “today”.  I can haz internet!
[06:05] <RAOF> Hm.  Although apt seems to be having trouble contacting mirrors half the time with 504 timeouts.  That makes sbuild a sad panda :(
[06:31] <desrt> RAOF: turns out that the 5-7 business days quote was for _reliable_ internet
[07:24] <didrocks> good morning
[07:29] <pitti> Good morning
[07:37] <didrocks> hey pitti!
[07:45] <chrisccoulson> good morning everyone
[07:46] <pitti> hey chrisccoulson
[07:46] <pitti> chrisccoulson: currently looking at NEW :)
[07:46] <chrisccoulson> hi pitti, how are you?
[07:46] <chrisccoulson> excellent :)
[07:47] <pitti> I'm great! had a long night's sleep, feeling much better
[07:47] <pitti> chrisccoulson: do we need to seed the package, or did you already make it a recommends from something?
[07:48] <chrisccoulson> pitti - it's recommended by firefox. that should be enough to pull it in shouldn't it?
[07:48] <pitti> ack
[07:48] <pitti> it is
[07:48] <chrisccoulson> excellent :)
[07:51] <didrocks> good morning chrisccoulson
[07:51] <chrisccoulson> hi didrocks, how are you?
[07:51] <didrocks> chrisccoulson: very tired, need a week-end! But otherwise, good :)
[07:52] <didrocks> happy that latest "kept me busy but I have unity to hack on"-task like the scrollbar overlay is out :)
[07:52] <didrocks> still have some utouch review to do though :/
[07:52] <didrocks> and you?
[07:52] <chrisccoulson> heh :)
[07:52] <pitti> didrocks: TGIF! (and do try to not work on the WE..)
[07:53] <chrisccoulson> didrocks - yeah, pretty busy too. buy i'm glad that the menubar work for firefox has landed now :)
[07:53] <didrocks> pitti: heh thanks :) (I still need to do the gnome-session stuff as nobody seems to be interested in it)
[07:53] <didrocks> chrisccoulson: yeah, congrrats for that \o/
[07:53] <pitti> didrocks: we postponed that a little bit
[07:53] <pitti> didrocks: is it that urgent?
[07:54] <pitti> -- natty/main build deps on libhal-dev:
[07:54] <pitti> xorg-server
[07:54] <pitti> bryce_, RAOF: ^ oh noes, it's back!
[07:54] <pitti> didn't we already kill that previously?
[07:54] <didrocks> pitti: not really, because the nux detection tool doesn't make the difference between unity and compiz yet
[07:54]  * pitti hoped to demote the hal source package today
[07:54] <didrocks> (for hw requirement)
[07:54] <didrocks> but when if will come, we will need that
[07:54] <didrocks> and touching that piece earlier than later is the best thing to do :)
[07:55] <didrocks> chrisccoulson: TBH, I really hope that one day I'll be able to use firefox with launchpad
[07:55] <didrocks> chrisccoulson: then, I'll be delighted with your appmenu integration :)
[07:55] <pitti> didrocks: is there anything on your plate which doesn't require a lot of special knowledge which I could take off you?
[07:55] <didrocks> pitti: gnome-session, that was why I opened the bug :)
[07:55] <didrocks> and tried to describe
[07:55] <didrocks> but I think you're busy, I'll tackle that tomorrow
[07:56] <pitti> ok
[07:56] <didrocks> speaking of utouch :)
[07:56] <pitti> didrocks: not tomorrow..
[07:56] <didrocks> pitti: well, let's see when I feel I can do it without breaking my mind, rather :)
[07:56] <didrocks> pitti: I think I'll need your release team hat for a FFe for utouch (just doing a final check first)
[07:58] <didrocks> pitti: so bug #702630
[07:58] <ubot2> Launchpad bug 702630 in mtview "[FFe] New Source Package: mtview" [Undecided,New] https://launchpad.net/bugs/702630
[07:58] <pitti> micahg: mind if I try building xulrunner-1.9.2 without hal? 2.0 doesn't need it either, and it's the last pacakge holding hal in main
[07:58] <didrocks> it's a new package which will be in universe
[07:58] <pitti> didrocks: will looko
[07:58] <didrocks> (a test tool mainly)
[07:58] <didrocks> rydberg: am I right or terribly wrong? :)
[07:58] <rydberg> spot on!
[07:58] <didrocks> nice!
[07:58] <didrocks> thanks pitti :)
[07:59] <pitti> (done)
[07:59] <pitti> new universe package FFEs are mainly a question of finding an archive admin to process them
[07:59] <pitti> I'll sign up
[07:59] <didrocks> pitti: thanks :) I'll upload and NEW it
[07:59] <Sweetshark> Morning!
[08:00] <didrocks> (the packaging has been done by rydberg, I've cleaned up and reviewed it)
[08:00] <rydberg> it has didrocks awesomeness written all over it now ;-)
[08:00] <Sweetshark> pitti: do you think we should put the 3.3.1-1ubuntu5 LO and the OOo transitionals in natty? or should we wait for 3.3.2rc1?
[08:01] <didrocks> s/awesomness/intrusiveness/ ;)
[08:01] <chrisccoulson> pitti - yeah, you can do that
[08:01] <didrocks> hey Sweetshark!
[08:01] <rydberg> haha
[08:01] <chrisccoulson> although, i'd prefer xulrunner to be in universe too ;)
[08:01] <pitti> Sweetshark: I'd like to have the transitionals in soon, as they are currently NBS and thus prone to cleanup
[08:01] <pitti> Sweetshark: will they change (much) with 3.3.2rc1?
[08:02] <pitti> chrisccoulson: right, we still need to sort that out; but I want to see hal gone for good
[08:02] <chrisccoulson> oh, i still need to open a bug about that too
[08:05] <pitti> micahg: can I send you the debdiff to commit to https://code.launchpad.net/~mozillateam/xulrunner/xulrunner-1.9.2.head ?
[08:06] <Sweetshark> pitti: I just looked up the git logs and its less than two commits per repo and those seem to be critical fixes anyway. I found no "feature" commits there.
[08:06] <pitti> Sweetshark: you mean for the oo.o transitional source package?
[08:10] <Sweetshark> pitti: no, for the upstream changes at rc2
[08:10] <Sweetshark> ahhh
[08:11] <Sweetshark> between 3.3.1 and 3.3.2
[08:12] <Sweetshark> the only thing that changes about the transitionals is how many of them are build.
[08:12] <Sweetshark> so even less changes there
[08:18] <Sweetshark> pitti: but we could dput the OOo transitionals now (as they wont change because of a 3.3.2 release), and wait with the LO stuff for 3.3.2 rc1 (which is planned upstream for monday, debian package by tuesday i guess).
[08:18] <pitti> Sweetshark: sounds like a plan
[08:18] <pitti> Sweetshark: just tell me where to get the transitional oo.o from and I'll sponsor it
[08:19] <Sweetshark> pitti: ok, I will prepare the stuff and tell you when you can pick them up from chinstrap
[08:19] <pitti> awesome, thanks!
[08:20] <pitti> Sweetshark: btw, for the Monday/Tuesday LO upload, could you please drop the -tango recommends?
[08:20] <pitti> Sweetshark: bug 726921
[08:20] <ubot2> Launchpad bug 726921 in libreoffice "libreoffice-gtk should recommend either libreoffice-style-human or libreoffice-style-tango" [Medium,Fix committed] https://launchpad.net/bugs/726921
[08:21] <didrocks> pitti: oh, I didn't follow the full end of the story unfortunately, but is there any move on the gir python override stuff vs our integration tool?
[08:21] <pitti> didrocks: Debian didn't respond yet :/
[08:22] <pitti> didrocks: I think for now I'd recommend using dh_python2 and adding an extra symlink to the pysupport dir; or is that too hackish for you?
[08:22] <didrocks> ok, that's a blocker for s-c, but I think we can still wait a little bit
[08:22] <pitti> or just use pysupport
[08:22] <didrocks> no, that's fine to get things moving
[08:22] <didrocks> will do that on Monday
[08:22] <pitti> and the overrides shoudl be in the gir*
[08:23] <Sweetshark> pitti: see bug, fix commited so np
[08:23] <pitti> \o/
[08:24] <didrocks> pitti: thanks, will definitively do that and add some FIXME somewhere so that we don't lost sight of it
[08:24] <didrocks> loose*
[08:24] <pitti> rockin' -- latest pygobject fixes gdbus server side
[08:24]  * pitti will test and cherrypick
[08:24] <didrocks> oh nice!
[08:25] <pitti> so now we can do full gdbus with gi
[08:25]  * didrocks is eager to have some test to really do more than a "hello world" gtk app in gi :)
[08:25] <didrocks> time*
[08:25] <pitti> didrocks: we have about 6 pygi GTK apps in natty now
[08:25] <didrocks> \o/
[08:26] <pitti> apport, jockey, software-properties, language-selector, gtimelog, aptdaemon
[08:26] <didrocks> nice work :)
[08:26] <pitti> oh, and computer-janitor
[08:26] <didrocks> is the gdbus really a win for python compared to the previous binding? I remember your blog post about the length it took
[08:26] <didrocks> excellent, so now the "big application" to port is USC?
[08:26] <pitti> didrocks: all those niceness patches are upstream now
[08:27] <pitti> didrocks: so it's about as nice as python-dbus now (you just need to specify the signature, but that's desired and a feature)
[08:27] <didrocks> yeah, good to know! (and to only use "one way of doing it" between C/python) ;)
[08:29] <pitti> didrocks: as for gdbus: you need less dependencies, and it's a lot better with threads
[08:30] <didrocks> yeah, with the separate worker thread. Didn't think about it! Nice win indeed :)
[08:31] <didrocks> pitti: oh? do you want to take care of the NEWing of mtview (saw the bug report)? as I've done a "review" + advice and not the packaging of all the "utouch*" new stack, I've NEWed them myself (maybe I shouldn't have done that)
[08:33] <pitti> meh, compiz freeze; there goes my xulrunner build
[08:33] <pitti> didrocks: *shrug*, too late now :) I can do the binNEW
[08:34] <didrocks> pitti: I didn't upload yet :)
[08:34] <didrocks> pitti: I was talking about the stack I NEWed one month ago
[08:34] <didrocks> as I was doing their reviewed, it was some sort of "pre-AA review for me"
[08:34] <didrocks> hence the fact I took care if it until the end :)
[08:35] <didrocks> as it's not "my" packaging
[08:53] <pitti> micahg, chrisccoulson: can you please commit http://people.canonical.com/~pitti/tmp/xulrunner.nohal.debdiff into lp:~mozillateam/xulrunner/xulrunner-1.9.2.head ? I tested and uploaded it
[09:02] <rodrigo_> morning
[09:02] <pitti> hey rodrigo_
[09:02] <seb128> hey rodrigo_ pitti
[09:03] <seb128> dpm, hey, your keyboard layout bug, can you switch layouts with the keyboard? i.e is that only an issue with the indicator?
[09:03] <dpm> hey seb128, no, I cannot use the keyboard shortcut to switch layouts
[09:03] <seb128> dpm, do you run the updated version from yesterday? did you restart your session since?
[09:04] <dpm> I did an upgrade yesterday and this morning. I first detected it this morning, and I did not restart the session, so I guess I should do this now :)
[09:04] <dpm> just need to orderly close some windows :)
[09:05] <seb128> dpm, it would be useful if you could restart gnome-setting-daemon or better your session
[09:05] <seb128> dpm, no hurry don't close your work just for that
[09:05] <seb128> dpm, next time you have the opportunity restart it and let me know how it's working
[09:06] <dpm> seb128, ok, thanks for the pointer. Yeah, as soon as I finish off the couple of things I'm doing I'll restart the session
[09:26] <dpm> seb128, ok, so restarting the session fixed the problem, I've marked the bug as invalid, thanks for the tip!
[09:27] <seb128> dpm, thank you for testing ;-)
[09:27] <dpm> hey, does the indicator-datetime work for anyone? It's been displaying nothing but the time (i.e. no dropdown menu with the calendar) for me for quite a few days
[09:27] <seb128> dpm, let me know if your previous issue is fixed as well
[09:27] <seb128> the out of synchro
[09:28] <seb128> dpm, it works for me but I didn't update yet
[09:28] <dpm> seb128, it seems to be fixed now, I've just checked
[09:28] <seb128> great
[09:29] <seb128> dpm, you can try to kill -9 $(pidof indicator-datetime-service); /usr/lib/indicator-datetime/indicator-datetime-service
[09:30] <seb128> dpm, then see if errors are printed
[09:30] <dpm> ok
[09:36] <dpm> seb128, here's the output http://paste.ubuntu.com/575390/ - I'm not sure about the indicator-datetime-service PID, it seems to change quite often
[09:38] <dpm> ah, that was the pidof part, just a sec...
[09:39] <dpm> http://paste.ubuntu.com/575391/
[09:40] <seb128> dpm, ok, seems it keeps crashing for you
[09:40] <dpm> yeah, I'm seeing this behaviour in two natty computers
[09:41] <seb128> dpm, can you get a stacktrace of the crash?
[09:42] <seb128> dpm, doing that
[09:42] <seb128> gdb -p $(unity-panel-service)
[09:42] <seb128> taht will hang the unity-panel so it stops reloading the indicators
[09:42] <seb128> then
[09:42] <seb128> gdb /usr/lib/indicator-datetime/indicator-datetime-service
[09:42] <seb128> (gdb) run
[09:42] <seb128> (gdb) bt
[09:42] <seb128> you might want to indicator libglib2.0-0-dbgsym indicator-datetime-dbgsym before
[09:43] <dpm> I cannot use unity due to bug 726496, is there anything I should change in the instructions above if I'm in the Classic Desktop (No effect) session?
[09:44] <ubot2> Launchpad bug 726496 in nvidia-graphics-drivers "Cannot use Unity or Classic desktop with effects after the latest nvidia+xorg update" [Undecided,New] https://launchpad.net/bugs/726496
[09:44] <seb128> dpm, yes, remove the indicator-applet instead of using gdb on unity-panel-service
[09:44] <and471> mpt, hey, did you get my email?
[09:45] <seb128> dpm, then add it back after doing "run" in gdb
[09:45] <seb128> dpm, the "bt" is after gdb stop saying the indicator crashed
[09:45] <dpm> ok, thanks, give me a few mins and I'll try that
[09:45] <mpt> and471, not yet, let me check
[09:46] <seb128> dpm, thank you ;-)
[09:48] <dpm> seb128, np. I cannot find the debug symbols package for indicator-datetime. Is there any other one I should install, apart from the glib one?
[09:49] <mpt> and471, found it, I was searching for the wrong name
[09:49] <and471> ah :
[09:49] <and471> :)
[09:49] <seb128> dpm, not easy to say, just do the few steps and I will ask you again to do them a second time if we lack symbols
[09:50] <dpm> ok, sounds good
[09:50] <seb128> dpm, but a first run without those will give us some details on what is needed
[09:50] <dpm> ok
[09:50] <mpt> and471, so, I might work on some sketches over the weekend
[09:50] <and471> cool :)
[09:51] <and471> mpt, that would be very interesting :)
[10:02] <dpm> seb128, https://pastebin.canonical.com/44278/ (there is some info about accessing the Canonical calendar there, so I'm pasting it here just in case)
[10:06] <pitti> rodrigo_: hm, bug 718805 got reopened, apparently it still doesn't work :/
[10:06] <ubot2> Launchpad bug 718805 in libcanberra "[Natty] system-ready and login sounds do not play" [Medium,In progress] https://launchpad.net/bugs/718805
[10:08] <rodrigo_> pitti, yes, saw it, will look at it
[10:08] <pitti> rodrigo_: thanks
[10:08] <rodrigo_> seemed to work for me though
[10:09] <seb128> dpm, ok, seems you have an account where you don't store you password, like you need to type it when you run evolution?
[10:09] <dpm> seb128, yeah, it should store it, but it never does, and keeps asking me for the password
[10:10] <seb128> dpm, ok, so there is 2 bugs there
[10:10] <dpm> (in Evolution, that's where I first set it up)
[10:11] <seb128> dpm, the crash is bug #724856
[10:11] <ubot2> seb128: Error: Could not parse data returned by Launchpad: list index out of range (https://launchpad.net/bugs/724856)
[10:11] <dpm> ok
[10:11] <seb128> dpm, it's a side effect or the fact it can't access to the calendar
[10:12] <seb128> dpm, it wants to ask you for your password but the indicator doesn't handle that
[10:12] <seb128> so rather than asking it crashes
[10:12] <dpm> ok, understood
[10:12] <seb128> dpm, does it stop happening if you run evo and authentificate for the calendar?
[10:12] <seb128> or if you turn off this calendar in evo
[10:12] <dpm> let me try
[10:13] <dpm> although the problem is that evo never stores the password for some reason
[10:13] <seb128> did you open a bug about that?
[10:13] <dpm> I never bothered, but I will now ;)
[10:13] <seb128> if not please do, run evo on a command line and see if it prints errors as well
[10:13] <seb128> thanks
[10:13] <dpm> ok
[10:35] <mvo> hey, why exactly is window-picker-applet in main? and do we still need it there?
[10:36] <seb128> it was used by UNE before
[10:36] <seb128> but it can probably go to universe now
[10:37] <mvo> seb128: I can not find it in the seeds or any rdepends, so I guess demotion is fine
[10:37] <seb128> yes
[10:37] <mvo> just fixed a ftbfs and stumbled over it there
[10:37] <seb128> weird, if nothing pulls it in it should be on components-mismatch
[10:37] <seb128> check with ogra I thin
[10:38] <seb128> it was probably only staying it due to mobile images
[10:38] <seb128> but they have unity-2d now
[10:38] <didrocks> right
[10:38] <mvo> maybe I don't have the right seed
[10:38]  * mvo checks
[10:38] <didrocks> we kept it for the mobile image
[10:38] <ogra> mvo, the efl UI just moved off the seeds before A3
[10:38] <didrocks> as seb128 told, I think it's not anymore needed now that there is unity2d
[10:38] <didrocks> :)
[10:38] <mvo> ok, cool
[10:38]  * mvo waves bybye
[10:38] <ogra> i just didnt find the time to ask for demotion yet
[10:39] <seb128> well it should show on component-mismatchs
[10:39] <seb128> something is likely still bringing in
[10:39] <mvo> still in a seed somewhere?
[10:39] <mvo> maybe?
[10:39] <seb128> likely
[10:39] <seb128> get the seeds directory and grep in it
[10:40] <Sweetshark> do we have anyone who is familiar with the iternal of openjdk?
[10:40] <Sweetshark> someone who could comment on bug 710641?
[10:40] <ubot2> Launchpad bug 710641 in openjdk-6 "During usage of LibreOffice: A fatal error has been detected by the Java Runtime Environment" [Undecided,New] https://launchpad.net/bugs/710641
[10:42] <mvo> well, I don't have them all, but from netbook it was remvoed 2011-02-15
[10:42] <seb128> mvo, could still be on a dvd or something
[10:43] <seb128> brb session restart with the new indicator stack
[10:43] <ogra> ogra@osiris:~$ apt-cache showsrc window-picker-applet|grep -i section
[10:43] <ogra> Section: universe/gnome
[10:43] <ogra> mvo, ??? ^^^
[10:44] <and471> mvo, hey, long time no speak :) when do you think you could merge the synaptic resize-grip fix ?
[10:44] <ogra> mvo, the binary is still in main, i wonder if it needs a rebuild or something for the publisher to pick up
[10:45] <mvo> well, rebuild will be there in a couple of minutes, just upload a ftbfs
[10:45] <mvo> then we know
[10:45] <mvo> and471: hey, let me check
[10:49] <mvo> seb128: are you aware of the gnome-games build failure? http://launchpadlibrarian.net/63290767/buildlog_ubuntu-natty-i386.gnome-games_1%3A2.32.1-0ubuntu3_FAILEDTOBUILD.txt.gz: dh_girepository: Could not find library libgames-support-gi.so.0
[10:49] <mvo> and471: looks fine, merging now
[10:50] <seb128> mvo, no, but pitti might have a clue of that's a gi issue
[10:50] <pecisk_darbs> hi people, I wanted to ask - what are Ubuntu/Canonical plans with GNOME 3 (except GNOME Shell of course, as Canonical moves forward with Unity)?
[10:55] <and471> mvo, many thanks
[10:56] <seb128> pecisk_darbs, what do you want to know exactly?
[10:56] <seb128> pecisk_darbs, we don't plan to stay on GNOME2 for ever if that's the question
[10:56] <mvo> and471: thank you! and sorry for the delay, I have no clue why LP did not send me a mail about it
[10:57] <and471> mvo, no problem :)
[11:00] <pitti> seb128, mvo: might be missing an -I to the dir where libgames-support-gi.so.0
[11:00] <pitti> is built?
[11:01] <pitti> the .so is built fine
[11:10] <dpm> if I need to file a bug report in the time and date settings, is indicator-datetime the right package? Or do the settings have a separate package?
[11:10] <seb128> dpm, it's the correct component
[11:11] <seb128> dpm, check open bugs though some issues a known
[11:11] <seb128> like some of the settings not working
[11:11] <dpm> ok, yeah, I'll check, but it seems not to be very locale aware, though :(
[11:11]  * Sweetshark reboots
[11:12] <seb128> dpm, how so?
[11:15] <dpm> seb128, it seems to ignore the locale settings for time and dates in several places. In the first tab to set the time, the date is in ISO format. The appointment times from the Evo calendar are shown in 12-hour format, despite my locale specifying 24-hour format
[11:15] <dpm> and the explicit setting in the indicator itself to use 24-hour format
[11:15] <seb128> right
[11:16] <seb128> I can confirm those
[11:20] <GunnarHj> pitti: Hi Martin, as regards the backports of l-s and gdm that I am suggesting, I found it easiest to create branches based on the latest Lucid respective Maverick version and add the Natty stuff, i.e. they are similar to -updates.
[11:20] <GunnarHj> pitti: For that reason, Scott K. wants that somebody in the desktop team "blesses" bug 719815 before the branches are uploaded. Guess he would like to see something more of a stand-point than the quick bug comment you added last week.
[11:20] <ubot2> Launchpad bug 719815 in maverick-backports "Please backport gdm and language-selector to Lucid and Maverick" [Undecided,Incomplete] https://launchpad.net/bugs/719815
[11:20] <GunnarHj> pitti: Would it be ok with you to provide the requested endorsement?
[11:21] <seb128> dpm, those 2 crashes you reported, did you already clean the .crashes?
[11:22] <RAOF> pitti: That hal dependency looks like a false-positive af your tool?  Unless we're secretly planning a kfreebsd kernel? :)
[11:22] <pitti> RAOF: aah, thanks
[11:23] <pitti> hah! look what's on http://people.canonical.com/~ubuntu-archive/component-mismatches.txt now \o/
[11:23] <pitti> hey GunnarHj
[11:24] <pitti> GunnarHj: I guess you tested the PPA on actual lucid/maverick installations?
[11:24] <GunnarHj> pitti: Yes, I did.
[11:42] <Sweetshark> pitti: Whats the exact the of the desktop meeting on tuesday?
[11:43] <Sweetshark> 16:30UTC?
[11:43] <pitti> Sweetshark: exact time?
[11:43] <pitti> yes
[11:43] <Sweetshark> thanks
[11:55] <pitti> didrocks: small correction to mtview's copyright file:
[11:55] <pitti> Files: * (unless noted below)
[11:55] <pitti> please just "*"; the "unless noted below" is implicit, and this breaks machine parseability
[11:55] <pitti> otherwise it's fine, accepted
[11:55] <didrocks> oh right, I didn't pay attention to that, sorry
[11:56] <didrocks> changing
[11:56] <didrocks> pitti: no need for new upload for now? just changing in the vcs, right?
[11:56] <pitti> didrocks: right
[11:56] <didrocks> ok, thanks pitti :)
[12:02] <scarleo> Quick question: Will there be mouse wheel scrolling in Unity Places? (or whatever the app-view is called)
[12:04] <seb128> scarleo, hey, no reason to not do it, it's just that the unity team focussed on getting features to land recently, those sort of issues will be tackled next
[12:04] <seb128> scarleo, hey, no reason to not do it, it's just that the unity team focussed on getting features to land recently, those sort of issues will be tackled next.
[12:04] <seb128> ups
[12:04] <scarleo> seb128: Great, thanks
[12:04] <htorque> iirc there's already a bug open for scrolling in the dash
[12:04] <seb128> scarleo, bug #721447
[12:04] <ubot2> Launchpad bug 721447 in unity "Unable to scroll in Applications/Files and Folders Place using mouse wheel" [Medium,Triaged] https://launchpad.net/bugs/721447
[12:05] <seb128> scarleo, if you want to track the issue
[12:05] <scarleo> seb128: ty
[12:05] <seb128> you're welcome
[12:22] <seb128> pitti, can you try if gnome-display lists gnome-display-properties?
[12:22] <pitti> "gnome-display"?
[12:22] <seb128> pitti, I think it's rather an issue with 1 letter words than with "-"
[12:22] <seb128> pitti, in the dash
[12:22] <pitti> aah
[12:23] <pitti> seb128: it's called "Bildschirme" here
[12:23] <seb128> pitti, it's supposed to ignore "-" but use each word for the query, but your example had 1 letter words
[12:23] <seb128> pitti, well gnome-display-properties is still the command name ;-)
[12:23] <pitti> seb128: "display" works, "display-" works, "display-p" stops working
[12:24] <pitti> gnome-display doesn't work
[12:24] <pitti> seb128: so by that logic, shouldn't it be "d-feet" -> (hyphen elimination) -> "d feet" -> (ignore 1 letters) -> "feet"?
[12:24] <pitti> "feet" does work
[12:24] <seb128> weird, it stopped working as well here
[12:24] <seb128> it's a bug for kamstrup anyway ;-)
[12:25] <seb128> pitti, yeah, there is something buggy there, I was just wondering if it's one letter words rather than -"
[12:25] <seb128> "-"
[12:25] <kamstrup> seb128, pitti: we're not indexing Exec lines
[12:26] <seb128> kamstrup, well it's Name entries in this case
[12:26] <seb128> kamstrup, bug #729025
[12:26] <ubot2> Launchpad bug 729025 in unity "dash search does not find names with '-' (d-feet, e-mail)" [Undecided,New] https://launchpad.net/bugs/729025
[12:26] <pitti> kamstrup: by design, or just omission?
[12:26] <kamstrup> seb128: gnome-display-properties in Name?
[12:26] <seb128> kamstrup, no, that was me doing wrong debugging
[12:26] <kamstrup> pitti: i can't recall :-) I think it's by design
[12:26] <seb128> kamstrup, d-feet or frozen-bubble are buggy
[12:27] <kamstrup> pitti: but it's trivial to add
[12:27] <seb128> kamstrup, but those are the names listed in the place view
[12:27] <didrocks> and d- is showing d-feet, just when you press f it vanishes
[12:27] <kamstrup> right, i can see that
[12:27] <seb128> same for frozen-bubble
[12:28] <seb128> so it's not 1 char words
[12:28] <didrocks> same for the file place
[12:28] <pitti> didrocks: ah, confirmed
[12:28] <didrocks> kamstrup: if that can help ^^
[12:29] <didrocks> (yeah, I just found I have an avi called "frozen-bubble") :)
[12:29] <pitti> for the file place it shouldn't do any magic on the file names; you do want to search for - + :, etc.
[12:29] <seb128> lol
[12:29] <kamstrup> didrocks, seb128: don't worry, I think I know why
[12:33] <kamstrup> pitti, seb128, didrocks: I am hesitant to add Exec to the indexed fields - now that we get Alt-F2 anyway, and most mortal users wont have the faintest idea why searching for "properties" brings up the screen res changer
[12:34] <pitti> kamstrup: *nod*
[12:34] <kamstrup> or, what I'm trying to say is that users probably don't know the exec names of apps
[12:34] <kamstrup> and might be confused
[12:34] <didrocks> kamstrup: yeah, Exec= doesn't really make sense as alt + F2 will get it
[12:34] <kamstrup> but let's wait and see the situation once we have alt-f2 working
[12:34] <didrocks> "-" support in name is needed though
[12:34] <kamstrup> if alt-f2 doesn't cut it, it's a 2-liner to add
[12:34] <kamstrup> agreed
[12:35] <didrocks> alt-f2 will do it :)
[12:35] <seb128> kamstrup, right
[12:49] <dpm> hi pitti, according to the schedule we worked out, next week we should upload the next maverick langpack updates to -proposed and begin testing. Does that still sound ok to you, is that doable?
[12:49] <dpm> https://wiki.ubuntu.com/Translations/MaverickLanguagePackReleaseSchedule
[12:56] <seb128> dpm, did you see my question before?
[12:56] <seb128> mterry, hello you ;-)
[12:56] <mterry> seb128, hello!
[12:56] <seb128> chrisccoulson, there is still an indicator bug in gnome-bt ;-)
[12:57] <dpm> seb128, I got disconnected for a couple of minutes, I think, I might have not seen it. would you mind repeating the question?
[12:57] <seb128> dpm, do you still have the .crashes for your crashes?
[12:57] <dpm> seb128, the ones in /var/crash? Probably
[12:57] <seb128> it lacks the appmenu symbols and since you did send the minimal crash infos it can't be retraced
[12:58] <seb128> dpm, is there any reason you don't want to send the normal crash for nautilus?
[12:58] <seb128> dpm, if you don't I will ask you to install appmenu-gtk-dbgsym and retrace it locally
[12:58] <dpm> seb128, yeah, it was like 60 MB, IIRC, it takes a while to upload on my connection
[12:59] <seb128> dpm, can you install appmenu-gtk-dbgsym and see if you get the issue again then?
[12:59] <seb128> well install it
[12:59] <seb128> so if you get a crash again it has the missing infos
[13:00] <dpm> seb128, ok, let me do that
[13:01] <seb128> dpm, thanks
[13:01] <dpm> seb128, I cannot find an appmenu-gtk-dbgsym package. Any hints on any other name it might have?
[13:01] <seb128> dpm, deb http://ddebs.ubuntu.com natty main restricted universe
[13:02] <dpm> oh, I see
[13:02] <seb128> dpm, do you have that source in your sources.list?
[13:02] <dpm> ok, thanks
[13:02] <seb128> dpm, you're welcome
[13:19] <pitti> dpm: sure, sounds fine
[13:23] <dpm> thanks pitti, I'll just ping you at the time next week then
[13:29] <dpm> seb128, I've attached the nautilus .crash file to the bug. The file itself was only 12 Mb, so it wasn't too bad tu upload. I've installed the debug symbols for next crash. In the meantime I hope this helps
[13:29] <dpm> and with this, I'll leave for lunch :)
[13:30] <seb128> dpm, hum, "thanks" I guess, but for next time please use apport to send it again, the retracers know how to handle new bugs, not .crashes in comments of an open issue
[13:30] <seb128> dpm, enjoy
[13:31] <seb128> dpm, "thanks" I guess should have come with a ";-)"
[13:32] <Sweetshark> pitti:  openoffice.org_3.3.0-6ubuntu1_source.changes is on chinstrap
[13:40] <pitti> Sweetshark: uploaded
[14:03] <mterry> chrisccoulson, is Firefox supposed to be using global menu?
[14:07] <pitti> mterry: it was uploaded to natty and newed this morning
[14:07] <pitti> so with today's packages yes
[14:08] <pitti> mterry: (chris is out today, FTR)
[14:08] <pitti> dist-upgrade does pull in firefox-globalmenu for me
[14:20] <pitti> mterry: WFM here -- not for you?
[14:20]  * kenvandine grumbles about LO not using F11 for fullscreen
[14:21] <mterry> pitti, I don't see the -globalmenu package, but I did get the updated firefox, so thought something was odd.  maybe it's just not built for amd64 yet?
[14:21] <kenvandine> pitti, i got firefox-globalmenu today
[14:21] <kenvandine> mterry, ^^
[14:21] <pitti> mterry: I'm on amd64
[14:21] <pitti> and I NEWed all arches at once
[14:21] <kenvandine> me too
[14:21] <mterry> Hmm, it's in my apt cache
[14:21] <mterry> But nothing pulled it in to be installed
[14:22] <pitti> Package: firefox
[14:22] <pitti> Version: 4.0~b12+build1+nobinonly-0ubuntu3
[14:22] <pitti> Recommends: ubufox, firefox-globalmenu
[14:22] <pitti> looks fine to me
[14:23] <mterry> I dunno either
[14:23] <mterry> I have the newer firefox, which clearly Recommends the globalmenu
[14:23] <pitti> perhaps you used upgrade, not dist-upgrade?
[14:23] <mterry> Probably.  And once that opportunity passed, dist-upgrade won't show it again, eh?
[14:24] <pitti> *nod*
[14:24] <pitti> it remembers that it doesn't offer again previously declined recommends
[14:30] <seb128> re
[14:38] <seb128> I hate retracers
[14:39] <seb128> or I hate python packaging on ubuntu not sure ;-)
[14:39]  * pitti hugs seb128, again !?!
[14:39]  * seb128 hugs pitti
[14:40] <seb128> pitti, yeah, I just fixed the i386 one
[14:40] <seb128> needed to install -reinstall python-launchpadlib
[14:40] <seb128> why do they break almost daily?!
[14:50] <seb128> ok
[14:50] <seb128> mterry, congrats, you just won bug #729065 ;-)
[14:50] <ubot2> Launchpad bug 729065 in indicator-appmenu "gnome-display-properties crashed with SIGSEGV in g_object_set()" [Undecided,Confirmed] https://launchpad.net/bugs/729065
[14:51] <mterry> yay!  w00
[15:11] <dobey> hrmm
[15:11] <pitti> dpm: FYI, I requested a full natty langpack export now; I'm very close to fixing firefox XPI handling
[15:11] <dobey> i can just upload an updated package with the same version to -proposed right?
[15:12] <pitti> dobey: same version as where?
[15:12] <dobey> as the one i previously uploaded to proposed
[15:12] <dpm> pitti, oh, that's awesome, thanks for the heads up and for working on that
[15:13] <pitti> dobey: if it hasn't been accepted yet, yes; otherwise you need to bump
[15:13] <dobey> pitti: accepted into archive, or into -updates?
[15:13] <pitti> dobey: archive, i. e. into -proposed
[15:13] <dobey> ok
[15:13] <dobey> thanks
[15:16] <pitti> ronoc: I now have two audio sliders in the indicator; the upper one works, the second one doesn't change the volume at all, but clicking on it causes RB to reappear (it's sitting in the background, playing)
[15:36] <seb128> mterry, I found bug #729128 if you run out of bugs and want to add another one to your list
[15:36] <mterry> seb128, I'm good for now thanks.  :)
[15:36] <seb128> not sure if it's in the indicator-application stack or libdbusmenu
[15:37] <seb128> mterry, ok
[15:37] <seb128> no bot?
[15:37] <mterry> seb128, I guess keep it in your backpocket
[15:37] <seb128> I do ;-)
[15:37] <seb128> or I could start bugging ted as well about indicator bugs, since we are over feature freeze now he should have time for those
[15:38] <seb128> tedg, ^ you might want to claim that bug
[16:02] <pitti> there, the xpi/langpack side of firefox translations now work
[16:02] <pitti> including test cases \o/
[16:03] <pitti> now, if Firefox would actually check the locale and _select_ the language, that'd be even better..
[16:03] <pitti> but firefox -UILocale de is all German again
[16:03] <pitti> dpm: ^ FYI (I'll mail Chris about the locale check problem)
[16:03] <pitti> but that doesn't stop us from shipping XPIs in langpacks
[16:03] <dpm> pitti, \o/
[16:04] <pitti> dpm: note that I just fixed the case of non-devmode
[16:04] <pitti> dpm: IOW, I completely ignore po2xpi, xpi2xpi etc. and just copy/rename the XPIs as they are to the right place
[16:04] <pitti> it is soooo much easier now
[16:04] <pitti> dpm: fixing devmode is part 2 now, I guess
[16:07] <dpm> pitti, yeah, I agree. The important part is to ship translations first. If it cannot be done this cycle we should talk about it at UDS and perhaps allocate some time for po2xpi on the next one
[16:07] <dpm> chrisccoulson, ^
[16:10] <pitti> dpm: hm, lucid cronjobs were disabled (probably for 10.04.2), reenabled
[16:10] <pitti> keeping natty disabled until next week when I manually rebuild a full export
[16:10] <pitti> dpm: maverick packages in PPA should be reasonably current (cron job is on)
[16:12] <dpm> pitti, ok. We didn't talk about it after the point release, but were all langpacks listed on https://wiki.ubuntu.com/Translations/LanguagePackUpdatesQA uploaded in the end? i.e. can I clear the page to list the maverick ones next week?
[16:13] <pitti> dpm: oh, probably missing a few
[16:13] <pitti> dpm: give me some minutes to copy the remaining good ones
[16:14] <pitti> (have release meeting, slow..)
[16:14] <dpm> pitti, cool, thanks
[16:19] <pitti> dpm: seems only the Polish ones were missing, copying now
[16:19] <pitti> dpm: copying, you can flush
[16:29] <pitti> didrocks: do we have an XDG overlay dir for unity?
[16:29] <didrocks> pitti: not that I know of, why?
[16:29] <pitti> didrocks: I wonder how to make gnome-cc.desktop appear in unity's app search, but not in gnome classic
[16:29] <didrocks> oh you mean for some filtered app
[16:29] <didrocks> yeah, there is .menu blacklist
[16:29] <didrocks> in the application place
[16:30] <pitti> didrocks: in classic gnome I don't see /usr/share/applications/gnomecc.desktop (NoDisplay=true), which shuold be kept
[16:30] <pitti> didrocks: but bug 727823 requests to show it in unity searcherf
[16:30] <didrocks> pitti: I'm not sure the .menu file can override the NoDisplay=true, isn't it?
[16:30] <hrw> does someone has idea if bug 720434 will get fixed?
[16:32] <pitti> didrocks: oh, I could add it to unity-place-applications.menu perhaps?
[16:32] <didrocks> pitti: that's what I told, there is already one
[16:32] <pitti> didrocks: cool, thanks! I'll play with that
[16:32] <didrocks> pitti: but this override the NoDisplay=true in the desktop file?
[16:33] <didrocks> pitti: data/unity-place-applications.menu.in in the source
[16:33] <pitti> didrocks: I'll figure something out; we might also remove the NoDisplay and filter it out in applications.menu
[16:34] <didrocks> pitti: if you can show baobab in the same time, that would be awesome :)
[16:34] <pitti> just needed a first pointer
[16:34] <didrocks> yeah
[16:34] <pitti> didrocks: sure, once it works for this, it's trivial to replicate for others
[16:34] <didrocks> pitti: it's just we blacklisted some before of UNE
[16:34] <pitti> NotShowIn=KDE;
[16:34] <didrocks> pitti: just need an update on which one should be shown now :)
[16:34] <pitti> hm, it's not actually hidden
[16:35] <pitti> didrocks: anyway, will investigate
[16:35] <didrocks> it's not a NoDsiplay=true rather?
[16:35]  * pitti doesn't want to steal more time from you
[16:35] <didrocks> pitti: no worry, I just see:
[16:35] <didrocks> NoDisplay=true
[16:35] <pitti> (and have release meeting)
[16:35] <didrocks> in /usr/share/applications/gnomecc.desktop
[16:35] <didrocks> oh, you mean for brasero?
[16:36] <pitti> didrocks: for baobab
[16:36] <didrocks> yeah baobab
[16:36] <didrocks> pitti: it's in the data/unity-place-applications.menu.in
[16:36] <didrocks> we blacklisted it there for UNE :)
[16:36] <pitti> ah :)
[16:36] <pitti> so, I have all pieces of the puzzle together now
[16:37] <didrocks> yeah ;)
[16:37] <didrocks> good luck!
[16:37] <seb128> pitti, what are you trying to do?
[16:37] <pitti> seb128: bug 727823
[16:38] <seb128> where is the bot today? ;-)
[16:38]  * pitti slaps ubottu
[16:38] <pitti> https://bugs.launchpad.net/ubuntu/natty/+source/unity-place-applications/+bug/727823
[16:39] <seb128> hum, k, I had some email discussions about that with people as well this week
[16:40] <hrww> does someone has idea if bug 720434 will get fixed? (sorry if repeated, was disconnected)
[16:40] <seb128> hrww, not likely since only you get it so far and it has no details
[16:41] <dpm_> pitti, I've added a simple status table to better keep track of when cronjobs are disabled and need reenabling. I cannot think of an easier automated way, so I think this might do for now. What do you think, do you think you could update the table every time langpack builds are enabled/disabled (or ping me to do it, whatever works best for you)?
[16:41] <dpm_> https://dev.launchpad.net/Translations/LanguagePackSchedule
[16:41] <dpm_> https://dev.launchpad.net/Translations/LanguagePackSchedule/Status
[16:41] <pitti> seb128: we just got a major netsplit in #meeting as well; I guess the bot is on the other side of the pond
[16:42] <pitti> dpm_: hm, I'll try to remember
[16:43] <pitti> dpm_: would it help if I'd export the current crontab to a web accessible dir?
[16:44] <dpm_> pitti, yeah
[16:45] <pitti> dpm_: http://macquarie.canonical.com/~langpack/crontab
[16:45] <hrww> seb128: right
[16:45] <seb128> pitti, btw the decision to hide the g-c-c entry was before the interface has issues, it's slow to load and has some bugs
[16:45] <seb128> before -> because
[16:45] <seb128> pitti, it would make sense to let the place find it but we shouldn't expose it in the indicator
[16:46] <pitti>  seb128: ok
[16:46] <pitti> dpm_: I added crontab export to the crontab now :)
[16:46] <pitti> dpm_: I can also pre-process it in some way if you want
[16:48] <dpm_> pitti, that'd be cool. I'm only interested in fact in the distro name and if it's enabled or not (and perhaps optionally the day and time)
[16:58] <pitti> dpm:
[16:58] <pitti> natty at 14:00 on 2: disabled
[16:58] <pitti> lucid-updates at 14:00 on 6: enabled
[16:58] <pitti> maverick-updates at 14:00 on 3: enabled
[16:58] <pitti> dpm: now I just need to translate the day number into a name..
[16:59] <dpm> pitti, yeah, that'd be perfect
[17:00] <pitti> perl -nae 'print ("$F[-1] at $F[1]:00 on ", ("Sun", "Mon", "Tue", "Wed", "Thu", "Fri", "Sat", "Sun")[$F[4]], ": ", ( ($F[0] =~ /^#/) ? "disabled" : "enabled"), "\n")'
[17:00] <pitti> hah! Perl FTW
[17:00] <pitti> dpm: http://macquarie.canonical.com/~langpack/crontab
[17:01] <pitti> dpm: is it possible to include something like that into a moin page (an external link displayed inline)?
[17:01] <pitti> dpm: if so, I can easily add some || for table formatting
[17:03] <dpm> pitti, I don't know of any way of doing that, other than having a moin user writing regularly to the page. Let me ask around...
[17:04] <pitti> dpm: otherwise just link to it
[17:05] <mterry_> seb128, in https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/726388 you say you can get similar crashes by running indicator-messages (I assume) under valgrind then running apps.  The messages indicator or the service?
[17:05] <seb128> mterry_, the service sorry
[17:05] <mterry_> k, will try
[17:05] <seb128> mterry_, way to get it, attach gdb to the unity panel service to block it, run the indicator-message-service under valgrind, unblock gdb, open pidgin
[17:06] <dpm> pitti, yeah, that's what I'll do for now. I'll try to find out if it's possible to update the wiki page in the meantime, and if it is, I might ask you to add table formatting later on
[17:06] <mterry_> seb128, ah, thanks
[17:06] <dpm> pitti, thanks, that'll be really helpful!
[17:06]  * mterry_ still wants a --replace argument for services
[17:06] <seb128> mterry_, "open pidgin" is by using the indicator menu
[17:06] <seb128> mterry_, yeah, my workaround is to block the loader with gdb time to start the other instance
[17:07] <pitti> dpm: btw, you should get added to the langpack group on macquarie, then you can check/change yourself; I'll send an RT
[17:07] <seb128> mterry_, I got gedit to crash once with the appmenu-gtk bug you made a ppa for btw but I've no clue what I did for that
[17:07] <pitti> dpm: hm, you don't have a chinstrap account?
[17:07] <seb128> mterry_, i've the feeling it had with me stopping the unity-panel under gdb, something in appmenu didn't like it
[17:08] <mterry_> hm
[17:08] <pitti> dpm: nevermind, mis-grepped
[17:08] <dpm> ok
[17:09] <mterry_> seb128, was the pidgin thing 100% reproducable?
[17:09] <seb128> mterry_, yes, it might have been fixed, do you want me to try?
[17:10] <mterry_> seb128, please try.  if you can still hit it, maybe I can send a PPA your way.  i have another idea, but would like to be able to test it
[17:14] <seb128> mterry_, right, still happening
[17:14] <seb128> mterry_, pidgin segfault on start
[17:14] <mterry_> seb128, yay.  will let you know when I have a package
[17:14] <seb128> mterry_, ok
[17:15] <mterry_> seb128, thanks for being my guinea pig
[17:15] <seb128> mterry_, thanks for dealing with those bugs ;-)
[17:16] <seb128> mterry_, do you know if there is a bug about the empathy issues you discussed before btw? seems like that should be on the natty list as well
[17:17] <mterry_> seb128, empathy issues I thought I had fixed, but I just heard in #ayatana that there are still issues.  So yeah, I guess there are still bugs but not sure about bugs (I recall that all open bugs had been closed)
[17:17] <mterry_> I mean, not sure about bug numbers
[17:17] <seb128> ok, I didn't know there was still issues either
[17:17] <seb128> I just read the discussion earlier
[17:17] <seb128> I will check on that
[17:22] <GunnarHj> pitti: Did you put my backports question on hold till you get better time? (which is perfectly fine - just checking that you didn't forget it).
[17:23] <pitti> GunnarHj: right (release meeting and some other stuff, sorry)
[17:23] <GunnarHj> pitti: No problem; thx for letting me know.
[17:32] <pitti> mvo: would you mind fixing up the state of bug 665572? (there's a pending SRU upload for it)
[17:35] <mvo> pitti: yes, will do after dinner
[17:35] <pitti> mvo: thanks!
[17:45] <mterry_> seb128, packages for testing the valgrind crash are here:  https://launchpad.net/~mterry/+archive/ppa2/+packages   not built yet, but you can either wait or build them yourself
[17:47] <seb128> mterry_, I will build those myself, it's not like it was hours of build ;-)
[17:55] <dobey> pitti: for bug #661292 - i have a patch i'm working on getting uploaded to -proposed (hence my question earlier); but i think quilt is giving me some grief at the moment
[17:56] <dobey> but seems to be working, albeit quietly
[18:04]  * pitti waves good bye, have a nice weekend everyone
[18:04] <pitti> GunnarHj: (patches ack'ed, thanks for working on this!)
[18:04] <didrocks1> pitti: see you! enjoy your week-end
[18:05] <pitti> didrocks1: you too!
[18:08] <dobey> doh
[18:08] <dobey> pitti: i was going to ask you to approve my package :)
[18:09] <dobey> but cheers anyway :)
[18:21] <GunnarHj> pitti: Thanks, Martin. Have a nice weekend!
[18:26] <seb128> mterry_, the ppa build fixes the crash under valgrind
[18:27] <mterry_> seb128, yay!!!
[18:27] <mterry_> seb128, ok, will file a merge
[18:27] <seb128> thanks
[18:27] <seb128> mterry_, just curious how do you debug those?
[18:27] <seb128> by reading the code and understanding the sequences of events?
[18:27] <mterry_> seb128, these past few where I can't test, yeah
[18:27] <seb128> or is there any way to make useful logs?
[18:28] <mterry_> seb128, it's a common pattern of forgetting to cancel pending callbacks when an object the callback relies on dies
[18:28] <seb128> k
[18:28] <mterry_> Easy thing to forget to cleanup
[18:28] <seb128> I guess experience debugging those sort of issues help there ;-)
[18:28] <mterry_> yeah :)
[18:28] <seb128> mterry_, thanks
[18:29] <seb128> mterry_, btw was that the same issue that the g_object_set crash from today?
[18:29] <dobey> mterry_: are you an archive admin?
[18:29] <mterry_> seb128, that's what I thought, but the user has reported a different crash with my ppa.  Trying to determine if that's a good or bad sign right now . :)
[18:29] <mterry_> dobey, no
[18:30] <dobey> ah ok
[18:44] <seb128> mterry_, ok, found a way to crash easily using your ppa version
[18:45] <mterry_> seb128, ack!
[18:46] <mterry_> seb128, so not fixed after all?
[18:46] <mterry_> seb128, or you talking about the display dialog crash?
[18:46] <seb128> mterry_, the indicator-messages thing is fixed
[18:46] <seb128> mterry_, not sure if it's a new one
[18:46] <seb128> run gedit and close it immediatly
[18:46] <seb128> or other gtk apps will do I guess
[18:46] <mterry_> seb128, with the appmenu-gtk version in the ppa I sent you?
[18:46] <seb128> yes
[18:46] <mterry_> seb128, OK.  I have to reboot, but will try in a sec
[18:49] <seb128> mterry, wb
[18:49] <mterry> seb128, :)
[18:49] <seb128> mterry, ok, just tried on gconf-editor
[18:51] <seb128> mterry, http://paste.ubuntu.com/575638/
[18:52] <seb128> mterry, you will make fun of me again but it's easy to get in valgrind, just close the dialog before it's loaded
[18:52] <mterry> seb128, I can get it with gedit too
[18:52] <seb128> like valgrind gconf-editor and click on the close wm button before it finished loading
[18:52] <didrocks> have a good week-end guys!
[18:52] <seb128> gconf-editor is faster to load than gedit so it's better to try ;-)
[18:52] <seb128> didrocks, thank, you as well
[18:52]  * didrocks launches his spam script and go away :)
[18:53] <didrocks> thanks!
[18:53] <seb128> mterry, gedit seems to crash in some recently used gtk code though
[18:53] <seb128> well the crash I got in gdb was in that code
[18:53] <seb128> gconf-editor shows the issue I just pastebined in valgrind
[18:57] <mterry> bratsche, wait a sec on that timeoujt merge
[18:57] <bratsche> mterry: I'll let you merge if you want.
[18:57] <dobey> bratsche: oh, there you are
[18:58] <mterry> bratsche, I can't, but I think I have a tiny change to fix the new crash
[18:58] <bratsche> mterry: Actually, are you interested in taking over appmenu-gtk entirely?  I forgot about it, and today is my last day at Canonical.
[18:58] <bratsche> Hey dobey
[18:58] <dobey> bratsche: is there a style setting or something i can put in my gtkrc to disable the resize triangles?
[18:58] <dobey> oh
[18:58] <rickspencer3> kenvandine, hey, around at all?
[18:58] <mterry> bratsche, well, I'm not DX
[18:59] <kenvandine> rickspencer3, yup
[18:59] <mterry> bratsche, and bye!  :)  good luck!
[18:59] <rickspencer3> kenvandine, do you know what's up with this FFE for overlay scrollbars?
[18:59] <rickspencer3> I can't find a bug or anything on it
[18:59] <seb128> rickspencer3, there is no ffe for it
[18:59] <rickspencer3> just a mention on sabdfl's blog and a mention in the release meeting this morning
[18:59] <rickspencer3> hi seb128
[18:59] <seb128> rickspencer3, wasn't the consensus that it was a ppa thing only for this cycle?
[18:59] <rickspencer3> so, er ... what's the deal?
[19:00] <seb128> rickspencer3, we already got crashers due to it
[19:00] <rickspencer3> seb128, I don't know
[19:00] <rickspencer3> I just saw it mentioned in the release meeting
[19:00] <rickspencer3> as a FFE
[19:00] <rickspencer3> and now I can't get any more info about it
[19:00] <seb128> seems not a great idea to make gtk unstable in natty for something we don't use
[19:00] <bratsche> dobey: I don't think so.. there are style properties GtkWindow::resize-grip-width and ::resize-grip-height - maybe you could set them to 0, but I doubt that would be exactly what you want.  We might need to add one to disable it.
[19:00] <rickspencer3> seb128, I agree
[19:00] <seb128> rickspencer3, who mentioned the ffe for it? dbarth?
[19:00] <rickspencer3> seb128, yes
[19:00] <rickspencer3> just a couple of hours ago in the release meeting
[19:01] <rickspencer3> so I'm trying to figure out what's going on, because it seems like not a great idea
[19:02] <dobey> hrmm
[19:03] <mterry> bratsche, ok, well, new fix pushed.  it should be good now
[19:03] <mvo> pitti: updated, all the stuff is in natty already
[19:03] <mterry> seb128, got a fix for the new crash, thanks for noticing
[19:03] <bratsche> mterry: awesome
[19:03] <kenvandine> i tried it out...the only thing it worked for was appearances dialog
[19:04] <seb128> mterry, thanks, want me to try the new version?
[19:05] <mterry> seb128, sure just to be safe, let me spin it up
[19:06] <mterry> seb128, in the ppa
[19:07] <seb128> mterry, ok, you can give me a vcs as well, easier to build that going on launchpad to dget and dpkg-source and build ;-)
[19:07] <mterry> seb128, lp:~mterry/appmenu-gtk/fix-timeout-crash
[19:08] <seb128> thanks
[19:13] <seb128> mterry, ok, will run that for a bit and let you know if I still get an issue
[19:13] <seb128> dinner time though
[19:13] <seb128> see you later
[20:14] <Ampelbein> what is the preferred way of determining the default browser in natty? (i.e. the browser xdg-open/gnome-open will choose when opening http-URLs)
[20:14] <mterry> Ampelbein, programmatically?
[20:14] <mterry> Ampelbein, gio has functions for that
[20:15] <dobey> Ampelbein: it is determined via .desktop files instead of gconf now, if that's what you mean
[20:16] <Ampelbein> mterry: no, dobey has the answer I wanted ;-) thanks.
[20:17] <dobey> Ampelbein: x-scheme-handler/ mime types are looked at for what can handle different URI types
[20:17] <Ampelbein> dobey: so, bug 726504 should have been filed against the chrome-package (the "default browser")
[20:17] <Ampelbein> dobey: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/726504
[20:18] <dobey> yeah probably
[20:18] <dobey> although there's no chrome package in ubuntu afaik
[20:18] <Ampelbein> or in this special case invalid since chrome isn't in ubuntu (chromium is)
[20:18] <Ampelbein> yeah, that's what I was thinking.
[20:19] <dobey> i think chromium is fixed already
[20:19] <dobey> and google will have to fix chrome's .desktop file upstream
[20:22] <Ampelbein> just out of curiosity, if I have firefox and chromium installed, both will register http URIs for themselves, I can change the default via the preferred applications app.
[20:22] <Ampelbein> but where does that get saved? sorry if that sounds noobish.
[20:23] <desrt> does anyone know if it's possible to have a sekret PPA?
[20:23] <desrt> more to the point: can we get access to them for free?
[20:24] <desrt> mterry: hey
[20:24] <desrt> mterry: thanks for your part in the gnome3 ppa.  i'm running it now.  saves me from all the troubles associated with jhbuilding.
[20:25] <mterry> desrt, yw, my part was small compared to others, but glad it's working.  I've been meaning to look at it again recently and update some bits (like glade).  Is the PPA reasonably up to date?
[20:26] <desrt> it seems to be bug-compatible with the version i installed via jhbuild from a few days ago :)
[20:28] <GunnarHj> seb128: Hi Sebastien, do you possibly have time to help with a couple of uploads to lucid-backports and maverick-backports? It's bug 719815, and both pitti and ScottK have cleared the branches for backports.
[20:28] <mterry> desrt, :)
[20:29] <desrt> mterry: in particular, the window frame theme seems to be missing...
[20:29] <desrt> ditto the gtk theme
[20:29] <seb128> GunnarHj, hi, not really it's over end of the week there, you should try on monday rather on a friday evening
[20:30] <desrt> mterry: i might believe that this is an ubuntu-specific issue (but i've seen it both with jhbuild and with the PPA)
[20:30] <seb128> rather "than" on
[20:31] <mterry> desrt, hrm.  I'm not terribly familiar with gtk3 theming.  Maybe we're just missing an updated package after gtk3's theme support got finalized?
[20:31] <GunnarHj> seb128: Ok, won't steal your holiday. ;-) No hurry, really.
[20:31] <desrt> mterry: i'm also not familiar and i haven't had time to look into it
[20:31] <desrt> have you noticed the problem on your machine, or are you not running shell?
[20:31] <mterry> desrt, I'm not running the PPA, no
[20:32] <mterry> desrt, unless I'm updating it
[20:32] <seb128> GunnarHj, it's not holidays, it's just an end of week evening and no worry it's just that I'm tired enough that I don't want to start on new things and backports are moderated anyway and people doing moderation are probably over their work time for the week as week so better to wait next week rather
[20:34] <GunnarHj> seb128: s/holiday/weekend/  No problem; have a nice _weekend_. :)
[20:34] <seb128> GunnarHj, thanks, have a nice one as well!
[22:07] <rickspencer3> kenvandine, so you released my delicate and comprehensive bug fix for Pithos!
[22:07] <rickspencer3> sweet
[22:07] <rickspencer3> I am so da man
[22:07] <rickspencer3> !
[22:08] <kenvandine> rickspencer3,  you are!
[22:08] <kenvandine> i got really tired of that :)
[22:09] <rickspencer3> lol
[22:09] <rickspencer3> my knowledge of PyGtk is getting scary comprehensive
[22:09] <rickspencer3> too bad it's so generally inapplicable ;)
[22:10] <rickspencer3> kenvandine, can you add sound menu support to Pithos
[22:10] <rickspencer3> ?
[22:11] <nperry> Evening people.. trying to test gnome3 in natty, however getting this error, any ideas? GLib-GIO-ERROR **: Settings schema 'org.gnome.desktop.interface' does not contain a key named 'automatic-mnemonics'
[22:12] <bcurtiswx> you mean every 3rd song it didn't want to go to the next one?
[23:26] <Ampelbein> kenvandine: re your upload of pithos, you versioned it -2ubuntu1, yet debian is at -1 revision?
[23:27] <Ampelbein> kenvandine: and the debian maintainer just asked in #ubuntu-motu what can be done about it
[23:29]  * lfaraone waves at kenvandine 
[23:30] <Ampelbein> lfaraone: I think he's afk