[00:11] <chrisccoulson> hi RAOF - you didn't spend any time looking at the gjs build failure did you?
[00:12] <RAOF> chrisccoulson: I did, but then punted it to michag
[00:12] <chrisccoulson> heh, it looks like it's been punted to me now then ;)
[00:12] <chrisccoulson> i just wanted to make sure i wasn't duplicating effort there
[00:13] <RAOF> Right.  I'll describe what I know for you then.
[00:13] <RAOF> It seems there's probably two bugs; 1) gjs just plain segfaults in mozjs on armel whenever you ask it to do anything.
[00:14] <chrisccoulson> the bug i was looking at was the test-suite failure due to a leaked object
[00:14] <RAOF> 2) the behavioural ABI for mozjs on i386 seems to have changed when the JIT is enabled - it seems that at least one finaliser isn't called when you destroy the context.
[00:14] <RAOF> Right.  That's the second one.
[00:14] <RAOF> That can be worked-around by just disabling the JIT on i386; the armel one needs something more.
[00:14] <chrisccoulson> ok, i'll spend some time trying to figure that out
[00:15] <RAOF> We could also just disable the test-suite; I'm not sure how critical the leak is for i386
[00:15] <chrisccoulson> i'd rather not disable JIT on i386 if i can avoid it, as it could be a real problem
[00:15] <chrisccoulson> yeah, i'm not surehow big a problem it is really :-/
[00:16] <RAOF> Armel isn't a simple matter of disabling jit, sadly :/
[00:16] <RAOF> (Otherwise I would have uploaded packages that just disable the jit on armel & i386)
[00:19] <dutchie> looks like it's built alright
[00:20] <humphreybc> gah... compiz + cursors
[00:21]  * dutchie pushes to LP
[00:25] <rickspencer3> kenvandine, back around yet?
[00:33] <humphreybc> compiz will ONLY let me use compiz mega-large black cursor
[00:43] <multi-x> hi guys. in the upcoming 10.04 lynx, any idea if the gdm will upport multiseat-X, and if not, if it will be possible under KDE?
[00:43]  * RAOF is unsure what you mean by “multiseat X”
[00:44] <multi-x> RAOF: using a single machine with multiple seats via multiple video cards, USB keyboards & mice: https://help.ubuntu.com/community/MultiseatX
[00:45] <multi-x> it's (apparrently) been a standard feature of X for a very long time, up to gdm 2.20, but got bloken under the recent 2.28 rewrite
[00:46] <RAOF> Ah.  That version of multiseat.
[00:46] <RAOF> I don't know; try it with a livecd?
[00:47] <multi-x> been doing some work on it recently for implementation in schools, offices & home (with kids). especially now that desktop virtualization is becoming a reality, I can remote-X/NZ/VNC/RDP to a destop in a VM
[00:48] <multi-x> RAOF: ???? don't understand what you mean by liveCD. it's an extremely complex setup, initially, so I'll loose all settings between reboots
[00:48] <multi-x> well, let me then rather ask: what version of gdm is rolling out with 10.04?
[00:49] <RAOF> 2.30
[00:49] <humphreybc> where are pointer themes stored?
[00:49] <multi-x> RAOF: thanks
[00:49] <RAOF> You could do it with a liveusb, where settings can be stored.
[00:50] <RAOF> I think you'll also be fighting ConsoleKit, unless you've already worked that out.
[00:55] <multi-x> RAOF: yip. it may actually be an asset in this case, though
[00:59] <chrisccoulson> we don't have multiseat support in consolekit in ubuntu
[01:00] <chrisccoulson> there is a lot of work happening in separate branches of GDM and consolekit to support true multi-seat
[01:01] <multi-x> chrisccoulson: thanks for that. could you please elaborate?
[01:02] <chrisccoulson> well, the multi-seat branch of consolekit is here: http://cgit.freedesktop.org/ConsoleKit/commit/?h=multi-seat
[01:02] <chrisccoulson> and i think the gdm work is here too: http://git.gnome.org/browse/gdm/tree/daemon?h=multi-stack
[01:02] <chrisccoulson> oops, sorry, http://git.gnome.org/browse/gdm/commit/?h=multi-stack
[01:04] <multi-x> chrisccoulson: what does that exactly mean? my (poor) understanding of konsolekit is a way of abstracting the user from the system, similar to what was done with PulseAudio, so that the user can use services on a server without actually being present. (client/server). this may be an oversimplfication, but seems compatible with milti-seat
[01:05] <chrisccoulson> consolekit is for primarily for tracking sessions
[01:05] <chrisccoulson> but currently, it only supports one local seat (which all local users are added to)
[01:06] <chrisccoulson> but with multi-seat, you will be able to define multiple seats and assign hardware to those
[01:06] <multi-x> so, future/beta implementations of consolekit would be very well-suited to multi-seat, and ease the setup & config thereof?
[01:06] <chrisccoulson> that is my understanding of how multi-seat will work anyway ;)
[01:06] <chrisccoulson> yes
[01:07] <multi-x> sweeeeeet!
[01:07] <multi-x> it was pretty difficult to get it working in the first place. any help is appreciated....
[01:15] <dutchie> can someone review https://code.edge.launchpad.net/~jshholland/ubuntu/lucid/poppler/backport-anti-alias/+merge/22511 please?
[01:17] <chrisccoulson> dutchie, wasn't seb128 reviewing that?
[01:18] <dutchie> he seems to have gone to bed
[01:18] <chrisccoulson> yeah, you would be better off asking him to have a look at it tomorrow
[01:19] <dutchie> shall I subscribe him to the merge proposal?
[01:20] <chrisccoulson> you might be better off just pinging him tomorrow. i'm not sure we use the lp:ubuntu branch for the poppler packaging
[01:26] <multi-x> thanks guys. will keep an eye out for gdm+consolekit+multiseat
[02:29] <LaserJock> kenvandine: when you get back give me a ping
[04:09] <ccheney> kwwii: any idea about the status of the OOo splash change?
[04:18] <ccheney> rickspencer3: ping, you happen to be around?
[04:21] <rickspencer3> ccheney, 'sup?
[04:24] <rickspencer3> RAOF, thanks for fixing the * bug in f-spot
[04:24] <rickspencer3> :)
[04:25] <rickspencer3> I love that turn around!
[04:25] <ccheney> rickspencer3: i haven't heard anything back from the art team about the new splash, but we already got the logo a while back and i had sent it to ken, any idea what i should do?
[04:26] <rickspencer3> ccheney, what specifically is blocking you?
[04:26] <rickspencer3> and does the logo contain the new wording?
[04:26] <ccheney> the logo's are just the oracle logo itself it has to be combined with the artwork from ubuntu art team to produce the final product
[04:27] <ccheney> so right now all i have is the oracle logo and haven't heard anything back from the art team yet
[04:27] <rickspencer3> ccheney, was there not some legalize that need to be refined as well?
[04:27]  * ccheney double checks
[04:28] <rickspencer3> ccheney, in any case, can you please send an email to kwii reminding him that you need this?
[04:28] <rickspencer3> and cc ivanka and I?
[04:28] <ccheney> there are a few minor changes to the copyright file and update in the wiki to do, but the main blocker is the artwork
[04:28] <ccheney> ok will do
[04:28] <rickspencer3> ccheney, I'll ask about the wording right now
[04:29] <ccheney> once we get the artwork from the art team we have to show it to oracle to get approval but that shouldn't take too long, might miss apr 1 though (2 days from now)
[04:34] <ccheney> rickspencer3: ok sent
[04:34] <rickspencer3> thanks ccheney
[04:34] <rickspencer3> I also asked Amanda about the wording
[04:35] <rickspencer3> I'll keep you posted
[04:35] <ccheney> rickspencer3: ok thanks
[04:35] <rickspencer3> wow, I installed UNE fresh from the daily today, and now have 109M of updates!
[04:36] <ccheney> rickspencer3: if we get the images and oracle/amanda approval by sunday it should be ok assuming its processed during the freeze
[04:36] <rickspencer3> ccheney, it depends where the hold up is
[04:36] <ccheney> it takes about 2 days to build on arm, but the arm buildds have been apparently having issues and couldn't build the last upload :-\
[04:36] <ccheney> yea
[04:37] <rickspencer3> If they got us the stuff by April 1, I feel duty bound to do as promised
[04:37] <ccheney> the last upload arm couldn't build wasn't materially different from the previous one that did work afaict
[04:38] <rickspencer3> ccheney, is a rebuild actually required to replace artwork?
[04:38] <rickspencer3> that seems rather, uh, old fashioned
[04:40] <ccheney> yea, well its part of the build process for the filename to use which currently has sun in it and also the fact that the artwork itself is in the openoffice.org source instead of in a separate theme package, etc
[04:41] <ccheney> also they are planning on changing up the color and location of the progress bar which requires a code patch
[04:41] <ccheney> its a very minor patch but is more than just replacing the graphic for that part
[04:51] <rickspencer3> thank goodness I'm getting the new aislerot
[05:00] <rickspencer3> RAOF, I see you also liked bug #536925 yesterday !
[05:18] <rickspencer3> bryceh, are you around?
[05:23] <Sarvatt> rickspencer3: guessing you have a problem after the updates? tjaalton just uploaded the evdev and synaptics packages to fix it if so
[05:24] <rickspencer3> Sarvatt, a slight problem, yes
[05:24] <rickspencer3> the touchpad is sensitive in the button area on my dell mini 10v again
[05:24] <rickspencer3> it is quite enraging
[05:25] <rickspencer3> Sarvatt, is this the regression you are mentioning? I just did a fresh install of UNE daily today, so wasn't an update
[05:25] <tjaalton> but "working", so it's not the same issue :)
[05:25] <rickspencer3> tjaalton, yes
[05:25] <rickspencer3> if by "working" you mean make me want to throttle the person who created such a diabolic device
[05:25] <rickspencer3> ;)
[05:25] <rickspencer3> but in fact, it does point the mouse and such
[05:26] <tjaalton> I'm afraid that people upgrading to the new xserver will be disappointed until -evdev/synaptics are released
[05:26] <tjaalton> but I need someone to shove those past the build queue
[05:26] <rickspencer3> anyway, I assigned a bug to tseltiot
[05:26] <rickspencer3> tjaalton, oh? will there be breakages on touchpads tomorrow?
[05:26] <Sarvatt> rickspencer3: http://sarvatt.com/downloads/xorg.conf.d/ has the steps to fix it if you need the fix ASAP
[05:27] <tjaalton> rickspencer3: well that's what Sarvatt suggests, though we took measures to get around that..
[05:27] <rickspencer3> I'm confused (which is normal)
[05:27] <tjaalton> the new xserver with xorg.conf.d/inputclass backports
[05:28] <rickspencer3> I'm thought tseliot patched the synaptics driver for this sensitiviy in the button area usability nightmare
[05:28] <rickspencer3> like a 6 months ago
[05:28] <rickspencer3> Sarvatt, but thanks for the xorg.conf files
[05:28] <rickspencer3> I'll use those if it comes down to it
[05:28] <tjaalton> should just work with the input drivers exporting 'x11_driver' from the udev rules (included a patch for that in the xserver), but apparently doesn't
[05:29] <rickspencer3> JumpyCursorThreshold - lolz
[05:29] <Sarvatt> tjaalton: ah actually I believe it may be working for him but the quirks for his model aren't
[05:30] <tjaalton> Sarvatt: but I don't think he's got the new xserver yet
[05:31] <rickspencer3> thanks gents
[05:31] <rickspencer3> gots to run
[05:31] <rickspencer3> ttyt
[05:33] <Sarvatt> rickspencer3: can you pastebin your /var/log/Xorg.0.log?
[05:34] <Sarvatt> rickspencer3: ah nevermind, you need both the udev rule and the xorg.conf.d snippet for the quirk to work which you dont have yet, hopefully it'll be built soon
[05:38] <RAOF> rickspencer3: I can reproduce the “Save as” freeze, too, but it looks like the problem's in GTK# rather than f-spot.  Freezing is a pretty obnoxious behaviour for a save dialog!
[06:08] <rickspencer3> RAOF, can you seed the dialog with a name to at least mitigate the bug a tiny bit?
[06:09] <RAOF> rickspencer3: I *do* seed the dialog with a name - are you additionally not seeing a default filename?
[06:09] <rickspencer3> RAOF, correct
[06:11] <rickspencer3> RAOF, http://imgur.com/LFvxv
[06:13] <rickspencer3> Sarvatt, fwiw, here's bug #552317
[06:14] <rickspencer3> you can reassign, comment, etc... as you like
[06:23] <Sarvatt> rickspencer3: thanks, it's definitely just the quirk not getting applied and the xserver-xorg-input-synaptics with the fix just finished building - https://edge.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/1.2.2-1ubuntu1/+build/1593577
[06:24] <rickspencer3> thanks Sarvatt, looking forward to getting that tomorrow
[06:26] <Sarvatt> you can just run this in a terminal to fix it until the upgrade is there by the way - synclient JumpyCursorThreshold=90 AreaBottomEdge=4100
[06:30] <rickspencer3> thanks Sarvatt
[06:30]  * rickspencer3 copies and pastes
[06:56] <RAOF> Oh, dear.  That's actually a GTK+ bug.
[06:56] <RAOF> That *will* hit people.
[06:56] <RAOF> Over the head, with swords.
[07:07] <pitti> Good morning
[07:08] <RAOF> pitti: Good morning
[07:28] <pitti> hey RAOF, how are you?
[07:29] <RAOF> Good.  Yourself?
[07:30] <RAOF> I've been having fun finding bugs that go all the way down the stack :)
[07:43] <pitti> RAOF: yeah, just saw the save as dialog bug..
[07:43] <pitti> weird that  this hasn't been noticed much earlier
[07:45] <RAOF> Yeah.  I would have thought that *someone* would complain loudly that they accidentally hit “save” without a filename and it froze the program without saving.
[07:50] <pitti> RAOF: reproduces perfectly in gedit
[07:52] <RAOF> And in the trivial test program.
[07:52] <RAOF> (I trust :))
[08:13] <didrocks> good morning
[08:26] <kenvandine> good morning didrocks
[08:26]  * kenvandine goes to get some sleep, good night :)
[08:26] <didrocks> have a good night kenvandine!
[08:28] <mvo> night kenvandine
[08:35] <kenvandine> hey aquarius
[08:36]  * kenvandine really goes to crash now
[08:37] <aquarius> hey kenvandine
[08:40] <seb128> hello there
[08:40] <pitti> bonjour seb128
[08:40] <seb128> hello pitti
[08:41] <seb128> how are you?
[08:42] <pitti> I'm pretty good, thanks; you?
[08:42] <pitti> trying to finish off the db4.7 deprecation
[08:44] <pitti> seb128: btw, gnome-panel amd64 binaries still aren't published, which caused some FTBFS; I asked #soyuz, and they sorted it out (they think)
[08:44] <seb128> pitti, I'm great thanks
[08:44] <pitti> so we need to wait for the publisher to finish
[08:44] <seb128> ok
[08:44] <pitti> then we can give back stuff
[08:44] <pitti> didrocks: ^ FYI (if you saw amd64 FTBFS)
[08:44] <seb128> I tried to give some builds back yesterday
[08:44] <seb128> armel is wracked
[08:44] <didrocks> hey seb128, pitti
[08:44] <didrocks> pitti: thanks for the notice :)
[08:44] <seb128> salut didrocks
[08:45] <pitti> seb128: hm, ok, they are still investigating
[08:45] <seb128> didrocks, did you start on any update today?
[08:45] <didrocks> seb128: not yet, still finishing triaging email, I'll then (almost finished)
[08:45] <seb128> k
[08:45] <seb128> I'm doing gnome-desktop and libgnome-keyring now
[08:47] <didrocks> ok
[08:48] <seb128> didrocks, bug #552132
[08:49] <seb128> could you investigate?
[08:49] <seb128> it started recently
[08:49] <seb128> not sure if that's the update or your changes
[08:49] <baptistemm> Ola !
[08:49] <seb128> but since you are not one who touch it ;-)
[08:49] <seb128> salut baptistemm
[08:49] <didrocks> seb128: yeah, that's on what I am in fact :)
[08:50] <seb128> thanks
[08:52] <baptistemm> are the retracers down ?
[08:53] <pitti> seb128: gnome-panel should be good now
[08:53]  * pitti gives back gdm
[08:54] <seb128> baptistemm, they keep going up and down why?
[08:56] <seb128> pitti, I'm looking to gnome-menus caching issues
[08:56] <seb128> pitti, not sure why you filtered non displayed items out
[08:56] <pitti> seb128: well, that was the point of it?
[08:56] <seb128> pitti, it's what create bug #542300
[08:57] <pitti> gnome-menus filters them out anyway?
[08:57] <seb128> pitti, those are usually listed as hidden in editor
[08:57] <seb128> and you can check those
[08:57] <seb128> ie enabling by clicking
[08:57] <pitti> and without the pre-filtering, the cache would get twice as big, and become useless
[08:57] <seb128> but with your cache not seeing those at all you can't do that now
[08:58] <seb128> well NoDisplay means not displayed by default
[08:58] <seb128> the editors should still list those are not displayed
[08:59] <seb128> pitti, quite some users enable the gnome-control-center item in the system menu this way for example
[08:59] <pitti> seb128: the bug description of that is very weird, though; the caching certainly doesn't cause _all_ of those to go away; most people have the capplets/system tools, etc?
[08:59] <seb128> well as you commented
[08:59] <seb128> it filter out all the NoDisplay=true
[08:59] <seb128> they are not in the cache
[08:59] <seb128> so they don't exist for the editors
[09:00] <seb128> but they should
[09:00] <seb128> lot of users tweak their menus and active things we don't display by default
[09:00] <seb128> gnome-control-center
[09:00] <pitti> ok, so some of them should appear (like "control center"), and some others shouldn't (like apport, gdebi, etc.)
[09:00] <seb128> eog
[09:00] <seb128> gconf-editor
[09:01] <seb128> I don't think you should change the spec semantic with your cache
[09:01] <pitti> can we make a difference between "do not ever show this" (gdebi/apport which are mime links) and "we just hide it by default"?
[09:01] <seb128> things with no categories would not be listed
[09:01] <seb128> well, I don't understand why you want to change the semantic
[09:02] <seb128> the cache should do what we had before but in a faster way
[09:02] <pitti> ah, ok; so NoDisplay=True should be in the cache, but not empty categories and non-matching OnlyShowIn, right?
[09:02] <seb128> I'm not sure about that and the sideeffect that can have
[09:02] <seb128> I think we should just list all entries installed
[09:02] <seb128> the way it works without cache
[09:02] <pitti> oh, we shouldn't change the semantic _in_ the caching patch
[09:02] <seb128> to avoid breaking softwares relying on that behaviour
[09:02] <pitti> I was just pointing out that there are desktop files which should not EVER be shown
[09:03] <seb128> right
[09:03] <seb128> but gnome-menus take care of that
[09:03] <pitti> I get tons of bugs "I enabled the apport.desktop and clicking on it doesn't work"
[09:03] <pitti> I regularly close them with "don't do that"
[09:03] <seb128> I don't think we should duplicate that work by tweaking what goes in the cache or not
[09:03] <pitti> yes, as I said, it's not the cache patch which should enforce that
[09:03] <seb128> well then fix gnome-menus or the desktop entry you use
[09:03] <seb128> it does right now though
[09:03] <seb128> it's all the
[09:04] <pitti> but if we can mark those differently, then the cache doesn't need to even contain the ones which aren't ever displayed
[09:04] <pitti> and my question was if there's a flag to mark them differently
[09:04] <seb128>     if de.getNoDisplay() or de.getHidden():
[09:04] <seb128>         return
[09:04] <pitti> e. g. /usr/share/applications/apport-gtk-mime.desktop currently uses NoDisplay=true
[09:05] <pitti> which apparently isn't strong enough
[09:05] <seb128> right
[09:05] <seb128> but it should be the cache enforcing that policy
[09:05] <pitti> (should "not")?
[09:05] <seb128> it means gnome-menus with and without cache doesn't behave the same
[09:05] <seb128> yes sorry
[09:05] <pitti> yes, we agree
[09:05] <seb128> should *not*
[09:05] <seb128> ok
[09:05] <seb128> can I drop those filters in the cache code then for lucid?
[09:06] <pitti> http://lists.freedesktop.org/archives/xdg/2009-May/010389.html
[09:06] <pitti> seb128: yes, I guess we have to
[09:06] <pitti> seb128: well, I don't know about "Hidden"
[09:06] <pitti> but certainly getNoDisplay()
[09:06] <seb128> I would drop everything
[09:07] <seb128> reading the cache should be the same than reading the directory content
[09:07] <seb128> then we can fix issues like the apport one as they should
[09:07] <seb128> ie by updating the desktop or fixing gnome-menus code
[09:07] <pitti> ok, seems that the spec itself doesn't really support that :(
[09:07] <seb128> no it doesn't
[09:07] <seb128> we might be able to hack around by having no categories I think
[09:08] <seb128> see gnome-theme-installer.desktop
[09:08] <pitti> seb128: we don't use "Hidden" in /usr/share/applications/ anyway, so you can as well drop the check
[09:08] <seb128> right
[09:08] <seb128> Hidden means hidden from menus and mimetypes too
[09:09] <seb128> ie that's equivalent of not installed
[09:09] <seb128> there is no point to do that in system entries
[09:09] <seb128> that's good to delete some from the user config though
[09:09] <seb128> pitti, ok, doing that, thanks
[09:09] <seb128> pitti, but see gnome-theme-installer.desktop for your apport bug
[09:11] <pitti> ah, changing it to "Categories=GNOME;GTK;" works indeed
[09:11] <pitti> i. e. it doesn't appear any more in alacarte
[09:11] <pitti> seb128: thanks!
[09:11]  * pitti commits
[09:11] <seb128> pitti, you're welcome
[09:11] <seb128> pitti, thanks for taking the time to clarify that with me there ;-)
[09:17] <seb128> didrocks, yet another bug eating the dust thanks to you ;-)
[09:17]  * seb128 hugs didrocks
[09:17] <seb128> thanks for fixing that crasher
[09:18]  * didrocks hugs seb128, was my fault :)
[09:19]  * didrocks gives back glade, gnome-menus, gnome-utils on amd64 and back on update
[09:27] <pitti> nice, libdb4.7 is 653 kB; which will now drop from the CDs
[09:28] <pitti> 20% of a langpack :)
[09:28] <seb128> how much do we need to get an extra one back?
[09:28] <seb128> ie are those the first 20%?
[09:28] <pitti> haven't checked yet
[09:28] <seb128> or do we have like 80% space now
[09:28] <pitti> CD builds were broken in the last couple of days
[09:29] <seb128> I guess the GNOME 2.30 uploads don't help there
[09:29] <pitti> nope
[09:29] <TheMuso> pitti: If  you are working seeds atm, could you cut a langpack or two from powerpc? The desktop CD is oversized.
[09:29] <didrocks> seb128: taking seahorse and seahorse-plugins
[09:30] <TheMuso> Otherwise I can take care of it myself.
[09:30] <seb128> didrocks, thanks
[09:30] <pitti> TheMuso: I'm not, it's all your's
[09:30] <pitti> TheMuso: I just did some libdb4.7 -> 4.8 migration
[09:30] <TheMuso> oh ok
[09:30] <TheMuso> thanks
[09:32] <pitti> seb128: investigating apport retracer crashes now
[09:32] <seb128> pitti, thanks
[09:32] <pitti> seb128: the amd64 one stumbled over a broken bug report again (https://bugs.edge.launchpad.net/ubuntu/+source/nspluginwrapper/+bug/551044)
[09:32] <pitti> -> oopses
[09:32] <seb128> pitti, do you have an opinion on when to turn apport off?
[09:32] <seb128> same for the lpi "report a bug"
[09:33] <pitti> seb128: apport> right after the release candidate, traditionally
[09:33] <pitti> lpi> can we do a test drive (package in ubuntu-desktop with that disabled)?
[09:33] <pitti> and then disable it aronud that time as well?
[09:34] <seb128> pitti, well it's easy, it's one line to comment in lpi
[09:34] <seb128> ok
[09:34] <pitti> seb128: what do you think? you want to do it later?
[09:34] <pitti> erm, eralier?
[09:35] <seb128> no, that seems fine
[09:35] <pitti> seb128: right, but we did the apport disabling a lot of times now
[09:35] <pitti> seb128: I'm slightly worried that disabling the menu entry has some side effects
[09:35] <seb128> you want me to upload that before beta2?
[09:35] <pitti> like apps trying to change the menus after calling lpi, etc.
[09:36] <pitti> seb128: to the PPA? not that time critical, but I guess it would be good to do it soon
[09:36] <seb128> I've no concern about not having bugs for annoying issues
[09:36] <seb128> we have enough bugs sent our way menu item or not
[09:36] <seb128> ok
[09:36] <seb128> I will upload to the ubuntu-desktop ppa today
[09:36]  * pitti hugs seb128, merci!
[09:37]  * seb128 hugs pitti
[09:37] <seb128> de rien!
[09:49] <TheMuso> hrm only en is on powerpc desktop CD. Have to cut something else, and I think part of openoffice is what it may have to be.
[09:51] <pitti> TheMuso: any idea why powerpc is so big?
[09:51] <pitti> does it have that much extra packages?
[09:51] <pitti> s/much/many/
[09:51] <TheMuso> pitti: No it doesn't, but it doesn't help that one of the kernels is huge, the kernel in questino being powerpc64-smp.
[09:51] <TheMuso> question
[10:03] <baptistemm> seb128, this is just someone opened a bug yesterday, and the retrace is not yet done
[10:03] <seb128> baptistemm, ok, it might take a while
[10:03] <baptistemm> and it seems to be a reproductible crasher I'm interested to have
[10:04] <seb128> do you have the bug number?
[10:07] <baptistemm> yep
[10:08] <baptistemm> bug 551955
[10:10] <seb128> retracing will not be useful
[10:10] <seb128> double free requires a valgrind log
[10:11] <TheMuso> hrm livefs is not the latest anyway, so will wait for tomorrow to see where things stand.
[10:11] <baptistemm> seb128, okay
[10:13] <didrocks> re, I'm striking with any no more keyboard on gdm and gnome session after upgrade + reboot. On my right TTY now
[10:13] <seb128> hum
[10:13] <seb128> ot nice
[10:13] <seb128> not
[10:14] <didrocks> no, it's not :( I'm looking at the bunch of update I had this morning to see what's in fault
[10:14] <didrocks> gdm is already out of this :)
[10:14] <seb128> I would tend to blame tjaalton
[10:15] <tjaalton> what now? :)
[10:15] <seb128> there was quite some xorg updates
[10:15] <seb128> tjaalton, some update from today broke xorg keyboard for didrocks
[10:15] <seb128> tjaalton, I would think it's due to some of your uploads ;-)
[10:15] <tjaalton> didrocks: pastebin Xorg.0.log
[10:15] <seb128> but I'm random blaming there
[10:16] <tjaalton> seb128: Sarvatt saw the same, but I couldn't reproduce it
[10:16] <seb128> so feel free to ignore me :p
[10:16] <tjaalton> things should be fine with the new evdev
[10:16]  * seb128 doesn't update
[10:16] <didrocks> tjaalton: I'm trying to downgrade xserver-xorg-input-evdev, reboot in progress
[10:16] <tjaalton> didrocks: which arch?
[10:16] <didrocks> tjaalton: i386
[10:17] <tjaalton> so you got a new evdev? then things should definitely work
[10:17] <didrocks> ok, it's back
[10:17] <tjaalton> kbd/mouse?
[10:18] <popey> seb128: I note you updated tomboy to 1.2.0. Did you take into account the new files that are deployed in tomboy 1.2.0 that aren't in previous releases?
[10:18] <didrocks> one sec, finishing booting :)
[10:18] <seb128> popey, which?
[10:18] <popey> seb128: http://paste.ubuntu.com/406951/
[10:19] <tseliot> MacSlow: ping
[10:19] <seb128> poningru, do you have any issue?
[10:19] <seb128> ups
[10:19] <seb128> popey, ^
[10:19] <seb128> popey, going backward is usually not a good thing
[10:19] <seb128> popey, try rather to tell us what doesn't work than trying to guess what is broken
[10:19] <didrocks> tjaalton: so, the guilty version for me was 1:2.3.2-5ubuntu1, installing back 1:2.3.2-3ubuntu2 works
[10:19] <seb128> popey, and yes the new files are installed
[10:20] <tjaalton> didrocks: you need to install xserver-xorg-core
[10:20] <popey> seb128: ok. i'm not saying something doesn't work, i just couldn't see the difference in the debian/rules, sorry to have bothered you
[10:20] <didrocks> tjaalton: ok, trying upgrading ok and installing it
[10:20] <seb128> tjaalton, you should use breaks in those cases
[10:20] <tjaalton> didrocks: no guarantees about partial upgrades :)
[10:20] <seb128> tjaalton, or versioned depends
[10:20] <tjaalton> too ugly
[10:20] <seb128> tjaalton, wrong reply
[10:20] <dutchie> seb128: did you see https://bugs.edge.launchpad.net/ubuntu/+source/poppler/+bug/248355/comments/46?
[10:20] <seb128> tjaalton, ? it has been made for those cases
[10:21] <seb128> dutchie, yes, did you see the comment from james_w?
[10:21] <dutchie> that's the comment
[10:21] <tjaalton> seb128: well, too late anyway
[10:21] <dutchie> I don't see the what Makefile.in problem is
[10:21] <didrocks> tseliot: xserver-xorg-core is already installed here
[10:21] <tjaalton> the xserver was uploaded first just for this reason
[10:21] <tjaalton> didrocks: which version
[10:22] <tseliot> ?
[10:22] <didrocks> tjaalton: 2:<IP_ADDRESS>~git20091215.77221c91-0ubuntu0tormod
[10:22] <tjaalton> uh oh
[10:22] <didrocks> tseliot: sorry, wrong hl (dummy weechat ;))
[10:22] <tseliot> aah, ok
[10:22] <tjaalton> yeah if you use edgers you're busted
[10:22] <didrocks> tjaalton: ok, I had to use it at some point because of nvidia
[10:22] <didrocks> tjaalton: removing it now :)
[10:23] <didrocks> tjaalton: that's why I was surprized, I hadn't a "partial upgrade"
[10:23] <seb128> dutchie, what is not clear there?
[10:24] <tjaalton> didrocks: yeah, glad that you didn't have the real version ;)
[10:25] <dutchie> seb128: isn't the Makefile.in file just generated from the .am? it builds fine for me
[10:25] <seb128> dutchie, not it's not
[10:25] <seb128> dutchie, you need to run automake for this
[10:26] <didrocks> tjaalton: glade too that not everybody will break so (just those using edgers for some reason at one point on lucid, like "no more nvidia driver for new xorg" ;)). I removed it for a while and even didn't remember that I still can have some piece from it :/
[10:26] <dutchie> oic
[10:26] <seb128> dutchie, which it's not done on the build servers since it's not in the build-depends
[10:26] <seb128> dutchie, I will fix that one
[10:26]  * didrocks dist-upgrade again and reboot
[10:26] <seb128> dutchie, could you tag the patch as indicated though?
[10:26] <dutchie> done
[10:26] <seb128> dutchie, I know how to do the automake update
[10:26] <seb128> dutchie, cool, thanks a lot for your work there
[10:26] <tjaalton> didrocks: yeah edgers is a double-edged sword..
[10:27] <dutchie> and pushed
[10:27] <milanbv> does anybody know whether there's a plan to suggest users coming from Karmic to add the notification applet to get the sound icon?
[10:27] <didrocks> tjaalton: yeah, but it was that or can't test compiz at the start of lucid cycle and I had to test it… so :) What could be good is when you removed a ppa to be able to see "list all remaining components from this ppa" (I just removed nvidia-* related package)
[10:27] <milanbv> seems gnome-volume-control-applet is disabled
[10:28] <tjaalton> didrocks: there's a ppa-purge script somewhere
[10:28] <chrisccoulson> hello everyone
[10:28] <seb128> hey chris
[10:28] <seb128> hey chrisccoulson
[10:28] <chrisccoulson> hmmm, is desktop-couch a little bit CPU-heavy for anybody else today?
[10:28] <seb128> indicator-sound is used in lucid
[10:28] <didrocks> tjaalton: oh? interesting. I'll have a look then. Thanks :) confirming it's ok now
[10:28] <didrocks> hey chrisccoulson
[10:28] <chrisccoulson> hey seb128, how are you>
[10:28] <milanbv> didrocks: ppa purge is at https://launchpad.net/~xorg-edgers/+archive
[10:28] <chrisccoulson> hey didrocks
[10:29] <milanbv> hi chrisccoulson!
[10:29] <chrisccoulson> hi milanbv
[10:29] <tjaalton> didrocks: excellent, thanks
[10:29] <seb128> chrisccoulson, good, thank you, what about you?
[10:29] <didrocks> milanbv: thanks. I'll give it a look
[10:29] <didrocks> tjaalton: thanks for helping on this :)
[10:29] <chrisccoulson> seb128 - good thanks, but a little tired. i stayed up quite late building mozilla updates
[10:30] <seb128> iz bug #530605
[10:30] <MacSlow> tseliot, pong
[10:30] <seb128> chrisccoulson, the cpu use is bug #530605
[10:30] <MacSlow> tseliot, sorry... was on a very long conf-call
[10:30] <chrisccoulson> seb128 - thanks
[10:30] <seb128> chrisccoulson, np
[10:30] <milanbv> anyone about the sound icon migration? ^
[10:31] <seb128> I replied
[10:31] <seb128> indicator-sound is used in lucid
[10:31] <seb128> the indicator-applet is in the default configuration
[10:31] <tjaalton> didrocks: np, the updates need to go fine so any issues like this are critical ;)
[10:31] <seb128> it's set on upgrades too
[10:31] <tseliot> MacSlow: let's use pm and the canonical freenode
[10:32] <milanbv> seb128: sorry, i missed it in the greetings ;-)
[10:32] <seb128> seems indicator-sound doesn't get installed for some users though
[10:32] <milanbv> but you say it should have been added automatically to the panel?
[10:32] <milanbv> yeah
[10:32] <seb128> those likely use apt-get to upgrade
[10:32] <seb128> and not upgrade-manager
[10:32] <milanbv> no, I didn't ;-)
[10:32] <seb128> the recommends are not enforced
[10:32] <seb128> there is a bug open on apt about that I think
[10:32] <milanbv> I've just checked with a test user that I had in Karmic
[10:32] <seb128> well indicator are autolaunched
[10:33] <seb128> you have on indicator-applet
[10:33] <seb128> it used to have only the message icon
[10:33] <milanbv> but they aren't launched, they are an applet
[10:33] <seb128> they are not
[10:33] <seb128> they are indicators
[10:33] <seb128> the indicator-applet is part of the default config
[10:33] <seb128> if you remove it nothing we can do
[10:33] <milanbv> yeah, but the *indicator* applet is missing!
[10:33] <seb128> you removed it
[10:33] <seb128> you probably decided you don't like it
[10:33] <milanbv> I mean: I created a standard account for testing purposes in Karmic
[10:33] <seb128> or don't use it
[10:34] <milanbv> and now the applet isn't there
[10:34] <seb128> no way
[10:34] <milanbv> (I don't really care personally, it's just that a bug was reported and my test account seems to confirm)
[10:34] <seb128> we would have noticed if karmic was buggy this way
[10:34] <milanbv> well, there's bug 552221
[10:34] <seb128> how did you test?
[10:34] <seb128> those bugs are usually indicator-sound not installed
[10:35] <milanbv> test? I had created that account, which I hadn't modified
[10:35] <seb128> which as said before is an apt issue
[10:35] <seb128> recommends are not installed on dist-upgrade in some cases
[10:35] <milanbv> and I simply started the session now I'm in Lucid
[10:35] <seb128> is indicator-sound installed?
[10:35] <milanbv> yes
[10:35] <milanbv> simply adding the indicator applet fixed the bug
[10:35] <seb128> I don't understand
[10:35] <seb128> indicator-applet is in the default gnome-panel config
[10:35] <seb128> since before karmic
[10:35] <seb128> we did zillion of installs and nobody got it not there
[10:36] <milanbv> hmm, if I'm the only problematic case, forget it
[10:36] <seb128> it has only the message thing in karmic
[10:36] <milanbv> let's see what the reporter says
[10:36] <seb128> the same containiner is used for the sound one now
[10:36] <seb128> well try a guest session
[10:36] <seb128> or adding an user on karmic
[10:36] <seb128> I would be interested if the default config is buggy
[10:36] <milanbv> I can't go back to Karmic now
[10:37] <seb128> because we tested that a lot and it never came as buggy
[10:37] <seb128> what usually happens is that users don't like the message indicator
[10:37] <seb128> because it changes the way im notification work
[10:37] <milanbv> yeah, maybe he removed it when going to Karmic, and now he needs it
[10:37] <seb128> so they drop it from their config in karmic
[10:37] <milanbv> shouldn't we enforce adding indicator applet to the panel again?
[10:37] <seb128> we do now
[10:37] <milanbv> because now they really need it
[10:37] <seb128> we didn't before beta1 though
[10:37] <milanbv> OK
[10:37] <milanbv> so I close the bug
[10:38] <seb128> not sure when he upgraded
[10:38] <milanbv> he came too early :-)
[10:38] <seb128> either that or this apt bug
[10:38] <seb128> you can look to open apt bug
[10:38] <seb128> quite some users didn't get indicator-sound installed
[10:38] <seb128> it's only a recommends from indicator-applet or something
[10:38] <seb128> we should perhaps had it as a direct ubuntu-desktop recommends
[10:39] <seb128> since apt seems to handle transitionnal recommends in a buggy way
[10:39] <seb128> I will check that with mvo
[10:39] <seb128> chrisccoulson, btw the gnome-desktop might fix those weird display error on undocking
[10:40] <milanbv> might be nice
[10:40] <seb128> +update
[10:40] <seb128> chrisccoulson, there is a "ignore errors" change there
[10:41] <chrisccoulson> seb128 - oh, that's good. i made sure i got a backtrace and xtrace log of g-s-d when i undocked last night so i can investigate the crasher at some point when i get some spare time, without disrupting my workflow too much
[10:42] <seb128> was that a crash?
[10:42] <seb128> or a badmatch or something?
[10:42] <chrisccoulson> i get a crash when i dock / undock, which seems to be related to the Fn+F8 crash that people see as well
[10:43] <chrisccoulson> seb128 - yeah, it's the crash on badmatch error
[10:43] <seb128> the gnome-desktop change I mention was a badmatch g-s-d crash too
[10:43] <seb128> so it might be the same one
[10:43] <chrisccoulson> oh, that would be good
[10:43] <seb128> https://bugzilla.gnome.org/show_bug.cgi?id=599914
[10:44] <seb128> see that bug
[10:45] <chrisccoulson> seb128 - yeah, that's the same issue
[10:45] <seb128> good!
[10:45] <chrisccoulson> i'm not sure the fix is the right thing to do
[10:46] <seb128> well see federico comment on the bug
[10:46] <seb128> but meanwhile if it doesn't crash that's better than nothing
[10:46] <chrisccoulson> setting the monitor size fails because g-s-d's knowledge of the screen configuration is out of date
[10:47] <chrisccoulson> (ie, it has already changed some configuration but has not processed the events back from the server to update all the client-side values)
[10:47] <chrisccoulson> so setting the screen size to a value it *thinks* is ok fails
[10:48] <chrisccoulson> i'll dig in to that a bit more though and comment on the upstream bug
[10:48] <seb128> so we should make sure it does the event handling first and then the update?
[10:48] <chrisccoulson> seb128 - yeah, possibly. but i need to look at that again to refresh my memory, just to be sure i've got it right
[10:48] <seb128> ok
[10:48] <seb128> in any case buggy better than crashy
[10:49] <seb128> especially when themes don't reapply when g-s-d restart
[10:51] <chrisccoulson> yeah, it would definately be nice for g-s-d not to crash
[11:57] <didrocks> seb128: doing the pango & sabayon update. What to do with other components that are just released as "2.28.1/2", do you think we should update them if there is no 2.30 release for them?
[11:58] <seb128> didrocks, no pango
[11:58] <didrocks> ok
[11:58] <seb128> didrocks, I'm lunching, let's talk about that in a bit
[11:58] <seb128> didrocks, I need to look at pango
[11:58] <didrocks> seb128: sure, enjoy :)
[11:58] <seb128> there was only on unstable version
[11:58] <seb128> and we didn't use it since it was not a clear schedule
[11:58] <seb128> I need to check if we want to update or not
[11:58] <didrocks> seb128: go go go to your lunch, we can talk about that later ;)
[11:59] <seb128> other components, only translation changes I would wait on debian
[11:59] <seb128> but if we are done with everything we can do some
[11:59] <didrocks> understood, I can switch on other things more important TBH :)
[11:59] <seb128> right
[11:59] <seb128> be back in a bit
[12:02] <pitti> ok, LP is down now
[12:03] <pitti> perfect time for lunch and some errands
[12:09] <seb128> doh, I forgot about that today
[12:09] <seb128> why do they need to do update on middle of work days
[12:11] <chrisccoulson> bah, now is not a good time for LP to be down
[12:12] <chrisccoulson> i can't even grab the bzr branches i need to work
[12:12] <seb128> same here
[12:12] <seb128> didrocks, you are lunching now?
[12:13] <didrocks> seb128: not yet, I'm testing the new daily iso to see if I still don't have scolling with my touchpad
[12:13] <didrocks> (and I haven't :/)
[12:13] <seb128> k
[12:13] <seb128> didrocks, do you have any opinion on the pango update?
[12:13] <seb128> do you want to look at it, do it?
[12:13] <didrocks> seb128: also, I saw the new installer (no more syslinux question for booting live or install). I have to try if that doesn't impact my UNE session
[12:14] <seb128> hum
[12:14] <seb128> what did they do with it?
[12:14] <didrocks> seb128: TBH, I only saw the update on the ftp. I didn't look at the NEWS file
[12:14] <seb128> no way to install without running the desktop now?
[12:14] <seb128> didrocks, ok, I will look at it if you want
[12:14] <seb128> didrocks, I'm back from lunch and launchpad is down
[12:14] <seb128> so I'm blocked on other tasks
[12:14] <didrocks> seb128: now, you directly start ubiquity in install mode with a first question "do you want to try it/install it" and select the language
[12:14] <didrocks> seb128: ok, thanks :)
[12:15] <seb128> oh, k
[12:15] <didrocks> seb128: it's nice, I'm just afraid that it doesn't respect session value in custom.conf :)
[12:15] <didrocks> ok, usb key ready, let's have a try
[12:15] <seb128> good luck
[12:22] <didrocks> ok rock! it works :)
[12:22] <seb128> cool
[12:23] <didrocks> I think people will just be surprized if they have an nvidia card, start with -elf, and then, install the "recommended driver", the nvidia blob will activate 3D and the launcher will look different :)
[12:23] <didrocks> but at least, that means the launcher is working
[12:25] <didrocks> ok, let's make a break now. I'm not fancy of speading the whole day to have scrolling on my touchpad working again. Will do that after beta
[12:26] <seb128> didrocks, enjoy the break
[12:26] <didrocks> seb128: thanks  :)
[12:37] <nessita> hello everyone. I was wondering if this is the proper channel to ask about an issue I'm having on a lucid install, with latest updates: network seems extremely slow since last weekend.
[12:41] <davmor2> pitti: https://bugs.launchpad.net/ubuntu/+source/libgphoto2/+bug/544994 launchpad is down so I've pasted it here http://paste.ubuntu.com/407010/ for now and will add to lp when it's back up
[13:04] <seb128> hum
[13:04] <seb128> pitti, do you think we still need the keyring cleaning change?
[13:05] <seb128> brb session restart
[13:23] <pitti> re
[13:23] <pitti> seb128: yes, we still need it; we just introduced it last week, so I think we need to keep it until at least after beta-2, for people upgrading from b1
[13:24] <pitti> davmor2: thanks; I'll just wait until LP is back, to see the full bug and be able to answer, etc.
[13:24] <chrisccoulson> my laptop feels painfully slow today :-/
[13:24] <MDC1> mvo, any chance to fix this before lucid? https://bugs.launchpad.net/update-manager/+bug/549959 and https://bugs.launchpad.net/update-manager/+bug/549936
[13:25] <seb128> pitti, ok, I will update it then, thanks
[13:25] <pitti> seb128: it doesn't apply any more?
[13:25] <pitti> it just added a single function call into existing code
[13:25] <seb128> pitti, the g_debug lines break things which source the command line output
[13:26] <seb128> some KDE users do that
[13:26] <seb128> we got a bug about it
[13:26] <seb128> I will just drop the g_debug
[13:27] <pitti> seb128: ah, that's fine
[13:27] <pitti> seb128: I just added that while developing the patch and kept it because it seemed harmless
[13:27] <seb128> right i didn't think it would break things either
[13:27] <seb128> quick update anyway no worry
[13:28] <mvo> MDC1: thanks, I check it out
[13:29] <MDC1> mvo, i plan to fix the other buttons with icons if you think the solution is ok
[13:29] <seb128> hey mvo
[13:37] <mvo> hey seb128
[13:49] <seb128> dpm, hey
[13:49] <seb128> dpm, could you look at bug #549008?
[13:49] <seb128> dpm, it's a polish translation issue
[13:49] <dpm> heya seb128, looking...
[13:50] <seb128> dpm, the code should probably deal with those errors better but it means the string is broken in the translation
[13:54] <seb128> dpm,
[13:54] <seb128>             # Translators: %(name)s and %(value)s should not be translated:
[13:54] <seb128>             # it's a way to identify a string, so just handle them like %s
[13:54] <seb128> dpm, they probably didn't follow that
[13:54] <seb128> dpm, but upstream translation seems ok
[13:54] <seb128> so maybe it has been changed on launchpad
[13:54] <dpm> ok, I get it, let me see if I can locate the string in LP...
[13:55] <seb128> dpm, it's msgid "%(name)s: %(value)s"
[13:55] <seb128> I think
[13:55] <seb128> or a variant
[13:56] <dpm> hmm, cannot make searches on LP while on read-only mode :/
[13:57] <dpm> ok, I'll find the link to the translation and I'll ping the Polish translations when LP is back
[13:58] <seb128> dpm, thank you
[13:58] <dpm> no worries, thanks for the heads up
[14:16] <chrisccoulson> come back please launchpad :)
[14:19] <seb128> chrisccoulson, the update is going to take an extra hour now...
[14:19] <chrisccoulson> seb128 - thanks
[14:20] <chrisccoulson> thats not good though :(
[14:20]  * pedro_ kicks lp
[14:22] <chrisccoulson> pedro_ - you make it take 10 minutes longer now for kicking it :P
[14:22] <chrisccoulson> ;)
[14:22]  * Tm_T hugs LP
[14:22] <chrisccoulson> heh
[14:23] <chrisccoulson> lp doesn't accept hugs in read only mode though
[14:24] <pedro_> chrisccoulson, noo! :'(
[14:27] <dholbach> hola
[14:27] <dholbach> my xkb config is broken
[14:27] <dholbach>  I just did an upgrade
[14:27] <dholbach>  and restarted
[14:27] <dholbach>  maybe now I find out why alt-1 doesn't work :-D
[14:29] <didrocks> dholbach: you can do that… or still answer in the gsoc list :)
[14:29]  * didrocks hugs dholbach
[14:29] <dholbach> didrocks: eh?
[14:30] <dholbach> didrocks: reply to what?
[14:30] <didrocks> dholbach: the thread about "how can i become a mentor/student in google groups"
[14:31] <Zdra> seb128, Did you know that indicator patch for rhythmbox is changing behaviour of rhythmbox's status icon?
[14:31] <dholbach> didrocks: sorry I didn't check out the google groups stuff yet
[14:31] <Zdra> seb128, dunno what happens if I have the indicator applet, but without it, middle click on the status icon doesn't play/pause anymore, right click doesn't show the rb window (it popups its menu instead)
[14:31] <dholbach> didrocks: what does https://wiki.ubuntu.com/GoogleSoC2010/Students and https://wiki.ubuntu.com/GoogleSoC2010/Mentors not answer?
[14:32] <didrocks> dholbach: they answer everything, just people don't read it before posting…
[14:32] <dholbach> oh yeah
[14:32] <seb128> Zdra, yes, the indicator fallback is to add the same menu to an icon rather than an indicator
[14:32] <dholbach> nothing new
[14:32] <seb128> Zdra, getting the old code back is a buildtime option
[14:32] <dholbach> that's why I sent a "this is what you need to do" mail every week
[14:32] <Zdra> seb128, which means if I want to show rb window, I have to click on status icon, then select "show rhythmbox" from the menu. And when the window is open to minimize to tray I cannot click the status icon anymore, I have to close the window
[14:33] <Zdra> seb128, IMO if indicator applet is not in the panel, it should fallback to upstream behaviour
[14:33] <Zdra> which is consistent with empathy
[14:33] <seb128> right, patches are welcome
[14:33] <Zdra> sigh :(
[14:33] <seb128> we will not have time to rewrite fallback code for lucid
[14:34] <seb128> we have a zillion bugs to fix
[14:34] <Zdra> don't write indicator code if you are unable to do it properly
[14:34] <seb128> it's done properly
[14:34]  * Zdra is sick of that indicator in ubuntu
[14:34] <seb128> you just don't want to use the indicator
[14:34] <seb128> which is a different usecase
[14:34] <seb128> we could have no fallback at all
[14:34] <seb128> I agree the fallback is suboptimal
[14:35] <seb128> but the idea is that people would try to use indicators
[14:35] <seb128> because they are nice
[14:35] <seb128> we spent our efforts have a nice default experience
[14:35] <Zdra> seb128, people are complaining UPSTREAM because they don't see new empathy messages, because of indicator
[14:35] <seb128> rather than trying to optimize fallback code
[14:36] <Zdra> that indicator should have been dropped, clearly
[14:36] <seb128> the fallback in empathy is not buggy that I know
[14:36] <seb128> that's not constructive comment
[14:36] <seb128> the indicator works fine for many users
[14:36] <seb128> that's not because some get confused and can't change an option that we should stop doing changes
[14:37] <seb128> I've work to do, going back to that
[14:37]  * cassidy read lot of negative comments about Empathy which are actually because of this patch :(
[14:37] <seb128> cassidy, specific issues?
[14:37] <seb128> or just the icon change not being obvious enough
[14:38] <cassidy> seb128, the usual things, the indicator isn't clear enough and people miss they have received messages
[14:38] <seb128> the other issue is that really read rants from geeks and vocal minorities usually
[14:38] <seb128> cassidy, the icon changed yesterday
[14:38] <seb128> it should be noticable now
[14:38] <seb128> it was not before
[14:38] <cassidy> ah good
[14:40] <Zdra> seb128, note that ubuntu changed rb's icon when not playing, but not the icond when playing, which makes the style totally inconsistent
[14:41] <Zdra> seb128, sorry to complain against you, surely it's not your personal fault ;)
[14:41] <pitti> well, to be honest, they are right
[14:41] <Zdra> just that you are maintainer of the package, afaik
[14:41] <pitti> the indicator is NOT clear enough
[14:41] <Zdra> seb128, canonical's own user testing proved indicator is not clear
[14:42] <seb128> Zdra, styles are consistent there, what icon theme do you use?
[14:42] <Zdra> for empathy at least
[14:42] <seb128> pitti, Zdra: I agree it's not clear enough
[14:42] <seb128> the green icon should be a bit better
[14:42] <seb128> I would still like flashing better
[14:42] <seb128> but not my decision *shrug*
[14:42] <pitti> yeah, design team thing
[14:42] <pitti> seb128: we'll get green?
[14:43] <vuntz> green is openSUSE!
[14:43] <vuntz> lalala
[14:43] <seb128> pitti, it's in since yesterday
[14:43] <pitti> \o/
[14:43] <seb128> pitti, you use outdated software :p
[14:44] <pitti> seb128: no, nobody pinged me on jabber today yet :)
[14:44] <pitti> ooh! green!
[14:44] <seb128> ;-)
[14:46] <seb128> oh come on launchpad enough being down now I've work to do
[14:46] <Zdra> seb128, Hm, don't know which icon theme I'm using since gnome-appearance-properties crash at startup now :(
[14:46] <Zdra> I think I have ubuntu's theme
[14:46] <seb128> Zdra, it has been fixed today
[14:46] <seb128> the crash
[14:47] <seb128> upgrade gnome-control-center
[14:47] <Zdra> just made the upgrade karmic->lucid today
[14:47] <seb128> yeah, things change quickly
[14:47] <seb128> didrocks fixed it this morning
[14:47] <seb128> you probably didn't get the update
[14:47] <Zdra> seb128, ah, probably related to the fact that capplets-data can't be installed
[14:48] <seb128> using amd64?
[14:48] <didrocks> capplets-data can't be installed ?
[14:48] <Zdra> seb128, yes
[14:48] <didrocks> ah, make sense :)
[14:48] <seb128> yeah, it's because i386 built first
[14:48] <seb128> and the binaries are out of sync on amd64
[14:48] <Zdra> ok
[14:48] <Zdra> I'll wait then :)
[14:48] <seb128> should be fixed in the next hours
[14:52] <pitti> oh, LP seems to be back
[14:54] <seb128> pitti, \o/
[14:56]  * didrocks bzr pull
[14:56] <seb128> dpm, hey again
[14:56] <seb128> dpm, https://bugs.edge.launchpad.net/ubuntu/+source/gnome-keyring/+bug/552358
[14:56] <dpm> looking... :)
[14:56] <seb128> dpm, do you think it's worth breaking translations?
[14:56] <seb128> "Enter Password for to unlock your login keyring"
[14:56] <seb128> I want to fix that string
[14:57] <Zdra> seb128, also it seems that the volume applet disappeared... when adding the indicator applet I get it together with the incidator thing... so I guess it's also yet-another-ubuntu-patch?
[14:57] <Zdra> same for bluetooth icon
[14:57] <seb128> Zdra, no, it's just that we use an indicator for it
[14:58] <seb128> you can run gnome-volume-control-applet
[14:58] <seb128> we just turn the autostart desktop file off by default
[14:58] <seb128> it's still there
[14:58] <Zdra> seb128, it's not in the list of applets I can add anymore
[14:58] <seb128> you can edit it in the session capplet
[14:58] <seb128> or run it by hand
[14:58] <dpm> seb128, could it be fixed by patching the sources and all those msgid's in the translations?
[14:58] <Zdra> any reason to remove from the list?
[14:58] <seb128> yes because we use an indicator
[14:58] <seb128> and it would mean having 2 mixers
[14:58] <Zdra> is that a reason to not let users add it back if they wanyt?
[14:59] <seb128> if you decide to remove the indicator you can add the applet too
[14:59] <seb128> they can
[14:59] <seb128> just check it in the session capplet
[14:59] <Zdra> seb128, I can't add the volume applet from the UI at least
[14:59] <seb128> Zdra, go to the session capplet
[14:59] <seb128> it should be listed as unticked
[14:59] <seb128> tick it
[15:00] <seb128> oh
[15:00] <seb128> we probably did hide it to not confuse users
[15:00] <Zdra> wtf?
[15:00] <seb128> you should use indicators really, they are nice ;-)
[15:00] <seb128> well see we build a desktop using indicators
[15:00] <seb128> so we optimize for the default experience
[15:00] <seb128> not for the fallback case for people who don't want to use what we do
[15:01] <seb128> I'm not sure why you don't just add the indicator
[15:01] <seb128> and change the empathy option to not use it
[15:01] <Zdra> why should I do that?
[15:01] <seb128> sound, bluetooth are as nice as the notification icons
[15:01] <seb128> you would avoid all those issues
[15:02] <Zdra> sound is just replacing a vertical bar by an horizontal
[15:02] <seb128> if you strongly disagree with the distro direction install an another distro...
[15:02] <seb128> well indicators are consistent
[15:02] <Zdra> bluetooth is the exact same menu afaik
[15:02] <seb128> you can move between those with the keyboard
[15:02] <seb128> or without closing the menu
[15:02] <seb128> right that's the idea
[15:02] <seb128> having notification area done right
[15:02] <Zdra> seb128, sadly, I really consider moving to another distro because of that
[15:02] <seb128> you will also get KDE software rendered in gtk
[15:03] <seb128> dpm, *shrug*, I guess we could but I'm already overworked and I don't fancy spending an hour on that
[15:03] <Zdra> seb128, what's the point in indicator if it's already known to be dead with gnome-shell?
[15:04] <seb128> Zdra, is it?
[15:04] <seb128> Zdra, there was some running discussion about what will be done with gnome-shell
[15:04] <seb128> and it didn't seem there was a decision yet
[15:04] <Zdra> anyway... thanks for your answers :)
[15:04] <seb128> you're welcome
[15:04] <dpm> seb128 I understand, let me think for a sec...
[15:05] <milanbv> Zdra: I think indicators are likely to work better in the future with GNOME Shell than notification icons
[15:05] <milanbv> because the shell will easily be able to render the menus the way it wants, and integrate them to the messaging bar
[15:06] <rickspencer3> good morning all
[15:07] <chrisccoulson> hey rickspencer3
[15:07] <seb128> hello rickspencer3
[15:07] <rickspencer3> hi chrisccoulson, seb128
[15:07] <pitti> hey rickspencer3
[15:08] <seb128> rickspencer3, how are you?
[15:09] <didrocks> hey rickspencer3
[15:10] <seb128> dpm, let me have a try to sed the po to change this string
[15:11] <seb128> dpm, the msgid need to be changed right?
[15:11] <dpm> yes
[15:11] <dpm> then when building the translations they will not be marked as fuzzy
[15:12] <dutchie> seb128: got onto merging the poppler thing yet?
[15:12] <dutchie> (I can see you're busy though)
[15:13] <seb128> dutchie, no, launchpad was down for 3 hours
[15:13] <seb128> there was no way to bzr pull anything
[15:13] <rickspencer3> I'm doing ok
[15:13] <dutchie> yeah, pain that
[15:13] <seb128> I'm quite annoying
[15:13] <rickspencer3> seb128, didrocks, chris, how's it going today?
[15:13] <seb128> I didn't remember they announced that a week ago
[15:13] <rickspencer3> nm
[15:13] <rickspencer3> :)
[15:13] <seb128> rickspencer3, out of the fact that I forgot that launchpad was down for 2 hours
[15:13] <seb128> which turned to be 3
[15:13] <seb128> and I didn't fetch things I needed before
[15:13] <seb128> good ;-)
[15:13] <baptistemm> if someone is able to reproduce bug 552140 thanks for providing a valgrind log
[15:13] <didrocks> rickspencer3: good LP down enabled me to do other things :)
[15:15] <rickspencer3> didrocks, like go outside?
[15:15] <rickspencer3> :)
[15:16] <dpm> seb128, if you see it's going to take you too much time, do you want me to quickly ask on the translators list? TBH, I'm undecided on this one as well. It's not a very visible string, if I understand it correctly, and it has a good chance to be fixed upstream, since it is clearly a typo. I think it might be ok to fix it, even if temporarily breaking translations. But of course, if it can be handled transparently, even better
[15:16] <mvo> seb128: fyi https://bugzilla.gnome.org/show_bug.cgi?id=614469 (the vte problem)
[15:16] <seb128> dpm, I will have a short try, if that works great otherwise I will upload with the break and let you know
[15:16] <didrocks> rickspencer3: not really, like finishing my last WI :)
[15:17] <seb128> mvo, thanks
[15:17] <rickspencer3> hehe
[15:17] <dpm> seb128, ok, sure, thanks for the heads up
[15:17] <mvo> seb128: I could move it outside the ifdef block, but it will most likely crash then in the frambuffer mode
[15:17] <mvo> seb128: so I will just wait for upstream for now, I don't think its super ugent, the NEW file looks like there is nothing earth shaking
[15:17] <seb128> mvo, so what do you recommand doing? skip the update for lucid?
[15:17] <seb128> mvo, ok
[15:18] <seb128> mvo, works for me, I pinged you because you said git had some pretty cool changes
[15:18] <mvo> seb128: lets see how fast upstream responds
[15:18] <mvo> seb128: right, git head, but the 0.24.x branch is medium interessting
[15:19] <seb128> k
[15:19] <seb128> mvo, I though the changes were in the current version
[15:20] <mvo> seb128: not AFAICS
[15:21] <seb128> mvo, ok, cool
[15:21] <mvo> :)
[15:24] <LaserJock> kenvandine: pingaloo
[15:24] <kenvandine> LaserJock, pong
[15:24] <LaserJock> kenvandine: so yesterday I did something wrong and now gwibber won't take *any* accounts
[15:24] <kenvandine> LaserJock, i have a fix for that in the works :)
[15:24] <LaserJock> ah, sweet
[15:25] <LaserJock> and here I thought I was going mad or something :-)
[15:25] <kenvandine> in disabling the keyring support that we added (to work around the keyring bug for now), account adding is a little busted :/
[15:25] <kenvandine> fix will be ready in a few
[15:26] <LaserJock> ok, np, thanks
[15:26]  * rickspencer3 grabs Dell mini touchpad, throttles it, throws it to the ground, kicks it
[15:31] <didrocks> rickspencer3: "touchpad for human being"
[15:31] <rickspencer3> hehe
[15:40] <Zdra> seb128, a more constructive issue: if I get an incoming call, the accept/reject dialog steal the focus and taping enter reject the call
[15:40] <LaserJock> rickspencer3: there must be some research on the computing equivalent of "road rage"
[15:41] <Zdra> seb128, this is using indicator "better user experience"
[15:41] <seb128> Zdra, no, that was a try to workaround the fact that users don't notice calls
[15:41] <seb128> Zdra, not sure why the focus stealing prevention is not working
[15:42] <Zdra> because focus stealing prevention never worked
[15:42] <Zdra> that's why empathy blink the status icon
[15:42] <seb128> well blinking icon is not really the best experience either
[15:42] <seb128> we should try and fix those focus issues
[15:42] <rickspencer3> seb128, Zdra I thought there was some time stamp thing to keep this from happening
[15:42] <rickspencer3> seb128, this happened to me when you called me yesterday
[15:42] <Zdra> seb128, if the user can see the incoming msg notification, they can see the same for incoming call, tbh
[15:42] <seb128> there is
[15:43] <seb128> rickspencer3, I would have to check with kenvandine how he did the change
[15:43] <rickspencer3> I'll log a bug
[15:43] <mvo> seb128: upstream replied!
[15:43] <seb128> mvo, waouh!
[15:43] <Zdra> rickspencer3, seriously that never worked, it was not working 15years ago and it is still not working now
[15:43] <mvo> seb128: the reply is "patch?"
[15:43] <Zdra> using metacity here
[15:43] <seb128> mvo, :-(
[15:43] <mvo> such is life
[15:43] <rickspencer3> Zdra, understood. note that I am not driving this, just responding
[15:43] <seb128> mvo, not your week
[15:43] <rickspencer3> I thought it was fine before
[15:44] <seb128> it's fine if the client side does what it should
[15:44] <seb128> ie set the correct timestamp
[15:44] <Zdra> rickspencer3, sure, thanks :)
[15:44] <Zdra> rickspencer3, you are filling a bug or should I do?
[15:44] <rickspencer3> Zdra, I am doing it right now
[15:44] <seb128> buggy cases are due to clients not setting a timestamp when they open something
[15:44] <Zdra> cool
[15:44] <rickspencer3> logging against indicator-messages
[15:44] <seb128> rickspencer3, I think it's empathy
[15:44] <seb128> but check with kenvandine
[15:45] <asac> pitti: what can we do in jockey to detect hardware ... is that constrainted to PCI etc. or can we add arbitrary scripts/binaries that do the detection etc.?
[15:46] <seb128> mvo, did you manage to get a better reply about openoffice issues?
[15:46] <kenvandine> rickspencer3, it didn't raise the accept/reject dialog when you got the call?
[15:46] <rickspencer3> kenvandine, it did
[15:46] <rickspencer3> while I was typing
[15:46] <kenvandine> ah
[15:46] <mvo> seb128: sort of, I have a better idea now and added it to the bug
[15:46] <rickspencer3> which then rejected the call
[15:46] <kenvandine> right... :)
[15:46] <kenvandine> eww
[15:46] <kenvandine> hummm
[15:46] <rickspencer3> I think we should probably back out the change
[15:46] <kenvandine> can't win...
[15:46] <mvo> seb128: I will ask rene about it again tonight I think
[15:47] <rickspencer3> and try again in Lucid + 1
[15:47] <seb128> mvo, ok
[15:47] <mvo> seb128: and then hopefully we know whats going on with OOo
[15:47] <rickspencer3> right, that's Zdra's point
[15:47] <pitti> asac: it normally uses modaliases, but handlers can do anything to decide whether they are "available" (i. e. do hw detection)
[15:47] <seb128> well you can win
[15:47] <mvo> seb128: but releeasing it like this is unacceptable
[15:47] <seb128> just set the correct timestamp
[15:47] <rickspencer3> try as you might, you can't raise a dialog without causing such issues
[15:47] <seb128> but at default of doing that go back to change the icon
[15:47] <rickspencer3> anyway, it's too late to keep chasing this
[15:47] <rickspencer3> imo we should back out that change, and focus on fixing bugs
[15:47] <rickspencer3> seb128, thoughts?
[15:48] <rickspencer3> pitti, thoughts?
[15:48] <seb128> if fixing it is adding one parameter to a call and we can try that today I would do it
[15:48] <seb128> otherwise back out
[15:48] <pitti> rickspencer3: sorry, didn't follow; reading scrollback
[15:48] <rickspencer3> pitti, nm
[15:48] <Zdra> note that some users have focus to the mouse, in that case timestamp can't help
[15:48] <kenvandine> seb128, setting the correct timestamp, that would still just raise it right?
[15:49] <rickspencer3> well, I am interested in your feedback pitti, but I think you may have other work to do ;)
[15:49] <seb128> kenvandine, not if you have a key event with a timestamp newer than the receive event
[15:49] <seb128> kenvandine, ie update-manager doesn't still your focus when autoopening
[15:49] <pitti> rickspencer3: when should I start reading? i. e. what's the topic?
[15:49] <seb128> or pidgin dialogs
[15:49] <seb128> pitti, empathy calls dialog steal focus
[15:50] <pitti> I wish they would..
[15:50] <seb128> pitti, try to fix it or go back to use the indicator
[15:50] <pitti> do they?
[15:50] <seb128> pitti, they do
[15:50] <kenvandine> pitti, they do now :)
[15:50] <rickspencer3> they steal focus, and if you are typing, your key clicks reject the call
[15:50] <pitti> ah
[15:50] <seb128> pitti, which means you refuse the call if you are typing
[15:50] <kenvandine> as of a couple weeks ago i think
[15:50] <seb128> without noticing
[15:50] <kenvandine> if you hit enter...
[15:50] <seb128> dpm, ok, I think I got it, sorry was sidetracked
[15:50] <pitti> seb128: hm, didn't we solve that problem ages ago in compiz?
[15:50] <rickspencer3> well if it's been a couple of weeks and is still not working ... I think we should roll it back
[15:50] <rickspencer3> don't throw good money after bad
[15:51] <pitti> rickspencer3: but yes, my default answer would be to go back to indicators
[15:51] <asac> pitti: handlers are triggered how? udev? or can we run than once on startup?
[15:51] <seb128> dpm, uploading that to lucid, if you could check that the gnome-keyring update looks fine to you when it lands
[15:51] <pitti> asac: (1) on first run after installation, (2) whenever you open jockey, (3) when you plug in a device which needs firmware
[15:51] <kenvandine> i am happy to back that out, but we should discuss this at UDS and come up with some good in between
[15:52] <seb128> works for me
[15:52] <asac> pitti: plug in device is detected through udev i guess?
[15:52] <pitti> seb128: ok, I updated the retracers with new .debs which should fix a couple of crashes; retracers crashed due to LP being down anyway, restarting now
[15:52] <kenvandine> seb128, ok, will do today
[15:53] <asac> pitti: is there a good example handler i could look at?
[15:53] <pitti> asac: update-notifier listens for "firmware" uevents, and invokes jockey if firmware is missing, yes; but its' a rather narrow special case
[15:53] <pitti> asac: what do you want to do?
[15:53] <asac> pitti: basically on arm we have bunch of firmware like things to enable all the hardware
[15:53] <asac> would love to use jockey to get this automatically done
[15:54] <seb128> pitti, \o/
[15:54] <pitti> asac: /usr/share/jockey/handlers/dvb_usb_firmware.py does that for DVB USB sticks
[15:54] <seb128> kenvandine, thanks for getting the update for the notification in btw
[15:54] <pitti> asac: and update-notifer listens for those
[15:54] <seb128> good contributor work
[15:54] <asac> pitti: this would be general hardware, video, but also gstreamer codecs at some point
[15:55] <asac> pitti: thanks. will check that
[15:55] <pitti> asac: gstreamer codecs won't trigger a firmware event, though
[15:55] <pitti>  4812 martin    20   0  106m  17m 4920 S   99  0.9  48:13.23 desktopcouch-se
[15:55] <asac> pitti: well. thats the point; most hardware is neither pci nur USB
[15:55] <asac> on arm
[15:55] <pitti> kenvandine: ^ any idea what this is doing? I haven't ever used desktopcouch
[15:55] <pitti> and it has eaten 100% cpu for 45 mins now apparently
[15:56] <kenvandine> that is the keyring bug
[15:56] <asac> pitti: what is a firmware event?
[15:56] <pitti> asac: missing firmware isn't related to any particular bus; the kmod just needs to request it
[15:56] <asac> e.g. where does that come from?
[15:56] <pitti> asac: the kernel module
[15:56] <asac> hmm
[15:56] <kenvandine> bug 530605
[15:56] <asac> well. for us its probably not only firmware, but also full kernel modeules
[15:56] <pitti> kenvandine: ah, thanks; can I just kill that?
[15:56] <pitti> kenvandine: uh, it uses gvfsd-smb?
[15:56] <kenvandine> pitti, yeah...
[15:56] <kenvandine> no
[15:57] <kenvandine> the bug is in libgnome-keyring
[15:57] <pitti> kenvandine: oh, I think I accidentally clicked "news accounts" in the me-menu
[15:57] <pitti> it didn't work, though
[15:57] <pitti> but some 20 s later, gwibber popped up
[15:57] <pitti> so I guess it worked after all, somehow
[15:57] <kenvandine> news?
[15:57] <Zdra> kenvandine, why is indicator applet showing random contacts in its menu?
[15:57] <pitti> well, that's what it says in German
[15:58] <kenvandine> Zdra, random contacts?
[15:58] <pitti> "Nachrichtenkonten"
[15:58] <pitti> which is "News accounts"
[15:58] <kenvandine> do they go away after a few seconds?
[15:58] <Zdra> kenvandine, I sometimes get some contacts there that I never chatted with
[15:58] <kenvandine> Zdra, login events showup for like 10s i think
[15:58] <kenvandine> with no timestamp
[15:58] <Zdra> kenvandine, it's not new msg, just seeing its avatar/name and clicking on it starts chat
[15:58] <pitti> the thing which should be "Microblogging accounts"
[15:58] <Zdra> kenvandine, ah, login/logout
[15:58] <Zdra> kenvandine, probably that
[15:58] <kenvandine> pitti, ah... yeah "broadcast accounts"
[15:58] <kenvandine> Zdra, yup
[15:59] <kenvandine> next cycle it should say something like "connected" next to the name
[15:59] <pitti> kenvandine: "broadcast" seems to be too confusing for translators then :)
[15:59] <kenvandine> pitti, agreed... i didn't pick the terms :)
[15:59] <LaserJock> it's confusing for native-English speakers too
[15:59] <Zdra> kenvandine, tbh it's just totally useless, since there is no visual effect to show that event
[16:00] <Zdra> kenvandine, I don't have that menu open all the time
[16:00] <kenvandine> Zdra, yeah, i know
[16:00] <kenvandine> Zdra, i think that gets disabled if you have notify for login events disabled in empathy
[16:00] <Zdra> kenvandine, no
[16:01] <kenvandine> ok, i can't remember exactly what the spec says
[16:01] <Zdra> kenvandine, I was about to say that it would make a bit of sense if that option was enabled, but it is not here
[16:02] <Zdra> Hm, scrolling on the rb indicator applet does not change its volume :(
[16:02] <dpm> seb128, thanks, I'll do! (re: gnome-keyring)
[16:03] <seb128> Zdra, you can do the same on the mixer next to it
[16:03] <seb128> which works
[16:03] <Zdra> well, it's really minor regression from upstream, but changing volume only for that app is useful
[16:04] <Zdra> I use that sometimes when listening to podcast or voip call, to have the music in background and still can hear the voice
[16:12] <ccheney> rickspencer3: got the images from ken and forwarded them on for approval, cc'd you as well
[16:12] <rickspencer3> ccheney, great
[16:12] <rickspencer3> and do you need any new wording, etc... for them?
[16:16] <ccheney> rickspencer3: the about dialog already has the new wording in it, i think the other wording is just changes in copyright file, etc
[16:16] <rickspencer3> ccheney, ook
[16:16] <rickspencer3> Amanda is getting that new stuff asap
[16:16] <ccheney> rickspencer3: ah just checked just changing Sun Microsystems to Oracle and updating the wiki page to refer to Oracle
[16:16] <ccheney> rickspencer3: ok
[16:27] <rickspencer3> kenvandine, by the way bug #552577
[16:27] <rickspencer3> ccheney, just make the change when you are ready and think the time is correct
[16:27] <kenvandine> rickspencer3, thx
[16:31] <ccheney> rickspencer3: ok
[16:46] <kwwii> mvo: hey, do you know where /usr/share/pixmaps/usb-creator-gtk.png comes from? I have a better icon for ubiquity and don
[16:46] <kwwii> don#t know who to give it to
[16:48] <seb128> james_w, there?
[16:49] <james_w> hi seb128
[16:49] <seb128> james_w, hey
[16:49] <seb128> james_w, I've a small bzr issue, do you have a minute to help me on it?
[16:50] <james_w> Mais oui
[16:50] <seb128> excellent!
[16:50] <seb128> james_w, so
[16:50] <seb128> bzr get lp:ubuntu/indicator-sound
[16:50] <seb128> wget http://edge.launchpad.net/indicator-sound/0.2/0.2.2/+download/indicator-sound-0.2.2.tar.gz
[16:50] <seb128> cd indicator-sound
[16:50] <seb128> bzr merge-upstream --version 0.2.2 ../indicator-sound-0.2.2.tar.gz lp:indicator-sound
[16:50] <seb128> james_w, that gives me one file conflct
[16:50] <seb128> conflict
[16:51] <seb128> I don't understand why
[16:51] <james_w> which file?
[16:51] <seb128> Text conflict in src/indicator-sound.c
[16:51] <james_w> ok, let me look
[16:51] <seb128> thanks
[16:51] <james_w> and you know that you don't need the wget?
[16:51] <seb128> no I don't
[16:52] <seb128> I can specific the http url in the bzr command?
[16:52] <james_w> yup
[16:52] <seb128> good to know
[16:54] <james_w> seb128: good question
[16:55] <james_w> I don't know off the top of my head
[16:55] <james_w> it's a bug somewhere
[16:56] <james_w> you can resolve for "MERGE SOURCE" and I'll file a bug about it
[16:56] <seb128> james_w, what do you mean for "MERGE SOURCE"
[16:56] <seb128> I usually cp the tarball .c
[16:56] <seb128> and bzr resolve src/indicator-sound.c
[16:57] <james_w> bzr resolve --take-other src/indicator-sound.c
[16:57] <james_w> should do it
[16:57] <seb128> oh, nice, thanks
[16:57] <james_w> otherwise edit the file and delete the stuff between <<<< TREE and [16:57] <seb128> right, it's just easier to copy the tarball version than to edit the file and risk having it wrong ;-)
[16:58] <seb128> ie no thinker
[16:58] <seb128> copy and resolve ;-)
[16:58] <james_w> except if there are other changes in the file you want to keep :-)
[16:58] <seb128> right
[16:58] <seb128> that's not the case there
[16:58] <seb128> we should have 0 change
[16:58] <james_w> right
[16:58] <seb128> thanks anyway
[16:58] <seb128> I know how to sort it
[16:59] <seb128> I was just wondering if I'm doing something wrong again or not
[16:59] <seb128> ;-)
[16:59] <james_w> nope, pretty sure it's a bug, but it's more than 30 seconds to diagnose it
[16:59] <pitti> seb128: waah waah python-support -- I already removed all the old *.pyc files from the chroots, seems that still wasn't enough; I'll deal with that after dinner
[17:00] <seb128> pitti, :-(
[17:00] <seb128> pitti, enjoy!
[17:00] <seb128> james_w, ok, good, no hurry, do you want me to keep the bzr in a broken state or can I just do my update?
[17:00] <james_w> nope, go for it
[17:00] <seb128> thanks
[17:00] <james_w> it's a version control system, we can grab the old version!
[17:00] <seb128> hehe
[17:23] <didrocks> grrr, the forbid enable user to use autologin if using encrypted dir is not as easy as I first thought :/
[17:30] <pitti> rickspencer3: hm, we missed our call?
[17:30] <rickspencer3> pitti, yes, but am on another call
[17:31] <rickspencer3> pitti, if it's time for you to go home, we can resched
[17:31] <pitti> heh, I'm at home all the time :)
[17:31] <pitti> rickspencer3: I'm here for another hour before I need to leave
[17:31] <rickspencer3> ok
[17:31] <pitti> rickspencer3: not much on my list, just OEM rotation (would appreciate a quick discussion)
[17:31] <rickspencer3> let's see
[17:31] <rickspencer3> dst is kicking my schedule's but
[17:31] <pitti> but I'm fine with calling tomorrow too, if that suits you better
[17:32] <rickspencer3> pitti, I'd like to do today if it works out
[17:33] <didrocks> pitti: do you have any idea if we should finally postpone the gdmsetup autologin for encrypted user stuff? I have the code, the issue is that you have to read a file which is /home/$USER/.ecryptfs/Private.mnt to know the mount point. As gdmsetup isn't runned as root, we're blocked there :/
[17:34] <pitti> didrocks: why do you need to know the mount point?
[17:34] <didrocks> so, the filtering code should be put in the server side, the issue with that is that we already connect to dbus signals that are used in various place, and so, we will have to create new signals…
[17:34] <pitti> didrocks: oh, if the user that is logged in automatically isn't the one you are running gdmsetup as?
[17:35] <didrocks> pitti: right
[17:35] <didrocks> pitti: also, some user like you only have a subdir mounted, this file contains the path
[17:35] <pitti> right
[17:36] <pitti> didrocks: what happens if you have an encrypted home and try to autologin
[17:36] <pitti> ?
[17:36] <pitti> didrocks: if gdm just falls back to the user list, it's good enough, I think
[17:36] <didrocks> pitti: you get an horrible "can't read Xauthority file" and you're stuck
[17:36] <pitti> didrocks: yes, let's not wrestle with the backend/dbus any more
[17:36] <didrocks> not back into gdm
[17:36] <didrocks> (let me try again, it's been a long time, one sec)
[17:37] <pitti> didrocks: can we hide the autologin thing if the user who calls gdmsetup has an ~/.ecryptfs/Private.sig?
[17:37] <pitti> didrocks: (please ask kirkland for which file to test for)
[17:37] <humphreybc> seb128: ping
[17:38] <pitti> didrocks: it wouldn't be perfect, but probably avoid the majority of cases
[17:38] <didrocks> pitti: I talked with him and he told me to test ~/.ecryptfs/Private.mnt
[17:38] <pitti> hm, I don't have taht
[17:38] <pitti> didrocks: but yes, fine with me
[17:38] <seb128> humphreybc, pong
[17:38] <didrocks> pitti: the issue is that if you are foo, launching gdmsetup, and bar is using autologin, you can't access to ~bar/.ecryptfs/Private.mnt
[17:38] <seb128> humphreybc, I was about to go, what's up there?
[17:39] <didrocks> pitti: so, you don't know if he has or not an encrypted dir
[17:39] <pitti> didrocks: yes, understood
[17:39] <humphreybc> seb128: sorry, just wondering what's the story with our friendly evince anti aliasing bug?
[17:39] <pitti> didrocks: but if foo == bar (which will be the case in most home setups), it'd work
[17:39] <pitti> didrocks: thus the "not perfect, but cover a majority of cases"
[17:39] <seb128> humphreybc, you are really pushy on this one, aren't you?
[17:40] <didrocks> pitti: ok, just tested again with an encrypted dir + autologin: you got 3 horrible error message and then, stuck with the wallpaper and nothing else
[17:40] <pitti> didrocks: i. e. we get 80% of the effect with 5% of the effort
[17:40] <seb128> humphreybc, I just uploaded a few minutes ago now
[17:40] <humphreybc> seb128: yep ;)
[17:40] <seb128> humphreybc, I need to go sorry
[17:40] <seb128> bbl
[17:40] <humphreybc> okay, thanks for your help!
[17:40] <didrocks> pitti: right, foo == bar works (I was just going to push my changes before seeing this cornercase)
[17:41] <pitti> didrocks: let's call that "good enough" then, shall we?
[17:41] <seb128> humphreybc, thank you for the work on the bug
[17:41] <humphreybc> don't thank me, thank dutchie :)
[17:41] <didrocks> pitti: ok, I can close my WI now and push this patch so :)
[17:41] <didrocks> pitti: maybe I shall just put a comment into my code about that case
[17:41] <didrocks> for further debugging and reading
[17:41] <seb128> I've to go now, see you later
[17:41] <pitti> didrocks: for lucid+1, gdm should probably just refuse to accept the new setting if the new user has that file
[17:41] <pitti> didrocks: i. e. no need to add new signals, etc.
[17:42] <didrocks> pitti: yeah, seems logical, but too late in the cycle to touch that now
[17:42] <didrocks> let's do it that way so
[17:42]  * pitti hugs didrocks, cheers
[17:43]  * didrocks hugs pitti
[17:43] <didrocks> I was afraid it will become for 1 hour of work to 10 more :)
[17:44] <didrocks> (btw, the bug is really horrible, you have to reboot, press shift to get to grub, recovery mode and edit /etc/gdm/custom.conf)
[18:11] <didrocks> well, time to enjoy a little bit of sun :)
[18:11] <didrocks> see you tomorrow everyone
[18:15] <kenvandine> have fun didrocks
[18:15] <didrocks> thanks :) have a good evening kenvandine
[18:34] <pitti> good night everyone!
[18:35] <chrisccoulson> good night pitti
[18:44] <rickspencer3> kenvandine, hi
[18:45] <kenvandine> rickspencer3, hey
[18:45] <rickspencer3> kenvandine, dx and OLS uploads tomorrow?
[18:46] <kenvandine> dx yes... OLS today/tomorrow
[18:46] <rickspencer3> kenvandine, okay, especially for Dx, please look at their code closely
[18:46] <kenvandine> ok
[18:46] <rickspencer3> to ensure that no freezes are violated, etc...
[18:46] <rickspencer3> so check for string changes, UI, changes etc...
[18:47] <kenvandine> ok
[18:47] <rickspencer3> and if you find them, flag them for me and dbarth
[18:47] <rickspencer3> thanks kenvandine
[18:59] <rickspencer3> kenvandine, gwibber client started up quicky and without issue on start up for me, first time ever!
[19:01] <kenvandine> woot!
[19:01] <kenvandine> excellent
[19:07] <jcastro> yes I just noticed the start up time today too
[19:07] <jcastro> well done!
[19:09] <kenvandine> :)
[19:10] <kklimonda> nope
[19:10] <kklimonda> ups, that was weird
[19:36] <nigelb> can someone please sponsor bug 314885 before the beta freeze? (its a main package and falls smack in desktop team territory :D)
[19:42] <duanedesign> while building a new upstream source I get some warnings in the build log that look like its trying to write gconf settings? http://paste.ubuntu.com/401850/
[20:02] <jcastro> kenvandine: I am starting to get 100% desktopcouch cpu right after I log in
[20:05] <zyga> intel drivers got crazy again
[20:05] <zyga> I got a video of that happening
[20:07] <mdc_laptop> mvo_, thanks :)
[20:18] <kenvandine> jcastro, yeah known bug in the keyring
[20:18] <kenvandine> jcastro, bug 530605
[20:19] <jcastro> I was suspecting that
[20:19] <jcastro> thanks
[20:23] <kenvandine> np
[20:23]  * kenvandine really hopes someone figures that out soon :/
[20:24] <kenvandine> my poor laptop is getting hot
[20:24] <jcastro> we're blaming dobey for this one right?
[20:25]  * dobey blames gnome-keyring people for mucking with threading inside the library
[20:25] <kenvandine> hehe
[20:25] <kenvandine> not dobey *this time* :)
[20:25] <mvo_> mdc_laptop: thank you!
[20:26] <mdc_laptop> :-)
[20:26] <kenvandine> dobey, you worked around it though..
[20:26] <mdc_laptop> np
[20:26] <dobey> kenvandine: in ubuntuone-client, yes :)
[20:26] <kenvandine> i am aftaid to try to do that in gwibber
[20:26] <dobey> i don't know where it's failing exactly in gwibber
[20:26] <kenvandine> funny thing though... when desktopcouch has the CPU pegged, gwibber doesn't
[20:27] <kenvandine> we only have like 2 lines that access the keyring
[20:27] <dobey> well you can't have 2 apps using 100% cpu
[20:27] <kenvandine> in the service anyway
[20:27] <jcastro> I am waiting for each of them to take a core
[20:27] <dobey> they can both use 50% though
[20:27] <kenvandine> dobey, bug gwibber-service is nearly idle most of the time when dc has it pegged
[20:29] <dobey> bah
[20:29] <dobey> kenvandine: url me to the code that calls keyring in gwibber
[20:29] <kenvandine> dobey, one sec
[20:31] <kenvandine> dobey, http://bazaar.launchpad.net/~gwibber-committers/gwibber/2.30/annotate/head%3A/gwibber/microblog/dispatcher.py
[20:31] <kenvandine> around line 53
[20:39] <dobey> ok, i see the problem :)
[20:40] <kenvandine> dobey, awesome.... how can i fix?
[20:40] <kenvandine> and can you find the problem in desktopcouch ?
[20:42] <dobey> one second, i have a branch to fix gwib :)
[20:42] <kenvandine> woot
[20:42] <kenvandine> dobey is my hero
[20:46] <dobey> lp can be slow sometimes
[20:48] <seb128> rickspencer3, pitti: bug #519553
[20:48] <seb128> I think that's an issue but I'm not sure what we should do about it
[20:51] <dobey> kenvandine: https://code.edge.launchpad.net/~dobey/gwibber/gwibber-keyring-unthreaded/+merge/22562
[20:51] <kenvandine> dobey, want to see if you can fix desktopcouch too?
[20:51] <dobey> i don't know if someone already did or not
[20:52] <seb128> is that fixing the cpu use issue?
[20:52] <kenvandine> seb128, i'll tell you in a few
[20:52] <dobey> seb128: yes. the problem is that it's threadlocking because gnome-keyring now does weird thread stuff in the library
[20:53] <seb128> hum
[20:53] <dobey> seb128: i fixed the lockups in ubuntuone, by switching the code to not run the keyring calls from threads
[20:54] <seb128> k
[20:56] <dobey> seb128: at least, my debugging points at that as the problem. my fixes in ubuntuone-client solved it there. it was blocking me from getting any work done on u1 after updating on monday :(
[20:56] <seb128> it started recently for you?
[20:56] <seb128> or did you just upgrade recently to lucid?
[20:57] <dobey> it started recently for me
[20:58] <dobey> it started after i managed to get rebooted on monday
[20:58] <dobey> it was only one of many problems i had
[20:59] <seb128> k weird
[20:59] <seb128> we have the cpu use issue on gvfs for weeks
[20:59] <dobey> like, one of the kernel updates apparently caused my hard disks to be reordered
[20:59] <dobey> so sda became sdb and vice-versa
[20:59] <dobey> which caused the boot to get stuck at the "checking filesystems" screen
[21:00] <baptistemm> pitti, for bluetooth I see there is a patch for disable hal, did you tried to just disable hal plugin sin main.conf ?
[21:01] <kenvandine> dobey, indeed that fixed it... but now there is a gtk import in the service... which ryan is very opposed to :/
[21:02] <kenvandine> seb128, the patch you uploaded on monday made it worse for ubuntuone-client and desktopcouch
[21:02] <seb128> well, it's a good workaround for lucid until stef look to gnome-keyring
[21:02] <seb128> oh ok
[21:02] <seb128> I'm fine dropping that one
[21:02] <kenvandine> gwibber was the same with and without the patch
[21:02] <kenvandine> which is weird
[21:02] <seb128> it was a try to see if that fixed the issue
[21:02] <seb128> but it doesn't
[21:02] <dobey> kenvandine: hmm
[21:03] <kenvandine> dobey, scratch that... your branch didn't fix it
[21:03] <seb128> kenvandine, I will drop the change now
[21:03] <kenvandine> just sometimes it takes longer to see the load
[21:03] <dobey> kenvandine: well you can fix libgnome-keyring0 to not rely on the glib main loop, and be thread safe
[21:03] <kenvandine> seb128, ok
[21:04] <dobey> huh?
[21:04] <dobey> weird
[21:04] <kenvandine> dobey, gwibber-service is now using 100% of one processor when the logs says it should be idea
[21:04] <kenvandine> idle
[21:04] <dobey> hrmm
[21:04] <dobey> perhaps there is another location that needs fixed?
[21:05] <kenvandine> nope
[21:05] <kenvandine> not in the service
[21:07] <dobey> weird
[21:07] <dobey> well the issue is that the keyring is being called in a thread that's not the glib main loop
[21:55] <kenvandine> seb128, can you please sponsor lp:~ubuntu-desktop/gwibber/ubuntu
[22:00] <seb128> kenvandine, ok
[22:04] <kenvandine> seb128, thx
[22:04]  * kenvandine heads out
[22:35] <RAOF> Morning all.
[22:39] <chrisccoulson> hey RAOF
[22:40] <TheMuso> Morning all.
[22:41] <chrisccoulson> hmmm, i can't customize my mouse cursor any more :-/
[22:45] <Sarvatt> chrisccoulson: yay compiz :)
[22:46] <RAOF> C'mon, evolution.  Filter that mail.  You can do it!
[22:46] <chrisccoulson> Sarvatt - yeah, i just noticed it works with metacity
[22:46] <chrisccoulson> i wonder what has broken that then :-/
[22:46] <Sarvatt> been broken here for years
[22:47] <chrisccoulson> hmmm, it worked here until today
[22:47] <RAOF> Worked for me until last night.
[22:47] <chrisccoulson> so, i'm not the only person who has this issue appear recently?
[22:48] <chrisccoulson> that's ok then :)
[22:50] <Sarvatt> it doesn't work for me right now, but I first noticed it didn't work under compiz in intrepid so I don't usually try and didn't notice if it did :D
[22:54] <seb128> chrisccoulson, bug #459647
[22:55] <chrisccoulson> seb128 - thanks. so, it doesn't look like it's a new issue then :-/
[22:56] <seb128> no
[23:00] <Sarvatt> chrisccoulson: maybe try booting alpha 3 or beta 1 and see if it really works there? looks like there was *some* change in the behavior in the past few days worth of updates at any rate judging by that bug report's responses
[23:07] <Sarvatt> hmm yeah my wife just said yesterdays updates (3 days worth) changed it so the oxygen cursor is used instead of DMZ (White) that was working before and she can't change it
[23:19]  * bryceh waves to RAOF
[23:19] <bryceh> RAOF, btw just posted a biggish update to -intel
[23:20] <Nafai> Hi aussie friends!
[23:20] <RAOF> Nafai: Good morning.  Or evening.  Or day!
[23:20] <RAOF> bryceh: Good morning :)
[23:21] <Nafai> RAOF: Afternoon here, :)  4:21 PM