[00:35] <chrisccoulson> pitti - i've implemented the AutostartDelay support in gnome-session already :)
[00:35] <chrisccoulson> i couldn't resist
[01:12] <chrisccoulson> vuntz, that was a quick response ;)
[01:13] <chrisccoulson> i didn't expect anybody to be around
[01:53] <LLStarks> i'd like to report a playback regression associated with today's gstreamer updates.
[01:53] <LLStarks> https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base0.10/+bug/502492
[01:53] <LLStarks> this is something that i've been observing through git over the past few weeks.
[01:54] <LLStarks> previously, matroska files would open fine save for improperly formatted subtitles.
[06:07] <pitti> Good morning
[07:55] <didrocks> good morning pitti
[07:56] <didrocks> how are you?
[07:58] <pitti> hey didrocks; I'm great, thanks!
[07:58] <pitti> got up at 7
[07:58] <pitti> and hammered on my mailbox to have a clean slate
[07:58] <pitti> =ubuntu [Msgs:0]
[07:59] <pitti> muhaha
[08:02] <didrocks> \o/
[08:02] <didrocks> pitti: battery icon not showing up when on battery and forcing icon show an obviously wrong value of 100% load. Known issue?
[08:03] <pitti> hm, not to me
[08:03] <didrocks> oh, this morning reboot fixed it
[08:03] <didrocks> but I had to unplug/plug again
[08:04] <didrocks> well, let's see if I can reproduce it later
[08:17] <baptistemm> hello
[08:17] <baptistemm> good morning
[08:18]  * baptistemm did an install with alpha 2 cd yesterday on its new ssd
[08:18] <didrocks> hey baptistemm
[08:18] <baptistemm> hey didrocks
[08:18] <baptistemm> the install process is really beautiful
[08:18] <didrocks> baptistemm: you didn't install karmic?
[08:18] <baptistemm> no
[08:18] <didrocks> (I didn't notice difference between karmic and alpha2 one)
[08:18] <didrocks> oh ok :)
[08:18] <didrocks> right, slideshow is really great
[08:19] <baptistemm> didrocks, I didn't have installed ubuntu since 2 years
[08:19] <baptistemm> I do only distupgrade
[08:19] <baptistemm> (I only have one computer)
[08:19] <didrocks> come in our French ubuntu party to give an hand, you'll install lot of time :)
[08:19] <baptistemm> so now I have grub2 & ext4 :)
[08:20] <baptistemm> ssd is fantastic, booting in a few seconds is awesome :)
[08:20] <didrocks> heh, new world of technology :)
[08:20] <didrocks> hum, I don't have the chance to use ssd yet
[08:20] <baptistemm> yeah, HD was the bottleneck before, no more with SSD
[08:25] <pitti> didrocks: don't you have an SSD mini 10?
[08:25] <didrocks> pitti: no, you took it. Mine is HD
[08:25] <didrocks> :)
[08:25]  * pitti feels guilty
[08:26] <didrocks> pitti: you'll find a better way to optimize it than me
[08:26] <didrocks> so, don't feel guilty ;)
[08:42] <chrisccoulson> good morning everyone
[08:42] <didrocks> hey chrisccoulson
[08:42] <chrisccoulson> hey didrocks, how are you?
[08:43] <didrocks> chrisccoulson: good, preparing the sprint and enjoying Friday of mostly paperwork :)
[08:43] <didrocks> you?
[08:43] <chrisccoulson> yeah, i'm good thanks. i'm preparing for the weekend instead though ;)
[08:44] <pitti> hey chrisccoulson
[08:44] <chrisccoulson> hey pitti
[08:44] <pitti> chrisccoulson: you rock
[08:44] <chrisccoulson> did you get my message last night?
[08:44] <pitti> chrisccoulson: I did; just didn't see a patch (it's not in bzr yet apparently)
[08:45] <pitti> http://people.canonical.com/~pitti/bootcharts/daniel-lucid-20100129-1.png
[08:45] <pitti> daily chart
[08:45] <chrisccoulson> pitti - the patch is on gnome bug 608402, although it has a couple of comments from vuntz
[08:45] <chrisccoulson> excellent - that looks good
[08:46] <chrisccoulson> i might try and investigate that unexplained delay at the start of the session later
[08:48] <pitti> chrisccoulson: ah, so you actually start them from a timer, instead of adding a sleep between the fork() and the exec()
[08:48] <pitti> that looks pretty nice
[08:48] <chrisccoulson> pitti - yeah, i wanted to try and avoid creating a whole new process until necessary
[08:54] <didrocks> chrisccoulson: how does this work with applications waiting for all soft in Applications phased to finish? (like the mouse cursor, xsplash…)
[08:54] <chrisccoulson> didrocks - it has no effect. gnome-session will emit the session running signal as soon as all non-delayed applications have started
[08:55] <didrocks> oh perfect :)
[08:55] <chrisccoulson> it works the same way as the conditionally autostarted applications
[08:55] <didrocks> right, gnome-session doesn't wait any signal from delayed started application
[08:56] <didrocks> good ;)
[08:57] <chrisccoulson> didrocks - are you using the session running signal then?
[08:57] <didrocks> chrisccoulson: no, it was just coming into my head in case of xsplash comes back
[08:58] <chrisccoulson> didrocks - yeah, this has been discussed before. the session running signal isn't an accurate indicator of when the session is ready, as it will be emitted once all applications in the last phase have connected to the session manager
[08:59] <chrisccoulson> and for most applications, that happens fairly quickly
[08:59] <chrisccoulson> before anything is drawn
[09:00] <chrisccoulson> didrocks - http://mail.gnome.org/archives/desktop-devel-list/2009-August/msg00079.html
[09:00] <seb128> hey chrisccoulson
[09:00] <seb128> what are you discussing?
[09:00] <chrisccoulson> my mail only got a single comment, but it was a positive one
[09:01] <didrocks> chrisccoulson: thanks
[09:01] <chrisccoulson> hey seb128 - we were just discussing the usefulness of the session running signal
[09:01] <didrocks> hey seb128
[09:02] <seb128> hey didrocks
[09:02] <seb128> chrisccoulson, usefulness or the fact that it's wrongly emited?
[09:02] <seb128> ie that it should be sent after being done with the screen rendering?
[09:03] <pitti> hey seb128
[09:03] <chrisccoulson> seb128 - i was just pointing out that it is emitted once all clients have registered, which isn't necessarily when things have drawn on screen
[09:03] <seb128> pitti, hey
[09:03] <seb128> how are you?
[09:17] <seb128> wb pitti
[09:18] <seb128> pitti, did you read my comment about making the fn key work without modifier yesterday?
[09:22] <baptistemm> Would you be instered by bootchart with a ssd on a lucid install ?
[09:22] <baptistemm> in order to have a view on another ssd.
[09:23] <seb128> sure
[09:24] <pitti> seb128: sorry, had some IRC trouble
[09:24] <pitti> seb128: don't think so, no?
[09:24] <seb128> pitti, not sure if you are annoyed by the fn keys being multimedia by default too
[09:24] <pitti> seb128: I changed that in the bios
[09:24] <seb128> pitti, rickspencer pointed you can change that in the bios
[09:24] <seb128> ok
[09:25] <seb128> I didn't look into bios options before rick pointed it
[09:25] <seb128> there is nothing useful usually in bioses nowadays
[09:25] <seb128> out of setting boot order
[09:28] <didrocks> seb128, pitti: I've tried to think a little about some caching policy we can use for wallpapers (2 proposals), if you can think about more, don't hesitate: https://bugzilla.gnome.org/show_bug.cgi?id=608419
[09:31] <pitti> didrocks: I'll answer in the bug report
[09:32] <didrocks> pitti: thanks :)
[09:33] <seb128> didrocks, g-s-d has cleaning code you could use btw
[09:33] <seb128> it clean thumbnails etc
[09:35] <huats> morning
[09:35] <didrocks> seb128: I think the code can be easy to do, but it can be interested to see how they do it in g-s-d. I just wait for upstream to define the strategy together first.
[09:35] <didrocks> seb128: thanks :)
[09:35] <didrocks> hey huats
[09:36] <pitti> didrocks: done
[09:37] <seb128> hum
[09:38] <seb128> chrisccoulson, I think you broke g-s-d media key
[09:38] <seb128> chrisccoulson, it has symbol not found errors on libnotify symbols
[09:38] <seb128> I guess the makefile change didn't work for a reason
[09:39] <seb128> or I messed up the upgrade
[09:39] <chrisccoulson> seb128 - oh, that worked when i tested it
[09:39] <seb128> I will check that
[09:40] <didrocks> pitti: I'm trying to think about the policy to keep only one wallpaper cache. Not that easy in fact (as we have to store the wallpaper name, the resolution and the transformation used)
[09:41] <pitti> didrocks: if it's in a directory anyway, just remove the one file?
[09:41] <asac> what does packagekit use xulrunner for?
[09:41] <pitti> didrocks: or use a symlink or separate .info file?
[09:42] <didrocks> pitti: if we just copy one, we can remove the directory I guess
[09:42] <didrocks> pitti: I was thinking about a separate .info file, but a symlink is good as well :)
[09:43] <pitti> .info is more portable though
[09:43] <pitti> (not sure how much this stuff needs to work on windows, etc.)
[09:44] <glatzor> hello asac, there's a firefox plugin
[09:44] <didrocks> pitti: right, let's see what upstreams say first
[09:45] <pitti> have an appointment now, bbl
[09:45] <glatzor> asac,     <object type="application/x-packagekit-plugin" width="300" height="150">
[09:45] <glatzor>       <!-- Name that will be used in the user interface -->
[09:45] <glatzor>       <param name="displayname" value="GNU Backgammon"/>
[09:45] <glatzor>       <!-- Whitespace separated list of package names -->
[09:45] <glatzor>       <param name="packagenames" value="gnubg"/>
[09:45] <glatzor>     </object>
[09:45] <glatzor> asac, this allows you to install an application from your browser
[09:45] <asac> glatzor: can we kill that?
[09:46] <asac> ok
[09:46] <asac> nevermind
[09:46] <asac> have to check the code how trivial that is
[09:46] <glatzor> asac, AFAIK there isn't any real use case
[09:47] <asac> yeah
[09:47] <asac> we will see if it "just works (TM)" to port to 1.9.2
[09:48] <baptistemm> against which component I should fill a bug for a problem with the lucid installer
[09:48] <baptistemm> is it casper?
[09:53] <didrocks> baptistemm: ubiquity?
[09:53]  * didrocks grrr at rhythmbox being a pain using upnp
[09:53] <chrisccoulson> seb128 - did you figure out what is wrong with gsd?
[09:53] <seb128> chrisccoulson, not yet, I was looking at something else
[09:53] <seb128> dholbach pointed it to me
[09:54] <seb128> and I noticed I've the issue too
[09:54] <seb128> ** (gnome-settings-daemon:1956): WARNING **: /usr/lib/gnome-settings-daemon-2.0/libkeybindings.so: undefined symbol: notify_notification_show
[09:54] <seb128> I don't use those keys often so I didn't notice
[09:54] <seb128> ** (gnome-settings-daemon:1956): WARNING **: /usr/lib/gnome-settings-daemon-2.0/libmedia-keys.so: undefined symbol: notify_notification_show
[09:54] <seb128> too
[09:55] <seb128> I'm wondering if that's an --as-needed issue
[10:09] <seb128> chrisccoulson, ok, found it
[10:09] <chrisccoulson> ah, what was it in the end?
[10:09] <seb128> chrisccoulson, it's a but in your change
[10:09] <seb128> chrisccoulson, you add LIBNOTIFY_LDFLAGS use
[10:09] <seb128> and configure.ac uses _LIB
[10:09] <seb128> and not _LDFLAGS
[10:10] <chrisccoulson> oops
[10:10] <chrisccoulson> thanks ;)
[10:10] <seb128> np ;-)
[10:17] <seb128> login speed is depressing some days
[10:17] <seb128> still around 9 seconds login there
[10:18] <seb128> with yesterday's gconf changes, etc
[10:36] <seb128> tseliot, hey, could you look to bug #509724?
[10:36]  * tseliot has a look
[10:39] <tseliot> seb128: if I disable corner tapping, people are going to be pretty angry (and they already are)
[10:39] <seb128> what does corner tapping do?
[10:40] <tseliot> seb128: there was a patch for the UI to allow users to change the settings of corner tapping
[10:40] <tseliot> when you tap on the top right or bottom right corner you get a right click
[10:40] <tseliot> (just an example)
[10:41] <seb128> doesn't seem to work on my mini
[10:42] <seb128> in any case the user doesn't suggest to disable that
[10:42] <seb128> just to disable it when tap to click is disabled
[10:43] <tseliot> oh, I see
[10:44] <seb128> I'm about to do a g-s-d upload
[10:44] <seb128> what do you think about the change? should we use it?
[10:46] <tseliot> seb128: I'm reading the patch
[10:48] <tseliot> seb128: data[1] = (state) ? 3 : 0; should be enough
[10:48] <tseliot> as we don't enable middle clicks any more
[10:49] <tseliot> which means that you can discard data[0] = (state) ? 2 : 0;
[10:49] <seb128> ok
[10:49] <seb128> you agree with doing the data[1] = (state) ? 3 : 0 change then?
[10:49] <tseliot> yes, it makes sense to me
[10:50] <seb128> tseliot, thanks
[10:50] <tseliot> np
[11:49] <chrisccoulson> vuntz - you there?
[11:52] <vuntz> chrisccoulson: hmm?
[11:53] <chrisccoulson> vuntz - thanks for reviewing my patch
[11:55] <chrisccoulson> vuntz - i was just having a look at the comments. the reason i check gsm_app_is_running before calling gsm_app_stop in gsm-manager, is because gsm_app_stop sets a GError if the application isn't running, which is then printed as a warning in gsm-manager. i wanted to avoid the warning in the case where the autostart condition goes from enabled -> disabled before the autostart delay has timed out, and the application hasn't been 
[11:56] <vuntz> chrisccoulson: ok
[11:57] <vuntz> chrisccoulson: on the other hand, if you use the _start_app code as I suggested, you wouldn't connect to the signal condition-changed early, so it'd be a non-existing case
[11:59] <chrisccoulson> vuntz - ok, i'll have another look at that
[12:25] <pitti> re
[12:28] <chrisccoulson> hey pitti
[12:29] <asac> pitti: do you know what the equivalent of postpone for bugs is wrt to blueprints and WI?
[12:29] <asac> just unlinking the bugs? or set wont fix for lucid?
[12:29] <asac> (can we keep the non-lucid target open)?
[12:29] <pitti> asac: drop entirely? yes, unlink it
[12:29] <asac> ok
[12:30] <pitti> lucid/wontfix could also work, I'm not sure
[12:30] <asac> hmm. let me try that first
[12:30] <asac> would better reflect that thats a postpone
[12:30] <pitti> asac: right, reading the code now
[12:30] <pitti> wontfix == postponed
[12:30] <asac> pitti: and does it work to only set lucid to postponed?
[12:32] <asac> ok trying that ... setting wontfix to lucid and milestoning the main task as "later"
[12:34] <pitti> asac: right, that should work
[12:35] <asac> cool
[12:35] <asac> did that ... we will see on next run i guess
[13:01] <pitti> Riddell: can you please update the Kubuntu bits on https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus ?
[13:11] <seb128> pitti, hey
[13:11] <seb128> pitti, bug #514281 might be due to your changes
[13:12] <seb128> pitti, seems the gconf keys for those have no value
[13:12] <seb128> pitti, I'm wondering if that's due to the gconf change you did
[13:12] <pitti> seb128: my first suspicion is ...
[13:12] <pitti> mvo: wrt above bug, can you check your .xsession-errors for
[13:12] <pitti> ** (gnome-settings-daemon:2113): WARNING **: /usr/lib/gnome-settings-daemon-2.0/libmedia-keys.so: undefined symbol: notify_notification_show
[13:12] <seb128> ogra and mvo did start to getit today
[13:12] <seb128> pitti, no, I made mvo installed my fixed g-s-d
[13:12] <pitti> this broke _everyone_'s hotkeys and keyboard settings
[13:13] <seb128> install
[13:13] <pitti> seb128: ok, will ask in the bug then
[13:13] <seb128> and that would not explain empty values
[13:13] <pitti> seb128: ah, there's a fixed g-s-d?
[13:13] <seb128> pitti, yes I uploaded before lunch
[13:13] <pitti> merci
[13:13] <seb128> de rien
[13:14] <mvo> pitti: I just installed the fixed g-s-d, it did not help
[13:14] <mvo>  /desktop/gnome/peripherals/keyboard/rate is also set to "no value" for me
[13:14] <seb128> it's weird that gconf-editor has "no value"
[13:14] <mvo> and on my karmic system it has meaningful values
[13:14] <seb128> whatever g-s-d does they should get a value
[13:14] <seb128> the value could be "0"
[13:15] <seb128> but I don't see how the symbol issue could lead to have vanishing key
[13:15] <mvo> no idea, but got broken during the upgrade
[13:15] <seb128> well as said I think it's due to pitti's gconf stripping
[13:15] <mvo> but when I "unset" the key it vanishes
[13:15] <pitti> mvo: I'll collect some ideas and ask in the bug
[13:15] <seb128> pitti, the g-s-d bug is there for a week and people started reporting the keyboard issue otday
[13:15] <pitti> ok, then I blame me
[13:19] <seb128> pitti, the schemas is in libgnome
[13:19] <seb128> desktop_gnome_peripherals_keyboard.schemas
[13:22] <pitti> ok, bug retitled, assigned to me and moved to gconf
[13:22] <seb128> pitti, mvo: iz gconf bug
[13:22] <seb128> pitti, I did dpkg -i *.deb on my previous gconf local build
[13:22] <pitti> so if you see similar things, please dupe to that one
[13:22] <seb128> and I get defaults values again
[13:22] <pitti> seb128: yes, clearly
[13:22] <pitti> I get it here, too
[13:23] <seb128> pitti, ok will do
[13:23] <pitti> sorry about that
[13:23]  * seb128 hugs pitti
[13:23] <seb128> that's ok
[13:23] <seb128> that's one of the reason I'm reluctant to do such changes to gconf
[13:23] <seb128> it's early in the cycle so we can break things still
[13:23] <mvo> pitti: ohhh, you removed my summary? I liked it :)
[13:23] <seb128> lol
[13:23] <pitti> mvo: for me it's the other way around; I lost key repeat completely
[13:27]  * vish hehe , imagined mvo shivering ;p [bug summary]
[13:31] <chrisccoulson> pitti - did you break gconf? ;)
[13:31] <pitti> apparently
[13:32] <seb128> it's weird, after downgrading and upgrading again it's working
[13:33] <pitti> perhaps it didn't like dropping the mtime
[13:33] <pitti> working fine now
[13:35] <seb128> pitti, btw it seems your une lacks a clock applet in the config
[13:35] <pitti> it's not just "my" UNE
[13:35] <seb128> well your charts
[13:35] <seb128> if you start the gnome session once it will be there
[13:35] <pitti> weird
[13:36] <seb128> gnome-panel fails to register it under une
[13:36] <pitti> shouldn't that be in the default settings somewhere?
[13:36] <seb128> I think that's due to the mandatory config
[13:36] <seb128> on first run default config is register as user config
[13:36] <seb128> I think the mandatory values from une break that for the clock in some way
[13:36] <seb128> I mentioned it to didrocks before
[13:37] <seb128> I was trying to figure why your charts are slighter faster than mines
[13:37] <seb128> that's one of the differences
[13:38] <pitti> how much difference does it make? clock loads evo and all that, so I guess it's quite heavy?
[13:38] <didrocks> strange that I still have it, I have to retry from a vanilla karmic UNR
[13:38] <pitti> seb128: I also have compiz and tomboy purged, but I think that's about it
[13:38] <seb128> didrocks, I get the issue every time I remove .gconf to reset my settings
[13:39] <seb128> pitti, 0.5 seconds
[13:39] <seb128> pitti, well atm 1 seconds but that's because you don't get nm-applet cpu use for some reason
[13:39] <seb128> which I do there
[13:40] <didrocks> seb128: oh right, before logging into the desktop session which recreate it
[13:40] <didrocks> and then, you got it into your UNE session, right?
[13:40] <seb128> didrocks, right
[13:41] <seb128> didrocks, but pitti never logged in the gnome session and is doing charts without it
[13:41] <seb128> not a real issue I was just pointing it
[13:41] <seb128> it makes boot slightly quicker
[13:44]  * pitti goes to pack stuff for the sprint
[14:48] <seb128> chrisccoulson, wb
[14:48] <seb128> chrisccoulson, so it's weekend time for you? ;-)
[14:48] <chrisccoulson> hey seb128
[14:48] <chrisccoulson> yeah, weekend time now :)
[14:49] <seb128> cool
[14:49] <chrisccoulson> although, i plan to do a bit of ubuntu stuff this afternoon
[14:49] <seb128> is your little girl feeling better btw? you said she was sick the other night?
[14:49] <chrisccoulson> yeah, she's a bit better now thanks
[14:50] <seb128> good ;-)
[14:52] <chrisccoulson> seb128 - do you have any plans for the weekend?
[14:52] <chrisccoulson> you'll be travelling won't you?
[14:54] <seb128> yeah, plan is to not sleep this night
[14:54] <seb128> ie I get up at 5am tomorrow to catch the plane and I don't manage to sleep before 1am usually...
[14:54] <seb128> so short night
[14:54] <seb128> and I'm travelling tomorrow for the day so
[14:55] <seb128> and we will see on sunday what happens in the other side of the world...
[14:55] <didrocks> seb128: when do you arrive at Portland?
[14:55] <seb128> :-)
[14:55] <seb128> didrocks, 12:20
[14:55] <seb128> saturday local time
[14:55] <seb128> you?
[14:55] <chrisccoulson> sounds like a busy weekend ;)
[14:55] <didrocks> 4pm, saturday too
[14:56] <seb128> chrisccoulson, yeah, but not busy in the best way you can imagine for a weekend :-)
[14:56] <seb128> chrisccoulson, do you have any plan for this weekend?
[14:57] <chrisccoulson> seb128 - i shall be relaxing this weekend, after spending most of last saturday driving around
[14:57] <seb128> relaxing sounds good ;-)
[14:58] <chrisccoulson> heh, one of my cats has climbed right to the top of the tree in the garden
[14:59] <seb128> climbing is the easy part for them usually
[14:59] <seb128> let's see how the going down is going ;-)
[14:59] <chrisccoulson> yeah, normally they fall back down again ;)
[14:59] <chrisccoulson> they tend to slip and then swing from the branches with their front paws
[15:00] <chrisccoulson> then fall down ;)
[15:00] <chrisccoulson> i should get the camcorder out
[15:09] <seb128> chrisccoulson, btw you can do gnome-screensaver update if you want, you don't need to though
[15:09] <seb128> ie just pointing I'm not going to do it this week
[15:10] <chrisccoulson> seb128 - yeah, i can look at that over the weekend
[15:10] <seb128> so if you want to do it feel free to grab it ;-)
[15:10] <seb128> ok
[15:10] <chrisccoulson> i can actually upload gnome-screensaver :)
[15:10] <seb128> hehe
[15:10] <seb128> one thing which is working ;-)
[15:17] <seb128> ok, I'm out for some erands before travelling tomorrow and packaging too...
[15:17] <seb128> I will be back later though
[15:17] <pitti> seb128: safe travels!
[15:17] <pitti> see you tomorrow then
[15:17] <seb128> see you later, or this weekend for those who stop early
[15:17] <seb128> pitti, I arrive tomorrow around midday there
[15:17] <seb128> so I guess we will meet in the afternoon
[15:18] <seb128> safe travels too
[15:18] <pitti> right
[15:18] <pitti> plane lands at 14:33
[15:18] <chrisccoulson> hmmm, note to self - don't try to sign e-mails with large attachments in evolution
[15:18] <seb128> bbl
[15:23] <chrisccoulson> vuntz - i'm going to work on fixing that gnome-session patch this afternoon
[15:24] <chrisccoulson> what do you want me to do about the libegg part of it? i've committed the change to libegg now - do you just want to sync gnome-session's local copy of this
[15:28] <vuntz> chrisccoulson: yep, sinc
[15:28] <vuntz> err, sync
[15:36] <chrisccoulson> vuntz - do you want me to do the sync now (as a separate commit), or do you want to do the sync?
[15:37] <chrisccoulson> also, i assume we just sync the whole of the libegg/smclient folder in to gnome-session?
[15:37] <chrisccoulson> (there's new files in there now)
[15:39] <vuntz> chrisccoulson: we'll do the sync when needed (ie, when pushing your patch, I guess)
[15:39] <vuntz> chrisccoulson: and no, we don't care about some files, so it's just what we have already
[15:40] <chrisccoulson> vuntz - ok, thanks
[15:40] <chrisccoulson> i'll work on fixing the patch now:)
[15:45] <mvo> pitti: ah, keyboard is fine again, thanks for the fix
[15:45] <pitti> \o/
[15:45]  * mvo goes back to packging 
[16:52] <didrocks> grrr, tomboy don't want to synchronize my notes
[17:01] <didrocks> upstream rejected my patch for not showing the ws switcher if only one ws is visible (they just don't want that feature): https://bugzilla.gnome.org/show_bug.cgi?id=606966
[17:03] <pitti> hm, I don't quite follow the rationale
[17:03]  * pitti follows up
[17:05] <didrocks> really, if you test with one ws, the ws switcher showing is really bad
[17:05] <pitti> it should not even bind the key if you only have one WS
[17:06] <didrocks> right
[17:22] <al-maisan> Hello there! I am running lucid alpha2 now and it's very nice :)
[17:22] <al-maisan> One problem: I cannot get it to give me more than 2 virtual desktops
[17:22] <al-maisan> under gnome
[17:23] <al-maisan> Is that a known issue?
[17:23] <pitti> hm, I'm happily using 4 here
[17:23] <al-maisan> sorry, "workspaces" is the word I've been looking for
[17:24] <al-maisan> pitti: just tried it and it worked for me as well, thanks!
[17:24] <pitti> al-maisan: I thought it wouldn't work for you?
[17:24] <al-maisan> pitti: it did not
[17:25] <al-maisan> when I tried to change 2->4 in the workspace switcher preferences it crashed
[17:25] <al-maisan> but I gave it another whirl after your comment and it just worked
[17:25]  * al-maisan shrugs
[17:28] <al-maisan> pitti: the last remaining gotcha: I defined a keyboard shortcut for "Toggle whether window is on all workspaces or just one" (Ctrl+Alt+A) but when I use it, it has no effect
[17:29] <pitti> asac: did that just started to happen today?
[17:29] <pitti> erm, al-maisan:
[17:29] <al-maisan> it may be conflicting with compiz somehow..?
[17:29] <pitti> al-maisan: if you dist-upgraded today, please do it again; yesterday I uploaded a bad gconf, fixed today
[17:29] <al-maisan> pitti: I only installed lucid today :P
[17:29] <pitti> al-maisan: do you have gconf2 2.28.0-1ubuntu3 ?
[17:30]  * al-maisan checks
[17:30] <al-maisan> pitti: yes, 2.28.0-1ubuntu3
[17:30] <pitti> al-maisan: right, that's busted; please upgrade to 4, restart session, and you should be happy again
[17:31] <al-maisan> pitti: great :) thanks!
[17:35]  * al-maisan does the logout/login dance
[17:37] <didrocks> pitti: it seems you nore more provide ubuntu desktop team WI report (I can't see mine which are related to Quickly)
[17:37] <didrocks> something like "ubuntu-desktop" WI
[17:38] <pitti> didrocks: how do you mean?
[17:38] <pitti> didrocks: http://people.canonical.com/~pitti/workitems/canonical-desktop-team.html#didrocks
[17:38] <pitti> all there
[17:39] <didrocks> pitti: oh, I was thinking they were separed into another one, as it's not directly related to my canonical job, but well :)
[17:39] <didrocks> thanks pitti, I can try gtg WI importer
[17:39] <pitti> didrocks: it's a spec targetted to lucid
[17:39] <didrocks> ok, fine
[17:40] <pitti> didrocks: you can also use all.html to get the entire ubuntu WI list
[17:40] <pitti> (not just the ones relevant to desktop)
[17:40] <didrocks> right, and import from there. Thanks!
[18:05] <pitti> bye everyone!
[18:30] <crimsun> from pm-utils, is it possible to know the UID of the user who initiated a suspend-to-* ?
[19:09] <dobey> hrmm, how do i fix debian/rules to run 'make check' with cdbs?
[19:23] <asac> anyone mono expert here?
[20:07] <vish> awe_: hi... hmm i didnt understand your comment :(  ... are you saying that the menu can be re-designed after user testing?  [anyways , i was just responding to danw upstream comments :)  ]
[20:07] <vish>  danw's upstream comment*
[20:08] <awe_> vish, well, I don't understand your comment...
[20:08] <awe_> seems like all the pertinent info is already in the bug
[20:08] <awe_> people are complaining that the adhoc icon is meaningless and needs to be removed
[20:08] <awe_> asac states that's a potential security violation
[20:09] <vish> awe_: i know the info..[i was part of the discussion] I felt Dan wanted someone from the design team to comment upstream as well
[20:09] <asac> awe_: check with dcbw on the sense and non-sense of that.
[20:09] <asac> i think the idea is to show that that AP usually doesnt give you internet access
[20:09] <awe_> yes
[20:09] <awe_> although it could
[20:09] <asac> it could
[20:09] <asac> but most times you see that its not
[20:09] <asac> i regularly see printers etc.
[20:09] <awe_> agreed
[20:10] <awe_> so the bug is left open until someone does user testing.... which hasn't happened yet
[20:10] <awe_> so vish, nobody's commented because the user testing hasn't happened or been scheduled
[20:10] <vish> i guess ...
[20:11] <vish> awe_: anyway , it was part of the nm hugdat list , since i knew the bug  , i sent it upstream :)
[20:11] <vish> hugday*
[20:13] <awe_> vish, ok thanks...
[20:14] <vish> awe_: so, you are taking care of nm this cycle ?
[20:14]  * vish me used to ask asac nm related doubts last cycle ;)
[20:15] <asac> there isnt much planned for this cycle wrt nm
[20:15] <asac> basically a stable 0.8 ...
[20:15] <asac> and more stabilization
[20:16] <vish> neat..
[20:16] <asac> someone might want to work on the Auth eth0 labelling bug ;)
[20:16] <awe_> vish, in my spare cycles
[20:17] <vish> asac: you've been pawning that one off for a long time  ;p
[20:17] <vish> asac: but seems dan wants to address the notifications and the naming in the connection editor simultaneously
[21:15] <baptistemm> hya
[21:16] <baptistemm> for those interested with boot time on ssd with lucid: http://bmm80.free.fr/GNOME/shots/oak-lucid-20100129-1.png
[21:26]  * dobey wants to get rid of boot time
[21:26]  * bryceh leaves dobey's computer on all the time and solves his problem
[21:27] <dobey> bryceh: i pretty much do leave my computer on all the time, unless i *have* to reboot it
[21:27] <dobey> like, i install enough updates that pulseaudio finally breaks
[21:27] <dobey> but that's not what i meant by getting rid of boot time
[21:30] <baptistemm> dobey, with a ssd you almost get ride of boot time :)
[21:31] <dobey> baptistemm: no you don't
[21:31] <dobey> and i wish people would stop counting "boot time" as "only the time it takes once grub actually tells the kernel to initialize"
[22:22] <JanC> dobey: you also wish we could get rid of the BIOS?  ;)
[22:24] <crimsun> dobey: what sort of updates?
[22:25] <dobey> JanC: yes
[22:26] <dobey> crimsun: hrmm?
[22:26] <crimsun> 16:27 < dobey> like, i install enough updates that pulseaudio finally breaks
[22:26] <dobey> crimsun: i don't know. i just know stuff breaks, and i have to either restart completely, if not just restart some apps, to resolve sudden breakage
[22:27] <dobey> crimsun: sometimes kernel, sometimes pulseaudio updates i guess
[22:27] <dobey> of course, ono my laptop, pulseaudio wants to keep the sound muted :-/
[22:27] <crimsun> dobey: under lucid?
[22:28] <dobey> crimsun: under karmic. i just updated my laptop to lucid yesterday so haven't used lucid a whole lot yet
[22:28] <dobey> i need to fix the video on it though
[22:28] <dobey> grmbl grmbl intel
[22:28] <crimsun> I already fixed the mute issues in lucid
[22:28] <dobey> ok, then maybe it's ok with lucid
[22:29] <crimsun> dobey: please look at amixer state prior to logging in via gdm and after logging in to GNOME
[22:29] <dobey> though the machine i care about it on is still running karmic
[22:29] <dobey> ok
[22:29] <dobey> anyway
[22:29] <dobey> i need to get away from the computer now
[22:29] <dobey> later
[22:29] <crimsun> I can't fix bugs I don't have good bug reports for