[00:08] <serialorder> hi, id like to join you guys in maintaining the desktop packages and am looking at this (quite long) list here: http://piware.de/workitems/desktop/lucid/versions.html
[00:09] <serialorder> i am wondering what the policy is for the ones that are not the latest version in debian
[00:10] <serialorder> one could imagine that for those we just wait for debian to update and then import once they have done so
[00:22] <chrisccoulson> serialorder - we don't have to wait for debian to update. we can update to the latest upstream version before debian does, or we can re-sync on the current debian version and update to the latest upstream version all in one go
[00:22] <chrisccoulson> but we're being quite conservative with which packages to update at the moment
[00:23] <serialorder> oh
[00:23] <chrisccoulson> because we don't want to risk introducing features which are not likely to be finished properly when lucid is delivered
[00:23] <serialorder> might you suggest a package that would be acceptable for me to work on?
[00:25] <chrisccoulson> seialorder - i haven't had a chance to look at the list yet, and i'm just about to go to bed. it's probably ok to do merges with debian for most packages, especially if the upstream versions are the same. but i'm not so sure about doing gnome 2.29.1 updates just yet
[00:26] <chrisccoulson> ^^^serialorder (i spelt your name wrong there)
[00:28] <chrisccoulson> mclasen - about the seahorse-agent crash - the X connection dying is actually a red-herring
[00:28] <chrisccoulson> the crash happens when exit() is called from any code path
[00:28]  * mclasen thinks that atexit handler may be his fault, actually
[00:28] <chrisccoulson> mclasen - it is
[00:28] <mclasen> because I complained  about the agent leaving tmpdirs behind
[00:31] <mclasen> did you reopen the upstream bug ? might be a good idea...
[00:32] <chrisccoulson> mclasen - i haven't seen the upstream bug yet
[00:32] <chrisccoulson> i left a comment here last night after i had a look at it: https://bugs.launchpad.net/ubuntu/+source/seahorse-plugins/+bug/429322/comments/37
[00:32] <chrisccoulson> it describes what I *think* is happening, but i haven't had time to look at it any more tonight
[00:40] <chrisccoulson> mclasen - oops, i misread your earlier message "thinks that atexit handler may be his fault, actually"
[00:40] <chrisccoulson> i read it as "thinks that atexit handler may be at fault, actually" when i replied "it is" ;)
[00:42] <mclasen> https://bugzilla.gnome.org/show_bug.cgi?id=579738 is the bug you probably want to reopen
[01:21] <chrisccoulson> i wish launchpad would not spam everybody each time a duplicate bug is reported
[01:21] <chrisccoulson> thats not good for a bug wit over 100 duplicates
[01:45] <Ng> chrisccoulson: it's the equivalent of bugzilla mailing you when someone CCs themselves to a bug ;)
[01:45] <Ng> (ignoring that you can stop it doing that)
[01:46] <chrisccoulson> yeah, it's really annoying
[01:46] <chrisccoulson> especially when people start sending "unsubscribe" messages and adding to the spam
[06:55] <TheMuso> robert_ancell: Sorry, screwed up with dch -r for brasero, meant to have your name on the changelog sign-off line.
[08:28] <pitti> Good morning
[08:30] <didrocks> hello pitti :)
[08:30] <didrocks> seems that we will have to update all our branches (and that seb128 will have to upgrade his netwoork connection too)
[08:39] <baptistemm> good morning gentlemen
[08:45] <Amaranth> not so sure I want to switch compiz to having all the source in bzr
[08:46] <Amaranth> would make it easier to update quilt patches but the only point I can see for having everything in bzr is 3.0 (bzr) source package format
[09:02] <seb128> hello there
[09:03] <chrisccoulson> hi seb128
[09:04] <huats> morning
[09:05] <pitti> hey seb128
[09:05] <pitti> huats: bonjour
[09:05] <seb128> hey chrisccoulson huats pitti
[09:05] <pitti> huats: would you mind testing udev in karmic-proposed and give feedback on the bug report? so that it can move to -updates soon?
[09:06] <huats> pitti, Guten Tag
[09:06] <huats> pitti, sure will do it right now
[09:06] <huats> hello seb128 and chrisccoulson
[09:06] <pitti> huats: merci
[09:06] <pitti> hey chrisccoulson
[09:07] <chrisccoulson> hey pitti and huats too
[09:07] <chrisccoulson> how is everyone this morning?
[09:07] <pitti> very lucid :)
[09:07] <chrisccoulson> heh ;)
[09:08] <chrisccoulson> i still haven't done any lucid stuff yet!
[09:08] <seb128> lol
[09:08] <huats> SO BUSY !
[09:08] <seb128> I'm good, 3 days weekend again this week
[09:08] <chrisccoulson> seb128 - i bet you're looking forward to that ;)
[09:09] <chrisccoulson> my weekend will be shorter than usual, as i have to work a full day today
[09:09] <seb128> sort of yes
[09:09] <chrisccoulson> (well, i need to work at least until all of my colleagues have gone home)
[09:09] <seb128> travelling on monday though so that will be a bit less relax
[09:10] <chrisccoulson> it's quite a long journey too isn' it/
[09:10] <seb128> having to wake up quite early, to pack before
[09:10] <seb128> and I didn't prepare my specs, etc yet
[09:10] <seb128> yes, some 15 hours travelling
[09:26] <seb128> pitti, 2028 i386 bugs to retrace
[09:26] <pitti> seb128: hm, it seems it's going _up_?
[09:26] <seb128> 689 amd ones
[09:27] <seb128> pitti, no
[09:27] <pitti> ♪ MADNESS takes its toll! ♫
[09:27] <seb128> pitti, 2181 892
[09:27] <seb128> those were yesterday's numbers
[09:27] <seb128> catching up slowly
[09:28] <seb128> pitti, could you stop restarting to hardy ones?
[09:28] <seb128> the load is 6 on the box
[09:28] <seb128> it would be faster to let only the karmic ones catch up now
[09:28] <pitti> seb128: hardy-amd64 is the one that processes all the python dupes, thuogh
[09:28] <seb128> oh ok
[09:28] <seb128> ignore me then
[09:28] <pitti> and the python ones should not cause much load; it's primarily LP communication
[09:29] <pitti> seb128: 6? hah, I've seen the box at 50 :)
[09:29] <pitti> (no fun to work on it then, though)
[09:29] <pitti> seb128: you know, I think I'll just change the cronjob to remove the lock
[09:29] <seb128> the brutal way
[09:30] <pitti> seb128: then we can let it catch up, and then investigate real breakage
[09:30] <seb128> but yes please do for the weekend at least
[09:30] <seb128> got some weird firefox issues
[09:30] <seb128> I untagged those
[09:31] <seb128> weird = binary not available
[09:31] <seb128> not sure if some directory changed or something
[09:31] <seb128> I didn't look into details
[09:31] <seb128> like it was installing firefox but still complain that the required binary was not there
[09:32] <pitti> seb128: oh, heck, no; cron job must not remove the lock files, otherwise they'd overlap and run in parallel
[09:32] <pitti> seb128: yeah, usually a previous microversion
[09:32] <seb128> good point
[09:32] <pitti> seb128: but I thought I already fixed that in karmic's apport
[09:32] <seb128> I though too
[09:32] <seb128> I will ping you next time it happens
[10:03] <seb128> bbl
[13:10] <ccheney`> i got a weird notify your distributor message in my notify area in karmic
[13:30] <Laney> pitti: (or someone else), could you pocket copy f-spot from karmic-proposed to lucid?
[13:31] <Laney> I'll sort the sync out as and when
[13:31] <pitti> Laney: yes, I'll do that anyway
[13:31] <Laney> oh cool
[13:31] <Laney> thought I might have put you off by saying that I planned to sync it
[13:38] <mpt> ccheney`, did it look like this? http://grossmeier.net/files/stupid-error.png
[13:48] <chrisccoulson> hmmm, there's a bug pattern for bug 429322, but it seems that users are still submitting them with apport
[13:53] <chrisccoulson> oh, ok, there is no bug pattern for it
[13:53] <chrisccoulson> it seems that there is a commit which says one was added, but the xml file is not included :-/
[14:01] <ccheney`> mpt: looking
[14:05] <ccheney`> mpt: yes that is it
[14:19] <rickspencer3>      good morning
[14:19] <pitti> hey rickspencer3
[14:28] <mac_v> mpt: ccheney`: Bug #423694
[14:29] <mac_v> for some the blanking it fixed  , but some get the message even with no blanking
[14:30] <chrisccoulson> mac_v - are you saying that some people are experiencing other issues in addition to seeing this icon?
[14:30] <chrisccoulson> i see the icon when i shouldn't see it, but there are no other issues
[14:31] <mac_v> chrisccoulson: in bug #397839 , users are still reporting blanking
[14:31] <chrisccoulson> hmmm, ok. i can't recreate that issue
[14:32] <chrisccoulson> under what conditions are they seeing blanking? does it blank when they are doing stuff, or just when they are watching a video (but not doing anything else)
[14:32] <chrisccoulson> that information is fairly important (i have to admit, i've not looked the whole way through the bug report yet)
[14:37] <chrisccoulson> anyway, home time for me
[14:37] <mac_v> chrisccoulson: thats why i was saying the idle counter still has some mismatch, somewhere... initially , even after the xorg patch, i too was having blanking [during typing and such] but blanking was fixed for me . and still the icon was displayed. so i thought it might have been a problem where the icon is unnecessarily displayed.  But the blanking had not gone fully , but rather became rarer...
[14:38] <mac_v> now , i have no blanking and now the icon is not displayed
[14:38] <chrisccoulson> that's strange. anyway, i've got to disappear now
[14:38] <chrisccoulson> weekend, here i come!
[14:38] <chrisccoulson> it might be my last weekend of freedom!
[14:38]  * mac_v vanishes too ;)
[14:59] <dpm> pitti, ccheney` I was thinking about having a dedicated session on OO.o translations, but seeing that there is https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-lucid-openoffice already, do you think it might be a better idea to discuss translations in there as well instead?
[15:00] <pitti> dpm: I defer to ccheney` for this; I'm fine either way; just let me know if you need a new session scheduled
[15:01] <dpm> thanks pitti
[15:01] <dpm> ccheney`, what do you think^?
[15:02] <ccheney`> dpm: yea we could do it in that session i think, its just an informational session so won't take too long
[15:05] <dpm> thanks ccheney`, may I ask you or pitti to add a short note on translations on the summary as well? Or if you've got a wiki page for the spec, I can do that myself
[15:05] <pitti> it's just a blueprint so far
[15:05]  * ccheney` in a meeting atm
[15:06] <dpm> no worries
[15:07] <pitti> I'll change it accordingly
[16:18] <Laney> I wonder why my laptop screen randomly dims
[16:18] <Laney> (and doesn't come back)
[17:26] <huats> pitti, I have commented the bug saying it works great with the one in proposed
[17:26] <huats> thanks again...
[17:26] <pitti> thanks
[17:26] <huats> sorry for the delay
[17:27] <pitti> np, it still needs to bake a bit anyway
[17:37] <and471> kenvandine: what is the correct/desired behaviour for xsplash on a dual monitor setup?
[18:02] <chrisccoulson> Laney - is your display dimming issue repeatable?
[18:05] <chrisccoulson> mclasen - do you have any opinion on bug 428884? (ie, do you think this functionality should be added back to gnome-screensaver)
[18:10] <mclasen> chrisccoulson: there's a FIXME in the code that describes what needs to be done to make it work again
[18:11] <chrisccoulson> mclasen - yeah, i was just wondering how to do it though. it seems that gnome-session and totem both contain some code which resets IDLETIME by simulating fake key presses, using xtest
[18:12] <mclasen> chrisccoulson: but as a general comment, idle handling is now in gnome-session, and inhibitors are the supported api to, well, inhibit things
[18:12] <Laney> chrisccoulson: not at will. I'll get back to you shortly when I get home
[18:12] <Laney> brb
[18:12] <chrisccoulson> mclasen - yeah, agreed
[18:12] <chrisccoulson> but some applications still rely on the old interfaces for now
[18:13] <chrisccoulson> mclasen - i'm just wondering if gnome-screensaver should copy the send_fake_event function from gnome-session, or if there is a better way to do it?
[18:14] <pitti> good bye everyone, have a nice weekend!
[18:14] <chrisccoulson> (although, judging from the comment in gnome-session, i don't think there is a better way)
[18:14] <chrisccoulson> have a good weekend too pitti!
[18:14] <chrisccoulson> are you travelling next week too?
[18:44] <kenvandine> and471, i am not sure actually, never seen it
[18:44] <kenvandine> bratsche, ^^
[18:44] <and471> bratsche: what is the correct/desired behaviour for xsplash on a dual monitor setup?
[18:49] <bratsche> and471: At the moment I think it just puts itself on monitor #0, regardless of which monitor is the primary one.
[18:49] <and471> bratsche: yup, what SHOULD be the behaviour though/what will you work up towards having it do?
[18:50] <bratsche> and471: That was never defined in the requirements, but presumably it should be put on the primary monitor.
[18:50] <and471> bratsche: okay, what happens on the other monitor whilst this is happening?
[18:51] <bratsche> Right now it's drawn by gnome-settings-daemon, and it will continue to be until someone specifies otherwise.
[18:52] <and471> bratsche: its just that at the moment, it shows the desktop before xsplash has finished and so it doesn't look very slick
[18:52] <and471> and471: will it be a black screen in the future? or what are the plans?
[18:53] <and471> bratsche: ^^ sorry talking to myself
[18:53] <bratsche> There's supposed to be a session on this at UDS, and I suppose people will have some thoughts there.  Right now there are no plans, I'm working on other stuff.
[18:56] <and471> bratsche: okay thankyou for you time :-)
[18:56] <and471> *your
[18:58] <bratsche> If you have something specific in mind, let me know.  But otherwise I'm not really thinking at all about xsplash these days.
[18:58] <and471> bratsche: not really, was just wondering what would happen, but at the moment a simple option is just a black screen that fades into the desktop the same time as the main splash
[18:59] <and471> bratsche: but I get you aren't working on xsplash now :-)
[20:24] <Laney> chrisccoulson: Hi there. Got any debugging hints? note: I am using some kernel module (nvidia-bl) that I got from a PPA to make it work so it could well be that
[20:32] <Laney> alright so I think it's when it restores from dimming it doesn't go back to the previous level
[20:32] <Laney> and it seems to dim too rapidly
[20:43] <Laney> oh
[20:44] <Laney> it's the "reduce display brightness" option I think
[21:24] <RevVader> anyone in here an lvm/luks/cryptsetup type person?
[22:08] <didrocks> pitti: thanks for the ack
[22:08] <didrocks> pitti: and for the link on how enabling proposed :) (ok, that's a user generic mail ;))
[22:56]  * Amaranth looks at his inbox and weeps
[22:57] <Amaranth> Did apport get turned off yet?
[23:13] <bryce> Amaranth, do the bugs mention Checkbox?
[23:14] <Amaranth> bryce: no, the "compiz crashes inside the nvidia libGL on close" one
[23:14] <Amaranth> I keep getting dupes but I don't know if those were just sitting around since apport apparently died recently
[23:15] <bryce> mm could be
[23:15] <bryce> fwiw I'm not seeing tons of apport bugs at the moment
[23:17] <bryce> I count 7 reported within the past week
[23:17] <dtchen> Amaranth: you can have my grub bugs if you'd like to trade.
[23:17] <Amaranth> probably old bugs that never got retraced
[23:17] <bryce> which could all be leftovers from pre-release installs I suppose
[23:17] <Amaranth> dtchen: No thanks, compiz is painful enough
[23:17] <bryce> I was getting inundated by checkbox bugs though.  glad to get that turned off
[23:18] <Amaranth> dtchen: That reminds me though, did you see that adding module-x11-bell or whatever to pulseaudio wasn't working to get the beep while using compiz anymore?
[23:18] <Amaranth> I mentioned that after adding a pulseaudio task so I dunno if you ever saw it
[23:18] <bryce> mostly "resolution isn't right" bugs.  I ought to investigate when I get a chance, in case it's something more than just monitors with bad edid or whatever
[23:19] <dtchen> Amaranth: it works here, though I tested using xmonad and metacity
[23:20] <Amaranth> dtchen: metacity doesn't even need it, metacity uses libcanberra directly to do the beep
[23:20] <Amaranth> while compiz and (I'm guessing) xmonad tell X to do it
[23:20] <dtchen> right, but I tested xmonad (my normal env)
[23:21] <dtchen> I suppose I'll just iterate through the other DEs I have
[23:21] <Amaranth> It might just be my computer, dunno
[23:21] <Amaranth> Maybe I've got the channels wrong or something
[23:21] <Amaranth> I know if I use 2ch I don't get the LFE or whatever but I've also got 4ch, 5ch, and 6ch to choose from
[23:23] <dtchen> all of which probably are getting bitten by the MMX bug
[23:23] <dtchen> [but are not related to this bell issue, I suspect]
[23:23] <Amaranth> mmx bug?
[23:24] <dtchen> the optimized asm for volume and channel mapping
[23:24] <Amaranth> ah
[23:24]  * Amaranth curses at launchpad