[00:06]  * Keybuk gets very deliriously happy about painting the screen blue
[00:07] <chrisccoulson> not purple?
[00:08] <Keybuk> not purple yet
[00:08] <chrisccoulson> ah
[00:08] <Keybuk> I won't do purple until tomorrow
[00:08] <Keybuk> because purple involves fucking around with the palette
[00:08] <Keybuk> and that involves thinking about colour matching algorithms
[00:08] <Keybuk> and that sounds like work instead of fun
[00:09] <chrisccoulson> yeah, you should wait until it's not the weekend ;)
[00:14] <RAOF> Keybuk: What?  Wait!  Futzing around with VGA registers was *fun*? :)
[00:15] <Keybuk> yes
[00:35] <Keybuk> http://twitpic.com/18nmqr
[00:39] <RAOF> Nice :)
[00:40] <Keybuk> I like magenta
[00:41] <Keybuk> I'm just setting the 8 basic colours by seeing if there's more then X% r/g/b in the argb32 buffer ;)
[00:41] <Keybuk> tomorrow I'll replace that with proper palette setting and a best match algorithm
[01:45] <Sarvatt> robert_ancell: how recently did it start?
[02:01] <robert_ancell> Sarvatt, been happening for most of Lucid
[02:01] <robert_ancell> I did change hardware about that time though so don't know if it's due to that
[06:35] <pitti> Good morning
[06:35] <robert_ancell> pitti, hey!
[06:35] <robert_ancell> pitti, do you have a good morning script?
[06:35]  * bryceh waves
[06:36] <pitti> RAOF: yes, apport reporting on staging is busted; so far I only commented in the relevant LP blog, but didn't get an answer yet, so a bug report against LP is fine
[06:36] <pitti> hey robert_ancell, how are you?
[06:37] <pitti> robert_ancell: script> hm, I never quite managed to fix the one which is supposed to make tea and breakfast; does your's work? :-)
[06:37] <pitti> I'd also appreciate one which automatically answers to over-weekend backscroll :)
[06:37] <bryceh> mine only makes coffee
[06:37] <pitti> that's something already
[06:37]  * RAOF is his wife's breakfast & tea script :)
[06:38] <lifeless> sudo mk_b & t; ?
[06:41] <robert_ancell> pitti, good, just realised we've fit beta freeze :)
[06:41] <robert_ancell> s/fit/hit
[06:41] <pitti> heh
[06:41]  * RAOF suddenly realises that there *is* a driver that has supported 3d for his nvidia card... the binary drivers!
[06:42] <RAOF> That'll make testing multi-head+netbook-launcher somewhat easier :)
[08:04] <dpm> good morning pitti. A question: how can the X-Ubuntu-Gettext-Domain key be added to packages that use python-distutils-extra? I was looking at the langpack.mk rule part that does that (http://pastebin.ubuntu.com/395505/), and that relies on the po folder containing a Makefile, which apps with p-d-e don't usually have. (I'm looking at bug 538851)
[08:13] <pitti> dpm: hmm -- the current build system doesn't even know about which gettext domain it's using
[08:15] <pitti> dpm: if we know, or would assume that it's the same as the project name, we might just create a po/Makefile with GETTEXT_PACKAGE=$projectname in python-mkdebian perhaps
[08:16] <didrocks> good morning
[08:17] <dpm> morning didrocks
[08:17] <didrocks> hey dpm, how are you?
[08:17] <pitti> hey didrocks
[08:18] <didrocks> Guten Tag pitti, how was your week-end?
[08:18] <pitti> pretty nice, thanks; your's?
[08:18] <dpm> didrocks, fine thanks, recovered from an annoying back injury last week
[08:19] <didrocks> pitti: yes, very great one, thanks :)
[08:19] <didrocks> dpm: oh? is it better now?
[08:19] <pitti> dpm: ugh, something serious?
[08:20] <RAOF> didrocks: Gooooooood morning!
[08:21] <didrocks> gooood evening RAOF :)
[08:21] <dpm> didrocks, pitti, I'm fine now, it wasn't anything serious, but couldn't move much last week and had to have a few physiotherapy sessions
[08:24] <dpm> pitti, on the general issue with p-d-e and adding the key to .desktop files, is there any way I can help on this? Shall I file a bug to any particular package?
[08:24] <dpm> In the meantime, in the particular case of gwibber, what do you think the best solution might be? Having a dummy Makefile with "GETTEXT_PACKAGE=gwibber" and then adding the langpack rule to debian/rules would work, but it sounds a bit hackish to me. Another option might be to just add the X-Ubuntu-Gettext key to the upstream files
[08:25] <pitti> dpm: adding it to the upstream files sounds like a good idea indeed
[08:26] <dpm> pitti, ok, I'll go for proposing that, then
[08:26] <pitti> dpm: the general fix is not immediately clear to me, since we don't have a way to set the gettext domain right now
[08:26] <pitti> dpm: btw, for upstream purposes they might use X-GNOME-Gettext-Domain
[08:26] <dpm> ah, yeah, good point, I forgot we were picking that one up as well
[08:29] <dpm> ok, thanks a lot pitti
[09:17] <Keybuk> tseliot: morning, how was your break?
[09:17] <pitti> hey tseliot, good morning Keybuk
[09:17] <tseliot> Keybuk: good morning, I feel much better now :-)
[09:17] <tseliot> morning pitti
[09:18] <Keybuk> tseliot: yes, you should take more day soff
[09:18] <tseliot> yes, I guess it will help me not to burn out ;)
[09:18] <Keybuk> that was what annoyed me most about that idiotic forums poll of "Developers should work weekends until release"
[09:18] <seb128> hey
[09:18] <Keybuk> as if we work better the closer we get to burn out ?!
[09:19] <Keybuk> personally I work best on a three hour day on a beach in the bahamas
[09:19] <tseliot> heh
[09:19] <tseliot> right
[09:19] <tseliot> :-)
[09:19] <seb128> pitti, do we really need to go through those unit changes and flameware now, can't that be reported to next cycle?
[09:19] <pitti> seb128: yes, I'm sure it can
[09:19] <pitti> seb128: bonjour
[09:20] <Keybuk> tseliot: I owe you an apology
[09:20] <pitti> seb128: I think we should revert the glib change and instead just fix nautilus fornow
[09:20] <tseliot> Keybuk: for what?
[09:20] <pitti> seb128: WDYT?
[09:20]  * seb128 hugs pitti
[09:20] <seb128> pitti, I'm all for it
[09:20] <Keybuk> tseliot: I had thought looking at the Plymouth code, and with no understanding, that the vga16fb stuff would not be hard
[09:21] <Keybuk> it looked like plymouth just needed to support visuals other than "true colour"
[09:21] <Keybuk> and thus just needed indexed palette stuff dropped in for the colours
[09:21] <seb128> pitti, we have lot of real bugs to work on without doing such changes and fighting the side effects
[09:21] <Keybuk> as you found out, it's not that easy
[09:22] <didrocks> hey seb128, morning Keybuk
[09:22] <tseliot> Keybuk: yes, it's not that easy but we can do it. No need for an apology. It's been a rather interesting learning experience :-)
[09:22] <seb128> lut didrocks
[09:23] <Keybuk> tseliot: I got most of the way - http://twitpic.com/18nmqr
[09:24] <tseliot> Keybuk: hey, that's much better than gray vertical lines ;)
[09:25] <baptistemm> asac, if I want to have http://www.bluez.org/obexd-022/ for lucid, I should request a FFe, right ?
[09:25] <Keybuk> tseliot: it needs palette creation and adaption though
[09:25] <baptistemm> it should solve corruption on file reception we have
[09:25] <Keybuk> at least you found the code to set the palette up already ;)
[09:25] <baptistemm> hi there everyone by the way
[09:26] <tseliot> Keybuk: right. Do you have the code somewhere so that I can take a look?
[09:27] <Keybuk> yup, give me a few minutes
[09:27] <Keybuk> just got to get laptop booted
[09:27] <Keybuk> press enter, then let X restart ;)
[09:28] <tseliot> heh
[09:34] <didrocks> baptistemm: hey ;) if it's just a bugfix version, no need
[09:42] <chrisccoulson> good morning everyone
[09:42] <pitti> hey chrisccoulson
[09:42] <chrisccoulson> hey pitti, how are you?
[09:43] <pitti> I'm great, thanks!
[09:50] <didrocks> hey chrisccoulson
[09:50] <chrisccoulson> hey didrocks, how are you?
[09:51] <didrocks> chrisccoulson: I'm fine thanks. Week-end without any email nor blog post reading. A lot to catch up today :)
[09:51] <didrocks> chrisccoulson: you?
[09:51] <chrisccoulson> yeah, i'm good thanks.
[09:51] <chrisccoulson> lots to catch up on today as well :)
[09:54] <chrisccoulson> that is seriously weird
[09:55] <chrisccoulson> i've just started copying a file from my desktop to my laptop, and my mouse has gone really jittery
[09:56] <seb128> hey chrisccoulson
[09:56] <chrisccoulson> hey seb128, how are you?
[09:56] <seb128> chrisccoulson, good, thanks! you?
[09:56] <seb128> lot of monday catchup to do there too
[09:56] <seb128> pitti, have you seen this bug about apport not able to connect to launchpad?
[09:56] <pitti> seb128: which one?
[09:56] <chrisccoulson> yeah, i'm good too thanks. i've just got my first coffee of the day
[09:56] <pitti> seb128: I know that it's totally broken on staging
[09:56] <seb128> bug #538097
[09:57] <seb128> pitti, ^ the one rick assigned to our team to sort
[09:57] <chrisccoulson> yeah, it's totally broken for everybody at the moment it seems
[09:57] <chrisccoulson> i would like to report a kernel bug about my file system corruption ;)
[09:57] <pitti> seb128: I'll have a look later on; I suspect it's an LP problem, but I'll check
[09:58] <seb128> pitti, thanks
[09:58]  * pitti still wrestles with gupnp-igd
[10:09] <seb128> bah
[10:10] <seb128> there is lot of noise following up the glib unit change
[10:10]  * seb128 marks another 15 emails as read on the topic
[10:10] <seb128> like half of those weekend bugs and comments are due to it
[10:11] <seb128> we should have a policy of not changing things if users don't complain about those ;-)
[10:16] <pitti> bigon: hi! hm, I'm afraid I need your help with bug 534311
[10:17] <pitti> bigon: I'm still waiting for my bz.openhand account creation (the mail seems to take ages), but perhaps you could look at my last comment in the LP bug?
[10:20] <bigon> pitti: the only issue still the g_warning, right?
[10:21] <pitti> bigon: I haven't reproduced that one yet, but I figure that's because I have a system d-bus running
[10:21] <pitti> bigon: I'll get to that next (there's an existing bug report)
[10:21] <pitti> bigon: ah, I found the bz mail in my spam filter, I'll register now and open an upstream bug for the CONSTRUCT_ONLY thing, if you want me to?
[10:22] <bigon> it could be interesting to disable nm support in gupnp (see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568892)
[10:22] <bigon> pitti: ok no problem
[10:24] <pitti> bigon: http://bugzilla.openedhand.com/show_bug.cgi?id=2031 now
[10:38] <bigon> pitti: downgrading the severity from g_warning to g_debug or something is the easiest way I think but the other bug could hit libnice like on debian
[10:39] <pitti> bigon: ok, I'll do that for now in the ubuntu gupnp package
[10:45] <seb128> robert_ancell, hey
[10:46] <robert_ancell> seb128, hey
[10:46] <seb128> robert_ancell, joining IRC after work hours now? ;-)
[10:46] <pitti> bigon: oh, git head tests succeed now, nice
[10:47] <robert_ancell> seb128, shh
[10:47] <seb128> ;-)
[10:47] <seb128> robert_ancell, how are you otherwise? had a good weekend?
[10:48] <robert_ancell> seb128, yeah, went to the zoo
[10:48] <seb128> to the Sydney one?
[10:50] <robert_ancell> seb128, yup.  didn't want to head out too far :)
[10:50] <robert_ancell> seb128, how is desktop work going?  We on track?
[10:50] <seb128> the Sydney zoo is quite nice, we have been there back then when visiting Sydney before UDS ;-)
[10:51] <seb128> there was a firework on the way back too ;-)
[10:51] <robert_ancell> seb128, yeah, I like the gondola so you can scope out what to see on the way up
[10:51] <robert_ancell> good timing!
[10:51] <seb128> indeed!
[10:54] <bigon> pitti: be carefull I get some random success/fails with the testes
[10:56] <robert_ancell> seb128, I was trying to work out, is imagemagick on the cd?  it is in maun
[10:56] <robert_ancell> main
[10:56] <pitti> main, yes
[10:56] <robert_ancell> where is the list of exactly which packages are on the cd?
[10:56] <pitti> robert_ancell: http://cdimage.ubuntu.com/daily-live/current/lucid-desktop-i386.manifest
[10:56] <pitti> and similar, *.manifest files for desktop CDs, and .list files for alternates
[10:57] <chrisccoulson> fantastic, my laptop is not being very nice to me again this morning
[10:59] <robert_ancell> pitti, I'm a bit worried imagemagick is too large.  I've used it in the latest simple-scan to get PDF compression working properly (though if it's not installed it falls back on the innefficient cairo versions)
[11:01] <Ng> robert_ancell: I don't think you were on here over the weekend when I said this... Simple Scan is utterly fantastic, thanks very much :)
[11:01] <seb128> pitti, trivial change to fix indicator-session switch from entry not being translated, is that for now or after beta rather?
[11:02] <robert_ancell> Ng, thanks!
[11:02] <seb128> pitti, ie should I upload or just wait for after beta?
[11:02] <pitti> seb128: upload it now; at worst, it'll stay in unapproved until after beta
[11:02] <seb128> pitti, ok thanks
[11:02] <pitti> but I'll review it
[11:02] <pitti> sounds fine for beta
[11:02] <Ng> robert_ancell: I bought an HP 4580, plugged it in, I could scan and print immediately with zero configuration. Also fwiw after poking at it with hp-toolbox I can scan and print to it over its wifi connection \o/
[11:03] <robert_ancell> Ng, nice!
[11:03] <Ng> sadly it doesn't avahi announce its scanning ability or I'd be asking for that to appear in the source list, but I can fire it up from hp-toolbox (which btw still defaults to xsane)
[11:11] <robert_ancell> gtg, no time to chat :(  See you all later!
[11:29] <chrisccoulson_> seb128, the visual problems we see with the notification area don't seem to be confined to just the notification applet
[11:29] <chrisccoulson_> i got it with my clock this morning too
[11:29] <chrisccoulson_> http://people.canonical.com/~chrisccoulson/Selection_001.png
[11:29] <seb128> urg
[11:35] <didrocks> chrisccoulson_: I noticed that this week-end too, but I didn't upgraded on my netbook for 4 days, so, I was waiting (never got that on my laptop)
[11:35] <vish> chrisccoulson_: hi.. regarding the new touchpad on/off notification , i'v seen you mention it.. but there is a bug the scalable icon seems to be the source icon rather than a cropped 48px version , this ends up being displayed rather than the 48px icon which package do i file the bug?
[11:35] <chrisccoulson_> vish - gnome-settings-daemon
[11:35] <vish> ty
[11:36] <chrisccoulson_> didrocks - yeah, i get the issue quite often
[11:36] <chrisccoulson_> but it normally only affects the notification area
[11:36] <chrisccoulson_> vish, with screenshot preferably
[11:36] <chrisccoulson_> i don't have a touchpad button ;)
[11:36] <vish> sure :)
[11:36] <chrisccoulson_> thanks
[11:46] <chrisccoulson_> kklimonda - what is the impact of "build transmission gtk+ client with both gconf and libcanberra support"
[11:46] <chrisccoulson_> does that make the client use gconf for all the configuration storage?
[11:52] <vish> chrisccoulson_: Bug #539025 with screenshots
[12:30] <seb128> mvo, hi
[12:30] <seb128> mvo, bug #530430, can I assign that one to you?
[12:31] <seb128> the polkit action returns an Error parsing subject struct
[12:32] <seb128> mvo, since you are the one who wrote the changes... ;-)
[12:34] <seb128> not sure if that's an ubuntu-system-service bug though
[12:48] <mvo> seb128: I can have a look now
[12:49] <mvo> seb128: hopefully its just something with polkit
[12:49] <seb128> mvo, thanks
[12:49] <mvo> seb128: will you/your team work on the UI change for http proxy inconsitencies :) ?
[12:50] <pitti> mvo: error parsing subject struct> that rings a bell
[12:50] <seb128> mvo, I don't know about this bug so I doubt it
[12:50] <seb128> pitti, I think you fixed a bunch of similar issue at start of the cycle
[12:50] <pitti> mvo: I got the same in jockey with the new polkit, it needs the start-time now
[12:50] <pitti> and usb-creator used the same code
[12:51] <mvo> pitti: aha, cool. I fix it, I saw in computer-janitor some days ago but forgot to fix it in u-s-s :(
[12:51] <mvo> pitti: doing that now :)
[12:51] <pitti> gnome-lirc-properties as well -- let's see how many other places copied my broken stuff :-P
[12:51] <mvo> pitti: heh :)
[12:51] <seb128> lol
[12:51] <pitti> mvo: ok, please ping if you need any help, or I should take a look at it
[12:51] <didrocks> pitti: everyone trust your code :)
[12:52] <pitti> well, it did work back then
[12:52] <pitti> but then PK got stricter
[12:52] <didrocks> oh ok, hence having the issue now
[12:53] <seb128> mvo, can you give details about your proxy question?
[12:53] <seb128> ie bug reference at least
[12:54] <mvo> seb128: sure, give me a second
[12:55] <pitti> I'm off for a bit, need to go to the supermarket
[12:55] <mvo> bug 432631
[12:56] <mvo> pitti: when you are back, could you have a look at comment https://bugs.edge.launchpad.net/ubuntu/+bug/432631/comments/9 please (if you haven't already)?
[12:56] <mvo> pitti: I saw it only after I did the apt upload
[12:58] <mvo> seb128: see bug above, its basicly that we need a way to warn if the system and session proxies are different
[13:00] <seb128> mvo, ok, reading
[13:02] <seb128> mvo, do we have any design recommendation on how to do that?
[13:04] <mvo> seb128: no :( sorry. at least not ATM. I need to think about it a bit more, maybe something simple as a "/!\ The system proxy settings are different from your settings [info]"
[13:04] <mvo> as a label on top/bottom
[13:04] <mvo> but that will need a UI freeze exception
[13:04] <seb128> right
[13:04] <seb128> I think that should be doable
[13:05] <mvo> let me know if you need help, I can try to help out, but not before beta-1 release (we will have to move it to beta-2 then)
[13:06]  * mclasen thinks we really need to get those system-wide patches upstream
[13:07] <mclasen> not healthy if you have some, and we have some others, and opensuse has some...
[13:07] <mvo> much agreed
[13:08]  * mvo tried to push them long ago when starting with the project, but did not got much love for them
[13:08] <seb128> right
[13:09] <mclasen> well, our patch wasn't loved either
[13:09] <mclasen> but I think fizz will accept them if we make it clear that everybody is shipping them anyway
[13:10] <mclasen> maybe we need to have that discussion on gnomecc-list
[13:11]  * mvo nods
[13:15] <mvo> seb128: fix commited, I upload in a little bit
[13:16]  * mvo should probably also test 
[13:16]  * seb128 hugs mvo
[13:16] <seb128> thanks
[13:16] <mvo> thanks, no worries
[13:23]  * didrocks just dicovered the "prerequisite" branch function in LP merge proposal. That's sweet
[13:37] <didrocks> seb128: just grabbing the sound patch for gdm now, let me backlog for robert's comment
[13:38] <seb128> so lp:~robert-ancell/gdm/gdmsetup-sound-enable
[13:38] <seb128> "
[13:38] <seb128> So, you just need to fill the blanks in common/gdm-settings.c
[13:38] <seb128> (09_gdmserver_sound_settings.patch).  Look for the '...' comments."
[13:38] <seb128> which is somewhat tricky
[13:38] <vish> mvo: hi.. i'm trying to add the icons for software store categories and subsections in Humanity , but i'm not sure what icon names software store looks for , there are too many subsections :s  more than what is listed in the gnome-menus , where can i find the icon names??
[13:38] <seb128> writing gconf config for a not running user sucks
[13:40] <soren> seb128: Isn't that what gconftool-2 --direct does?
[13:41] <seb128> soren, well it might be running or not
[13:41] <soren> Ah. :(
[13:41] <pitti> would it hurt to have a gconfd for gdm? gdm's dbus-daemon is running anyway
[13:41] <seb128> soren, we try to change gdm keys and the gdm gconf is active only when a greeter screen is displayed
[13:42] <mvo> vish: we can pick the iconnames, the file in /usr/share/app-install/software-center.menu, the key SCIcon
[13:42] <seb128> pitti, I guess not but how do you suggest to start it?
[13:42] <mvo> vish: if you send me the icons I will merge them and update the menu file
[13:42] <pitti> seb128: I thought libgconfd/gconftools would do that automatically
[13:42] <seb128> no, it tends to complain about failing to contact the server
[13:43] <didrocks> seb128: right, the code is tricky
[13:43] <vish> mvo: you want the icons to be included in the app[software store] itself? and not in the theme?
[13:43] <seb128> vuntz, mclasen: do you have an opinion on how to change a gconf key for an another user? there seems to be no easy way to do this
[13:44] <mclasen> seb128: you can't
[13:44] <seb128> :-(
[13:44] <mclasen> at least not in a supportable way
[13:44] <mclasen> his gconf db lives in his home dir
[13:44] <seb128> that's what I though
[13:44] <mclasen> which might be automounted
[13:44] <mclasen> or worse, encrypted
[13:45] <pitti> hardly for gdm, though?
[13:45] <mclasen> no
[13:45] <seb128> mclasen, well in this case that's for gdm
[13:45] <pitti> gdm is already running, after all
[13:45] <mclasen> yeah
[13:45] <mclasen> but it still doesn't work
[13:45] <seb128> mclasen, and we want to change it from the gdm server, so technically we can change the uid and do calls as gdm user
[13:45] <mclasen> thats why I set defaults/mandatory values in that case
[13:45] <seb128> we could change the ui and g_spawn gconftool
[13:46] <seb128> mclasen, the issue is that gdm and user sessions use the same keys
[13:46] <seb128> mclasen, so you change the setting for all users...
[13:46] <mclasen> yeah, well...you still can't really change another users gconf db
[13:47]  * seb128 wonders if we should some trick like write a file on disk
[13:47] <seb128> and make the greeter code change the gconf key on start when the file is there
[13:47] <mclasen> you can invent hacks like that
[13:47] <pitti> seb128: hm, TBH I still fail to see why seteuid(gdm) spawn(gconftool) would be failing, but if that's too hairy, perhaps we should write it to custom.conf instead
[13:47] <mclasen> pitti: it needs to run in the sandbox session (if there is one) so it can talk to the gconfd there
[13:47] <mclasen> you can run gconftool --direct on the db
[13:47] <pitti> seb128: it seems much easier to read custom.conf from the greeter session than to write gdm's gconf values from the daemon?
[13:48] <mclasen> but then you need to kill the gconfd in the sandbox session (if there is one)
[13:48] <seb128> pitti, right it seems so
[13:48] <mclasen> which might loose the unflushed changes that he has in memory
[13:48] <pitti> mclasen: why can't it just autospawn the gconfd if it's not running yet?
[13:48] <pitti> mclasen: gdm's session dbus is running all the time
[13:49] <mclasen> what keys are we actually talking about here, just the background ?
[13:49] <seb128> mclasen, the sound one
[13:50] <seb128> users want a way to make login quiet for use in public places
[13:50] <mvo> vish: oh, sorry. well, currently some of this have no icon names yet, so if you just pick some like "sc-category-boardgame" I will update the file
[13:51] <vish> mvo: neat, thanks..
[13:52] <seb128> mclasen, ie /desktop/gnome/sound/event_sounds  for the gdm user
[14:03] <didrocks> seb128: I think the most annoying part is not the sound in gdm, but the welcoming sound for the user you are login in. (and we are back about the issue of automounting and encrypted home)
[14:04] <seb128> didrocks, the welcoming sound?
[14:04] <seb128> didrocks, is that the session start sound?
[14:04] <didrocks> seb128: right
[14:04] <didrocks> seb128: this is per user, no?
[14:04] <seb128> didrocks, turning that one off from the sound capplet works
[14:04] <seb128> you can mute sound events there
[14:04] <seb128> I do it there and it works fine
[14:05] <didrocks> yes, I was thinking about per session like "I like the event sound, but not when in the train and I don't want to change before being there"
[14:06] <didrocks> that can be something we can work on next cycle, "launching a mute session"
[14:07] <tseliot1> rickspencer3: hey rickspencer3
[14:07] <rickspencer3> hi tseliot1
[14:08] <seb128> didrocks, ideally you could just press a key during boot to tell it to be quiet
[14:08] <seb128> didrocks, but anyway for this cycle we just want a way to tell gdm to not play the drum sound
[14:08] <didrocks> seb128: yeah, like Shift or something like that
[14:08] <didrocks> seb128: ok, it was just to ensure we were speaking about the same thing :)
[14:09] <seb128> I'm confused now about the best way to do what we want
[14:09] <seb128> hum
[14:09] <seb128> pitti, what do you think?
[14:09] <seb128> I think 3 ways
[14:10] <seb128> - trying to write in the gdm config
[14:10] <seb128> i.e calling g_spawn dbus-launch gconftool --direct
[14:10] <seb128> or without --direct if we use dbus-launch
[14:10] <seb128> - writing in custom.conf and making the greater read that
[14:11] <seb128> (not sure if it does now)
[14:11] <seb128> - just writing a file on disk and make the greater code set the key when it's there
[14:12] <pitti> seb128: (4) would be a less clean way of (3), I think
[14:12] <pitti> seb128: do we even need dbus-launch? it's already running
[14:13] <pitti> seb128: if g_spawn gconftool works, I'd use that; seems easiest to me
[14:13] <seb128> (4)?
[14:13] <seb128> I listed only 3 options :p
[14:13] <pitti> oh, sorry, s/4/3/ and s/3/2/ then
[14:13] <pitti> the --direct was on the start of the line here ;)
[14:14] <pitti> hey rickspencer3
[14:14] <kenvandine> hey seb128, FYI I pushed an updated app indicator patch for rhythmbox on friday, but not uploaded
[14:14] <seb128> kenvandine, doing what?
[14:14] <pitti> seb128: reading custom.conf should be easy, but would introduce a format incompatibility with upstream again
[14:14] <kenvandine> seb128, it was just removing a work around they had to use for a bug in app indicator
[14:14] <kenvandine> which is fixed now
[14:14] <seb128> kenvandine, oh, I've seen this email, thanks
[14:14] <kenvandine> np
[14:15] <kenvandine> not important enough for an upload... but the patch is there for next refresh :)
[14:15] <seb128> right
[14:15] <rickspencer3> hi pitti
[14:15] <rickspencer3> stupid dst
[14:15]  * rickspencer3 snore
[14:15] <seb128> pitti, " seb128: do we even need dbus-launch? it's already running"
[14:15] <seb128> pitti, what is already running?
[14:15] <pitti> gdm       3893  0.0  0.0  26248   840 ?        S    14:54   0:00 /usr/bin/dbus-launch --exit-with-session
[14:15] <pitti> seb128: ^ gdm's session dbus
[14:16] <seb128> pitti, it's not
[14:16] <seb128> pitti, running ps -u gdm = empty there
[14:16] <seb128> on the mini after a fresh boot and autologin
[14:16] <pitti> strange
[14:16] <pitti> aah
[14:16] <pitti> I don't have autologin here
[14:16] <seb128> the greeter is started first time you switch user
[14:16] <seb128> or when you don't use autologin
[14:17] <seb128> but in autologin case it's not started
[14:18] <seb128> pitti, I don't feel good about changing config format and are we sure the greeter has always right to read the daemon config?
[14:18] <mclasen> pitti, mvo: should I cc anybody from your side when starting a discussion about systemwide settings ?
[14:18] <mvo> mclasen: I'm on the mailinglist already, so that should be fine
[14:18] <seb128> same here
[14:18] <mvo> mclasen: thanks for pushing this again
[14:19] <mclasen> ok
[14:19] <seb128> pitti, I feel unsure about spawning gconftool for an another user too, we tried that previous cycle in the gdm postinst and ran into lot of issues
[14:20] <pitti> seb128: so, if you think it'll cause problems, let's go with the custom.conf thing then
[14:20] <seb128> pitti, I just don't feel comfortable adding hackish code in the server
[14:21] <seb128> let me check with #gdm guys what they think today
[14:21] <seb128> pitti, on an another hand adding the g_spawn call seems easy to do and not really crash prone
[14:22] <seb128> ie if the command fails the key is just not going to change
[14:22] <pitti> seb128: what kind of problems did we get in the postist scripts?
[14:22] <seb128> maybe we should do that now to get something in
[14:22] <pitti> seb128: at least that one seems to be revertable much more easily
[14:22] <pitti> and with a g_spawn_async() it would just be "fire and forget"
[14:22] <seb128> pitti, it was mainly pam issues by using sudo which will not get there
[14:22] <pitti> ah, right
[14:23] <seb128> + gconf not running which we worked around by using dbus-launch IIRC
[14:23] <seb128> I'm wondering if we should fire a gconftool --shutdown
[14:23] <seb128> and then a write --direct
[14:25] <pitti> seb128: the next action in a running gdm greeter would just respawn it again then, I think
[14:25] <pitti> so that might be better than dbus-launch
[14:25] <seb128> pitti, yes
[14:25] <seb128> ok, let's do that
[14:25] <seb128> didrocks, ^
[14:25] <seb128> didrocks, do you feel like doing that change?
[14:25] <seb128> didrocks, it's basically changing uid to the gdm one, doing 2 g_spawn_async calls
[14:25] <didrocks> seb128: right, can do that. I have also to add the get_sound_enabled method over dbus (not yet implemented)
[14:25] <seb128> didrocks, and going back to the previous uid
[14:26] <seb128> didrocks, robert_ancell didn't do that?
[14:26] <didrocks> seb128: no, he begans to write the get function but if I understand correctly the code, he didn't finish
[14:26] <didrocks> seb128: 2 g_spawn_async calls? how to know that the --shutdown will be finished before the --direct call?
[14:27] <seb128> didrocks, do the first one sync if you want
[14:27] <didrocks> seb128: ok
[14:27] <seb128> I've no strong opinion either way
[14:28] <seb128> didrocks, right it seems if just put an empty function for get
[14:28] <didrocks> seb128: yes, should be easy to fix
[14:56] <rickspencer3> bryceh, tedg, all InkScape devs - InkScape is awesome, that is all
[15:17] <sabdfl> cjohnston: hi
[15:17] <sabdfl> the plan is to stick with the current arrangement through beta1
[15:18] <pitti> rickspencer3, seb128: FYI, I talked to gary; he'll poke the apport bug uploading fix into production now (will take some 8 hours)
[15:19] <seb128> pitti, thanks
[15:20] <rickspencer3> pitti, thanks
[15:20] <rickspencer3> pitti, was this a diabolical plan to reduce our bug work load?
[15:21] <pitti> a FAILED plan
[15:21] <pitti> rickspencer3: it was a security fix for Launchpad which got a little too tight apparently
[15:22] <rickspencer3> heh
[15:25] <LaserJock> didrocks: is the go-home-applet icon hard-coded? I'm not sure if I'm supposed to see a monochrome Ubuntu logo or not
[15:25] <sabdfl> cjohnston: there are arguments for an against the move left. the decision to go left is mine, based on design preference and where i want the UI to move next
[15:26] <sabdfl> i'm open to real feedback, especially genuine reports of "i clicked the wrong thing accidentally" rather than speculative "people will click the wrong thing accidentally".
[15:29] <seb128> sabdfl, hey
[15:29] <seb128> sabdfl, how are you?
[15:29] <didrocks> LaserJock: it's not hard-coded, it's using a gconf key (just checked now). so, yeah, this should be changed
[15:29] <seb128> sabdfl, speaking about design do you know if the indicator message icon will go back to change to something less subtle?
[15:30] <pitti> like, something we can actually notice? :-)
[15:30] <pitti> seb128++
[15:30] <seb128> pitti, yeah, I read funny stories
[15:30] <seb128> like jcastro putting his phone next to the computer making noise on im messages to not miss those ;-)
[15:30] <pitti> gray vs. black isn't; especially now that the indicator is surrounded by other black icons
[15:31] <seb128> I keep missing messages again since they dropped the green icon
[15:31] <didrocks> I totally agree :)
[15:31] <LaserJock> seb128++ I keep missing messages
[15:31] <didrocks> LaserJock: it's the distributor_logo key which is the default. I will change that in the code.
[15:31] <didrocks> LaserJock: after beta 1 :)
[15:31] <sabdfl> hiya seb128 - excellent thanks, new home!
[15:32] <sabdfl> seb128: we may try a green indicator for "you've got mail"
[15:32] <pitti> sabdfl: a seminaked woman walking across the screen with a cardboard sign is out of the question then?
[15:32] <seb128> lol
[15:32] <kenvandine> hahahaha
[15:32] <didrocks> :)
[15:32] <rickspencer3> noooooo
[15:33] <rickspencer3> keep it classy indcators
[15:33] <sabdfl> pitti: can she be wearing *light*?
[15:33] <cjohnston> sabdfl: Is it going to stay the way it currently is on the left? If so I'll start closing bugs
[15:33] <seb128> sabdfl, we had a green icon for a few weeks, that seemed to work fine for most people there according to the feedback we got
[15:33] <cjohnston> Lol
[15:33] <sabdfl> cjohnston: it will stay that way through beta1 to gather feedback
[15:33] <sabdfl> clearly, there's a lot of feedback already being gathered :-)
[15:33] <pitti> bright green stood out much better, yes
[15:33] <didrocks> right, I agree with seb128, the green one we had for messaging menu was working great
[15:34] <cjohnston> Ok. So leave the bug reports open then?
[15:34] <sabdfl> it was also bulbous and 3d so had to die die die
[15:34] <rickspencer3> *sigh*
[15:34] <sabdfl> but a flat green one may be appropriate
[15:34] <sabdfl> i asked otto to play with some variations
[15:34] <kenvandine> sabdfl +1 from me on that
[15:34] <seb128> sabdfl, ok thanks, looking forward to see what he comes with ;-)
[15:35] <seb128> as long as it's noticable enough that I stop missing messages ;-)
[15:35] <pitti> like "pitti | seb128: plz fix this bug by tomorrow!"
[15:35] <kenvandine> i think with the light theme the current one is quite noticable, but i have a tough time with the dark theme
[15:35] <pitti> kenvandine: I am using the light theme, and it's not noticeable at all
[15:35] <seb128> kenvandine, I'm using the light theme and I don't notice it
[15:36] <pitti> kenvandine: I have two gray and 5 black icons, and with a message it doesn't look any different
[15:36] <kenvandine> pitti, ok, i actually switched to the light theme because i found it easier to notice the indicator
[15:36] <nigelb> sabdfl: so we can expect the left to stay? (just curious)
[15:37] <LaserJock> ... through Beta1 :-)
[15:37] <nigelb> I'm meh about where it, I use the keyboard anyway
[15:38] <seb128> we will try to change the capplet to change the side only for the new themes though
[15:39] <nigelb> yeah, I noticed that bug
[15:39] <pitti> seb128: would you mind eyeballing http://bazaar.launchpad.net/~ubuntu-core-dev/cdbs/ubuntu/revision/143 ?
[15:39] <pitti> seb128: do you see a potential problem with moving the X-U-Gettext-Domain line?
[15:40] <seb128> pitti, looking
[15:40] <pitti> oops, missing ^
[15:41] <LaserJock> didrocks: the gconf key is set to distributor-logo, is that not right anymore?
[15:41] <LaserJock> didrocks: it seems that the newer icon is start-here
[15:41] <pitti> seb128: missing ^ in regexp committed to r144
[15:41] <didrocks> LaserJock: distributor-logo is still the old one. I'll fix that to change the default key. Don't know if distributor-logo should be updated
[15:42] <seb128> pitti, ok
[15:43] <cjohnston> sabdfl: Im working right now. Would you mind a pm a little later on?
[15:45] <seb128> pitti, ok, done with my indicators changes, queue review appreciated if you want to do that
[15:46] <seb128> pitti, small fixes on indicator-{sound,me,application}
[15:46] <seb128> pitti, reviewing the cdbs change now
[16:04] <sabdfl> cjohnston: sure
[16:04] <sabdfl> nigelb: yes, that's the likely outcome
[16:05] <nigelb> sabdfl: I'd love it :)
[16:06] <nigelb> sabdfl: Mostly on principal, taking bold moves and sticking to them.
[16:08] <seb128> pitti, is the sed command there working for you?
[16:09] <seb128> bah typo
[16:10] <seb128> pitti, ok, that seems fine to me, I don't like much adding the domain there for readability reasons but I don't have a better suggestion either
[16:10] <pitti> seb128: yes, I tested it with simple-scan
[16:11] <pitti> seb128: isn't it for you?
[16:11] <pitti> seb128: we could make it more nice and add more parsing, but that would be more error prone, too
[16:11] <pitti> seb128: I'm fine to beat on it harder if you don't like it
[16:11] <seb128> pitti, it works, I was doing a typoe
[16:11] <seb128> typo
[16:12] <seb128> pitti, well using sed quickly limits what you can do easily
[16:13] <seb128> I would prefer having it insered before the second [ if there is one
[16:13] <pitti> I can use perl
[16:13] <pitti> sed was enough for the initial task
[16:16] <seb128> pitti, well, before the second ^[ or end of file would be nice
[16:17] <seb128> pitti, if you can make that easily
[16:21] <pitti> seb128: I'll look into that then
[16:23] <seb128> pitti, thanks
[16:23] <seb128> pitti, it seems that "after the first empty line" would work too
[16:23] <seb128> if that line is not the first one (some files seem to start with one)
[16:23] <pitti> seb128: for evolution yes, but we can't necessarily rely on having empty lines between
[16:23] <seb128> right
[16:32] <ccheney> rickspencer3: i got epiphany built and doing testing now, it is crashing due to some bugs and I am trying to debug it at present
[16:32] <rickspencer3> ccheney, thanks for the update
[16:32] <rickspencer3> glad it is building
[16:32] <rickspencer3> ccheney, did bratsche help you get it building?
[16:33] <ccheney> rickspencer3: it even loads a page up but when i click in the url bar it crashes
[16:33] <ccheney> rickspencer3: yea
[16:33] <rickspencer3> thanks bratsche
[16:33] <bratsche> np
[17:19]  * ccheney bbl, lunch and doctor :-\
[17:19]  * ccheney hates needles
[17:22] <chrisccoulson_> it's strange not getting very much bug mail today
[17:22] <chrisccoulson_> i assume that's because people aren't able to report issues ;)
[17:23] <LaserJock> chrisccoulson_: why is that?
[17:24] <chrisccoulson_> LaserJock, bug 538097
[17:25] <LaserJock> oh, I see
[17:25] <LaserJock> how many people use apport these days?
[17:25] <LaserJock> I remember mdz doing some stat quite a while ago and it was something like 13%
[17:26] <chrisccoulson_> i think quite a few people use apport
[17:26] <LaserJock> I'm assuming more people are doing it these days but I wonder if it's over 50%
[17:26] <seb128> launchpad does block filling bugs from the UI without knowing the url to use for that now no? or did they revert that change?
[17:26] <LaserJock> I thought it was reverted
[17:26] <milanbv> chrisccoulson_: have you seen my debdiff to bring back services-admin?
[17:26] <chrisccoulson_> seb128 - my understanding is that it was reverted for us
[17:27] <chrisccoulson_> but normal users are still re-directed
[17:27] <seb128> us = ubuntu members?
[17:27] <seb128> right
[17:27] <milanbv> I don't want to nag you too much about that - please tell me if I can help, or if we should forget about this goal ;-)
[17:27] <rickspencer3> seb128, http://theravingrick.blogspot.com/2010/03/beyond-release-blockers-also-bit-on.html
[17:27] <chrisccoulson_> milanbv, i haven't had any time to look yet, i've already got a lot of work to do
[17:27] <milanbv> sure
[17:27] <chrisccoulson_> and we're frozen for beta-1 anyway
[17:27] <seb128> rickspencer3, excellent!
[17:27] <milanbv> just - do you plan to get this for Lucid?
[17:28] <milanbv> do you prefer a debdiff to make services-admin a separate package?
[17:28] <rickspencer3> milanbv, I think we decided next week not to deliver the sevices admin by default in Lucid
[17:28] <rickspencer3> (assuming you are talking about the UI that controls running services like databases, etc...)
[17:28] <milanbv> rickspencer3: yes
[17:29] <milanbv> rickspencer3: not even as a separate package? I really think that would be worth it
[17:29] <chrisccoulson_> rickspencer3, was there any consensus on whether we should ship it in a separate package or not
[17:29] <chrisccoulson_> ?
[17:29] <LaserJock> chrisccoulson_: they are redirected to a wiki page that tells them to either use apport of +filebug right?
[17:29] <chrisccoulson_> LaserJock, yes, i think so
[17:31] <rickspencer3> chrisccoulson_, milanbv I think shipping it so that users can install it at their own risk is ok, assuming the quality of the package is sufficient
[17:31] <rickspencer3> but we agreed not to ship it by default
[17:31] <milanbv> shouldn't be too hard, given network-admin is already installed that way
[17:31] <chrisccoulson_> thats easy enough for me to do after beta-1 if everyone agrees with that
[17:32] <milanbv> cool
[17:32] <rickspencer3> chrisccoulson_, will need normal freeze exceptions and such
[17:32] <milanbv> if you need me to do this because you're in a hurry, please just tell me
[17:32] <chrisccoulson_> rickspencer3, no worries
[17:33] <chrisccoulson_> milanbv, i can look at that. i need to make sure we use the correct conflicts/replaces etc so that hardy -> lucid upgrades don't break
[17:33] <milanbv> oh yes
[17:34] <milanbv> so I can stop bringing this subject again and again!
[18:07] <pitti> seb128: ok, I figured it out
[18:08] <pitti> seb128: http://bazaar.launchpad.net/~ubuntu-core-dev/cdbs/ubuntu/revision/145 (in a few minutes)
[18:08] <pitti> seb128: it's now appending to the end of the [Desktop Entry] block, or failing that, at the end of the file
[18:08] <pitti> I tested it with evo's .desktop, with evo's desktop with newlines all stripped, and simple-scan
[18:08]  * pitti uploads
[18:09] <seb128> pitti, you rock
[18:10] <pitti> it's a pretty h4ck1sh seddery now, but *shrug*
[18:10] <seb128> if it works ;-)
[18:11] <pitti> above URL is updated now
[18:12] <seb128> pitti, look "good", ie unpleasant to read but seems to do what we need too ;-)
[18:13] <seb128> time for sport and dinner bbl
[18:13] <seb128> pitti, not sure if you read my ping about indicators before
[18:13] <seb128> if you can get those through that would be nice
[18:13] <pitti> seb128: ah, doing now
[18:13] <seb128> otherwise that can wait after beta but they are small changes and would be nice to have there
[18:14] <seb128> pitti, danke
[18:14] <kenvandine> seb128, question, i am going to prepare the new empathy for after beta
[18:14] <kenvandine> should we enable the favorites feature?
[18:14] <seb128> kenvandine, what does that do?
[18:14] <kenvandine> so you can mark contacts as "favorite"
[18:14] <kenvandine> now that empathy defaults to showing offline contacts
[18:15] <kenvandine> and facebook
[18:15] <kenvandine> i think it might be an important feature
[18:15] <kenvandine> my buddy list is huge now :)
[18:15] <kenvandine> seb128, but it is a new feature to enable at build time
[18:16]  * kenvandine hasn't tested it yet though... 
[18:16] <seb128> kenvandine, it does default to show offline contacts?
[18:16] <kenvandine> yes
[18:16] <seb128> since when?
[18:16] <seb128> it doesn't do it there
[18:16] <kenvandine> this release
[18:16] <kenvandine> .93
[18:16] <seb128> oh
[18:16] <seb128> we should probably roll that back
[18:16] <kenvandine> ok, i can revert that
[18:16] <seb128> that doesn't seem an appropriate change
[18:16] <seb128> or let it this way for now
[18:17] <kenvandine> well
[18:17] <kenvandine> it sorts by status though
[18:17] <seb128> and raise it as a meeting topic for tomorrow?
[18:17] <kenvandine> so offline people will be off the bottom
[18:17] <kenvandine> ok, i'll bring it up tomorrow
[18:17] <seb128> still, lot of visual clutter
[18:17] <seb128> why do you want to list a zillion of offline contacts
[18:17] <kenvandine> yeah, sounded like a strange change to me too
[18:18] <seb128> I will look for the rational before tomorrow
[18:18] <seb128> and ask cassidy
[18:18] <seb128> but I need to run for now
[18:18] <seb128> bbl
[18:18] <kenvandine> later
[18:18] <kenvandine> thx
[18:29] <sabdfl> kenvandine: hiya, has anybody reported a bug that gwibber is not sending avatars to notify-osd?
[18:29] <sabdfl> they come up with the gwibber icon, be nicer to have the avatar of the tweeter
[18:31] <thekorn> hey, desktop experts ;) when running lucid's update-manager on battery should there be a dialog like "you are running on battry, sure to continue?"
[18:31] <thekorn> I think there was one on karmic, but maybe I'm just wrong
[18:32] <pitti> Taekwondo time, cu tomororw!
[18:33] <james_w> thekorn: I've seen that before in lucid
[18:33] <james_w> confirmed that it has gone though
[18:38] <thekorn> james_w, ok, I think I'll just report a bug and see what happens
[18:38] <thekorn> ... if apport/launchpad would let me ;)
[18:41] <james_w> thekorn: the code is still there, so it looks like a bug
[18:42] <thekorn> james_w, yes, I'm wondering what "no_focus_on_map" does
[18:42] <james_w> thekorn: I think that's pop-up-in-the-background
[18:43] <james_w> thekorn: if you run from a terminal does it print an error?
[18:43] <james_w> it looks to me like it needs porting to upower
[18:44] <thekorn> james_w, no, no errors
[18:45] <james_w> oh, the error code is commented, how did I miss that? :-)
[18:45] <james_w> http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/lucid/update-manager/lucid/annotate/head:/UpdateManager/Core/utils.py#L210
[18:45] <james_w> but yes, file a bug, point to that and say that it needs to use the upower paths due to the rename.
[18:46] <thekorn> okidoki, will do, thanks
[18:54] <thekorn> james_w, fyi, bug 539211
[18:57] <james_w> thanks thekorn
[19:08] <thekorn> james_w, it looks like an easy fix, I can work on it right now. If noone else does, of course
[19:15] <kenvandine> sabdfl, not sure if there is a bug report on it, but it is a known problem
[19:16] <kenvandine> sabdfl, we are waiting for webkit-gtk to fix/implement some caching stuff
[19:16] <kenvandine> so we don't have to do the caching ourselves
[19:16] <kenvandine> currently we would need to fetch the avatar each time we send a notification
[19:37] <jjardon> Hello, I wonder if firefox-gnome-support package could be compiled with Gio support instead GnomeVFS
[19:37] <jjardon> I've already filled a bug here: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/539226
[19:37] <bratsche> Is there code for that already?
[19:40] <james_w> thekorn: I say go for it!
[19:40] <thekorn> james_w, already done, ready for review ;)
[19:40] <james_w> nice :-)
[19:41] <cjohnston_> sabdfl: I'm back if you are around.
[19:41] <chrisccoulson_> bratsche, jjardon - AFAICT nothing actually uses it yet
[19:42] <chrisccoulson_> so we can't do that yet
[19:42] <jjardon> bratsche, This is the upstream code: https://hg.mozilla.org/mozilla-central/file/69cb1df1cb0f/toolkit/system/gnome/nsGnomeModule.cpp
[19:44] <chrisccoulson_> jjardon, that's not even in 3.6
[19:45] <jjardon> chrisccoulson_, ah, ok. Anyway the request was for lucid+1
[19:46] <chrisccoulson_> yeah, when it arrives, i'm sure that we will enable it ;)
[19:48] <jjardon> great :)
[19:49] <jjardon> hope Ubuntu can kill gnome-vfs (and HAL) in the next cycle ;)
[19:52] <chrisccoulson_> jjardon, HAL is already gone by default
[19:52] <jjardon> chrisccoulson_, but gnome-vfs depends on HAL
[19:55] <jjardon> HAL was removed from Xorg
[19:57] <jjardon> but there still are some apps depending on HAL: https://wiki.ubuntu.com/Halsectomy
[19:58] <Sarvatt> RAOF: this looks like the same bug as you were working on - https://bugs.edge.launchpad.net/netbook-remix-launcher/+bug/293201
[20:00] <Sarvatt> these savages only have 16 bit visuals offered and it looks like clutter has major problems with that
[20:02] <Sarvatt> probably many dupes in gthumb bugs
[21:04] <rickspencer3> kenvandine, can you pm in so I can I test if the xchat plugin is causing a crash?
[21:05] <kenvandine> :)
[21:05] <kenvandine> rickspencer3, working?
[21:05] <rickspencer3> yeah
[21:05] <rickspencer3> one more time, maybe in channel instead of a PM?
[21:05] <kenvandine> rickspencer3, test
[21:06] <rickspencer3> pass
[21:06] <rickspencer3> kenvandine, well
[21:06] <rickspencer3> good :)
[21:06] <rickspencer3> thanks kenvandine
[21:06] <kenvandine> :)
[21:06] <kenvandine> np
[21:07] <rickspencer3> I am very much enjoying the "block" feature in identi.ca
[21:07] <rickspencer3> which I thought of this weeks ago
[21:09] <crimsun> a bit bedraggled from the ranting about window control changes? ;-)
[21:11] <bjf> crimsun, don't you feel that the number of "bugs" which are just muted sources are in fact ui-bugs?
[21:12] <crimsun> bjf: difficult to say. For Karmic, there's the alsa-utils bug (fixed in Lucid). For Lucid, there's the indicator-sound bug (which was just fixed). Unless I misunderstand "source" as you used it there -- do you mean pulse's source semantics?
[21:13] <bjf> crimsun, no I mean the number of people reporting microphone issues when it's just that the mic is muted
[21:13] <bjf> crimsun, or similar issues
[21:14] <crimsun> bjf: ah, so you do mean pulse's source. Ok, well, the mic is muted by default on login. That is arguably a pulse issue. OTOH, you have the hardware side: if you unmute mic by default, you could have some *nasty* feedback.
[21:15] <dobey> vuntz: around?
[21:15] <crimsun> bjf: so, I don't know of a really suitable approach there.
[21:15] <jcastro> kenvandine: I believe that test gwibber you had me test has totally removed my ability to run it
[21:15] <jcastro> kenvandine: is there something I can blow away to make it all better?
[21:15] <bjf> crimsun, ack
[21:15] <crimsun> jcastro: feature!
[21:15] <dobey> hmm, i should probably bug stef
[21:15] <kenvandine> jcastro, no... that isn't it
[21:15] <kenvandine> well
[21:16] <kenvandine> it is the stuff ryan added to turn off syncing of gwibber_messages to u1
[21:16]  * dobey wonders what stef's irc nick is
[21:16] <kenvandine> jcastro, your are paired with u1... with no pairing record
[21:16] <kenvandine> something like that
[21:16] <kenvandine> jcastro, asking in #ubuntuone how to fix that :)
[21:16] <kenvandine> s/asking/ask/
[21:16] <lifeless> dobey: smb perhaps
[21:17] <lifeless> dobey: depending on who you meant
[21:17] <dobey> lifeless: stef walter
[21:17] <jcastro> kenvandine: I don't mind blowing things away - my u1 breaks enough that there's no real data in there anyway. :p
[21:17] <kenvandine> jcastro, supposedly that is a situation that can't happen
[21:17] <kenvandine> hehe
[21:17] <kenvandine> check with them first
[21:17] <lifeless> ah know I don't know them
[21:18] <crimsun> bjf: also, bugs titled "[9.10 regression] HDA power_save=10" arguably can be closed; Lucid's alsa-driver source no longer ships the power-saving enabled by default. Also, the necessary changes to actually fix the driver bugs won't land until 2.6.34.
[21:18] <bjf> crimsun, ok, will do from now on
[21:18] <crimsun> bjf: cheers
[21:29] <RAOF> Gooood morning everyone!
[21:30] <TheMuso> Good morning
[21:30] <didrocks> good morning RAOF and TheMuso :)
[21:32] <RAOF> Sarvatt: That does indeed look like the very same bug, yes.  I've worked-around it in netbook-launcher so that it'll start (the 2D) netbook-launcher-efl, but we can't really do anything for clutter, can we?
[21:45] <Sarvatt> RAOF: besides upgrade to 1.2.x I doubt it, maybe extend the netbook-launcher gl check to look for required extensions instead of just using 3D when direct rendering isn't available and its not using swrast/osmesa
[21:47] <RAOF> Sarvatt: What I'm doing now is checking that Clutter successfully creates the stage, and if it fails fall back to 2D.  That seems a more foolproof check than wandering through GL extensions hoping to catch all the ones clutter will need.
[21:48] <RAOF> On the other hand, that'll fall back to 2D more slowly than the nice, early GL checks n-l does, so this'll negatively impact boot speed for users who have GL that doesn't support clutter.
[21:53] <Sarvatt> maybe a new gconf key thats written if it ever fails to create the stage that stops it from happening in the future so later boots aren't impacted?
[21:54] <RAOF> What happens when savage magically grows ARB_rectangle (or, more likely, the user replaces the video card)?
[21:54] <Sarvatt> or just changing the existing one, sorry working on 2 things at once and brain isn't all here :)
[21:55] <vuntz> dobey: pong
[21:55] <RAOF> That's ok :)
[21:56] <dobey> vuntz: are you maintaining keyring now, or you just made one release?
[21:56] <vuntz> dobey: I just rolled the tarball
[21:56] <vuntz> dobey: there's no way I maintain this :-)
[21:57] <dobey> vuntz: ok, thanks. do you remember what stef's nick is?
[21:58] <vuntz> dobey: he's usually not on irc, I think. Mail is the safe way to contact him
[21:58] <dobey> ok, thanks
[21:58] <seb128> he's not really around atm
[21:58] <seb128> busy with real life rather
[21:59] <dobey> hrmm
[21:59] <dobey> there seems to be a rather serious bug in gnome-keyring 2.29.x
[21:59] <dobey> with ACLs
[21:59] <seb128> there is several annoying issues
[21:59] <seb128> which one is that one?
[22:00] <dobey> well either ACLs don't work, or are just ignored, because the "ask me to access this secret in the keyring" dialog isn't popping up when it should, and seahorse isn't displaying the applications in the properties dialog for secrets
[22:01] <dobey> which means any application could just ask for your secrets and just get them without your knowledge, afaict :(
[22:01] <seb128> did you open a bug about that?
[22:03] <dobey> i was trying to find one, and see if it's a known issue or done on purpose, but i guess i'll just file it now
[22:56] <fuzzybear3965> does anyone know how to sync evolution with the default gnome-shell calendar?
[22:56] <fuzzybear3965> the clock used in shell isn't the default gnome-calendar applet used in Gnome <3.0
[22:58] <fuzzybear3965> anyone???
[22:58] <chrisccoulson> fuzzybear3965, this isn't the best place to ask
[23:03] <chrisccoulson> hey seb128
[23:03] <seb128> hey chrisccoulson
[23:03] <chrisccoulson> did you have a good day?
[23:04] <seb128> yes
[23:04] <seb128> lot of weekend catching up on monday as usual but good otherwise
[23:04] <seb128> you?
[23:05] <chrisccoulson> yeah, quite a busy day today
[23:06] <fuzzybear3965> where should i go, chris?
[23:06] <fuzzybear3965> #ubuntu?
[23:06] <rickspencer3> fuzzybear3965, sounds about right, but that sounds like a good topic for the forums as well
[23:07] <chrisccoulson> seb128 - if you have a few minutes, would you be able to approve micahg's merge request? (https://code.edge.launchpad.net/~micahg/ubufox/ubufox-0.9b1-ubuntu2/+merge/21409)
[23:07] <chrisccoulson> i can upload his change, but i can't push to the bzr branch ;)
[23:08] <fuzzybear3965> Thanks rick
[23:08] <fuzzybear3965> later you guys
[23:08] <seb128> chrisccoulson, sure, looking
[23:08] <chrisccoulson> thanks :)
[23:08] <seb128> np
[23:09] <seb128> chrisccoulson, how does that work? I just need to flag it approved on the webpage?
[23:09]  * seb128 never uses the web ui for those
[23:10] <chrisccoulson> seb128 - i don't normall use the web UI either. i just normally grab both branches, merge and then push the change back again
[23:10] <chrisccoulson> i'm not sure how everyone else deals with those
[23:11] <RAOF> Flagging it as “approved” on the webpage doesn't actually merge it in, so you want to grab both branches, merge & push back the changes *anyway*.
[23:11] <seb128> chrisccoulson, I'm confused now, you want me to review the change or just to make sure it lands to the ubuntu bzr?
[23:12] <chrisccoulson> seb128 - just make sure it lands in bzr ;)
[23:12] <chrisccoulson> i can upload it, but i just can't push to the branch
[23:14] <seb128> chrisccoulson, ok
[23:16] <seb128> chrisccoulson, done
[23:16] <chrisccoulson> seb128 - excellent, thanks :)
[23:16] <seb128> np
[23:46] <seb128> chrisccoulson, how is your workload for lucid looking?
[23:47] <chrisccoulson> seb128 - it's pretty busy this week
[23:47] <chrisccoulson> did you have something in mind?
[23:47] <seb128> chrisccoulson, wondering if I should assign bug #445951 to you or the team rather
[23:47] <seb128> chrisccoulson, it collects duplicates
[23:47] <seb128> chrisccoulson, it's not a bug for this week just building that lucid bugslist
[23:47] <chrisccoulson> i don't mind really. i can take a look at that when i get the chance
[23:48] <seb128> chrisccoulson, ok, assigning to you then if you feel you have to many things to look at before lucid please bounce back to the team rather
[23:48] <chrisccoulson> thanks
[23:49] <seb128> in fact I'm wondering if that's not only a karmic issue looking through duplicates
[23:49] <seb128> I will ask if somebody gets it on lucid
[23:59] <seb128> chrisccoulson, ok forget that, it's bug #462944 and has been fixed in lucid