[00:02] <seb128> robert_ancell, btw I did add small changes to version to let specify a different regexp or url for some sources
[00:02] <robert_ancell> seb128, sweet
[00:02] <seb128> robert_ancell, and I did add a lucid table
[00:02] <seb128> so we can clean a bit the list
[00:02] <robert_ancell> seb128, where is the offical url now?  I notice pittis one no longer works
[00:03] <seb128> cf topic? :-)
[00:03] <robert_ancell> ha!
[00:04] <seb128> hehe
[00:04] <seb128> anyway enough work for today
[00:04] <seb128> good night everybody!
[00:05] <robert_ancell> night!
[00:51] <chrisccoulson> vish - i understand what is going on with this gpm blanking issue now
[01:22] <bryceh> hey, from python how do you detect if a program is available in the path (i.e. equivalent of `which dkms`)
[01:27] <james_w> bryceh: I believe there is no standard library function
[01:28] <bryceh> ok, I'll just check for path existence
[01:28] <james_w> bryceh: you can subprocess.Popen it and catch OSError and check for errno.ENOENT, which is likely to be that the command isn't available
[01:29] <bryceh> I think checking existence of /var/lib/dkms is probably cleaner
[01:38] <chrisccoulson> vish - i fixed the blanking bug :)
[03:43] <kklimonda> chrisccoulson, I can confirm 515155
[03:43] <kklimonda> bug 515155
[03:44] <chrisccoulson> kklimonda, thanks
[03:45] <kklimonda> chrisccoulson, do you want stacktrace?
[03:45] <kklimonda> it doesn't crash but I've connected to the process itself
[03:45] <chrisccoulson> i'm not going to look at that tonight though. i've spent all evening debugging a gpm race and i'm going to bed now :)
[03:45] <kklimonda> sure
[03:45] <chrisccoulson> yeah, a backtrace would be useful
[03:45] <chrisccoulson> i suspect that it's not really a gnome-screensaver issue
[03:46] <chrisccoulson> anyway, i can look at that tomorrow sometime
[03:46] <kklimonda> if so I'll have to install more debug symbols :)
[03:47] <chrisccoulson> heh ;)
[03:47] <chrisccoulson> anyway, me -> sleep
[03:47] <chrisccoulson> 'night!
[03:47] <kklimonda> good night
[06:40] <pitti> Good morning
[06:50] <pitti> didrocks: bonjour
[07:13] <kenvandine_> good morning pitti
[07:13] <pitti> http://people.canonical.com/~pitti/bootcharts/daniel-lucid-20100212-1.png
[07:14] <kenvandine> pitti,  nice!
[07:18]  * kenvandine just uploaded (to my gnomex ppa) the first pass at merging the f-spot patch adding editing to view mode 
[07:24] <kwwii> pitti: morning! one question: if I want to update the humanity-icon-theme which package should I start from? In the meantime it is quite unclear to me what is in lucid and where that is in LP
[07:25] <pitti> kenvandine: ooh!
[07:25] <pitti> kenvandine: as a backport, or trunk snapshot?
[07:25] <kenvandine> backport
[07:25] <kwwii> pitti: morning! one question: if I want to update the humanity-icon-theme which package should I start from? In the meantime it is quite unclear to me what is in lucid and where that is in LP
[07:26] <pitti> kwwii: Vcs-Bzr: says lp:~ubuntu-art-pkg/humanity/release
[07:26] <pitti> kwwii: that ought to be the authoritative place
[07:26] <kenvandine> there are a couple of crashers, but shouldn't be hard to work out
[07:26] <kenvandine> and we should make edit mode more discoverable
[07:26] <kenvandine> details :)
[07:26] <pitti> kwwii: lucid has 0.4.1ubuntu5, which is in that bzr as well, so it seems fine
[07:27] <pitti> even better: http://people.canonical.com/~pitti/bootcharts/daniel-lucid-20100212-1-no-rsyslog-dd.png
[07:27] <kwwii> pitti: ok, cool...things are better than I thought. upstream as two repo's for it and someone has a ppa with new packages
[07:27] <pitti> (dropping rsyslog's dd process, which is on the plan for lucid)
[07:27] <kenvandine> pitti, that is pretty damn impressive
[07:27] <kwwii> pitti: thanks for the info, I'll merge things, review them and then get a package ready for upload
[07:28] <pitti> kenvandine: 11.5 s is quite good already \o/
[07:28] <pitti> kenvandine: and we have didrocks' bg caching in the pipe still
[07:29]  * kenvandine drools
[07:30]  * kenvandine should go get a little sleep before the little ones wake me :)
[07:30] <kenvandine> good night folks!
[07:31] <pitti> kenvandine: sleep well!
[07:31] <pitti> kwwii: thanks
[07:35] <pitti> I need to run out for ~ 2 hours
[07:50] <ericjames> I'm having a bit of trouble registering acpi events.
[07:51] <ericjames> I've created an event file, and an action script. the acpi events are reported from acpi_listen, however, the script doesn't execute when the event occurs
[07:51] <ericjames> when I attempt to start, stop, or debug acpid i get the message: acpid: can't open /proc/acpi/event: Device or resource busy
[08:13] <didrocks> good morning pitti
[08:14] <didrocks> pitti: I think I need some sponsoring for gnome-desktop, just grab the branch and it should be ok :)
[08:15] <huats> morning
[08:24] <didrocks> hey huats
[08:25] <huats> hello didrocks
[08:25] <huats> don't try to talk to me here :)
[08:25] <didrocks> :p
[09:06] <chrisccoulson> good morning everyone
[09:07] <didrocks> hey chrisccoulson, ready for your week-end? ;)
[09:07] <chrisccoulson> hey didrocks, yeah, i'm definately ready for the weekend. it was quite a late night again last night
[09:07] <chrisccoulson> are you ready for the weekend?
[09:09] <didrocks> chrisccoulson: tons of stuff to finish first, but yeah, it'll be again a FLOSS week-end :)
[09:10] <chrisccoulson> ooh, bbiab - breakfast has arrived :)
[09:11] <didrocks> enjoy ;)
[09:12] <baptistemm> heya
[09:14] <didrocks> salut baptistemm
[09:15] <baptistemm> salut didrocks
[09:29] <chrisccoulson> well, i could sleep after that :)
[09:34] <didrocks> heh
[09:34] <didrocks> ;)
[09:34] <didrocks> short Friday, isn't?
[09:35] <didrocks> wake up, go to work, breakfast and sleep :)
[09:35] <chrisccoulson> kklimonda: your gnome-screensaver backtrace misses quite a few symbols. also, was that the only thread running? (i expected to see the PAM stuff in another thread there)
[09:35] <chrisccoulson> didrocks - yeah, short friday :)
[09:35] <chrisccoulson> then home to do some hacking ;)
[09:36] <chrisccoulson> i think i'm going to go the whole day without looking at anything gpm related today
[09:36] <didrocks> some kind of "gpm day" :)
[09:36] <didrocks> or gpm-free day
[09:36] <didrocks> rather :)
[09:37] <chrisccoulson> gpm-free day today ;)
[09:37] <didrocks> heh
[09:37] <chrisccoulson> after spending all last night investigating an issue with blanking
[09:38] <didrocks> asac: so, netbook-launcher-efl works well with netbook-launcher installed. Some packaging tweaks to remove the conflicts/replaces against netbook-launcher (not sure why there is a replaces btw as there is no common file) and so, creating a wrapper. That should be doable
[09:40] <chrisccoulson> hey seb128
[09:40] <seb128> hey chrisccoulson
[09:40] <chrisccoulson> how are you today?
[09:40] <seb128> good!
[09:40] <seb128> I overslept again ;-)
[09:40] <didrocks> salut seb128, on se couche toujours aussi tardivement ? :)
[09:40] <seb128> you?
[09:40] <chrisccoulson> seb128 - i overslept today too ;)
[09:40] <seb128> didrocks, lut, ouais, mais on dors le matin pour compenser!
[09:41] <chrisccoulson> i had quite a late one again last night
[09:41] <didrocks> seb128: héhé. Ça t'a permi d'uploader seahorse-plugins vu qu'il a poussé sa branche à 22h30 :)
[09:41] <seb128> didrocks, oui
[09:42] <seb128> chrisccoulson, so you didn't manage to get your early night again? ;-)
[09:43] <geser> gir1.0-webkit-1.0 is currently build from two packages (webkit and gir-repository) which makes currently the build of gir-repository "Fail to Upload". Does somebody know which of those two packages should build it?
[09:44] <seb128> geser, ignore that, I've it on my list
[09:44] <geser> ok
[09:44] <seb128> geser, there is no difference between current gir and the new one
[09:44] <seb128> so we don't really need it
[09:44] <seb128> debian will drop webkit from gir in the next upload
[09:44] <seb128> I pinged one of the debian guys about it some days ago
[09:45] <seb128> so next upload will work
[09:49] <chrisccoulson> seb128 - no, i didn't manage an early night this time. i've had 1 early night this week, so that's ok ;)
[09:53] <pitti> re
[09:54] <pitti> didrocks: yep, will do
[09:54] <didrocks> pitti: thanks a lot ;)
[09:55] <seb128> hey pitti
[09:56] <pitti> seb128: bonjour!
[09:56] <pitti> seb128: not sure whether you saw the chart from this morning: http://people.canonical.com/~pitti/bootcharts/daniel-lucid-20100212-1-no-rsyslog-dd.png
[09:57] <seb128> pitti, no
[09:57] <pitti> this is with the rsyslog/dd thing fixed locally
[09:57] <seb128> pitti, I'm doing indicator-sound sponsoring
[09:57] <seb128> waouh, 11.5 seconds?
[09:58] <pitti> seb128: :)
[09:58] <pitti> seb128: i-s> merci
[09:58]  * pitti tries some more shuffling
[09:59] <seb128> the bar seems misleading
[09:59] <seb128> actual end of cpu use is around 13s
[09:59] <seb128> you don't have g-s-d background tweaked there right?
[10:00] <pitti> seb128: no, not yet; I just sponsored that
[10:00] <pitti> will do another chart once that's built
[10:00] <pitti> seb128: yeah, seems to do some lazy init later on
[10:01] <pitti> but that's pretty much what we do with gnome-screensaver, e-d-s, and the like
[10:01] <chrisccoulson> hey pitti
[10:02] <pitti> hey chrisccoulson, how are you?
[10:02] <chrisccoulson> i'm good thanks, how are you?
[10:03] <pitti> I'm good, thanks!
[10:08] <seb128> pitti, I will need you soon ;-)
[10:08] <seb128> pitti, to NEW review indicator-sound
[10:09] <pitti> chrisccoulson: is it still on your plan to speed up the xrandr plugin? or want me to look into that?
[10:09] <pitti> seb128: standing by
[10:09] <seb128> pitti, if you want to clean a wi too both didrocks and kenvandine have a gwibber mir listed
[10:09] <chrisccoulson> pitti - i can still look at that to see if there is anything we can do
[10:09] <seb128> pitti, one can go
[10:11] <pitti> seb128: hm, I see it on https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-lucid-une-applications, but none on https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-lucid-social-from-the-start
[10:11] <pitti> seb128: or anywhere at http://people.canonical.com/~pitti/workitems/canonical-desktop-team-lucid-alpha-3.html#ken-vandine ?
[10:11] <seb128> pitti, ok, I pinged kenvandine about that yesterday he must have cleaned it already
[10:12] <seb128> I'm not subscribed to this spec
[10:12] <seb128> so I didn't get the diff to tell
[10:12] <pitti> ah, good
[10:12] <pitti> I remember that diff flying by
[10:14]  * pitti hmmms at http://people.canonical.com/~pitti/bootcharts/daniel-lucid-20100212-1-mutter-phase-init.png
[10:14] <pitti> that could be something to consider (start mutter early on)
[10:15] <pitti> this is now _real_ 11.8 s (no lazy init)
[10:15] <pitti> and the CPU block looks almost perfect
[10:15] <pitti> no pause in between any more
[10:16] <pitti> it's funny how sensitive all of this is
[10:17] <pitti> http://people.canonical.com/~pitti/bootcharts/daniel-lucid-20100212-1-mutter-phase-wm.png is the "middle ground" between "application" and "init" phase, and it's much worse
[10:17] <seb128> what did you change?
[10:17] <pitti> seb128: move mutter to autostart-phase=init
[10:17] <pitti> so that it starts with g-s-d
[10:17] <seb128> ah right
[10:17] <pitti> I don't think it's using a theme or so
[10:20] <didrocks> pitti: there is still some "not 100% busy cycle" around gdm start time, weird
[10:20] <pitti> that's a needle eye indeed
[10:21] <pitti> one CPU is fully busy, the other is free
[10:21] <pitti> so there's a theoretical saving of .5 s there
[10:21] <didrocks> hum, sounds great if we can launch something in between :)
[10:22] <pitti> it's the I/O block of X.org and Xsession.d/
[10:22] <didrocks> pitti: how do you see that? (and also that only one CPU is fully busy), on the bootchart?
[10:22] <pitti> but I think we should deal with that once the kernel fix lands, and the loadkeys.sh block goes away
[10:23] <pitti> because I bet it'll look differently again then :)
[10:23] <pitti> didrocks: it has two CPUs, thus if the CPU chart is at 50%, it means that one CPU is idle
[10:23] <pitti> gnome-desktop is built, installed locally
[10:23]  * pitti bootcharts
[10:24] <pitti> didrocks: I just put a ruler on the point when it drops CPU usage, follow downwards, and see what happens at that time
[10:24] <didrocks> pitti: ok, just from assumptions so, not from something strictely written in the bootchart :)
[10:24] <didrocks> ok
[10:25] <pitti> didrocks: well, it does enumerate the CPUs in the headers
[10:25] <pitti> ~/.cache/wallpaper/stretched_1024_600__usr_share_backgrounds_warty-final-ubuntu.png
[10:25] <pitti> \o/
[10:25]  * pitti hugs didrocks
[10:25]  * didrocks hugs pitti back ;)
[10:27] <seb128> pitti, should we use a -1 or -0ubuntu1 for dx indicator uploads?
[10:28] <pitti> seb128: I don't mind so much, but I'm slightly biased towards -0ubuntu1
[10:28] <pitti> just for consistency
[10:28]  * seb128 is annoyed at debuild complaining about ubuntu revision but no ubuntu maintainer
[10:28] <seb128> which doesn't let me build it
[10:28] <seb128> I can tweak DEBEMAIL to build but still annoying
[10:28] <pitti> DEBEMAIL= bzr bd -S ?
[10:29] <seb128> right, what I just said
[10:29] <pitti> but oh well, why not set it to ubuntu-desktop@ or u-d-discuss@
[10:29] <seb128> we should not have to pay for being upstream
[10:29] <pitti> seb128: but it just checks for any @ubuntu.com address
[10:29] <seb128> *shrug*
[10:29] <pitti> what is in the Maintainer: field right now?
[10:29] <seb128> the email is a canonical one
[10:29] <pitti> ah
[10:29] <seb128> Maintainer: Conor Curran <conor.curran@canonical.com>
[10:31] <didrocks> I saw some packages using the Original Maintainer when we are upstream and ubuntu-desktop@ as maintainer (a bit weird, but well…)
[10:32] <seb128> yeah, I did tha
[10:32] <seb128> yeah, I did that
[10:32] <pitti> didrocks: http://people.canonical.com/~pitti/bootcharts/daniel-lucid-20100212-2-mutter-phase-init.png
[10:32] <pitti> that's with your caching patch
[10:33] <pitti> it's not faster in total, but we have some free CPU cycles left
[10:33] <pitti> so I'll shuffle the bits some more to get a compact chart again
[10:33] <didrocks> pitti: right, I'm a bit disappointed that the time is not used for anything else :)
[10:33] <didrocks> pitti: moving some bits to start earlier?
[10:33] <pitti> or later, I don't know
[10:34] <didrocks> pitti: you have the collector running, isn't it?
[10:35] <pitti> oh, hang on, this was the wrong one
[10:35] <pitti> it started mutter in phase=windowmanager, which is bad
[10:35] <pitti> didrocks: it's always running apparently
[10:35] <pitti> that's ureadahead
[10:35] <didrocks> but ureadahead isn't showed in the graph?
[10:35] <seb128> pitti, what do we need to do to be able to push to lp:ubuntu/source?
[10:35] <didrocks> oh sorry, seeing it now :)
[10:35] <seb128> pitti, we need to upload the source first right?
[10:36] <pitti> seb128: the package must be in any PPA, or in NEW
[10:36] <pitti> seb128: right, get it into NEW, push it to ~ubuntu-desktop/ubuntu/lucid/pkgname/lucid, and afterwards ping james_w to set that as the official branch
[10:36] <pitti> it's currently a bit complicated for new packages
[10:37] <seb128> pitti, why not just ~ubuntu-desktop/ubuntu/source?
[10:37] <pitti> if that works
[10:37] <pitti> I thought you had to specify the full 5-component path
[10:38] <seb128> we are there yet for the easy to use ;-)
[10:38] <seb128> james_w, help, I'm being confused :p
[10:40] <seb128> pitti, indicator-sound your way btw (just uploaded should hit NEW)
[10:47] <davmor2> pitti: came across a weird issue last night.  I did an upgrade from karmic to lucid and somehow it removed my broadcom sta driver, problem is I can't get it back on.  Jockey log say /sys/module/wl/drivers does not exist, cannot rebind wl driver
[10:47] <pitti> davmor2: could it be bug 506816 ?
[10:48]  * davmor2 reads
[10:50] <davmor2> pitti: yeap
[10:52] <davmor2> pitti: any more info you need for it?
[10:52] <pitti> I don't think so, it's pretty well triaged now, and easy to reproduce
[10:53] <davmor2> okay cool
[10:53] <pitti> Qapla!
[10:53] <pitti> seb128, didrocks: http://people.canonical.com/~pitti/bootcharts/daniel-lucid-20100212-2-mutter-phase-init_maximus-phase-app.png
[10:53] <pitti> purrrrfect
[10:54] <seb128> what did you shuffle?
[10:54] <pitti> mutter -> phase init, maximus -> phase app (instead of wm)
[10:54] <chrisccoulson> niiiiiiiiiiiccccceeeeee!
[10:54] <pitti> so that maximus can spread out into the empty CPU ranges instead of blocking startup
[10:54] <chrisccoulson> 11 seconds isn't long enough to go and make a coffee though ;)
[10:54] <seb128> cool
[10:54] <seb128> hehe
[10:54]  * pitti ^5s seb128, didrocks, and chrisccoulson
[10:54] <didrocks> sweet ;)
[10:55] <pitti> and Keybuk, too!
[10:55] <pitti> I'll reboot two or three times to see how it reproduces
[10:55] <seb128> I've a friend who told me that the computer work he's using under win takes 7 minutes to start and finish activity
[10:55]  * seb128 hugs pitti
[10:55] <pitti> minutes??
[10:55] <seb128> yeah
[10:55] <pitti> that's with a million virus scanners surely?
[10:55] <chrisccoulson> seb128 - i've found that too with most company PC's
[10:55] <chrisccoulson> they put all sorts of rubbish on
[10:56] <chrisccoulson> hence the comment about not being long enough to go and make a coffee ;)
[10:56] <didrocks> seb128: it was 4 at my previous work. Time to go to bathroom, say hello to co-worker ;)
[10:56] <seb128> pitti, likely yes
[10:56] <chrisccoulson> wow, in 2 weeks time i'll not have to use a windows machine again
[10:56] <Keybuk> pitti: I got 10.2s over the weekend with some fiddling
[10:57] <seb128> chrisccoulson, feels good ;-)
[10:57] <Keybuk> as soon as I can get reliably dailies, I'm going to retest and if it still works, upload :D
[10:57] <didrocks> chrisccoulson: you'll see, it's very good. I'm addicted now ;)
[10:57] <chrisccoulson> seb128 - oh yes ;)
[10:57] <seb128> Keybuk, plumber fiddling or desktop?
[10:57] <Keybuk> (removes almost a second from the kernel-X bit)
[10:57] <Keybuk> seb128: plumbing fiddling
[10:57] <seb128> cool
[10:57] <pitti> Keybuk: rock, and that's not even with the recent bg caching and the autostart shuffling
[10:57] <Keybuk> indeed
[10:57] <seb128> so with the background cache + pitti tweaks we are on target
[10:57] <didrocks> \o/
[10:58] <seb128> Keybuk, btw what is happening with gdm to desktop?
[10:58] <Keybuk> you know, as soon as we hit 10s, I'm going to send an e-mail telling everyone to stop what they're doing, the release is DONE! :p
[10:58] <seb128> will we get plymouth covering background during loading or something?
[10:58] <Keybuk> seb128: not sure what you mean?
[10:58] <Keybuk> yeah we should
[10:58] <seb128> right now you can see the gnome-panel being drawned etc
[10:58] <Keybuk> there's some plymouth vt bugs with fixes pending
[10:58] <Keybuk> oh, that's DX's stuff
[10:58] <Keybuk> you'd have to ask Cody
[10:59]  * Keybuk will biab - got a hair cut
[10:59] <pitti> meh, between two identical boots there's so much noise these days
[10:59] <chrisccoulson> i really should get a bootchart from my laptop
[10:59] <seb128> ("being drawn")
[10:59] <chrisccoulson> it definately isn't 11 seconds though ;)
[10:59] <seb128> Keybuk, ok thanks
[11:00] <seb128> chrisccoulson, ssd?
[11:00] <chrisccoulson> seb128 - no, it's not ssd unfortunately
[11:00] <chrisccoulson> i might get a mini though
[11:00] <pitti> Keybuk: your daily charts are still killed by the broken ubiquity automation, I figure?
[11:01] <pitti> darn, the next boot takes 11.42 instead of 11.15
[11:01] <pitti> but either way, we've come a loong ay
[11:01] <pitti> way, even
[11:01] <seb128> yeah
[11:02] <pitti> but as long as we get one solid CPU block without pauses, we're good
[11:02] <pitti> didrocks: oh, we still need the ubiquity hook for the bg cache, right?
[11:02] <didrocks> pitti: right, ubiquity and update-manager one
[11:02] <didrocks> pitti: that's why I didn't close the WI :)
[11:03] <pitti> didrocks: it won't be in u-m, but in the gnome-desktop postinst, I figure
[11:03] <pitti> we need a 5-line mini C program to refresh the background and trigger the caching, right?
[11:03] <didrocks> exactly
[11:03] <pitti> didrocks: I'll do those WIs explicitly
[11:04] <didrocks> pitti: ok. I'll complete them on Monday morning (I want to finish triaging and selecting bugs for UNE today)
[11:05] <pitti> didrocks: done
[11:05] <james_w> seb128, pitti: yeah, it has to be the full 5-part path for the first push: lp:~ubuntu-desktop/ubuntu/lucid/package/lucid
[11:05] <pitti> didrocks: that's fine, it's not so urgent
[11:05] <didrocks> pitti: thanks :)
[11:05] <seb128> james_w, why?
[11:05] <seb128> james_w, I used ~ubuntu-desktop/source/ubuntu that doesn't work?
[11:05] <james_w> seb128: that's what LP requires
[11:06] <seb128> bah, sucker
[11:06] <james_w> seb128: that does work
[11:06] <seb128> (not you)
[11:06] <seb128> james_w, thanks ;-)
[11:06] <james_w> that's just not what you said earlier :-)
[11:06] <seb128> james_w, can you get ~ubuntu-desktop/indicator-sound/ubuntu
[11:06] <seb128> to be lp:ubuntu/indicator-sound?
[11:06] <james_w> yes
[11:06] <seb128> thanks
[11:06] <seb128> james_w, ups, did I switch ubuntu and source again in the url?
[11:07] <seb128> I tend to do that often ;-)
[11:07] <james_w> yeah :-)
[11:08] <didrocks> james_w: hey o/ btw, does the new plugin version/bzr are now available into lucid for merge-upstream command?
[11:08] <seb128> james_w, sorry about that and thanks for looking into it ;-)
[11:08] <didrocks> james_w: (btw, I've converted two new branches to that workflow and it really rocks :-))
[11:08] <pitti> didrocks: btw, I'm using lp:ubuntu/maxiums now (it doesn't have a Vcs-Bzr, and I didn't find a packaging branch)
[11:09] <didrocks> pitti: I've done that too IIRC, maybe the changes have been removed as it was in the time I encountered that issue
[11:09] <james_w> seb128: done
[11:10] <james_w> didrocks: nice
[11:10] <james_w> didrocks: no, I haven't done an upload yet
[11:10] <seb128> james_w, thanks!
[11:10] <didrocks> james_w: ok thanks, I keep doing from the local checkout so ;)
[11:11]  * seb128 gently nudge pitti about NEW
[11:11] <seb128> pitti, I would like to get that new indicator landing before weekend if possible ;-)
[11:11] <didrocks> james_w: oh, the only annoying issue is that for the first merge, I have always to bzr revert debian/
[11:11] <seb128> in case things break so somebody is still around working to fix it
[11:11] <james_w> didrocks: because all the dx branches use to have packaging in them?
[11:12] <pitti> seb128: doing, sorry
[11:12] <didrocks> james_w: I was thinking that too, but I'm sure not the last one
[11:13] <james_w> didrocks: if you find a case where they didn't then please file a bug
[11:13] <seb128> pitti, np, thanks
[11:13] <didrocks> james_w: ok, will do :)
[11:20] <pitti> seb128: looks good except the wrong license in debian/copyright; can you please reupload with dropping the "or any later version"?
[11:20] <seb128> pitti, ok
[11:21] <seb128> sorry I overlooked that one
[11:24] <seb128> pitti, done, bzr updated and source reuploaded
[11:29] <pitti> seb128: wrt. the bzr branch, I still don't know how to get pristine-tar manually
[11:29] <pitti> the auto-imports have those
[11:29] <pitti> seb128, kenvandine: so indicator-sound will replace gnome-volume-control in lucid already?
[11:29] <pitti> (source NEWed into main, FTR)
[11:30] <seb128> pitti, yes, when you NEW the indicator I will comment gnome-media
[11:30] <seb128> pitti, ok thanks
[11:30] <seb128> doing the gnome-media autostart change now
[11:32] <pitti> gnome-volume-control uses a fair chunk of CPU; let's see how i-s will behave
[11:32] <seb128> yeah
[11:32] <seb128> I'm out of benchmarks land for now
[11:32] <seb128> I don't want to reboot my work box all the time
[11:33] <seb128> and cpu there is fast anyway so it doesn't behave the same way
[11:35] <seb128> lunch time, bbl
[11:36] <pitti> seb128: I'll benchmark it, don't worry
[11:36] <pitti> enjoy lunch!
[11:43] <pitti> seb128: binary-NEWed, too
[11:46] <tjaalton> fun, bug 330766 haunts me, but on NFSv4
[11:46] <tjaalton> doesn't hang, but fails to start
[11:48] <tjaalton> ok, saw why
[11:50] <asac> didrocks: coool. thanks
[11:51] <asac> didrocks: do you need anything from us?
[11:51] <asac> or will you just try to do the fallback?
[11:52]  * asac wonder if we have enough space for both launcher on UNE image
[11:57] <didrocks> asac: I didn't look at the space. It brings a lot of depends
[11:59] <didrocks> asac: I think it's ok, I'll change the packaging for netbook-launcher-elf and try to run the fallback in that case
[12:06] <asac> didrocks: rock.
[12:07] <asac> didrocks: even if general UNE doesnt ship it that way we probably want to do that in our armel images
[12:08] <didrocks> asac: I think ship it directly will depend on size/speed of startup of the wrapper
[12:08] <cassidy> kenvandine, seb128: your libindicate patch introduced *another* weird crash which has been reported upstream and waste my time again...  see https://bugzilla.gnome.org/show_bug.cgi?id=609417#c9
[12:08] <didrocks> asac: but as you can now install UNE in a general desktop, that can be interested
[12:08] <asac> RIGHT
[12:08] <seb128> cassidy, the tone is not really required or useful there
[12:08] <asac> oops
[12:08]  * asac fights with his keyboard being kind of broken
[12:08] <cassidy> seb128, I'm a bit tired of those tbh
[12:09] <seb128> cassidy, what do you suggest doing?
[12:09] <cassidy> especially as the patch here is obviously wrong
[12:09] <cassidy> be more careful before pushing patches?
[12:09] <seb128> you really think people add bugs for the fun?
[12:11] <cassidy> I don't. But it's pretty frustrating for me to see that's the same patch adding bugs again and again
[12:12] <seb128> what about getting the change upstream so it's maintained properly there?
[12:13] <seb128> what about getting the change upstream so it's maintained properly there?
[12:13] <seb128> ups
[12:13] <seb128> cassidy, is there anything which was blocking that?
[12:13] <seb128> I've not been following reviews and issues
[12:13] <seb128> but I'm happy to help getting it in shape if work is still needed
[12:14] <cassidy> the plan was to re-implement the libindicate integration by using the proper Telepathy API; but this has been delayed to lucid+1
[12:14] <seb128> what can we do meanwhile to make things better?
[12:14] <cassidy> (partially because Empathy doesn't implement approvers either, so that's our fault too)
[12:15] <seb128> I can understand it's annoying sometime for you
[12:15] <cassidy> as said, be more careful before pushing your patches. This hunk is obviously wrong, a simple review of the patch would have spot the issue
[12:15] <seb128> on an another side it's not trivial to jungle with hundred of component for which you don't know the codebase well as a distributor either
[12:16] <seb128> especially when you are under pressure to get a stack ported in a day for a transition
[12:16] <seb128> (which is what happened for this one)
[12:16] <cassidy> :\
[12:16] <seb128> cassidy, I will have to look to the code but the libindicator api added timestamp now
[12:17] <seb128> cassidy, and I guess the same callback is used for both codepath
[12:17] <cassidy> yeah but this is a GTK+ signal, not a libindicate one
[12:17] <seb128> cassidy, and ken probably looked only at the indicator case
[12:17] <seb128> cassidy, thanks for pointing it and we will try to do better, we have been talking about code review
[12:18] <cassidy> yeah he changed both cb
[12:18] <seb128> cassidy, we had lucid broken due to the libindicator abi change though and had been in a hurry to fix things before travelling back from a sprint
[12:18] <seb128> cassidy, note that I know it's not a justification, sorry about that, I will get it fixed today
[12:19] <cassidy> thanks
[12:19] <seb128> hate bzr some days
[12:20] <seb128> why does it say that things have diverged when I try to bzr pull on a checkout which I didn't touch
[12:20] <cassidy> so do I :)
[12:20] <seb128> cassidy, it's nothing compared to how much I dislike git though ;-)
[12:20] <didrocks> seb128: someone used maybe --overwrite?
[12:20] <seb128> at least pushing to a sftp is one command with bzr
[12:21] <seb128> didrocks, I doubt it
[12:21] <seb128> didrocks, I doubt somebody overwrote my revisions on the ubuntu-desktop copy
[12:21] <seb128> I don't see a reason to do that
[12:21] <didrocks> seb128: still the same last revision?
[12:22] <seb128> no, I'm trying to pull new revisions
[12:22] <didrocks> hum, strange, if your revision have been untouched… right
[12:25] <seb128> in fact there was a revision missing
[12:25] <seb128> I'm wondering what did kenvandine did
[12:25] <seb128> and if he did overwrite my revision
[12:26] <seb128> he did pulled in my change though
[12:26] <seb128> but it doesn't appear has a commit on the online version
[12:28] <didrocks> seb128: should be that. I'm constantly playing with bzr (pushing to my server, getting from netbook -> laptop, server -> netbook) and so on. Never encountered such issue except from using --overwrite removing a revision of course
[12:28] <seb128> can we see if that has been done somewhere?
[12:29] <didrocks> from the little knowledge I had reading the doc, --overwrite really rewrite the .bzr file from your source and remove the commit as they never existed. I don't know how it's handled with stacked branch
[12:58] <seb128> lool, \o/
[12:59] <seb128> lool, thanks for fixing valgrind, I had that on my list of things to look at but didn't manage to come to it yet
[13:07] <seb128> pitti, bug #494561
[13:08] <seb128> pitti, the build issue has been fixed now, anything else was blocking it?
[13:08] <kenvandine> cassidy, damn... sorry about that
[13:08] <kenvandine> hummm
[13:08] <pitti> seb128: ah, looks fine now, hang on
[13:09] <pitti> seb128: approved
[13:09] <seb128> pitti, thanks
[13:09] <kenvandine> seb128, which package lots your changelog?
[13:10] <seb128> kenvandine, empathy
[13:10] <kenvandine> i didn't use --overwrite
[13:10] <seb128> kenvandine, it didn't lost my changelog but my r85 which was fixing a new line issue in the indicator patch
[13:10] <kenvandine> no idea what could have happened
[13:10] <seb128> kenvandine, I might have forgotten to push
[13:10] <seb128> and did the same change to fix the build when you worked on it
[13:10] <kenvandine> ah... was it the one in the glade file?
[13:10] <seb128> yes
[13:11] <kenvandine> ok, i fixed it too
[13:11] <kenvandine> i wondered how you got it to build :)
[13:11] <seb128> it was just a stupid editor error
[13:11] <seb128> well, I fixed, commited and probably didn't push
[13:11] <seb128> sorry about that
[13:11] <kenvandine> ok
[13:11] <kenvandine> np
[13:11] <seb128> kenvandine, I'm fixing the crasher cassidy indicated btw
[13:11] <lool> seb128: eh np
[13:11] <kenvandine> cool
[13:11] <kenvandine> thx
[13:11] <seb128> was cleaning some bugs on the way
[13:11] <lool> seb128: I didn't actually test it, just that it builds with new libc
[13:11] <seb128> np
[13:11] <seb128> lool, ok, let's see if it makes it happy too
[13:12] <seb128> lool, right now valgrind ls lists thousand errors and exit
[13:12] <seb128> ls or any software
[13:12] <kenvandine> seb128, i got that f-spot patch backported
[13:12] <lool> upstream only committed a patch to configure WRT to glibc 2.11, so I'd be surprized if more is needed
[13:12] <kenvandine> it is a little crashy
[13:12] <kenvandine> and i want to change a few things about the behavior
[13:12] <kenvandine> but it kind of works :)
[13:12] <lool> seb128: Probably the suppression file not being set correctly
[13:12] <seb128> kenvandine, oh, nice
[13:12] <seb128> lool, yes, it seemed to be something like that
[13:12] <kenvandine> but i don't have any crashers that aren't in sde's branch :)
[13:13] <kenvandine> i'll try to get those worked out today
[13:13] <seb128> kenvandine, indicator-sound is in lucid btw
[13:13] <kenvandine> they all seem to be the editor no being happy it isn't in the library view
[13:13] <kenvandine> thx!
[13:13] <seb128> kenvandine, I made indicator-applet recommends it too
[13:13] <kenvandine> excellent
[13:13] <seb128> kenvandine, and stopped the gnome-media autostart
[13:14] <seb128> so we should be set
[13:14] <kenvandine> sweet!
[13:14] <seb128> works great there
[13:14] <kenvandine> did you get it pushed to lp:ubuntu/indicator-sound?
[13:14] <seb128> yes
[13:14] <kenvandine> thx
[13:14] <pitti> seb128: what will pull in indicator-sound?
[13:14] <kenvandine> indicator-applet
[13:14] <pitti> is that a dependency of something? or do we need to seed?
[13:14] <seb128> pitti, cf 5 lines up
[13:14] <pitti> ah, sorry
[13:14] <kenvandine> it's a recommends
[13:14] <pitti> nice timing, I'm just typing the weekly report for release meeting
[13:14] <seb128> ;-)
[13:14] <kenvandine> :)
[13:14] <kenvandine> seb128, it actually doesn't work for me... but it looks pretty :)
[13:15] <lool> pitti: In the FTBFS list which Lucas just posted, there's the latest version of apport
[13:15] <pitti> heh
[13:15] <kenvandine> i am experiencing the bug dbarth was talking about
[13:15] <lool> pitti: You might want to take a look if you have some time
[13:15] <pitti> lool: oh, I will (last version built fine on the buildds, hmm)
[13:15] <seb128> kenvandine, it works there, mutting and sound slider
[13:15] <lool> yeah I've seen that it built on the buildd, that puzzled me a bit
[13:15] <seb128> and preference entry
[13:15] <lool> I guess something related to icons or debhelper changed or something
[13:15] <kenvandine> for me muting and slider are disabled
[13:16] <seb128> pulseaudio is running?
[13:16] <kenvandine> yes
[13:16] <lool> http://people.ubuntuwire.org/~lucas/ubuntu-nbs/64/apport_1.12-0ubuntu5_llucid64.buildlog
[13:16] <seb128> ok, I guess a bug for ronoc then
[13:16] <kenvandine> yeah, well i think it has something to do with pulse's status when the service starts
[13:16] <kenvandine> we'll work it out :)
[13:16] <kenvandine> feature is in :-p
[13:16] <didrocks> asac: speaking about that, netbook-launcher-efl is FTBFS from lucas' list too, I know what the fix is and I'll upload it on Monday as well as removing C/R, moving .deskop file, and so on :)
[13:17] <lool> didrocks: I poked yesterday and JamieBennet is working on that one
[13:17] <lool> didrocks: You might want to check with him before working on it
[13:18] <lool> didrocks: What do you think the fix is BTW?
[13:18] <lool> I'm not sure that just changeing liblauncher-0.1 to 0.3 will allow it to build, it might need some porting
[13:18] <didrocks> lool: it's just changing liblauncher-dev by liblauncher-0.1-dev
[13:18] <lool> or we might need an old source package
[13:18] <lool> Oh we still have liblauncher-0.1-dev
[13:18] <lool> fine
[13:18] <didrocks> lool: there is a new source with 0.1 that was uploaded few days ago
[13:19] <lool> didrocks: That sounds fine indeed; didn't see we had a liblauncher-0.1 source already
[13:19] <didrocks> JamieBennett: ^ (but I can handle it, I have other changes to land on Monday)
[13:20] <lool> seb128: still loads of errors with new valgrind I'm afraid
[13:21] <seb128> :-(
[13:21] <asac> didrocks: cool.
[13:22] <asac> didrocks: does -efl really build with the new -dev?
[13:22] <asac> i doubt it does
[13:22] <didrocks> asac: no only, with 0.1, cf ^
[13:23] <asac> what does cf stand for?
[13:23] <asac> Cystic Fibrosis. CF
[13:23] <asac> ;)
[13:23] <lool> asac: aha valgrind tip has nice work on an arm port!
[13:23] <asac> cool
[13:23] <lool> asac: confere
[13:24] <lool> latin for "see also"
[13:24] <asac> oh
[13:25] <asac> nevermind ;)
[13:33] <lool> seb128: Upstream valgrind doesn't have the issue, I guess I should package a new snapshot
[13:34] <seb128> lool, $beers++ for you at next uds if you do that one ;-)
[13:36] <pitti> kenvandine: do you know the status of https://blueprints.edge.launchpad.net/ubuntu/+spec/lucid-ubuntu-one-client-app ?
[13:41] <kenvandine> pitti, they still say in time for feature freeze...
[13:41] <kenvandine> dobey, ^^
[13:41] <kenvandine> i harassed josh about it wednesday and he was going to get more detailed status for me
[13:42]  * kenvandine needs to run out for a few, bbiab
[13:42] <pitti> kenvandine: ok, thanks; I was just curious
[13:46] <pitti> lool, asac: did the nautilus change help in bug 512959? It looks like lool's upload intended to fix it, but it's still open, and there are no followups
[13:47] <lool> pitti: I uploaded a workaround which was confirmed as hiding the issue
[13:47] <lool> pitti: But I kept the bug open because it's apparently a toolchain issue
[13:47] <lool> (the workaround is dropping -Wl,-O1 from LDFLAGS)
[13:47] <pitti> right, the binutils task
[13:47] <lool> And the gvfs task is to revert the hack once that's fixed
[13:47] <pitti> lool: but I guess we can at least close the karmic task from gvfs then
[13:48] <pitti> (it's not alpha-3 critical any more)
[13:48] <lool> Ack
[13:48] <pitti> lool: merci
[13:48] <lool> pitti: (You're doing it or shall I?)
[13:49] <pitti> I'm doing it
[13:50] <lool> thanks
[13:51] <asac> do we need to kep the gvfs task open?
[13:52] <asac> e.g. if its binutils its covered
[13:52] <asac> but i dont mind in either way
[13:52] <seb128> asac, it's a reminder to drop the workaround
[13:55] <pitti> ^ right
[13:55] <pitti> but not as an RC task
[13:56] <seb128> not questioning that ;-)
[13:56] <seb128> a low importance triaged task should do
[13:57] <pitti> that's what I did
[14:02] <asac> sure that -O1 isnt a workaround in first place?
[14:02] <asac> in my book dropping a special flags reset stuff to "normal" ;)
[14:04] <seb128> asac, you mean we should use -O1 by default?
[14:05] <asac> oh ... nevermind. thought it was the other way around
[14:06] <asac> misremembered
[14:09] <Nafai> Good morning all
[14:09] <seb128> hey Nafa
[14:09] <seb128> hey Nafai
[14:14] <dobey> kenvandine, pitti: yes, feature freeze :)
[14:16] <lool> seb128: valgrind PDF manual (which is installed in the package) can't build due to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566591  I'm stuck on that one to update valgrind
[14:17] <seb128> lool, ok, thanks for trying and letting me know!
[14:29] <seb128> could people there install indicator-sound
[14:29] <seb128> and restart gnome-panel
[14:29] <seb128> (or dist-upgrade which should install it)
[14:29] <seb128> and tell me if the indicator is working for them
[14:30] <seb128> didrocks, pitti: ^
[14:30] <pitti> doing
[14:30] <didrocks> doing as well
[14:30] <pitti> on the mini, anyway (I currently need my session)
[14:30] <cedric_> This worked for me works well
[14:31] <seb128> cedric_, thanks, the slider is active and the mute button?
[14:32] <Nafai> seb128: works for me too
[14:32] <Nafai> now if the sound icon in the notification area would go away :)
[14:33] <seb128> Nafai, it will when you dist-upgrade and restart the session
[14:33] <seb128> Nafai, did you try the mute and slider?
[14:33] <Nafai> weird, I did restart
[14:33] <Nafai> yeah, both work great
[14:33] <seb128> Nafai, you probably didn't get the gnome-media update yet
[14:33] <didrocks> hum, indicator applet is dying for me
[14:33] <cedric_> everything is good for me
[14:33] <seb128> Nafai, it disable the autostart under GNOME
[14:33] <chrisccoulson_g1> well, this is fun
[14:33] <pitti> seb128: it does upgrade and install i-sound, but it doesn't upgrade gnome-media
[14:33] <Nafai> probably not
[14:33] <seb128> pitti, uploaded a publisher run later
[14:33] <Nafai> chrisccoulson_g1; IRCing from your G1?
[14:33] <seb128> pitti, sorry about that
[14:34] <pitti> no prob
[14:34] <pitti> I'll just wait for 20 mins
[14:34] <chrisccoulson_g1> Nafai - yeah, I'm stuck in my car
[14:34] <Nafai> heh
[14:34] <seb128> pitti, is the indicator working?
[14:34] <seb128> chrisccoulson_g1, oh? :-(
[14:34] <chrisccoulson_g1> I'm blocked in by a fire appliance and some police cars :(
[14:34] <chrisccoulson_g1> there's a car on fire nearby
[14:35] <chrisccoulson_g1> interesting afternoon ;)
[14:35] <didrocks> bah, indicator applet is crashing everytime now :/
[14:35] <seb128> didrocks, can I get a stacktrace?
[14:36] <seb128> chrisccoulson_g1, sucks :-(
[14:36] <didrocks> seb128: I'll try to remove it first to ensure it's the cause
[14:37]  * pitti uploads udisks
[14:38] <seb128> wououh
[14:38] <pitti> seb128: well, it's there
[14:38] <pitti> seb128: but I can't operate the slider
[14:38] <seb128> oh, suck
[14:38] <pitti> opening the dialog works, though
[14:39] <kenvandine> pitti, same thing i am getting
[14:42] <didrocks> seb128: ok, confirming, removing I got no pb, but I bring it back, I have a failure again. How do you get a stacktrace for the indicators, btw? gdb gnome-panel --replace?
[14:42] <seb128> didrocks, apport?
[14:43] <seb128> didrocks, what is crashing,
[14:43] <seb128> didrocks, the applet should  not take the panel down
[14:43] <didrocks> seb128: I have no apport crash report. Just the panel telling me "can't load the indicator"
[14:43] <seb128> didrocks, which one?
[14:43] <seb128> can you give the exact error
[14:44] <didrocks> seb128: "Can't load the OAFFID:GNOME_IndicatorApplet"
[14:44] <didrocks> do you want to remove the applet…
[14:45] <didrocks> hence my "indicator applet is dying" (the whole applet can't be added to gnome panel)
[14:45] <seb128> didrocks, gdb /usr/lib/indicator-applet/indicator-applet
[14:45] <seb128> (gdb) run
[14:45] <seb128> and then click "reload" on gnome-panel dialog
[14:46] <seb128> you need to run it on a command line first
[14:46] <seb128> ls
[14:46] <seb128> ups
[14:46] <seb128> run it on a command line then add it on the gnome-panel or reload it there if it waits on crash dialog
[14:46] <didrocks> seb128: ok
[14:48] <didrocks> seb128: no stacktrace really, but at least an undefined symbol: http://pastebin.com/f108fe4c2
[14:49] <didrocks> (I have to change pastebinit in my netbook to post on pastebin.ubuntu.com btw)
[14:50] <pitti> ugh
[14:50] <pitti> my box seems to be pretty broken now, I get gnome-session segfaults
[14:51] <seb128> what did you do to it?
[14:51] <pitti> dist-upgrade
[14:51] <seb128> what got upgraded?
[14:51] <pitti> but no to the new gnome-media yet
[14:51] <seb128> do you have a bt for the crash?
[14:51] <seb128> I blame udisk ;-)
[14:51] <pitti> indicator-sound
[14:51] <pitti> udisks isn't even running :)
[14:52] <pitti> but purging indicator-sound doesn't help either
[14:52]  * pitti tracks down
[14:52] <pitti> bbl
[14:54] <kenvandine> so who is our firefox guy now?
[14:57] <seb128> kenvandine, you? ;-)
[14:57]  * kenvandine hides
[14:57] <seb128> kenvandine, chrisccoulson, but officially not yet
[14:57] <pitti> seb128: sorry, PEBCAK; I chmodded nautilus to 0
[14:57] <pitti> (for running the udisks test suite)
[14:57] <seb128> pitti, and that makes gnome-session segfault?
[14:58]  * pitti )#*$#)$ at respawning
[14:58] <chrisccoulson> hey
[14:58] <seb128> hey chrisccoulson
[14:58] <chrisccoulson> i saw my name mentioned there
[14:58] <chrisccoulson> did i miss something? ;)
[14:58] <seb128> chrisccoulson: managed to go home?
[14:58] <kenvandine> chrisccoulson: hey... the u1 guys have a new version of bindwood that needs uploading to universe
[14:58] <chrisccoulson> yeah, i'm back now. they let me out :)
 so who is our firefox guy now?
