[00:00] <TheMuso> Hey rickspencer3, robert_ancell.
[00:00] <robert_ancell> TheMuso, hi
[00:00] <rickspencer3> hi TheMuso
[00:01] <rickspencer3> guys ready?
[00:01] <TheMuso> Indeed.
[00:01] <rickspencer3> this should be brief
[00:01] <rickspencer3> any agenda items?
[00:01] <rickspencer3> to add?
[00:01] <rickspencer3> https://wiki.ubuntu.com/DesktopTeam/Meeting/2009-06-23
[00:01] <TheMuso> no
[00:01] <rickspencer3> robert_ancell: ?
[00:02] <robert_ancell> no
[00:02] <rickspencer3> k
[00:03] <rickspencer3> so the meeting is mostly announcements this week, but some discussion regarding paper cut bugs
[00:03] <rickspencer3> announcements:
[00:03] <rickspencer3> pitti: Reminder: do you merges (https://merges.ubuntu.com/main.html) pitti: spec status Karmic Sprint is in Dublin
[00:03]  * TheMuso is already sorting out flights for that.
[00:03] <rickspencer3> oops, that should have been ..
[00:03] <rickspencer3> pitti: Reminder: do you merges (https://merges.ubuntu.com/main.html)
[00:03] <rickspencer3> pitti: Reminder: do you merges (https://merges.ubuntu.com/main.html)
[00:04] <rickspencer3> ah forget it
[00:04]  * rickspencer3 can't copy and paste today :P
[00:04]  * awe remembers
[00:04] <rickspencer3> hi awe
[00:04] <rickspencer3> back for more?
[00:04] <TheMuso> heh
[00:04] <rickspencer3> TheMuso: robert_ancell: are your specs all reviewed by Martin?
[00:04] <awe> was looking for some launchpad help and realized y'all had the east coast mtg in progress
[00:04] <robert_ancell> rickspencer3, yes
[00:05] <rickspencer3> east coast of Australia, that is
[00:05] <TheMuso> All of mine have gone through a review, and one is approved. The audi oone still needs reviewing after changes needed to be made. Unfortunately I haven't really had the community help on this with some bits that I h oped for.
[00:05] <rickspencer3> TheMuso: did you get your work items on the blueprint?
[00:05] <TheMuso> rickspencer3: Yes.
[00:05] <TheMuso> In the whiteboard.
[00:05] <awe> TheMuso: what kind of help do you need?  Review?
[00:06] <rickspencer3> about 30 work items went missing from the burndown chart last night:
[00:06] <rickspencer3> http://piware.de/tmp/desktopteam-burndown-karmic.png
[00:06] <rickspencer3> pitti will fix it tomorrow I suppose
[00:06] <TheMuso> awe: That and someone to fill in about volume scaling stuff, I don't really understand that.
[00:07] <rickspencer3> awe: can you help?
[00:07] <awe> on the review part yes.
[00:07] <awe> on the volume scaling stuff i'll offer what knowledge i have
[00:08] <rickspencer3> thanks!
[00:08] <rickspencer3> ACTION: awe to review Audio spec and to comment on volume scaling
[00:09] <rickspencer3> ok
[00:09] <awe> TheMuso: please send me a link to the spec
[00:09] <rickspencer3> Ken is tracking U1 status here: https://wiki.ubuntu.com/UbuntuOne/DesktopIntegration/Status
[00:09] <TheMuso> awe: just a sec.
[00:10] <TheMuso> awe: https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-karmic-audio-experience
[00:10] <rickspencer3> kenvandine is also expecting the plan from DXE eow
[00:11] <rickspencer3> "the plan" being their work items and what they plan to do in their iterations
[00:11] <rickspencer3> robert_ancell: TheMuso: any questions, or should I keep going?
[00:11] <robert_ancell> go on
[00:11] <TheMuso> keep going, I've shot ahead again. :p
[00:12] <rickspencer3> bryce says that x is on track wrt to quality, and ahead wrt to packaging
[00:12] <TheMuso> Nice to hear.
[00:12] <rickspencer3> also that the kernel changes seem have more or less fixed the issues with i965 in Jaunty
[00:13]  * TheMuso mostly has NVIDIA hardware here so won't get to enjoy some of the niceties coming our way eg KMS.
[00:13] <rickspencer3> when KMS is turned on, he expects a flood of bugs
[00:13] <rickspencer3> TheMuso: yes, that is unfortunate ... perhaps next release
[00:13] <TheMuso> Yeah.
[00:13] <rickspencer3> unless the -nouvea guys pull a rabbit out of the hat for you
[00:13] <awe> +1
[00:14] <rickspencer3> they are working on KMS iirc
[00:14] <rickspencer3> also, there's this edgers stuff that is very popular
[00:14] <rickspencer3> so you can get a taste of the latest and proposed by installing the xorg-edgers ppa
[00:15] <robert_ancell> rickspencer3, so tempted but will keep away from that in the interest of having a working machine :)
[00:15] <rickspencer3> lol
[00:15] <rickspencer3> in the meantime, here are a couple of links that are interesting:
[00:15] <rickspencer3> http://www2.bryceharrington.org:8080/X/PkgList/versions_current.html
[00:15] <rickspencer3> http://people.ubuntu.com/~seb128/versions.html
[00:16] <rickspencer3> essentially bryce had invented a similar tool to what you guys have been using to track GNOME updates
[00:16] <rickspencer3> you might want to check that out and see if there is some cross pollination that might be helpful
[00:17] <rickspencer3> so this brings us to paper cut bugs
[00:17] <rickspencer3> the upshot was this:
[00:17] <robert_ancell> TheMuso, are you in the regional membership board for Ubuntu - I want to blog about versions but I need to be a member
[00:17]  * rickspencer3 waits
[00:17] <TheMuso> robert_ancell: Yes I am, but I think you'd be best getting membership by the usual channels.
[00:18] <robert_ancell> TheMuso, I need a testimonial
[00:18] <robert_ancell> (according to https://wiki.ubuntu.com/Membership)
[00:18] <TheMuso> THat I can do.
[00:18] <robert_ancell> TheMuso, thanks. rickspencer3 done interrupting :)
[00:19] <rickspencer3> no interuption, that's what this is for
[00:19] <rickspencer3> back to versions: there was some discussion about ...
[00:19] <rickspencer3> having one page for packages on the CD, and another page for packages that someone has expressed on interest in
[00:20] <rickspencer3> then community members could ping seb and ask for foo package to be added to the tracking list
[00:20] <robert_ancell> That was the idea of the (+) sign. I was initially considering a tag system where you toggle which packages are shown by tag (e.g. karmic, jaunty, ubuntu-desktop)
[00:21] <rickspencer3> mmm
[00:21] <rickspencer3> back to paper cut bugs?
[00:21] <robert_ancell> sure
[00:21] <rickspencer3> ok
[00:21] <rickspencer3> so ..
[00:21] <rickspencer3> 1. some engineers are being flooded with related bug mail
[00:22] <rickspencer3> ignore the bug mail because the design team is picking 10 bugs per week to fix, so
[00:22] <rickspencer3> 2. Look for the paper cuts mail each week, and pick something to fix, if there is a good match for you
[00:23] <rickspencer3> however, if it looks like more than about 4 hours of work for you, you can either:
[00:23] <rickspencer3> just comment on the amount of work, and leave it for someone who has the time or could do it faster
[00:23] <TheMuso> There is one audio related bug that is marked as a paper cut, I'll probably work on that sooner than the round its marked for, which I guess is fine.
[00:23] <rickspencer3> or if you think it is non-trivial for anybody to fix, you can set it to invalid
[00:23] <rickspencer3> TheMuso: yes, that is fine
[00:24] <rickspencer3> 3. Paper cut bugs should be prioritized at about the same level as spec work
[00:24] <rickspencer3> 4. Please expect about half a day every two weeks, at least
[00:24] <rickspencer3> if you have excess capacity, by all means, fix more paper cuts
[00:24] <rickspencer3> </end paper cuts spiel>
[00:25] <rickspencer3> questions, thoughts regarding paper cuts?
[00:25] <TheMuso> Not from me.
[00:26] <rickspencer3> k
[00:26] <rickspencer3> any other business?>
[00:26] <robert_ancell> no
[00:27] <rickspencer3> ok then, that's a wrap!
[00:27] <TheMuso> no
[00:27] <TheMuso> Great.
[00:27] <TheMuso> rickspencer3: Now that I have a calendar, we need to schedule a time to talk about my goals for this 6 months for PDR.
[00:27] <rickspencer3> thanks guys
[00:27] <rickspencer3> thanks awe
[00:27] <awe> rickspencer3: np
[00:27] <rickspencer3> TheMuso: yes
[00:27] <rickspencer3> please do so, your morning/my evening
[00:28] <TheMuso> rickspencer3: Ok will get on that ASAP.
[00:28] <awe> rickspencer3: I also have a question for you whenever you're done with TheMuso
[00:28] <rickspencer3> awe: sure
[00:28] <rickspencer3> shoot
[00:29] <awe> how do bugs in lp get linked to upstream bug trackers?
[00:29] <awe> i couldn't find the obvious button and/or control to do it
[00:29] <bryce> awe, I can answer that
[00:29] <rickspencer3> hehe
[00:29] <rickspencer3> go ahead bryce
[00:29] <bryce> it's kind of non-intuitive, but...
[00:29] <rickspencer3> bryce: have you done this before?
[00:29] <bryce> click "Also affects project"
[00:29] <awe> ok
[00:29] <bryce> rickspencer3, hah, like daily!
[00:30] <awe> i see now
[00:30] <bryce> awe, if you're lucky someone will have specified the default upstream project, and you can just paste in the URL to the upstream bug
[00:30] <awe> lp non-intuitive.  nah..
[00:30] <bryce> awe, if not, then try typing in the name of the upstream bug, or use the Choose link to search for it
[00:31] <awe> bryce: yea, it looks like i can just paste the url
[00:31] <awe> cool
[00:31] <bryce> if it's not in there, then you can register the upstream project - sort of a pain in the ass, but you only have to do it once.
[00:31] <bryce> awesome, then you're set
[00:31] <bryce> awe, a couple things I like to do
[00:32] <awe> shoot
[00:32] <bryce> 1.  in the upstream bug paste in a link to the ubuntu bug, so you can cross-reference later on
[00:32] <awe> already did that...
[00:32] <bryce> 2.  tell the original bug reporter to subscribe to the upstream bug, so they can answer questions directly
[00:32] <bryce> (if the reporter is !you)
[00:32] <awe> ok
[00:32] <awe> the upstream's in bugzilla
[00:32] <awe> ;(
[00:33] <bryce> otherwise you'll be cut-and-pasting questions and answers back and forth, which is extraordinarily mind numbing
[00:33] <awe> oh, i guess there's a cc list
[00:33] <bryce> yeah, but in bugzilla you can't add arbitrary people to the cc
[00:33] <awe> ;(
[00:33] <bryce> guess it's a spam thing *shrug*
[00:33] <rickspencer3> bryce: is that "registered upstream project" available in python-launchpadlib?
[00:33] <awe> well, i've verified that the *code* is busted, so i don't think there'll be a lot more conversation
[00:34] <bryce> rickspencer3, yes, it is called a "watch" in launchpadlib speak
[00:34] <rickspencer3> nice
[00:34] <rickspencer3> so for my triaging button, if watch is not null, can I use python-launchpadlib to create the new bug?
[00:35] <bryce> almost
[00:35] <bryce> actually lpapi allows having *multiple* watches
[00:35] <bryce> so you'd want to check if num(watches) == 0
[00:36] <rickspencer3> in any case, you can use new bug and just copy the info over?
[00:36] <bryce> in theory
[00:36] <rickspencer3> okay
[00:36] <rickspencer3> so I can make seb128's "upstream" button that way
[00:36] <rickspencer3> and if there is no watch, make a picker for the project
[00:37] <rickspencer3> and perhaps create a watch for the package while I;m at it
[01:14]  * TheMuso sighs. Another new piece of code from Lennart that pulseaudio depends on, i.e pulse by lennart depends on another new piece of code from Lennart.
[01:18]  * TheMuso sighs again. This piece of code needs 2.6.31 or better. :S
[01:55] <KenEdwards> Yingying_Zhao, sorry I was late to the call
[06:48] <pitti> Good morning
[06:52] <pitti> bryce: btw, how do you collect feedback about xorg-edgers? people crying in #u-devel when it breaks?
[06:52] <pitti> bryce: (e. g. I dist-upgrade daily, and usually don't have much trouble with it)
[06:52] <pitti> bryce: btw, Jesse sent a patch to fix suspend/resume with KMS, works fine \o/ I applied it to i915 locally for now
[06:52] <pitti> good to see some bug fixing upstream again
[07:12] <bryce> pitti, good to hear
[07:12] <bryce> pitti, we accept bug reports about problems in xorg-edgers
[07:12] <pitti> okay
[07:12] <bryce> indeed, those are the easiest bugs for us to upstream, so we encourage people with troubles to post them to launchpad and we push them from there
[07:12] <pitti> I filed one in the past, but it got fixed upstream fast
[07:12] <bryce> see?  :-)
[07:13] <pitti> well, it got fixed before I even filed it :)
[07:13] <bryce> ahh, even better
[07:13] <Zdra> if I take current live cd, it will boot with kms on intel hw?
[07:13] <pitti> bryce: anyway, seems that most troubles that I still have are with suspend, everything else works just fine
[07:13] <bryce> Zdra, tomorrow's daily live cd should I think
[07:13] <bryce> pitti, great to hear
[07:13] <pitti> bryce: http://bugs.freedesktop.org/show_bug.cgi?id=21719 is my last one
[07:13] <pitti> and Jesse just replied
[07:13] <bryce> pitti, awesome
[07:14] <bryce> pitti, yeah if you feel like filing the bugs straight upstream, go for it
[07:14] <pitti> bryce: extremetuxracer is fun to play now! (~ 30 fps with 800x600)
[07:14] <pitti> bryce: I usually do, yes
[07:14] <Zdra> bryce: ok, thx
[07:14] <pitti> at least this early in the game, when we don't need to track them for release purposes yet
[07:15] <bryce> pitti, having a bug in launchpad as well is useful if there is a patch I should be pulling in
[07:15] <pitti> bryce: right
[07:15] <pitti> bryce: the i915 one is against the kernel, though
[07:17] <pitti> bryce: btw, do you trip over i915.ko patches a lot?
[07:18] <bryce> yep
[07:18] <pitti> bryce: yesterday I figured out how to just build the module without much fuss, so it shoudl be possible to dkmsify it easily
[07:18] <pitti> so it might be useful for xorg-edgers
[07:18] <bryce> yeah I've not done kernel builds so much myself
[07:19] <pitti> bryce: I added the recipe to https://wiki.ubuntu.com/KernelCustomBuild FYI
[07:19] <pitti> took me a while to figure out
[07:19] <bryce> but I've a procedure worked out with the kernel team to pass bugs along to them once a kernel patch is found, and they take it from there
[07:19] <pitti> but I really don't feel like building the entire kernel to test a 915 patch
[07:19]  * bryce bookmarks
[07:27] <pitti> ooh!
[07:27]  * pitti deletes /etc/modprobe.d/i915-kms.conf
[07:46] <bryce> ahh
[07:57] <huats> morning everyone !
[07:59] <huats> robert_ancell: hey
[07:59] <robert_ancell> huats, morning
[07:59] <huats> robert_ancell: evening !
[08:00] <huats> (well for you)
[08:00] <didrocks> morning o/
[08:00] <huats> robert_ancell: just so that you know, I have started a bit on anjuta...
[08:00] <huats> I'll continue today
[08:00] <huats> hey didrocks :)
[08:00] <robert_ancell> huats, sweet, I was making a mess of it :)
[08:00] <didrocks> hey huats, robert_ancell
[08:01] <huats> robert_ancell: don't be too hard with you
[08:01] <huats> so far I haven't seen tons of stuffs to fix...
[08:06] <pitti> hey robert_ancell
[08:06] <robert_ancell> pitti, hey pitti
[08:06] <pitti> bonjour didrocks and huats
[08:07] <didrocks> hey pitti :)
[08:08] <huats> guten morgen pitti
[08:42] <seb128> didrocks, hey
[08:51] <didrocks> hey seb128
[08:51] <seb128> didrocks, hello
[08:51] <seb128> had a good evening and night? ;-)
[08:52] <didrocks> yes, very nice :-) You?
[08:52] <seb128> yes!
[09:02] <chrisccoulson> seb128 - i was trying to figure out last night why the "About Ubuntu" menu item has disappeared from the panel in Karmic
[09:02] <chrisccoulson> it seems ubuntu-docs no longer ships a /usr/share/omf/about-ubuntu/about-ubuntu-C.omf file anymore, which the panel checks for the existence of first
[09:03] <seb128> chrisccoulson, right, I was writting that
[09:03] <seb128> chrisccoulson, I just reviewed your gnome-panel merge looks correct
[09:03] <chrisccoulson> thanks:)
[09:03] <seb128> do you know if 08_clock_applet_event.patch is still needed?
[09:03] <chrisccoulson> i wasnt sure if that was an ubuntu-docs bug or not, or whether we should change 01_layout.patch in gnome-panel
[09:03] <seb128> we dropped it before because I think it was fixed upstream in some way
[09:03] <seb128> but debian still have it
[09:04] <seb128> chrisccoulson, did they rename the file or what?
[09:04] <chrisccoulson> seb128 - i wasnt sure about that patch or not. it seems we dropped it once already, but debian still have it, so i wasnt sure how to justify removing it really, without understanding what it does
[09:04] <seb128> ok
[09:05] <chrisccoulson> debian have some pretty wierd patches to their panel :-/
[09:05] <seb128> indeed
[09:05] <seb128> I've stopped resyncing some packages on debian because they have too many weird changes
[09:06] <chrisccoulson> yeah, i've started to notice that, especially with gnome-session too
[09:20] <pitti> uh, why did the desktop workitems drop yesterday? http://piware.de/tmp/desktopteam-burndown-karmic.png
[09:22] <laxmi> hello
[09:23] <laxmi> I am from Nepal
[09:23] <laxmi> facing a problem
[09:24] <laxmi> r all u sleeping?
[09:24] <pitti> !ask | laxmi
[09:24] <pitti> laxmi: hello
[09:24] <Laney> seb128: I will make a tomboy upload for you, you only had to ask
[09:25] <laxmi> I lost gdm conf file
[09:25] <seb128> Laney, I'm fine syncing on debian if they do upload it one day
[09:25] <Laney> we just have a big problem with lack of DD time
[09:25] <seb128> laxmi, try #ubuntu for user questions
[09:25] <seb128> Laney, well that's why I suggest not blocking on debian ;-)
[09:25] <laxmi> ok
[09:25] <seb128> chrisccoulson, gnome-panel uploaded
[09:26] <chrisccoulson> seb128 - thanks
[09:26] <seb128> chrisccoulson, I'm not sure if your replied about my question on whether they renamed the index
[09:26] <Laney> let's do it then, because meebey is now away for some days
[09:26] <seb128> Laney, ok, let me know if you need sponsoring
[09:26] <Laney> I will do, just give me 2 mins to fix up the changelog
[09:27] <chrisccoulson> seb128 - which index is that?
[09:28] <seb128> chrisccoulson, the about ubuntu one
[09:28] <seb128> you said that the omf is not there in karmic
[09:28] <seb128> has it been renamed or something?
[09:28] <seb128> pitti, should we move empathy back to universe to get the new version built?
[09:29] <chrisccoulson> ah, yes. the about-ubuntu-C.omf file has gone. it hasnt been renamed, but the package is only shipping the translated files now
[09:29] <pitti> seb128: sure, go ahead; I kept it in main for now to make the dependency problems more obvious
[09:29] <seb128> chrisccoulson, do you know if that's a mistake or a choice?
[09:29] <chrisccoulson> i was thinking that the about-ubuntu desktop file would make more sense shipping with ubuntu-docs. then the panel could just check for the existence of the desktop file
[09:30] <seb128> could be
[09:30] <chrisccoulson> i'm not sure if that was a mistake or a design decision in ubuntu-docs
[09:30] <chrisccoulson> i tried to speak to mdke on #ubuntu-devel last night but i dont think he was around
[09:31] <seb128> ok, no hurry to get that changed anyway
[09:32] <chrisccoulson> no problem. i'll try and speak to mdke again later
[09:42] <seb128> slomo, helo
[09:42] <seb128> slomo, do you think you could tweak the gstreamer packages to have gnomevfs ranked lower than gio?
[09:47] <asac> hmm.  Launchpad will be going offline for maintenance in 14 minutes.
[09:53] <seb128> asac, yes announce on the mailing list this week, they switch it to read only for one hour at 9utc
[09:53] <seb128> ie in 6 minutes from now
[09:54] <Laney> bug 381101
[09:55] <Laney> oh I forgot to close it in the changelog
[09:55] <seb128> Laney, thanks
[09:55] <Laney> can you add that before sponsoring? I've got to go for a littl ebit
[09:55] <Laney> back soon
[09:55] <seb128> ok
[10:22] <slomo> seiflotfy1: not sure if that is a good idea atm... the gio plugin is still far from perfect because of misdesign in gio :/ i'll improve the situation a bit for 0.10.24 in the next days though and improve the usage in totem...
[10:22] <slomo> erm, seb128 ---^
[10:50] <slomo> seb128: not sure if that is a good idea atm... the gio plugin is still far from perfect because of misdesign in gio :/ i'll improve the situation a bit for 0.10.24 in the next days though and improve the usage in totem...
[10:51] <seb128> slomo, ok because it takes over gio and breaks rhythmbox right not for example
[10:51] <seb128> ie vfs locations don't work when installed
[10:52] <slomo> seb128: yeah, that's why the gnomevfs package does conflict with meta-gnome in debian ;) that's the worst solution for this problem though, it would've been better if joss just talked to me before doing that...
[10:53] <seb128> ok, I didn't do that change but I though it could be a good idea to rank gio over gnomevfs, fedora does that apparently from what people told on IRC
[10:53] <seb128> brb session restart
[11:09] <seb128> bryce, pitti: is running the xorg edger ppa a good idea for everybody? will those things all land in karmic?
[11:10] <pitti> yes, it's a staging area for karmic, with pretty much upstream git head COTD
[11:10] <seb128> testing current git code seems a nice idea but if that's a different version from karmic or what will land there that seems split of feedback and efforts
[11:10] <pitti> I asked bryce about that some days ago, since that was my concern as well
[11:10] <pitti> he said currently xorg-edgers feedback is preferred, since upstream is more interested in that, and we still do regular karmic updates
[11:11] <seb128> well, upstream is interested in git trunk right
[11:11] <seb128> but that doesn't mean they will roll stable tarballs of those versions before karmic
[11:11] <pitti> we should stop testing xorg-edgers after FF
[11:11] <seb128> or that we will track the unstable versions
[11:11] <pitti> right now they are working towards 2.8.0 final for -intel
[11:11] <seb128> ie I think xorg-edger had intel drivers versions which didn't land to jaunty before jaunty
[11:12] <pitti> right, as I said; it's not a good idea to run it forever, but it's good right now
[11:12] <pitti> for catching regressions early and comparing/reverting to karmic
[11:12] <seb128> I don't like much the idea to run something different than what we ship to our users
[11:13] <pitti> seb128: well, *shrug*, it was just a suggestion, not a "everyone do it now!" :-)
[11:13] <seb128> yeah, I'm just thinking about that
[11:13] <seb128> I feel early testing is good but from an another side we should be working on what users get too
[11:13] <seb128> so I'm a bit torned on what I should be running
[11:13] <pitti> right now, we will definitively get new stuff into karmic, so better to report regressions on the day they happen
[11:14] <seb128> we could as well push those snapshots to karmic proper if we feel they are good enough to be used
[11:14] <pitti> *nod*
[11:15] <seb128> anyway thanks for the replies
[11:15] <seb128> I think I will keep running karmic versions for now so I know where we stand
[11:15] <pitti> seb128: btw, except for the compiz memleak, how is it working for you now?
[11:15] <pitti> performance, artifacts, suspend/resume, KMS, etc.?
[11:16] <seb128> kms turned on after upgrading recently
[11:16] <pitti> suspend with external monitor is broken for me (upstream working on it), otherwise it's pretty much perfect now
[11:16] <seb128> things work fine so far, suspend resume, vt switch
[11:16] <pitti> seb128: right, 2.6.30-10.12
[11:16] <pitti> suspend got fixed for me with a recent upstream patch to i915
[11:16] <pitti> so it seems that didn't affect your 965, only my 945
[11:16] <seb128> I never had performances issues but I'm not using anything which require speed
[11:16] <pitti> (although the fix wasn't 945 specific)
[11:16] <seb128> ie no game, nothing using 3d drawing, etc
[11:17] <pitti> seb128: try extremetuxracer :)
[11:17] <seb128> the only real issue I get is that memory leak
[11:17] <seb128> I've to reboot at least once a day
[11:17] <pitti> we should rename that to "opengl-benchmark" and require everyone to use it for an hour every week :-P
[11:17] <seb128> ;-)
[11:17] <pitti> seb128: right, that could be a mesa memleak, or compiz itself
[11:17] <pitti> seb128: did you get it in jaunty?
[11:18] <pitti> if not, would be worth downgrading compiz to jaunty and check if it's still there
[11:18] <seb128> compiz didn't change really in karmic I doubt it's due to it
[11:18] <seb128> no
[11:18] <pitti>     compiz | 1:0.8.2-0ubuntu8.1 | jaunty-updates | source, all
[11:18] <pitti>     compiz | 1:0.8.2-0ubuntu13 |        karmic | source, all
[11:18] <seb128> we didn't get a new compiz version in karmic
[11:18] <pitti> right
[11:18] <seb128> right, only minor changes
[11:18] <pitti> any upstream code changes in the 6 ubuntu revs?
[11:19] <seb128> one patch from debian re-added
[11:19] <seb128> otherwise they are changes in the packaging or the wrapper
[11:19] <seb128> I doubt it's due to compiz
[11:20] <pitti> okay, so likely mesa then
[11:20] <seb128> grrr, launchpad still down
[11:20] <seb128> do they need to do their update in european work hours?
[11:24] <pitti> seb128: ^ that's why the retracers fell over, so don't worry about the cron mails
[11:24] <seb128> yeah I figured ;-)
[12:51] <Laney> crap
[12:51] <Laney> pngquant is in universe and is a new build-dep of tomboy
[12:53] <pitti> kenvandine: ugh, just tried gnome-scan the first time; that thing is terrible!
[12:54]  * pitti purges and reinstalls xsane
[12:54] <pitti> the UI is totally in the wrong order, and it doesn't even offer the simplest color/contrast corrections
[12:55] <pitti> KenEdwards: is that any better in the current version?
[12:58] <pitti> kenvandine: ^, sorry
[13:00] <seb128> pitti, did you use the karmic version or the ppa one?
[13:29] <seb128> pedro_, ola
[13:29] <pedro_> salut seb128, did you got my email?
[13:29] <seb128> pedro_, yes, we didn't switch yet so I would not do any change for now
[13:29] <pedro_> seb128: i know just thinking in the future there
[13:29] <seb128> especially that rhythmbox is still a cool project and has somewhat responsive upstream now
[13:30] <seb128> well the "move to universe" will not really be revelant with archive reorganization
[13:30] <asac> is there a way to refer to a spec in changelog? so that launchpad parses it somehow?
[13:30] <seb128> and I'm fine having desktop-bugs still looking at it
[13:30] <seb128> asac, launchpad parses it to do what?
[13:31] <pedro_> seb128: alright, that's good to know :-)
[13:37] <asac> seb128: not sure if launchpad has a feature for that ;) ... maybe so that you can get a clickable URL in the launchpad changelog?
[13:37] <asac> but nevermind. i will just use the full url
[13:52]  * asac lunch
[13:53] <seb128> asac, enjoy!
[13:55] <kenvandine> seb128, has anyone reported compiz segfault with the update that came last night?
[13:55] <seb128> dunno I'm not working on compiz nor watching its bugs
[13:55]  * kenvandine searches
[13:56] <seb128> I upgraded yesterday night and got no segfault there but I don't think compiz changed recently
[13:56] <kenvandine> it was in the upgrade last night
[13:57] <didrocks> seb128: do you want a bzr branch for planner?
[13:57] <seb128> no
[13:57] <didrocks> ok, I attach a diff.gz so
[13:58] <seb128> well you can use a +junk on your account if you want
[13:58] <seb128> just don't use the team vcs for it
[13:58] <seb128> ie we can use it for review and upload but we will not keep it there
[13:58] <didrocks> seb128: ok, I prefer to not use it, though, attach diff.gz and debdiff
[13:58] <seb128> alright
[13:58] <seb128> did the version change? otherwise debdiff is enough
[13:59] <didrocks> seb128: yes, upstream version changed
[13:59] <seb128> ok
[13:59] <seb128> diff.gz is good then
[13:59] <didrocks> seb128: I think we have to setup a list of packages we don't want in bzr
[13:59] <didrocks> (maybe, merge it with versions.py)
[14:00] <didrocks> I will give a look at that
[14:00] <seb128> I would say everything on the default page is team maintained
[14:00] <seb128> everything in the + details is not
[14:00] <didrocks> ok, so everything in default page in bzr, the other, not...
[14:00] <seb128> right, something around those lines
[14:00] <seb128> I think we should write an another page for the extra components
[14:01] <didrocks> I agree
[14:01] <seb128> have this list in a public place so other people can edit it
[14:01] <seb128> and have it updated once a day only that's enough
[14:02] <pitti> seb128: karmic
[14:03] <cassidy> seb128: bigon: are you going to provide an empathy-full package or something with geoloc support?
[14:05] <dobey> pitti, seb128, james_w: anyone care to advocate ubuntuone-storage-protocol and ubuntuone-client? :)
[14:06] <pitti> hey dobey; just returned from lunch, it's on my list now :)
[14:07] <kenvandine> pitti, cool :)
[14:07] <seb128> pitti, ok you might want to use the ppa one karmic is outdated by years
[14:08] <seb128> cassidy, nothing planned for that that I know but that seems rather a toy that an useful thing, focus would better be spent on making the im part work correctly ;-)
[14:09] <cassidy> seb128: I agree, but people already starts to ask on #telepathy how to enable geoloc :D
[14:09] <cassidy> we'll probably provide a full package in our PPA
[14:10] <seb128> yeah do that ;-)
[14:10] <seb128> is there a way to split the option in an another binary?
[14:10] <seb128> or is that a build option changing the main binary?
[14:10] <cassidy> bigon: ^ Not sure to understand, I'm not a packaging guy :)
[14:12] <seb128> cassidy, the question is "is geoloc a different .so which can be moved to universe"?
[14:12] <bigon> seb128: no it modifies the binnary and the libs
[14:12] <bigon> s/binnary/binary
[14:12] <seb128> ok, so it's not easy to have it as something not installed by default but available by installing an another binaruy
[14:12] <seb128> binary
[14:14] <bigon> I will upload the full pkg in the ppa and a pkg only with webkit support to the main archive (or at least proposing a patch)
[14:16] <mvo> is launchpad oopsing for somone else too when going to https://launchpad.net/ubuntu/+source/update-manager ?
[14:17] <StevenK> mvo: I get timeout error too
[14:17] <seb128> mvo, yeah, timeout on edge there
[14:21] <bigon> seb128: we want webkit (adium theme) suport in karmic right?
[14:21] <seb128> not sure
[14:21] <seb128> pitti, kenvandine: ^
[14:21] <seb128> webkit is an another issue for CD space
[14:21] <seb128> I'm still watching if GNOME will make it a requirement this cycle or not
[14:23] <kenvandine> seb128, gwibber is going to require it too
[14:23] <kenvandine> i am not ready to do the MIR for that yet though
[14:23] <seb128> gwibber is going to be installed by default?
[14:23] <kenvandine> yes
[14:23] <kenvandine> "social from the start"
[14:23] <seb128> *shrug*
[14:24] <kenvandine> not as it is today... more integrated as a desktop service
[14:24] <seb128> well, I though that would require installer integration etc
[14:24] <kenvandine> nope
[14:24] <kenvandine> nobody liked that idea
[14:24] <seb128> just dropping gwibber in the desktop doesn't seem a big win to me
[14:24] <kenvandine> that isn't what we are doing
[14:24] <seb128> the thing is hard to use and not bring a lot
[14:24] <seb128> ok, I'm waiting to see how things are turning then
[14:25] <seb128> I sort of fail to see what value gwibber is bringing
[14:25] <seb128> we should rather have facebook integration or whatever in the im client
[14:25] <kenvandine> i guess you aren't into social networking :)
[14:25] <seb128> the way pidgin-facebook is doing
[14:26] <kenvandine> that is just for chat
[14:26] <kenvandine> and it isn't reliable :/
[14:26] <seb128> well, I've tried gwibber in jaunty
[14:26] <seb128> and I fail to see how it does something decent out of watching twitter
[14:26] <seb128> ie it doesn't seem a replacement to facebook login right now
[14:26] <kenvandine> it will be
[14:26] <kenvandine> mostly
[14:27] <kenvandine> facebook has added APIs to do most things
[14:27] <seb128> anyway I'm not a web2 addict
[14:27] <kenvandine> :)
[14:27] <seb128> gwibber doesn't seem the right way though
[14:27] <seb128> but I will watch what you guys are doing
[14:27] <seb128> I would have though that integration to desktop components was the way
[14:28] <kenvandine> that is what we are doing, sort of
[14:28] <kenvandine> the config for gwibber will be in gnome-about-me
[14:28] <kenvandine> fusa is going to use it too
[14:28] <seb128> *shrug*, extra gnome-control-center patching without upstream discussion
[14:28] <kenvandine> and hopefully other stuff will jump on the band wagon
[14:28] <seb128> seems you are going the wrong way about that
[14:28] <kenvandine> seb128, we discussed it... they are going to do the work
[14:29] <seb128> rather than getting a proper framework upstreamable you take a random application and try to workaround it
[14:29] <seb128> "they"?
[14:29] <kenvandine> upstream
[14:29] <seb128> I'm sort of part of the upstream team for gnome-control-center (not active recently)
[14:29] <kenvandine> rodrigo_ or dobey :)
[14:29] <seb128> and I've read nothing about that on bugzilla, mailing list or IRC
[14:30] <kenvandine> discussed on irc
[14:30] <seb128> alright
[14:31] <Laney> seb128: what do you want to do about tomboy? promote pngquant or patch that stuff out?
[14:32] <pitti> pngquant is a nice tool
[14:32] <Laney> it's given us quite some space savings
[14:32] <pitti> but what does tomboy do with it?
[14:32] <pitti> ah, for compressing help images, etc.?
[14:32] <Laney> Installed-Size: [-12820-] {+7684+}
[14:32] <Laney> exactly
[14:32] <pitti> indeed
[14:32] <pitti> I use it in my "scan-document" script
[14:32] <pitti> it rocks
[14:33] <pitti> Laney: I'd say, keep and MIR
[14:33] <pitti> 5 MB for the price of 19 kB? deal
[14:33] <Laney> alright
[14:33] <seb128> +1
[14:37] <pitti> kenvandine: was the gwibber integration discussed at UDS with gwibber/g-c-c upstream?
[14:37] <kenvandine> yes
[14:38] <kenvandine> rodrigo_ and dobey, one of them will do the g-c-c work
[14:38] <pitti> and the g-c-c upstream is fine with that?
[14:39] <pitti> kenvandine: as you remember, that's a major point I banged on in the spec, since it seems pretty weird to me
[14:39] <kenvandine> pitti, we really wouldn't want to carry a patch like that... so getting it upstream i very important
[14:40] <pitti> right
[14:47] <pitti> dobey: reviewed
[14:54] <hggdh> seb128, good morning (at least for me), and can we add the Evolution apport hook I wrote to the Evo package?
[15:00] <seb128> hggdh, hi, what does it do exactly? did you open a bug about that?
[15:02] <hggdh> seb128, no, I have not yet opened a bug on it, I decided to ask before; it grabs a bit of non-private data from gconf (disabled plugins, and similar), and anonymises the BTs
[15:02] <seb128> seems a good idea but I need to see the hook before saying if it's good to be added or need changes ;-)
[15:03] <hggdh> seb128, no problems; I will open a bug on it, and add the hook as an attachment; Should I subscribe you?
[15:06] <seb128> subscribe ubuntu-main-sponsors rather
[15:06] <seb128> I'm subscribe to evo so I will get the email
[15:07] <seb128> but the sponsoring list is better to keep track of what need to be uploaded
[15:07] <hggdh> OK, thansk
[15:08] <seb128> hggdh, you're welcome, thank you for working on those changes ;-)
[15:09] <dobey> pitti: hrmm. is it absolutely necessary to split out the python module bits for our daemon and u1sync to python-foo packages? there are other packages that don't (like gnome-app-install)
[15:09] <chrisccoulson> devicekit-disks can monitor smart data on hard disks can't it?
[15:10] <pitti> yes, it does that now
[15:10] <pitti> check out palimsest
[15:10] <pitti> it draws nice graphs and has a nice smart list
[15:10] <chrisccoulson> thanks. will there be something in the users session that can notify of smart failures?
[15:11] <chrisccoulson> the only reason i ask is because someone opened a bug report asking for smartmontools on the default install, but i think that's sort of redundant now in karmic isnt it?
[15:12] <pitti> /etc/xdg/autostart/gdu-notification-daemon.desktop
[15:12] <pitti> I'm not actually sure what that does, though
[15:12] <pitti> chrisccoulson: well, so far we don't install gnome-disk-utility by default
[15:12] <pitti> it's quite a power user tool
[15:13] <chrisccoulson> ah, ok. i'll leave that for now
[15:13] <chrisccoulson> thanks
[15:13] <pitti> I didn't quite make up my mind whether we want it
[15:13] <chrisccoulson> pitti - you're looking at polkit-1 arent you?
[15:13] <pitti> chrisccoulson: but it says "Provides notifications related to disks", so I guess it's something like SMART alerts
[15:13] <pitti> chrisccoulson: yes, it's in NEW
[15:13] <pitti> chrisccoulson: and all the stuff up to new g-d-u is in ubuntu-desktop PPA
[15:13] <pitti> seb128 was working on new gvfs, AFAIK
[15:14] <chrisccoulson> the migration to polkit-1 looks painful. i just looked at the fedora spec, and it seems gnome-session is completely broken with it
[15:14] <pitti> chrisccoulson: if you have stuff depending on pk-1, please upload to the PPA for now
[15:14] <pitti> and we move it over once it's through NE
[15:14] <pitti> W
[15:14] <seb128> pitti, I've 1.3.1 ready locally but it doesn't build in karmic due to devicekit-disks
[15:14] <pitti> seb128: should build against ubuntu-desktop PPA
[15:14] <pitti> chrisccoulson: YM http://fedoraproject.org/wiki/Features/PolicyKitOne ?
[15:14] <seb128> pitti, I can upload the new gvfs to the ppa if you want
[15:15] <chrisccoulson> pitti - yeah, thats the one
[15:15] <pitti> seb128: if it's no effort for you, would be nice for testing
[15:15] <pitti> seb128: and further patch development
[15:15] <seb128> ok, I need to upgrade devicekit-disk locally to the ppa version first to test gvfs locally
[15:15] <seb128> will it break my laptop install? ;-)
[15:15] <pitti> not more than usual
[15:16] <seb128> alright
[15:16] <pitti> NEW processing seems a bit stuck, but I hope I can upload all of that new crack to Karmic soon
[15:17] <pitti> I don't quite like that transition, but seems we're pretty much sold on it anyway
[15:17] <seb128> pitti, I don't do regular archive admin work atm but I can look at desktop changes you upload
[15:17] <seb128> just let me know if you need a review
[15:17] <pitti> and, for you happiness, it drops some old stuff like libsexy, libgnome, etc. :)
[15:18] <pitti> seb128: policykit-1 and policykit-1-gnome should be in NEW: they are by and large package renames only (forks)
[15:18] <pitti> seb128: but don't worry for now, it's not super-urgent
[15:21] <seb128> pitti, ok
[15:25] <mvo> seb128: iif you binary-NEW something anyway, could you please check auto-upgrader-tester too (with a extra pretty please?)
[15:27] <seb128> mvo, I'm not binary-newing anything but update-manager accepted now for you ;-)
[15:28]  * mvo hugs seb128!
[15:28]  * mvo hugs seb128 
[15:28]  * mvo hugs seb128 
[15:28]  * seb128 hugs mvo ;-)
[15:28]  * seb128 hugs mvo ;-)
[15:28]  * seb128 hugs mvo ;-)
[15:28] <mvo> haha
[15:29] <seb128> will auto-upgrade-tester run somewhere regularly?
[15:29] <seb128> and publish logs?
[15:29] <dobey> hmm
[15:29] <mvo> seb128: not currently :( but at least its available via a package now, there is still no DC kvm machine
[15:29] <mvo> and kvm is really the best test environment
[15:30] <mvo> btw, why does bluez-gnome conflicts with gnome-bluetooth?
[15:31] <seb128> mvo, because gnome-bluetooth is basically a bluez-gnome fork and have similar filenames etc
[15:31] <mvo> hm, thanks. right now its kept back on upgrades if you have both installed, what is the right solution here, is one replacing the other in the future? or will the fork be maintained in parallel?
[15:32] <baptiste> bluez-gnome is dead
[15:33] <mvo> baptiste: so we will go with gnome-bluetooth and bluez-gnome will vanish from the archive?
[15:33] <seb128> mvo, gnome-bluetooth will be used in karmic
[15:33] <seb128> mvo, not sure if bluez-gnome will be dropper or demoted
[15:33] <mvo> aha, thanks
[15:34] <mvo> that is fine then, I just want to know about it in the context of upgrades to ensure that the right thing happens
[15:35] <mvo> I see that asac will take care of it, excellent
[15:37] <seb128> yeah
[15:39] <asac> gnome-bluetooth vs. blueman
[15:39] <asac> so far blueman makes the race
[15:39] <asac> seb128: mvo: ^^
[15:39] <asac> but that might change depending on how well gnome-bluetooth catches up on features
[15:40] <seb128> asac, did you consider that gnome-bluetooth is a GNOME thing, ie regular tarballs, translations from upstream etc?
[15:40] <asac> yes. that will get into the equation
[15:41] <asac> i have to talk to gnome-bluetooth dev on what features will be added still
[15:44] <superm1> asac, seb128 looks like translations are done in launchpad for the blueman project too https://translations.edge.launchpad.net/blueman
[15:49] <mvo> asac: thanks, I added a note that we need to ensure clean upgrades to the spec
[15:49] <asac> reconnected
[15:50] <superm1> oh didn't see you disconnected before i said this, will replay. " asac, seb128 looks like translations are done in launchpad for the blueman project too https://translations.edge.launchpad.net/blueman"
[15:50] <asac> 6:41 < asac> i have to talk to gnome-bluetooth dev on what features will be added still
[15:50] <asac> thats what i said ;)
[15:50] <asac> 16:47 < asac> (also have to talk to blueman folks, whats up with their project - e.g. why didnt they contribute to  gnome-bluetooth, will they join efforts in future etc.
[15:51] <asac> 16:47 < asac> )
[15:51] <seb128> superm1, I disconnected after and read that, that's good but doesn't mean they are as active as GNOME translators ;-)
[15:51] <asac> yeah. i asked on both channels now to see whats up
[15:51] <asac> ;)
[16:08] <asac> pitti: do you see any reason why the karmic usbutils/udev/udev-extras combo wouldnt work in jaunty? (I need libgudev for NM ppa)
[16:08] <pitti> asac: should work fine, it's in https://edge.launchpad.net/~pitti/+archive/ppa
[16:09] <pitti> asac: people tested it for the keymap stuff
[16:09] <asac> pitti: so i dont need the udev part?
[16:10] <pitti> no, jaunty's udev should work fine
[16:10] <asac> great
[16:10] <asac> thx
[16:10]  * asac copies to ppa
[16:19] <dobey> pitti: did you miss my question re: python packaging earlier?
[16:20] <pitti> dobey: apparently I did; my keyboard broke and I had to reboot
[16:20] <kenvandine> pitti, mad typist?
[16:20] <dobey> pitti: hrmm. is it absolutely necessary to split out the python module bits for our daemon and u1sync to python-foo packages? there are other packages that don't (like gnome-app-install)
[16:21] <pitti> dobey: I really really recommend it; you'll go nuts later if you don't, as soon as you want to support KDE
[16:21] <pitti> also, I like to follow the Python policy
[16:21] <kenvandine> pitti, what does that have to do with python-?
[16:21] <kenvandine> pitti, i agree though... just don't see how that affects supporting kde :)
[16:22] <pitti> kenvandine: if you lump everything together in one package, you have to replicate half of it for KDE
[16:22] <pitti> otherwise you'd pull in all the nautilus/gtk dependencies
[16:22] <kenvandine> oh... well shouldn't that mean the nautilus bits get built into ubuntuone-client-gnome?
[16:22] <kenvandine> oh... nevermind
[16:22] <pitti> and shipping u1sync/python modules in two different pacakges cries for trouble, too
[16:22] <kenvandine> i see
[16:22] <pitti> kenvandine: that's exactly what I was proposing :)
[16:23] <pitti> (more or less, yes)
[16:23] <dobey> well, the u1sync and its modules can probably be in one package.
[16:24] <pitti> dobey: right
[16:25] <pitti> one python-ubuntuone-client and one ubuntuone-gnome package, or so (I'm not fussed about the names)
[16:32] <dobey> right, will be something similar
[16:33] <huats> seb128: as you know the anjuta stuff has been uploaded
[16:33] <chrisccoulson1> would someone mind inviting me to try ubuntuone? :)
[16:33] <huats> so if you have anything to be done....
[16:33] <seb128> huats, excellent
[16:33] <huats> just say it :D
[16:33] <seb128> huats, looks on versions.html?
[16:33] <huats> (I am looking at the page and I don't really something to do)
[16:34] <Laney> hit the + for more
[16:35] <huats> Laney: :D
[16:35] <huats> thanks :D
[16:35] <huats> I have left for a few weeks... and now there are lots of changes !
[16:35] <Laney> \o
[16:36] <Laney> huats: there's always the huge sponsor queue too
[16:36] <huats> Laney: sure
[16:37] <huats> Laney: to be honnest I'd like to do a few uploads til the end of the week
[16:37] <huats> next week I'll try to do some sponsoring
[16:37] <Laney> I want to start doing sponsoring more often
[16:37] <Laney> maybe sponsor-5-a-day
[16:38] <huats> Laney: any reason why you haven't updated glom ?
[16:38] <Laney> no
[16:38] <huats> or was it just the lack of time ?
[16:38] <huats> ok
[16:38] <Laney> I think I started it
[16:38] <Laney> please feel free
[16:39] <huats> ok will do then
[16:39] <Laney> huats: I was going to convert to a dh7 style rules file
[16:39] <Laney> that should be fun to do
[16:54] <huats> can someone merge lp:~christophe.sauthier/glom/ubuntu on the desktop-team branch ?
[16:54] <huats> thanks in advance
[16:54] <huats> (it is the first import)
[16:54] <huats>   
[18:03] <ccheney> bryce: what should i do about reporting the intel kms resolution bug? It seems to still not be fixed, I mentioned seeing it at UDS, but the intel guy said it was fixed already, i guess it still hasn't made it into the kernel tree
[18:04] <ccheney> bryce: should i report it against the intel video driver or the kernel, etc?
[18:04] <ccheney> it seems to be related to seeing two ghost connected DVI ports
[18:07] <ccheney> bryce: and is there any way to force the resolution for KMS to the correct one?
[18:13]  * ccheney can no longer maximize anything since it draws it off screen :-\
[18:15]  * ccheney tries to find place on wiki on how to disable KMS
[18:18] <bryce> ccheney, boot with i915.modeset=0 I think
[18:18] <ccheney> bryce: ok i'll try that out
[18:19] <ccheney> bryce: do you know if there is already a report about the x200 intel 4500 bug where it detects the extra DVI ports and sets the internal display to the 'ghost' resolution?
[18:20] <bryce> ccheney, for reporting bugs, you can report them against both linux and -intel to get maximum attention; I'll upstream ones filed against -intel, ultimately the kernel is what'll need fixed though
[18:20] <bryce> ccheney, yeah, that sounds like a missing quirk bug
[18:20] <ccheney> ok
[18:20] <bryce> ccheney, still should be reported tho
[18:20] <ccheney> bryce: i don't recall his name but he mentioned already knowing about the bug i showed him at UDS
[18:20] <ccheney> but yea i'll get it reported to make sure it is fixed
[18:21] <bryce> jesse barnes (jbarnes)
[18:21] <bryce> he hangs out on #ubuntu-x if you want to chat with him
[18:21] <ccheney> yea that is him :)
[18:21] <ccheney> ok
[18:27] <falconseye> hola
[18:27] <falconseye> hello
[18:31] <ccheney> bryce: what do i do to get the full xrandr dump that ubuntu-bug does?
[18:32] <ccheney> bryce: i was going to include what xrandr reports also when mode setting is off
[18:32] <pitti> good night everyone
[18:32] <kenvandine> hey pedro_
[18:32] <kenvandine> later pitti
[18:32] <kenvandine> pedro_, wanted to talk butterfly hug day
[18:33] <falconseye> hello someone can help me get surround sound on my toshiba x205-s9800 with ubuntu?
[18:33] <pedro_> kenvandine: hello, sure
[18:34] <kenvandine> pedro_, when do you think we can do it?
[18:34] <jcastro> pedro_: can we do it like, asap?
[18:34] <jcastro> pedro_: lots of people complaining about MSN sucking but not many bugs
[18:34] <pedro_> kenvandine: i was thinking about that, since we're going to guadec
[18:34] <jcastro> I'd like to make people go file bugs
[18:35] <pedro_> jcastro: asap for me would be like in two weeks from now on
[18:35] <kenvandine> pedro_, we need a nice list of bugs to work on
[18:35] <kenvandine> and we might be able to get some resources onto fixing them
[18:35] <jcastro> pedro_: dang.
[18:35] <jcastro> pedro_: so, what are you doing this friday? :p
[18:35] <kenvandine> i was hoping for next week :)
[18:35] <pedro_> since we're going to be traveling for the desktop summit
[18:35] <pedro_> i can ask to someone else to run it though
[18:36] <jcastro> pedro_: can we jam one in next week?
[18:36] <jcastro> pedro_: that would at least get us a bunch of bugs when were are at guadec with upstream
[18:36] <pedro_> Tuesday perhaps?
[18:36] <kenvandine> that would be great
[18:37] <jcastro> yes.
[18:37] <kenvandine> then we can have bugs to work on while at guadec
[18:37] <jcastro> pedro_: thanks, I know this is last minute.
[18:37] <kenvandine> pedro_, we really appreciate it
[18:37] <pedro_> ok all set then I'm going to create the page and all that and let you guys know for a quick review
[18:37] <kenvandine> thx
[18:37] <jcastro> perfect
[18:37] <pedro_> my pleasure ;-)
[18:41] <ccheney> bryce: bug 391720
[19:27] <jcastro> pedro_: linking to this page from the hugday page would be useful: http://live.gnome.org/Empathy/Debugging
[19:54] <pedro_> jcastro: will do it
[20:00] <pedro_> nice the telepathy ppa was updated with empathy 2.27.3
[20:00] <pedro_> and butterfly there is 0.3.4-1
[20:00] <pedro_> will promote that for testing on the hug day
[20:05] <kenvandine> great
[20:05] <kenvandine> pedro_, i assume all for jaunty?
[20:05] <pedro_> kenvandine: yeap on jaunty
[20:05] <kenvandine> awesome
[20:09] <bigon> kenvandine: I will drop the indicate patch as cassidy asked me
[20:09] <kenvandine> i have a fix for that
[20:09] <kenvandine> for the potential crasher anyway
[20:40] <kenvandine> bigon, i have a debdiff that should fix the issue cassidy was concerned with
[20:40] <kenvandine> with some help from tedg
[20:42] <kenvandine> bigon, http://pastebin.ubuntu.com/203105/
[20:42] <tedg> For the record, I think it's more likely to be a memory leak than a crasher.
[20:42] <kenvandine> tedg, cassidy said it should be a critical... but i wasn't getting that
[20:44] <bigon> I will prepare a patch
[20:44] <bigon> do I build with webkit or not?
[20:44] <kenvandine> i think so :)
[20:44] <kenvandine> other things will drag that on the CD too
[20:45] <bigon> k
[20:45] <tedg> kenvandine: Oh, I get it.  If the indicator gets activated, you'll still get the signal.  And then bad stuff will happen.  But, it seems that the cb_data needs to be free'd somewhere as well, and I'm not seeing that.
[20:48] <tedg> It needs to get removed from the hash_table as well.