[14:58] <pitti> seb128: I got a suspend during dist-upgrade, did several VT switches, and probably otherwise had a pretty bad state; all well after reboot
[14:58] <seb128> chrisccoulson: ^
[14:58] <kenvandine> chrisccoulson: want to look over it and reject or upload?
[14:59] <chrisccoulson> kenvandine - yeah, i can do. how urgent is it?
[14:59] <seb128> pitti, ok good
[14:59] <kenvandine> looks pretty straight forward, the awesome asac did most of the initial packaging
[14:59] <kenvandine> :)
[14:59] <kenvandine> chrisccoulson: i doubt it is super urgent...
[14:59] <chrisccoulson> cool, that's ok then. i need to get a drink before i do anything else :)
[14:59] <kenvandine> lp:~urbanape/firefox-extensions/bindwood.ubuntu-lucid
[14:59] <asac> is there a problem with bindwood?
[15:00] <kenvandine> no
[15:00] <kenvandine> new version
[15:00] <kenvandine> 1.0
[15:00] <kenvandine> imagine that... open source software with a 1.0 :)
[15:00] <asac> ok. if you have questions please check in mozillateam
[15:00] <asac> please check if it really is based on the latest we have in ~ubuntu-dev
[15:00] <seb128> asac, do you know if somebody is working on making search entry have something else than ask.com too?
[15:00] <kenvandine> ok
[15:01] <asac> seb128: its fix committed
[15:01] <seb128> asac, ok thanks
[15:01] <asac> did that today
[15:01] <seb128> you rock ;-)
[15:01] <asac> bug 520682
[15:03]  * pitti gratefully sees that indicator-sound is much nicer CPU-wise than gnome-volume-control-applet
[15:03] <kenvandine> asac, up ... merges cleanly too
[15:03] <kenvandine> chrisccoulson: ^^
[15:04] <seb128> pitti, nice
[15:04] <chrisccoulson> cool:)
[15:04] <james_w> which package provides the GNOME file chooser?
[15:04] <chrisccoulson> james_w - gtk?
[15:05] <james_w> thanks
[15:06] <didrocks> bb in a couple of hour, have an appointment
[15:07] <rickspencer3> good morning all
[15:07] <pitti> Mr. Spencer!
[15:07] <seb128> hey rick!
[15:08] <pitti> kenvandine: would you mind updating https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus for DX integration?
[15:08] <rickspencer3> seb128, so if I do a dist-upgrade now, I get the new sound indicator?
[15:09] <rickspencer3> kenvandine, are you up again, or still up?
[15:09] <seb128> rickspencer3, yes
[15:09] <rickspencer3> seb128, kenvandine great, can
[15:09] <rickspencer3> t wait to try it
[15:09] <seb128> rickspencer3, I like it
[15:09] <seb128> rickspencer3, and pitti testing says it uses less cpu than the GNOME one
[15:09] <seb128> so it's all good ;-)
[15:10] <rickspencer3> that's Connor's first contribution, right?
[15:10] <seb128> yes
[15:10] <seb128> rickspencer3, didrocks and pitti landed background caching too today
[15:10] <pitti> guys, check this out:
[15:10] <pitti> http://people.canonical.com/~pitti/bootcharts/daniel-lucid-20100212-3.png
[15:10] <seb128> rickspencer3, and scott said that with some plumper tweaking he was down to 10.5s boot
[15:10] <rickspencer3> !
[15:10]  * rickspencer3 cries tears of joy
[15:11] <rickspencer3> keep going guys!
[15:11] <rickspencer3> just 1 more week left
[15:11] <seb128> ;-)
[15:11] <pitti> rickspencer3: and that didn't even include the stuff that landed today (bg caching, and autostart shuffling)
[15:11] <rickspencer3> huh
[15:11] <pitti> that chart above has 11.09 s
[15:11] <seb128> pitti, did you reinstall the mini or do you still have my patched nm-applet there
[15:11] <rickspencer3> I'm literatly shaking a bit!
[15:11] <pitti> seb128: no, it's lucid's nm-applet
[15:11] <seb128> pitti, hum ok, no cpu use anymore, weird
[15:11] <pitti> but my chart already has the rsyslog/dd fix locally applied
[15:11] <rickspencer3> seb128, pitti last night on my non-SSD dell mini 10v, I noticed that it was starting up really fast
[15:12] <pitti> seb128: it seems to be pretty random; it does occur, just two seconds later when the chart stops
[15:12] <rickspencer3> I did a dist-upgrade, went to get something, and when I came back I assumed that it hadn't rebooted
[15:12] <pitti> rickspencer3: right, it does; now it's "really fast" to "amazingly fast" :)
[15:12] <seb128> pitti, it's not there on this chart
[15:12] <seb128> pitti, and the chart goes 3 seconds after the line
[15:12] <chrisccoulson> i need to invest in a mini so i can enjoy this fast booting :)
[15:13] <seb128> chrisccoulson: invest in a ssd for your laptop
[15:13] <pitti> chrisccoulson: just buy an SSD
[15:13] <pitti> cheaper, and it'll be even faster
[15:13] <seb128> people get faster boot than this now
[15:13] <chrisccoulson> yeah, i suppose i could do that too ;)
[15:13] <seb128> cpu sucks on the mini
[15:13] <seb128> with decent cpu and ssd some people do 7 seconds
[15:13] <seb128> or 8 seconds
[15:13] <pitti> chrisccoulson: you so much don't want to endure this abdomination of a touchpad
[15:14] <chrisccoulson> pitti - i hate touchpads anyway ;)
[15:14] <seb128> +1
[15:14] <seb128> tseliot, I guess you are too busy to work on this "disable touchpad" option for lucid?
[15:14] <chrisccoulson> i can work on that if it's wanted and noone else wants to take it
[15:14] <chrisccoulson> it should be easy shouldn't it? (we used to have the option before)
[15:15] <seb128> having the option in the capplet would be nice
[15:15] <seb128> I use external mouses
[15:15] <seb128> and keep touching the pad by error
[15:15] <chrisccoulson> yeah, me 2
[15:15] <tseliot> seb128: I'm too busy to work on anything other than the boot experience, I guess ;) but I can work on that disable touchpad thing after alpha 3
[15:15] <seb128> tseliot, thanks, we will see if somebody else do it before
[15:15] <pitti> the gnome-keyring-a... (ctivation-something) process is still pretty heavy
[15:15] <seb128> seems chrisccoulson is interested
[15:16] <pitti> I guess that wouldn't appear on Scott's charts, though
[15:16] <seb128> urg, make me thing I still have the new gnome-keyring to land at some point
[15:16] <seb128> I packaged it this week
[15:16] <seb128> but I've some issues with it
[15:16] <chrisccoulson> is it not getting a bit late to introduce that now?
[15:16] <seb128> we are not to ff yet
[15:16] <seb128> the lib is api compatible
[15:16] <baptistemm> chrisccoulson: YOU SHOULD BUY A SSD !!!!
[15:16] <baptistemm> :)
[15:16] <seb128> it's a drop in replacement
[15:16] <tseliot> seb128: ok, if no one does it, feel free to ping me again after alpha 3
[15:17]  * baptistemm join the ring
[15:17] <seb128> tseliot, will do, thanks
[15:17]  * chrisccoulson goes to look at SSD prices
[15:17] <seb128> chrisccoulson: but yeah, it's either before alpha3 or not
[15:17] <seb128> one thing they did is to split the services
[15:17] <seb128> so you have several process started now
[15:17] <seb128> pitti, I might ping you to try what difference that makes on bootchart next week
[15:18] <seb128> pitti, or do you want to test that on the mini today?
[15:18] <seb128> they have services for each component now
[15:18] <seb128> like ssh is a service with its autostart
[15:18] <seb128> etc
[15:18] <pitti> seb128: I'm happy to do some charts if there's a package to test
[15:19] <seb128> pitti, I've i386 debs, one minute I scp those
[15:20] <chrisccoulson> vish - my gpm change to (hopefully) fix your issue has been committed :)
[15:21] <vish> chrisccoulson: yeah , just noticed :)  [/me keeping fingers crossed :D  ]
[15:21] <chrisccoulson> hopefully people will never see that silly tray icon again
[15:23] <kenvandine> rickspencer3, yeah... i am up :)
[15:23] <kenvandine> rickspencer3, i have 3 kids, then ensure i never sleep past 6-6:30am
[15:23] <kenvandine> rickspencer3, i got the edit in view mode patch for f-spot backported
[15:24] <kenvandine> it's a little crashy
[15:24] <kenvandine> will work on it more today :)
[15:24] <rickspencer3> kenvandine, yeah!
[15:24] <rickspencer3> I should sleep an extra hour every morning
[15:24] <rickspencer3> I wake up ...
[15:24] <rickspencer3> new sound indicator
[15:24] <kenvandine> :)
[15:24] <rickspencer3> boot time is approaching the goal
[15:24] <kenvandine> boot time is rocking!
[15:24] <rickspencer3> image editing is being worked on
[15:25] <seb128> rickspencer3, I uploaded libgpod with iphone support too
[15:25] <seb128> rickspencer3, it's a good desktop day so far I think ;-)
[15:26] <rickspencer3> I'm meeting eeejay in 2.5 hours
[15:26] <rickspencer3> we're going to look into making empathy APIs easier to use
[15:26] <seb128> oh, nice
[15:26]  * rickspencer3 tries desperately to appear to be contributing
[15:27] <seb128> lol
[15:27]  * seb128 hugs rickspencer3, don't worry you do great work too
[15:27] <seb128> the team wouldn't run the same way without you ;-)
[15:27] <pitti> if everyone/everything is working so well, this is obviously the result of a great team leader!
[15:28] <kenvandine> hehe
[15:28] <pitti> (I'm actually serious)
[15:28]  * pitti hugs rickspencer3
[15:28] <kenvandine> yup!
[15:28] <kenvandine> pitti, i just marked 4 items done on the dx-integration blueprint
[15:28]  * pitti hugs kenvandine
[15:29] <chrisccoulson> there's a lot of love in here this afternoon :)
[15:30] <jcastro> pitti, is policykit-1-gnome still called "policykit-gnome" in upstream bugzilla?
[15:30] <chrisccoulson> jcastro - yeah
[15:30] <pitti> jcastro: yes, I think it is
[15:30] <jcastro> that's what I thought
[15:30]  * rickspencer3 sniff
[15:30]  * chrisccoulson finds that a bit confusing
[15:31] <pitti> now that it's gone from KDE as well, we can hopefully eventually rename them back
[15:31] <pitti> it has always been meant to be a temporary name fork, to have two ABIs
[15:34] <chrisccoulson> has anyone got any experience with buying SSD's?
[15:35] <rickspencer3> pitti, seb128, kenvandine hey, so codecs + music store + pitivi ....
[15:35] <rickspencer3> I'm putting together a call next week so we can hammer it out on the phone
[15:35] <kenvandine> rickspencer3, libubuntuone will be ready today
[15:35] <rickspencer3> shall I invite all three of you?
[15:35] <seb128> chrisccoulson: not me, but baptistemm and jcastro do
[15:35] <kenvandine> rickspencer3, sure
[15:35] <seb128> rickspencer3, works for me
[15:35] <chrisccoulson> cool, thanks :)
[15:36] <pitti> rickspencer3: ack
[15:36] <baptistemm> I bought mine on ebay for 350€ free of charge
[15:36] <baptistemm> which 70€ less expensive than any shop in EU
[15:36] <seb128> urg
[15:36] <seb128> that's expensive
[15:36] <baptistemm> yeah :)
[15:36] <baptistemm> it is my christmas present
[15:36] <seb128> you can get 2 minis for that price
[15:37] <chrisccoulson> baptistemm, which model did you get? (and what storage capacity?)
[15:37] <baptistemm> I took a 160GB intel x25m
[15:37] <seb128> 160G, that's why I guess
[15:37] <baptistemm> 80 GB is twice cheaper
[15:37] <jcastro> chrisccoulson, you want the intel x25-m g2. They go for about $289 US.
[15:37] <chrisccoulson> ah, that's pretty big
[15:37] <baptistemm> I tooka g2 too)
[15:38] <chrisccoulson> jcastro - thanks. will have a look :)
[15:46] <pitti> rickspencer3: tseliot postponed some 5 WIs, you added two for ArneGoetje, but we have more than yesterday; how can that be..
[15:48] <rickspencer3> pitti, I have no idea
[15:49] <rickspencer3> can we query the database?
[15:52] <pitti> rickspencer3: we can, yes
[15:52] <seb128> pitti, we need daily diffs ;-)
[15:53] <pitti> oh, I added two more to startu-speed
[15:53] <seb128> that still doesn't make for the 5
[15:53] <seb128> I did close 2 yesterday I think too
[15:53] <seb128> and the gwibber duplicate got closed too
[15:54] <seb128> we should have dropped by 8 or something
[15:54] <pitti> ah, and some more from https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-lucid-xorg-triaging-diagnosis got assigned from canonical-qa back to us
[15:54] <pitti> anyway, I'll have a closer look later on (meeting starts soon)
[16:02] <chrisccoulson> does anybody in here use multiple keyboard layouts?
[16:03] <seb128> chrisccoulson: I do yes
[16:03] <pitti> o/
[16:03] <Nafai> Can do you a different layout per keyboard?
[16:03] <rickspencer3> pitti, I think we are going to just punt the rest of those xorg triaging work items to Lucid + 1
[16:04] <Nafai> i.e., one for my built-in one and one for my external?
[16:04] <chrisccoulson> seb128 - is there any way of switching layouts other than using the layout switcher in the notification area?
[16:04] <pitti> rickspencer3: well, it's some time spent now which could help us to save lots of time later on
[16:04] <pitti> this is why I was a bit hesitant to postpone it
[16:04] <seb128> chrisccoulson: you can configure the keybing for that in the capplet
[16:04] <rickspencer3> pitti, I know
[16:04] <rickspencer3> please discuss with bryce
[16:04] <pitti> *nod* (already did)
[16:04] <rickspencer3> I believe that he has picked the low hanging fruit and is still working on some
[16:05] <pitti> still keeping it as target of opportunity for alpha-3
[16:05] <chrisccoulson> seb128 - ah, ok. thanks. so, it would be a reasonable request to provide a way to hide the layout switcher?
[16:05] <seb128> chrisccoulson: I think default is both alt together
[16:05] <rickspencer3> but I want us to stop blueprint work on the 18th!
[16:05] <seb128> chrisccoulson: yes
[16:05]  * rickspencer3 repeats mantra
[16:05] <rickspencer3> 1. find and fix the worst bugs
[16:05] <chrisccoulson> seb128 - thanks
[16:05] <rickspencer3> 2. ensure a smooth upgrade experience
[16:05] <rickspencer3> 3. integrate the latest and greatest from Dx
[16:05] <pitti> rickspencer3: that probably will contribute to 1. :)
[16:05] <rickspencer3> pitti, understood
[16:06] <rickspencer3> I think he's on track to do the right work items for Lucid
[16:06] <rickspencer3> they aren't *all* necessary to help with 1
[16:06] <pitti> *nod*
[16:06] <rickspencer3> anyway, I trust that bryceh will be able to make the right trade offs
[16:06] <rickspencer3> he always has in the past
[16:07] <rickspencer3> but seriously, this bears repeating ...
[16:07] <rickspencer3> everyone finish up your blueprint work for A3!!
[16:07] <rickspencer3> we need to switch gears to quality mode!!
[16:08] <rickspencer3> the users will appreciate that more than one or two more features
[16:08]  * rickspencer3 gets off soap box
[16:08]  * rickspencer3 stops preaching to choir
[16:08] <rickspencer3> ;)
[16:17] <baptistemm> does someone experience black display after booting, i don't see GDM greeter but I hear ubuntu login sound
[16:18] <baptistemm> If I switch to vt1 and do "restart gdm", gdm works fine
[16:18] <seb128> baptistemm, try ctrl-alt-f1 and ctrl-alt-f7
[16:18] <seb128> do you have plymounth installed?
[16:18] <seb128> bah
[16:18] <seb128> kenvandine, no cookie for you!
[16:19] <baptistemm> I guess so, is it installed by default in lucid (My computer is at home)
[16:19] <seb128> baptistemm, you can try to apt-get remove it
[16:19] <baptistemm> I installed my new disk with the A2 cd or a daily one but afterA2
[16:19] <seb128> it fixes issues for quite some users
[16:19] <baptistemm> just remove it
[16:19] <seb128> yes
[16:20] <baptistemm> I mean I won't have the real boot process
[16:20] <baptistemm> so I can't test
[16:20] <baptistemm> okay
[16:22] <didrocks> re
[16:22] <seb128> didrocks, wb
[16:24] <seb128> didrocks, oh btw I had an idea about your cheese crasher
[16:24] <seb128> didrocks, is your source online somewhere or do you want to try something ?
[16:25] <desrt> nice!
[16:25] <desrt> i'm in a coffee shop and the people behind me are discussing google's "don't be evil" motto
[16:26] <didrocks> desrt: heh, what kind of coffee shop are you in? ;)
[16:26] <chrisccoulson> lol
[16:27] <desrt> william's coffee pub
[16:27] <desrt> across the street from a university
[16:34] <chrisccoulson> whats happened to the volume osd notification?
[16:34] <chrisccoulson> does it work for anyone else?
[16:34] <chrisccoulson> oh, brightness is not working here either
[16:36] <seb128> chrisccoulson, is notify-osd working for you?
[16:36] <didrocks> seb128: sorry, I was rollbacking  the channel's log. let me scp it :)
[16:36] <didrocks> seb128: I can have a try if you want
[16:36] <chrisccoulson> seb128 - yeah, i'm seeing message notifications
[16:36] <didrocks> seb128: fredp told me yesterday that he doesn't have this issue on debian
[16:36] <chrisccoulson> but the synchronous notifications are busted
[16:37] <didrocks> (maybe related to udev, as I don't have the crash on my box without webcam?)
[16:37] <seb128> didrocks, I've a feeling I know what the issue is there...
[16:38] <chrisccoulson> hmmmm
[16:38] <chrisccoulson> they're working now
[16:39] <didrocks> seb128: do you me to try something or I just push the branch?
[16:39] <chrisccoulson> brb, session restart
[16:39] <slomo> seb128: thanks for syncing all the gstreamer packages :)
[16:39] <seb128> didrocks,
[16:39] <seb128> +LDFLAGS=$(shell echo $$LDFLAGS | sed -e 's/-Wl,-Bsymbolic-functions//')
[16:39] <seb128> +export LDFLAGS
[16:39] <seb128> didrocks, add that to the rules
[16:39] <didrocks> seb128: ok thanks, doing :)
[16:39] <seb128> didrocks, before the includes
[16:39] <james_w> could someone review http://paste.ubuntu.com/374830/ please?
[16:43] <seb128> chrisccoulson, <james_w> could someone review http://paste.ubuntu.com/374830/ please?
[16:43] <seb128> chrisccoulson, I think you know a bit this code?
[16:44] <seb128> james_w, looking at it too, but diff of diff is hard, I will apply that to the source :-p
[16:44] <chrisccoulson> seb128 - yeah, i will take a look shortly. i took a look at this a little while ago
[16:45] <james_w> I'm not sure it's the right fix, and I'd want to run with it for a while
[16:45] <james_w> seb128: no kidding :-)
[16:45] <chrisccoulson> james_w - i've actually got a feeling that there are 2 code paths which don't set a GError (when they should be doing)
[16:45] <chrisccoulson> i vaguely remember that from when i looked at it before
[16:46] <james_w> hmm
[16:46] <chrisccoulson> but i will take a look shortly
[16:46] <james_w> possibly
[16:46] <james_w> I was going on what was in the upstream report
[16:47] <didrocks> seb128: you ROCK!
[16:47]  * didrocks hugs seb128
[16:47] <pitti> ccheney: hey, good morning
[16:47]  * seb128 hugs didrocks
[16:48] <pitti> ccheney: do you know if there is a more precise release roadmap for OO.o 3.2.1 by now?
[16:48] <didrocks> seb128: even looking at ld, I have no idea about what this option in LDFLAGS is doing (and what it's doing wrong, in fact :))
[16:48] <chrisccoulson> kenvandine, did you say you had reviewed the gpm appindicator patch?
[16:49] <seb128> didrocks, the same symbol is defined in 2 binaries there
[16:49] <seb128> didrocks, the binary and the library probably
[16:49] <seb128> didrocks, that leads to such crashes when using -Bsymbolic
[16:49] <seb128> we had the issue with gnome-bluetooth previously
[16:49] <seb128> I know it by now ;-)
[16:50] <pitti> seb128: did you want me to test new keyring packages? I. e. did I miss an IRC ping of your's or so?
[16:50] <seb128> our toolchain has -Bsymbolic-function by default
[16:50] <seb128> pitti, oh right, not I just finished other stuff and forgot
[16:50] <didrocks> seb128: oh ok, make sense :) btw how to know what are the default flags? (it's something loaded by make, I guess)
[16:52] <seb128> pitti, http://people.canonical.com/~seb128/gnome-keyring
[16:52] <seb128> it's copying
[16:52] <seb128> one minute
[16:52] <seb128> didrocks, not sure right now how to do that, I know this one is on though
[16:53] <seb128> there is a wiki page with the toolchain option we activate
[16:53] <seb128> but I don't want to search for it now, busy with other things
[16:53] <didrocks> seb128: ok, I'll try to find it, good to know, thanks :)
[16:53] <seb128> np
[16:54] <seb128> didrocks, feel free to comment on the upstream bug saying it happens only with -Bsymbolic-function and it's probably a symbol defined in 2 binaries
[16:54] <seb128> you might want to look at which one
[16:54] <seb128> pitti, online
[16:54] <pitti> seb128: thanks, testint
[16:54] <seb128> pitti, danke
[16:54] <pitti> bah, Friday evening tpying :)
[16:54] <chrisccoulson> pitti - can we do a SRU for bug 160862?
[16:54] <didrocks> seb128: yep, I finish some bug triaging first and then cheese upload + report upstream
[16:55] <chrisccoulson> it's only a 1 liner :)
[16:55] <pitti> seb128: anything I should test in particular? (so far I only have wifi password here, but I can also test ssh easily)
[16:55] <pitti> chrisccoulson: without looking at the bug, the title very much suggests SRUability
[16:55] <seb128> pitti, well you can test if it works for you, but I was rather interested by bootchart on the mini
[16:55] <pitti> ah
[16:56] <seb128> pitti, be careful if you install that on your session it will break libgnome-keyring customers until gnome-keyring restart
[16:56] <seb128> or session restart
[16:56] <seb128> ie searhose if you run it will tell you it can't connect to the gnome-keyring daemon
[16:56] <seb128> I get empathy crashing with it too which I didn't investigate yet
[16:56] <chrisccoulson> pitti - thanks. would you mind adding targets for hardy, jaunty and karmic? (i suspect it's probably not worth effort fixing on intrepid)
[16:56] <seb128> or rather mission-control
[16:56] <pitti> np, I don't have anythign on that box
[16:57] <seb128> cassidy, do you know if there is some known issue between mission control and keyring 2,29?
[16:58] <cassidy> seb128, yes, a crash has been reported
[16:58] <cassidy> let me find it
[16:58] <cassidy> seb128, https://bugzilla.gnome.org/show_bug.cgi?id=608709
[16:58] <seb128> cassidy, thanks!
[16:58] <cassidy> which is a dup of https://bugzilla.gnome.org/show_bug.cgi?id=608510
[16:59] <pitti> chrisccoulson: done
[17:11] <chrisccoulson> pitti - thanks
[17:19] <pitti> seb128: the new one uses more CPU
[17:20] <pitti> http://people.canonical.com/~pitti/bootcharts/daniel-lucid-20100212-2.png
[17:20] <pitti> (old)
[17:20] <pitti> http://people.canonical.com/~pitti/bootcharts/daniel-lucid-20100212-5-new-gnome-keyring.png
[17:20] <pitti> (new)
[17:21] <seb128> pitti, is that enough that you would consider it an issue?
[17:21] <seb128> I'm still pondering what to do there
[17:21] <pitti> seb128: if we want the new one for functional reasons, I'm happy to take a look at it and see what we can optimize
[17:23] <seb128> pitti, I've having some email exchange with upstream about it
[17:23] <seb128> he wrote recently
[17:23] <seb128> " * Better startup, controlling which components launch through
[17:23] <seb128>    'Startup Applications'
[17:23] <seb128>  * Locking keyrings after a certain amount of idle time."
[17:23] <seb128> as new features
[17:23] <seb128> and "The two versions use the same file formats, and are completely
[17:23] <seb128> compatible with one another"
[17:23] <chrisccoulson> pitti - on the subject of SRU's, hughsie is considering backporting this commit back to gpm 2.28: http://git.gnome.org/browse/gnome-power-manager/commit/?id=7380ab4e13db76cb5be2e1bc4a42a810a5261fd4
[17:23] <seb128> the said the code has been refactored and should be nicer
[17:24] <chrisccoulson> i'm not sure if we want to consider that for karmic too
[17:24] <pitti> chrisccoulson: uh, sorry, what's the effect in plain English?
[17:24] <seb128> I will pay $beers to whoever fix gpm not coming back to the brighness level it should go to before lucid
[17:25] <chrisccoulson> pitti - the status icon appears in the notification area telling you that your display is broken, and the display blanks whilst you're working
[17:25] <pitti> seb128: if you think we should update, as part of 2.30, you have my support for that
[17:25] <pitti> chrisccoulson: eww; sounds worth fixing indeed
[17:25] <seb128> pitti, I've no strong opinion, what we have is known and works
[17:25] <seb128> new version didn't break compatibility though
[17:26] <chrisccoulson> pitti - he's going to run it for a while just to make sure it really fixes the issue
[17:26] <seb128> they splitted the lib and added those dbus interfaces
[17:26] <seb128> and some modularity
[17:26] <chrisccoulson> and i'll upload it to lucid too
[17:26] <seb128> but those are not really must have for lucid
[17:26] <seb128> what other people take would be on this one?
[17:26] <pitti> seb128: *nod*; so that could also be considered a "potential source of regressions without major benefits"?
[17:27] <pitti> seb128: don't other GNOME components make use of those new APIs sooner or later?
[17:27] <seb128> not this cycle
[17:27] <seb128> they plan to rework the store system etc
[17:27] <seb128> and will deprecate libgnome-keyring
[17:27] <seb128> but that didn't happen this cycle
[17:27] <seb128> store -> storage
[17:27] <seb128> I think they are working toward dbus method and a freedesktop storage
[17:29] <seb128> pitti, http://mail.gnome.org/archives/gnome-keyring-list/2010-January/msg00007.html
[17:29] <pitti> seb128: the only thing which I want to avoid is to update to it late (after beta-2 or so) because a newer gnome version depends on it
[17:29] <pitti> if that's very unlikely, staying on 2.28 sounds fine to me
[17:29] <seb128> didrocks, chrisccoulson: ^ opinion?
[17:30] <pitti> if we stay at 2.28, I'd like us to disable the "allow access to keyring" question, though
[17:30] <pitti> (but that should be easy)
[17:30] <seb128> right
[17:30] <chrisccoulson> i don't think it's worth updating it this cycle, especially if nothing else in GNOME needs it just yet
[17:30] <seb128> well I'm not decided between staying on a known codebase
[17:30] <seb128> or going with somebody which will be easier to maintain and an uptodate plateform for those use lucid for work
[17:31] <seb128> somebody -> something
[17:31] <didrocks> seb128: I agree too, staying at 2.28 seems fine for an LTS
[17:31] <chrisccoulson> i think we've probably already got plenty of bugs to start working on, without introducing lots of new ones
[17:31] <didrocks> (we can use the same flag "too many changes" than the one for evolution)
[17:31] <seb128> right, that's one way to see it
[17:31] <seb128> the other way is that the version you use is deprecated and upstream will not fix bugs on it
[17:32] <seb128> and some people might want to use the lts to hack and need an uptodate platform
[17:32] <chrisccoulson> yeah, that's true too
[17:32] <chrisccoulson> it's a difficult choice really
[17:32] <seb128> I will put it in the desktop team ppa now I think
[17:32] <seb128> and ask for testing
[17:33] <didrocks> good idea
[17:33] <pitti> that'd be nice
[17:33] <seb128> and we can upload next week or decide against
[17:33] <pitti> then I can test it on my amd64 laptop as well, with ssh and everything
[17:33] <seb128> thanks everybody
[17:33]  * didrocks adds "test heavily gnome-keyring from ppa" as next week task :)
[17:35] <seb128> should I use ubuntu-desktop ppa for that?
[17:35] <seb128> or use a gnome-keyring ppa there?
[17:38] <ccheney> pitti: not yet, no
[17:39] <ccheney> pitti: i'm not even sure if it is still going to be produced as 3.3 is expected by around June
[17:39] <ccheney> pitti: there are only two bugs on 3.2.1 currently so if they decide to release it could be pretty quick
[17:40] <ccheney> pitti: 3.2.0 was officially released yesterday
[17:42] <didrocks> seb128: there is a gnome-keyring ppa? maybe ubuntu-desktop is better, no? (to make it "more official about what we want to test/integrate")
[17:42] <ccheney> pitti: it looks like ooo-build and debian aren't caught up with yesterdays release yet though, but probably will be by early next week
[17:43] <seb128> didrocks, no, but you can create different ppas, I was pondering using the default ubuntu-desktop one or a subone named gnome-keyring still under ubuntu-desktop
[17:43] <didrocks> seb128: oh ok, I have no strong opinion if a new ppa is needed :)
[17:48] <kenvandine> whew... had to fsck / from a livecd again
[17:48] <chrisccoulson> kenvandine, i had to do that a couple of days ago too
[17:49] <kenvandine> happened to me last week as well
[17:49] <chrisccoulson> eeeeek, not good
[17:49] <kenvandine> yeah... time to shop for a drive
[17:50] <kenvandine> or re-install for real
[17:50] <kenvandine> this is a ext4 filesystem that was created by jaunty alpha1
[17:51] <chrisccoulson> kenvandine, this is a brand new install and it breaks too
[17:52] <chrisccoulson> i can't remember what the error was when it broke, as it remounted read-only
[17:52] <kenvandine> same here
[17:52] <kenvandine> well there is no error
[17:52] <kenvandine> both times it happened while the screen was locked
[17:53] <kenvandine> trying to login on a VT just says it is mounted read-only
[17:53] <kenvandine> so no access to the errors
[17:53]  * kenvandine looks at the logs
[17:53] <chrisccoulson> kenvandine, i got a load of ext4 related errors at the end of dmesg, and the message telling me it had remounted read-only
[17:53] <chrisccoulson> but they don't get saved
[17:53] <chrisccoulson> as the volume was read-only ;)
[17:53] <kenvandine> oh sigh
[17:53] <seb128> asac, pitti: bug #494549 is good to go?
[17:54] <seb128> asac, pitti: we need to have those promoted now if we want the current libgpod to build
[18:01] <jjardon> Hello, seems that the yelp version shipped with lucid is the webkit branch, but this is not a officially supported branch, Is this intentional?
[18:04] <Nafai> So what's the best way to handle when you upgrade things like indicator applet and such without having to log out and back in?
[18:06] <Nafai> just kill the process and let the panel re-load it?
[18:06] <pitti> seb128, asac: it seems that the issues were addressed
[18:06] <seb128> pitti, there is a new upstream version available I will upload it so we get the fixes in lucid
[18:06] <pitti> promoted
[18:07] <seb128> pitti, thanks
[18:07] <pitti> ccheney: "two bugs on 3.2.1" -> that is, to bugs in 3.2.0 which are regressions and to be addressed?
[18:07] <pitti> ccheney: that'd be pretty good
[18:09] <ccheney> pitti: there are two targeted bugs for 3.2.1 which would be what would block its release if they decide to make it
[18:10] <ccheney> pitti: of course as new major bugs are found the count will go up but not bad so far
[18:33]  * pitti waves goodnight
[18:39] <didrocks> dinner time, bbl :)
[18:41] <seb128> didrocks, enjoy
[18:56] <seb128> pedro_, gvfs seems to have quite some crashes duplicates if you want to clean it one day
[18:57] <pedro_> seb128, will have a look into it
[18:57] <seb128> thanks!
[18:57] <seb128> pedro_, btw how did the pitivi bug day go?
[18:57] <pedro_> my pleasure ;-)
[18:58] <pedro_> seb128, pretty fine! the product is looking very clean
[18:58] <pedro_> we also had some input from the pitivi folks so now it's just time to wait for the reporters feedback on what we did
[18:58] <seb128> nice
[18:59] <pedro_> no major issues though, just little annoyances with gstreamer crashing in the middle while you're editing something and things like that
[18:59] <seb128> I should open a bug at some point, pitivi seems to just do nothing on the video I tried
[18:59] <seb128> it the bar at the bottom doesn't get signal etc
[19:03] <rickspencer3> hey kenvandine ... I'm looking for some sample code for exporting a dbus service in a real app
[19:04] <rickspencer3> do you know off hand where I should look in gwibber?
[19:06] <kenvandine> rickspencer3, dispatcher.py
[19:06] <kenvandine> gwibber/microblog/dispatcher.py
[19:06] <rickspencer3> thanks kenvandine
[19:06] <kenvandine> np
[19:10] <asac> pitti: seb128: ack. thx. fine if we have the new upstream (or are sure we will get them)
[19:11] <Nafai> kenvandine: Did you see my gwibber bug? :)
[19:11] <kenvandine> Nafai, not yet
[19:11] <Nafai> not high priority, I filed it a couple days ago.  can't get stuff from friendfeed
[19:12] <kenvandine> ?
[19:12] <kenvandine> bug number please?
[19:12]  * kenvandine doesn't have it in bug folder
[19:12] <Nafai> just a sec
[19:12] <Nafai> 520537
[19:12] <kenvandine> thx
[19:12] <Nafai> np
[19:12] <kenvandine> bug 520537
[19:13] <Nafai> ah, I'll be sure to write bug before it next time ;)
[19:13] <kenvandine> Nafai, we might not fix it until after feature freeze :)
[19:13] <Nafai> that's fine
[19:13] <kenvandine> Nafai, nifty huh?
[19:13] <kenvandine> :)
[19:13] <Nafai> twitter and facebook work better for me
[19:13] <Nafai> rather, are more important
[19:13] <Nafai> :)
[20:17] <rickspencer3> kenvandine, what version of telepathy-gabble shall we deliver in Lucid?
[20:18] <kenvandine> we should talk to upstream
[20:18] <kenvandine> cassidy, ^^
[20:18] <kenvandine> opinions?
[20:19] <kenvandine> it would be nice to ship with the facebook chat feature :)
[20:19] <rickspencer3> kenvandine, tbh, I'm sitting next to eeejay right now
[20:19] <kenvandine> haha
[20:20] <rickspencer3> eeejay is thinking that maybe there is a good reason we are still on .8
[20:20] <kenvandine> oh... well .9 is the unstable series
[20:20] <kenvandine> is .10 planned soon?
[20:23] <kenvandine> or soon enough for lucid?
[20:23] <rickspencer3> kenvandine, dunno
[20:23] <rickspencer3> prolly not it sounds like
[20:23] <kenvandine> cassidy, ^^
[20:26] <eeejay> the facebook thingie will be in lucid no matter what
[20:28] <seb128> rickspencer3, we are using what cassidy recommended when I ask him about what we should use...
[20:28] <rickspencer3> seb128, okay, cool
[20:28] <seb128> when I asked
[20:28] <seb128> rather
[20:28] <seb128> I'm happy to revisit that if they come with a new stable serie
[20:28] <rickspencer3> me and eeejay are just trying to get some tubey pythony code working
[20:29] <rickspencer3> and just want to make sure we are hacking with the versions intended to land in lucid
[20:29] <rickspencer3> (and that we both have the same versions ;) )
[20:29] <rickspencer3> thanks seb128
[20:29] <seb128> np
[20:31] <lool> seb128: O'm dedicating this special upload for you, have a good weed-end  ;-)
[20:31] <lool> s/O/I
[20:31] <seb128> waouh
[20:31] <seb128> lool did fix the gtk bug
[20:31] <seb128> and updated valgrind
[20:31] <seb128> lool, you made my end of week ;-)
[20:32] <seb128> lool, enjoy your weekend!
[20:32] <lool> you too!
[20:32]  * seb128 hugs lool
[22:54] <jcastro> hey chrisccoulson you were handling g-p-m with app indicators right?
[23:45]  * didrocks has finished to triaged all UNE bugs for the last 1 year and half \o/