[06:58] <humphreybc> Hello everyone, who do I need to speak to about Lucid CD contents?
[07:25] <humphreybc> no one?
[07:30] <didrocks> good morning o/
[07:44] <oni> hi
[07:44] <didrocks> morning oni
[07:44] <oni> anyone tryed to use 9.10 on intel i5-clarkdale
[07:45] <oni> it is booting fine but when gnome starts in suddenly hangs any idea?
[07:48] <didrocks> oni: this is not a support channel, please, head to #ubuntu if you can find a workaround (if you have a X server running, maybe disabling compiz can be a start to see if it's related to 3D acceleration)
[07:49] <oni> in #ubuntu nobody could help so i tryed here
[07:49] <didrocks> oni: you didn't find anything related on LP or on ubuntuforums?
[07:50] <oni> no i think clarkdale is a bit to new
[07:50] <didrocks> maybe disabling 3D acceleration on the driver is a start. I have no other clue, sorry :/
[07:51] <oni> ok thanks i will try it
[07:57] <azteech> oni: use this search link for info regarding linux issues and such for the clarkdale - http://www.google.com/search?q=ubuntu+%2B+intel+i5-clarkdale&ie=utf-8&oe=utf-8&aq=t&rls=com.ubuntu:en-US:official&client=firefox-a
[07:58] <azteech> whole page of info, including bug reports
[08:00] <azteech> lot of it not specific to ubuntu-branded - but definitely linux hits
[08:02] <oni> my google(german) just finds reviews
[08:03] <azteech> try putting it in this way in a search window - "ubuntu + intel i5-clarkdale" without the quote marks
[08:04] <oni> thats exactly what your link is doing
[08:06] <oni> may i should put a detailt bug report to LP
[08:10] <rickspencer3> join #quickly
[08:10] <didrocks> hey rickspencer3 :)
[08:10] <rickspencer3> didrocks, good morning, welcome to the desktop team!!
[08:10] <didrocks> thanks a lot rickspencer3 :)
[08:14] <azteech> just as an example - here are a couple links that the search brought up: http://www.phoronix.com/scan.php?page=article&item=intel_lynnfield&num=1  http://www.uluga.ubuntuforums.org/showthread.php?p=7903098
[08:15] <azteech> oni: maybe you will need to try that, after disabling 3D acceleration, as didrocks advised above.
[08:17] <oni> these posts are about the "old" i5 series
[08:21] <azteech> oni: no problem - then recommend do as suggested, and if nothing works, file a detailed bug report then
[08:22] <oni> ok thanks
[08:39] <seb128> good morning there
[08:39] <chrisccoulson_g1> hey seb128, how are you?
[08:39] <seb128> hey chrisccoulson_g1, it's monday morning and I'm not fully awake yet but good I think
[08:39] <seb128> what about you?
[08:40] <chrisccoulson_g1> yeah, I'm good thanks. but stuck in a long queue of traffic in my car at the moment
[08:41] <seb128> oh :-(
[08:41] <seb128> still due to the winter weather?
[08:42] <chrisccoulson_g1> I'm not too sure yet. I think there must have been an accident somewhere on my route
[08:42] <chrisccoulson_g1> the weather isn't too bad now though
[08:43] <baptistemm> hello
[08:43] <seb128> hey baptistemm
[08:43] <seb128> chrisccoulson_g1, did you have any chance to look at g-c-c yet?
[08:44] <seb128> it should be rebuilt for tomorrow if we want to get the libgnome-desktop soname transition done for alpha2
[08:44] <chrisccoulson_g1> seb128 - I did it last night, and pushed to bzr
[08:45] <seb128> nice
[08:45] <seb128> any reason you didn't upload?
[08:45] <chrisccoulson_g1> I haven't had a chance to make sure everything still works though
[08:45] <chrisccoulson_g1> gcc is in desktop-core package set, so I can't upload
[08:46] <seb128> oh ok
[08:46] <seb128> if there is no breakage that's ok nowadays since g-c-c is only capplets
[08:46] <seb128> g-s-d is the session visible component
[08:46] <seb128> but I will give it a try later, thanks
[08:46] <seb128> I'm getting coffee first!
[08:47] <chrisccoulson_g1> coffee sounds good!
[08:47] <rickspencer3> hi seb128
[08:48] <seb128> salut rickspencer3
[08:48] <seb128> comment ça va ?
[08:48] <seb128> bien arrivé en France ?
[08:49] <rickspencer3> bon
[08:49] <rickspencer3> uh, don't know "yesterday" :(
[08:49] <rickspencer3> oops, running out of power
[08:49]  * rickspencer3 runs to fnac to get a covnerter
[08:49] <seb128> "hier"
[08:50] <seb128> see you later!
[08:50] <seb128> I don't think not having a ground plug is an issue btw
[08:51] <seb128> davidbarth, hey, I told you that upload on friday was not a good thing ;-)
[08:52] <didrocks> rickspencer3: see you later
[08:52] <seb128> I had to do fixing on saturday evening since things got screwed and all indicators were just crashing
[08:52] <rickspencer3> bbiab
[08:53] <davidbarth> seb128: what happened?
[08:53] <didrocks> hey chrisccoulson_g1 and baptistemm
[08:53]  * davidbarth reads up the log
[08:59] <seb128> davidbarth, new libdbusmenu-gk required new libdbusmenu-glib without saying so
[08:59] <seb128> davidbarth, and the new libdbusmenu-glib used a Breaks on indicators packages that need an update
[08:59] <chrisccoulson_g1> hey didrocks, how are you?
[09:00] <seb128> davidbarth, which leaded to have the gtk version update and not the glib one and things crashing on lack of symbols
[09:00] <chrisccoulson_g1> I wish I had got some coffee in my car
[09:01] <davidbarth> seb128: well, i told kenvandine that you did not recommend uploads on Friday, so what happened?
[09:01] <seb128> he did upload anyway
[09:01] <seb128> and things broke
[09:01] <seb128> anyway no real issue I sorted that
[09:01] <davidbarth> seb128: sure, but sorry for the issue
[09:02] <seb128> but it made me unhappy to have to work on saturday evening to fix things when I told people to not upload on firday for that reason ;-)
[09:03] <davidbarth> seb128: ok, i'll try to clarify that during our integration call today
[09:04] <seb128> davidbarth, don't bother that's a distro issue, I will talk to kenvandine when he's around
[09:04] <seb128> nothing your team did wrong
[09:04] <seb128> out of delays tarball to friday which leaded to the conflict ;-)
[09:04] <seb128> but that happens
[09:05] <didrocks> chrisccoulson_g1: fine thanks. Concerning the coffee, I'm sure you'll take some in a bottle for the return path :)
[09:07] <chrisccoulson_g1> didrocks - yeah, I think I need to invest in a flask for coffee
[09:08] <chrisccoulson_g1> I'm tempted to turn around, I've only moved 1 mile in the last hour
[09:08] <seb128> you can get out?
[09:08] <seb128> or you are stucked on a one way road?
[09:09] <didrocks> hum, too bad… good luck :/
[09:09] <chrisccoulson_g1> seb128 - fortunately, its not 1 way. I could turn around if I don't move much soon
[09:09] <seb128> that's something
[09:36] <seb128> cassidy, hey
[09:36] <seb128> cassidy, bug #399039, do you know if that will be backport to telepathy-gabble 0.8?
[09:37] <seb128> or if 0.9 is what we should use in lucid?
[09:39] <seb128> wb rickspencer3
[09:39] <seb128> did you found what you needed?
[09:39] <rickspencer3> thanks seb128
[09:39] <rickspencer3> seb128, yes
[09:39] <rickspencer3> people in Paris are quite helpful so far
[09:39] <rickspencer3> despite that I have the communication powers of a chimp here
[09:39] <didrocks> you seem to be surprised :)
[09:40] <rickspencer3> didrocks, not surprised
[09:40] <rickspencer3> didrocks, did you get onto wiki.canonical yet?
[09:41] <didrocks> rickspencer3: no, Alice sent me an email and I told her I've still no access to the wiki
[09:41] <rickspencer3> hmmm'
[09:41] <rickspencer3> well, you are on irc.canonical
[09:41] <rickspencer3> so go to #rt
[09:41] <rickspencer3> I'll meet you there
[09:44] <seb128> rickspencer3, communication: it's a good way to measure your french skills and to learn some extra bits too ;-)
[09:44] <rickspencer3> seb128, yup
[09:44] <rickspencer3> I still can't parse anything anyone says to me
[09:44] <rickspencer3> but occasionally vocabulary words pop
[09:45] <rickspencer3> or I'll hear someone say something I understand, but never to me ;)
[09:45] <didrocks> rickspencer3: you're already presenting you in French "Bonjour, je m'appelle…". I think this is well appreciated :-)
[09:46] <rickspencer3> didrocks, right, then they reply in French, and I look totally confused .. and they say "are you speaking English?"
[09:46] <rickspencer3> ;)
[09:46] <didrocks> ahah :)
[09:46] <seb128> hehe ;-)
[09:47] <rickspencer3> I can say "merci" as well
[09:47] <rickspencer3> I think also appreciated
[09:47] <didrocks> right
[09:47] <rickspencer3> and d'accord ;)
[09:47] <seb128> and chouette? :-)
[09:48] <rickspencer3> lol
[10:15] <rickspencer3> didrocks, want to come into town and meet up for some lunch?
[10:15] <seb128_> re
[10:15] <seb128_> I'm getting some wifi troubles recently
[10:15] <seb128_> I'm wondering if that the lucid driver or the laptop card having issues
[10:16] <cassidy> seb128, I think we should probably switch to 0.9 for Lucid yeah
[10:16] <didrocks> rickspencer3: yes, what time and where is the best for you?
[10:17] <cassidy> seb128, I'll ask to the Gabble guys what they think and I'll let you know
[10:17] <rickspencer3> didrocks, any time starting now
[10:18] <didrocks> rickspencer3: let me check for trains
[10:18] <seb128> cassidy, can you check if we will get a 1.0 or 0.9 stable on schedule?
[10:20] <cassidy> oki
[10:20] <didrocks> rickspencer3: I've one at 11:43, which should bring me next to the hotel at 12:05. Is it ok for you?
[10:20] <rickspencer3> didrocks, poifect
[10:22] <seb128> cassidy, ok thanks
[10:22] <seb128> cassidy, no hurry!
[10:22] <cassidy> sure
[10:32] <didrocks> rickspencer3: leaving now. I'll find you at the hotel lobby
[10:33] <rickspencer3> didrocks, great
[10:33] <rickspencer3> bon voyage
[10:45] <chrisccoulson_g1> excellent, I've finally arrive at work!
[10:45] <chrisccoulson_g1> it only took me 3 hours!
[10:45] <seb128> chrisccoulson_g1, took you only 3 hours?
[10:45] <seb128> lol
[10:45]  * seb128 hugs chrisccoulson_g1
[10:45] <seb128> not the best week to start the week
[10:46]  * chrisccoulson_g1 hugs seb128
[10:46] <chrisccoulson_g1> I'm quite tired now - I've normally had 3 coffees by now
[10:47] <seb128> hehe
[10:48] <seb128> davidbarth, do you know what's going on with the indicator-me options?
[10:48] <seb128> like im status, etc
[10:48] <seb128> is that a new source? is it expected to land this week?
[10:48] <seb128> the current session applet dropped those
[11:01] <davidbarth> seb128: atm the indicator-me code contains what was in the status sub-menu of the session menu
[11:01] <davidbarth> seb128: it will be enhanced to support more of the features that are now defined (and approved) in the "me menu" spec
[11:02] <seb128> what is indicator-me? a new source?
[11:02] <seb128> will it be available before beta2?
[11:02] <davidbarth> seb128: the me menu is part of the a2 delivery
[11:02] <seb128> alpha2 I mean
[11:02] <seb128> ok
[11:02] <davidbarth> seb128: it's a new source yes, with a separate package
[11:02] <seb128> it's not there atm and freeze is tomorrow
[11:02] <seb128> I guess it's rather a ted and kenvandine's question though
[11:02] <seb128> I will sort that with them when they are around
[11:02] <davidbarth> seb128: so, that was part of the "don't release of friday"
[11:02] <davidbarth> seb128: or i don't know
[11:03] <seb128> the point I tried to make is "don't make half baked broken changes before running away for the weekend"
[11:03] <davidbarth> but it's in our ppa, i'm running the code, it keeps running in integration with the supported IM clients, like it used to within the sesion menu
[11:03] <seb128> ie either do everything in a tested way or wait monday ;-)
[11:03] <seb128> thanks
[11:04] <seb128> I will sort that with ken and ted
[11:20] <chrisccoulson> seb128 - i wasn't the last person to arrive at work ;)
[11:20] <chrisccoulson> someone else has just arrived now
[11:20] <seb128> lol
[11:20] <seb128> in time for lunch!
[11:20] <seb128> oh, not yet, it's one hour earlier for you guys
[11:23] <chrisccoulson> heh, i'm definately ready for lunch now
[12:38] <cassidy> seb128, the chat state bug has been fixed in 0.8
[12:39] <seb128> cassidy, oh ok, the GNOME bug comments stated in didn't, thanks
[12:39] <cassidy> It did now. We just backported the patch :)  Adding a comment
[12:40] <seb128> thank you!
[12:40] <seb128> so you recommend staying on 0.8?
[12:41] <cassidy> for now yes. I think 0.9 still have few regressions
[12:41] <cassidy> we should hopefully get rid of them soon
[12:41] <seb128> ok thanks
[13:02] <mvo> seb128: hi
[13:02] <seb128> re
[13:02] <seb128> hey mvo
[13:03] <mvo> seb128: a quick question, we used to have a "text" option on boot that prevetned gdm from starting
[13:03] <seb128> I should sort that autoconnect and ip change issue
[13:03] <seb128> it tends to make my client bounce on session start
[13:03] <mvo> seb128: this seems to be gone again with the convert to a job file?
[13:03] <seb128> it should not
[13:04] <mvo> so that should still work? I have a look then
[13:05] <seb128> 	    case "${ARG}" in
[13:05] <seb128> 		text|-s|s|S|single)
[13:05] <seb128> 		    exit 0
[13:05] <seb128> mvo, ^ that's the upstart job
[13:05] <seb128> 	do
[13:06] <seb128> ups
[13:06] <seb128> wehre
[13:06] <seb128> 	# Check kernel command-line for inhibitors
[13:06] <seb128> 	for ARG in $(cat /proc/cmdline)
[13:06] <mvo> seb128: thanks. odd. I double check, maybe I did a typo or something with grub was odd
[13:07] <seb128> or maybe the job file is buggy in some way
[13:07] <seb128> but it has not been intentionally dropped
[13:10] <chrisccoulson> hey pitti, are you around?
[13:11] <seb128> chrisccoulson, he was around but stopped IRC, he said it's not stable enough in the train
[13:12] <seb128> but he reads scrollback every now and then apparently
[13:12] <chrisccoulson> seb128 - thanks
[13:12] <seb128> so better to just ask your question
[13:12] <chrisccoulson> seb128 - could you add a karmic task to bug 505789?
[13:12] <chrisccoulson> it seems to be a regression caused by a previous SRU
[13:12] <seb128> you can probably do that no? did you try?
[13:13] <chrisccoulson> seb128 - i just tried that, but i can't do it
[13:14] <seb128> chrisccoulson, you managed to suggest it for nomination but not nominate it right
[13:14] <seb128> chrisccoulson, I've accepted it now
[13:15] <chrisccoulson> seb128 - thanks
[13:15] <seb128> np
[13:58] <seb128> hey tedg
[13:59] <tedg> Good morning seb128
[13:59] <tedg> Looks like some work to do from Friday's upload :(
[13:59] <seb128> yeah
[13:59] <seb128> first we don't have im actions anymore now
[14:00] <seb128> but that apparently waits on a new source?
[14:00] <tedg> Yes, it was split out into the "indicator-me" package.
[14:00] <seb128> tedg, the rhythmbox menu looks weird now, previous and next got broken icons
[14:00] <seb128> and the power icon on the shutdown line is weird too, especially shifted
[14:00] <tedg> seb128: Yes, they're using GTK Stock icons and we need to figure out a way to translate that into icon-naming-spec icons.
[14:01] <tedg> GTK does that internally, but we need to do it somewhat externally.
[14:01] <seb128> ok
[14:01] <tedg> The shifting is somewhat on purpose.  It's so that the items can have checkboxes and icons as well.  GTK doesn't support this but all the other toolkits do.
[14:01] <seb128> tedg, you guys screwed the update by not update the shlibs version for libdbusmenu btw
[14:01] <tedg> There isn't enough spacing there, but that's a simpler fix :)
[14:02] <seb128> tedg, libdbusmenu-glib got blocked while -gtk got updated which leaded to crashland
[14:02] <tedg> So -gtk should depend on -glib?  (I saw the bug, but I'm not sure I understood)
[14:03] <seb128> it does use symbols from it since it was crashing on a not found symbol there
[14:03] <seb128> so yes, it should depends on the version which has all the symbols it needs
[14:03] <seb128> that's done usually by updating the shlibs number in the package when api are added
[14:04] <seb128> the current package has a shlib version for -gtk in its rules
[14:04] <seb128> but none for -glib
[14:04] <tedg> Why wouldn't we have -gtk depend on the exact version, as they'll always get updated together?
[14:04] <seb128> they didn't
[14:04] <seb128> which leaded to crash land
[14:04] <seb128> they are different binary
[14:05] <seb128> somebody made the new -glib Breaks the old indicators
[14:05] <seb128> which made -glib in hold until the indicators were updated
[14:05] <seb128> but nothing blocked the -gtk update
[14:05] <seb128> which leaded to new -gtk installed with all -glib
[14:05] <seb128> and the version mismatch doesn't work so well
[14:05] <tedg> Okay, so in the libdbusmenu-gtk0 should have "Depends: libdbusmenu-glib (= ${binary:Version})
[14:05] <seb128> >= should do
[14:05] <seb128> but yes
[14:06] <seb128> the shlibs system should take care of such depends
[14:06] <seb128> if you use a shlib
[14:06] <seb128> "shlib" means "the version required to have the current complete api set"
[14:06] <tedg> But since they're built together, wouldn't it not go through that?
[14:07] <seb128> the debian tools add a depends on the lib by going through ldd list basically
[14:07] <seb128> ldd library.so
[14:07] <seb128> and it add the package containing the lib (>= versin_shlib)
[14:07] <seb128> in this case you get -gtk depends on -glib (>= 0)
[14:07] <seb128> since you didn't set a shlib
[14:08] <seb128> it also means that right now that something building against libdbusmenu-glib0 will get a depends on it with no version
[14:09] <seb128> shlibs is a trick to make sure you get a least the api you built against
[14:09] <seb128> it doesn't do symbol granularity
[14:09] <kenvandine> seb128, eww...
[14:09] <seb128> it just says "I built against version <n> of this lib so I will depends on that version because I know it's working"
[14:10] <seb128> you can't know that version n-1 would work too
[14:10] <seb128> slightly tweaked to make that "depends on the version which has the current api"
[14:10] <tedg> Do you know a good package to look at to see how to set it up?
[14:11] <seb128> ie if the api has no addition between 0.2 and 0.3 the shlib stays to 0.2
[14:11] <seb128> libdbusmenu?
[14:11] <seb128> as said the rules has the line which set it for -gtk
[14:11] <seb128> but not for -glib
[14:11] <seb128> you need to add the same line for that one
[14:11] <tedg> Ah, I see.
[14:11] <seb128> and make sure you update the versions when you add things to the api
[14:12] <seb128> or use .symbols
[14:12] <seb128> which is the modern way
[14:12] <seb128> it lists all symbols and the version they have been added to
[14:12] <seb128> so you know from the symbols you use what version you need
[14:13] <tedg> Is there a tool to do that, or by hand?
[14:14] <seb128> dpkg-gensymbols is the tools used for those
[14:14] <seb128> once set up you don't have to do anything
[14:14] <seb128> typically build will break when it run into symbols not listed
[14:14] <seb128> and give you a diff with those listed as being added in the version you try to build
[14:14] <seb128> so you just apply the diff and rebuild
[14:15] <seb128> no need to do history
[14:15] <seb128> you can start by making a list of all symbols and say they have been added in the current version
[14:15] <seb128> and work incremental from there
[14:16] <seb128> kenvandine, hey, can you summarize where we stand now, what needs sponsoring, seeding, adding, etc?
[14:16] <seb128> kenvandine, the alpha2 freeze is tomorrow
[14:16] <seb128> and pitti is travelling today which somewhat limit you main promotion, newing etc speed
[14:17] <kenvandine> seb128, cjwatson fixed the upload perms
[14:17] <kenvandine> i got that stuff uploaded
[14:17] <kenvandine> only current issue i know of is jockey
[14:17] <seb128> which one?
[14:17] <seb128> there is no im menu anymore in current lucid
[14:17] <kenvandine> won't build, because of a regression in a kde lib
[14:18] <seb128> that's a new source no?
[14:18] <seb128> has that been uploaded?
[14:18] <kenvandine> yeah
[14:18] <kenvandine> one sec
[14:18] <kenvandine> pitti and i traded a couple emails this morning
[14:18] <seb128> kenvandine, btw next time avoid disruptive change on friday evening if you can, I told davidbarth to not to it...
[14:18] <seb128> ok
[14:19] <kenvandine> pykdeuic4 calls kde_i18n_string.escape() which doesn't exist any more
[14:19] <kenvandine> http://launchpadlibrarian.net/37627198/buildlog_ubuntu-lucid-i386.jockey_0.5.5-0ubuntu6_FAILEDTOBUILD.txt.gz
[14:19] <seb128> oh, you speak about jockey
[14:19] <seb128> good to know but I think if it's not in alpha2 that's ok
[14:19] <kenvandine> and the mono bindings to libappindicator are broken
[14:19] <seb128> I'm rather concerned about the new source
[14:19] <seb128> with the im status, etc
[14:19] <kenvandine> ah, just indicator-me then
[14:20] <seb128> yes
[14:20] <kenvandine> which isn't uploaded yet
[14:20] <seb128> as said before freeze is tomorrow
[14:20] <kenvandine> i need you for that :)
[14:20] <seb128> and our main promotion, newing etc will not be as efficient with pitti travelling
[14:20] <seb128> is it ready to be sponsored?
[14:20] <kenvandine> i think so, let me look at it one more time
[14:20] <seb128> thanks
[14:22] <kenvandine> tedg, ok... after updating this morning and rebooting the app indicator is working again
[14:23] <kenvandine> but not for mono
[14:23] <kenvandine> tedg, we really need that fixed asap...
[14:23]  * kenvandine files a bug
[14:25] <kenvandine> seb128, lp:~ubuntu-desktop/indicator-me/ubuntu is ready to be sponsored
[14:25] <seb128> kenvandine, looking
[14:25] <tedg> kenvandine: No one uses Mono ;)
[14:26] <tedg> kenvandine: Did you file a bug?
[14:26] <seb128> tedg in a troll mood today? ;-)
[14:26] <tedg> seb128: No, I'm applying for moderator on boycottnovell.com ;)
[14:27] <seb128> heh
[14:28] <seb128> tedg, why do you distribute a LGPL copy in the indicator-me source if there is only GPL code there?
[14:28] <seb128> kenvandine, ^
[14:28] <tedg> seb128: Uhm, good question? :)
[14:29] <kenvandine> tedg, bug 505923
[14:29] <kenvandine> tedg, please remove the crufty license file :)
[14:29] <seb128> tedg, also "POLKIT_REQUIRED_VERSION=0.92" in configure seems useless?
[14:30]  * kenvandine suspects there is plenty of cruft left over from indicator-session
[14:30] <seb128> lool, mvo: could one of you quickly sponsor lp:~ubuntu-desktop/indicator-me/ubuntu for me, I want to NEW in but I can't sponsor and NEW
[14:30] <seb128> it's a new source from dxteam and should be fairly trivial
[14:31] <seb128> I just had a quick look and it seems ok
[14:31] <lool> seb128: Looking
[14:31] <seb128> lool, thanks
[14:31] <kenvandine> lool, and it isn't really much "new" code... just split out for indicator-session
[14:31] <kenvandine> jcastro was rather disappointed it wasn't all the "bling" we saw at UDS :)
[14:32] <kenvandine> tedg,  the mono bindings problem should just be a case or re-generating the bindings?
[14:32]  * kenvandine thinks that should happen automatically... like in distcheck or something
[14:32] <tedg> kenvandine: I don't know, it seems like they should have been regenerated in the build.
[14:33] <tedg> kenvandine: Did you run Tomboy on the command line?
[14:33] <tedg> kenvandine: I'm curious if the error means something more to you :)
[14:33] <kenvandine> (tomboy:24379): GLib-GObject-WARNING **: IA__g_object_set_property: object class `AppIndicator' has no property named `PROP_STATUS_S'
[14:33] <seb128> tedg, are the broken previous and next icons in rhythmbox a rhythmbox patch issue?
[14:33] <kenvandine> that isn't a new message
[14:34] <tedg> seb128: They're a libappindicator issue.
[14:34] <seb128> tedg, ok thanks
[14:34] <kenvandine> tedg, however... running tomboy doesn't display it in the indicator and it does actually stay running as if it is
[14:34]  * seb128 reassign bug
[14:34] <tedg> kenvandine: Yeah, but that's why it's broken now :)  It's not setting the status.
[14:34] <kenvandine> does that need to be in the bindings or does the tomboy patch need to do that?
[14:34] <tedg> kenvandine: Before we ignored the status, so it didn't matter.  Now we're listening to applications :)
[14:35] <seb128> oh, nice to see that fixed
[14:35] <seb128> it means I could do the nautilus change now ;-)
[14:35] <tedg> kenvandine: It should set the status when creating the object -- atleast that's how it's done in C.  We don't provide another way to do it -- I'm not sure how Mono handles that.
[14:35] <lool> tedg: POLKIT_REQUIRED_VERSION=0.92 in configure.ac isn't used
[14:36] <kenvandine> tedg, but does tomboy need to set that?
[14:36] <tedg> lool: Yup.  Deleted it just now. :)
[14:36] <kenvandine> tedg, i am just wondering if we need to change the tomboy patch or mono bindings in libappindicator :)
[14:36] <tedg> kenvandine: Yes.  But, I'm not sure how.  If it's part of the "new" function or if it's explicit.
[14:36] <kenvandine> what is the C function?
[14:36] <lool> tedg: configure.ac requires DBUSMENUGLIB_REQUIRED_VERSION=0.1.1 and DBUSMENUGTK_REQUIRED_VERSION=0.2.0 but packaging requires 0.2 of both
[14:37] <kenvandine> that should be 0.2.0...
[14:37] <tedg> kenvandine: For instance, most C programs don't set the status as much as they set the value in the _new function.  But there is a set_status as well.
[14:37] <lool> tedg: You can drop AC_SUBST(APPLET_CFLAGS), _LIBS and same for STATUSERVICE_CFLAGS and _LIBS; PKG_CHECK_MODULES does it for you
[14:37] <kenvandine> tedg, app_indicator_set_status?
[14:38] <kenvandine> indicator.Status = Status.Active;
[14:38] <tedg> lool: Oh, cool.  I didn't realize they do that now.
[14:38] <lool> It has been so forever but apparently not a lot of people know
[14:41] <lool> tedg, seb128: uploaded
[14:41] <seb128> lool, thanks
[14:41]  * seb128 hugs lool
[14:42] <tedg> lool: Thanks, I've got a branch with those comments in it.
[14:43] <lool> tedg: Also, 4-spaces tabs are a crime!!  ;-)
[14:43] <lool>                           indicator >= $INDICATOR_REQUIRED_VERSION
[14:43] <lool> >------->------->------->------->------->-------  dbusmenu-gtk >= $DBUSMENUGTK_REQUIRED_VERSION)
[14:49] <tedg> james_w: I tried the "bzr send" command that you posted in Friday.  And it seems that merge@launchpad.net doesn't exist.
[14:50] <seb128> tedg, kenvandine: indicator-me newed to main
[14:50] <kenvandine> thx
[14:51] <tedg> seb128: Thanks!
[14:51] <seb128> thanks to lool who sponsored it so I can NEW it now ;-)
[14:51] <lool> NB: I didn't test build it (lalala)
[14:52] <lool> But you guys write perfect code anyway
[14:52] <seb128> it's in a ppa so it should be build tested
[14:52] <kenvandine> i built it in pbuilder too
[14:52] <lool> Yeah, but I'm always scared of the bzr bd -S export thing with the tarball; it should just work, but yaknow
[14:53] <lool> It just feels scary   ;)
[14:53] <tedg> james_w: It seems to be merge@code.launchpad.net -- haven't gotten an error yet :)
[14:53] <mvo> seb128: yes, I can do that
[14:53] <seb128> mvo, too late
[14:53] <seb128> mvo, but thanks
[14:53] <mvo> oh, ok
[14:54] <seb128> mvo, lool was quicker ;-)
[14:54] <seb128> mvo, did you sort you gdm text issue btw?
[15:04] <rickspencer3> kenvandine, read your empathy messages
[15:04] <rickspencer3> I can hear you, but need to set up my mic
[15:05] <rickspencer3> I could hear you fine, fwiw
[15:07] <seb128> kenvandine, could you push your libdbusmenu changes to bzr? I was fixing the shlib issue but apparently you didn't push the 0ubuntu2 revision there
[15:07] <kenvandine> i didn't
[15:07] <kenvandine> damn...
[15:07] <kenvandine> sure
[15:08] <seb128> thanks
[15:08] <kenvandine> seb128, pushed
[15:08] <kenvandine> sorry about that
[15:08] <seb128> no worry
[15:08] <seb128> thanks
[15:09] <mvo> seb128: text> that is fine, no idea what was wrong before but works fine
[15:09] <seb128> mvo, ok good
[15:24] <kenvandine> seb128, oh... by the way, i can't prevent xchat from setting the urgency on the window... not from the plugin
[15:24] <seb128> kenvandine, ok
[15:24] <kenvandine> seb128, i can unset the urgency, but xchat sets it again after the plugin is done with it
[15:24] <kenvandine> so we would need to patch xchat for it..
[15:24] <seb128> don't bother with that, that's a detail
[15:24] <kenvandine> yeah
[15:24] <kenvandine> :)
[15:24] <seb128> let me know when you want sponsoring for this one
[15:25] <kenvandine> in a few minutes
[15:25] <kenvandine> i want to do that this morning
[15:25] <kenvandine> and then we can patch xchat to set the plugin enabled by default
[15:25] <kenvandine> :)
[15:32] <baptistemm> hi seb128, Do you remember the problem I reported about blank display after boot and not VT switch? your fix didn't worked :/
[15:32] <seb128> ok, so I don't know
[15:33] <seb128> did you try wait for a while?
[15:33] <seb128> it could be fsck running...
[15:34] <baptistemm> I doubt, there is no I/O activity
[15:35] <baptistemm> and I don't find anything in X log. I can have gdm if I start using the "failsafe" mode, I launch netroot and then I do a "start gdm"
[15:36] <baptistemm> I'll report a bug but I have nothing relevant to provide :/
[15:36] <seb128> try asking on #ubuntu-x maybe
[15:36] <baptistemm> hmm you're right
[15:50] <seb128> tedg, kenvandine: I've newed indicator-me binaries and added the applet depends back now
[15:50] <kenvandine> seb128, thx!
[15:50] <seb128> tedg, kenvandine: I've newed indicator-me binaries and added the applet depends back now, I've also fixed the dbusmenu shlib issue
[15:50] <seb128> np
[15:50] <tedg> seb128: Thanks!
[15:50] <kenvandine> seb128, actually it should be a recommends, it will work without it :)
[15:50] <seb128> kenvandine, do you need help on the mono binding issue?
[15:50] <kenvandine> but we want it to come along for the ride
[15:50] <kenvandine> imho
[15:51] <seb128> ok
[15:51] <seb128> we can change that in the next upload
[15:51] <seb128> no hurry
[15:51] <kenvandine> seb128, if you have time to look at it
[15:51] <kenvandine> then i can prepare xchat-indicator for review :)
[15:53] <seb128> ok, I will have a look
[15:55] <kenvandine> seb128, i regenerated the bindings and tried to run the example in the examples dir
[15:55] <kenvandine> and got the same results
[16:05] <tedg> bratsche_: By chance, did you look at the Mono binding issue we were talking about on Friday?
[16:06] <bratsche_> No, sorry.
[16:06] <tedg> One thing I don't understand is why in the .metadata file there is two of several of the defines.
[16:06] <tedg> Like PROP_STATUS_S has two values.
[16:07] <tedg> Oh, name and type.
[16:08] <tedg> Do those #defines get evaluated or do we need to translate them into strings in that file?
[16:08] <bratsche_> Let me pull down the code and look, I can't remember.
[16:08] <tedg> Is there an easy way to dump the property names in Mono so that we can see what they think they are?
[16:09] <bratsche_> I can look at the IL disassembler.. that's the easiest way I know how to do it.
[16:09] <bratsche_> Or maybe in the generated sources.. I forgot about that.
[16:09] <bratsche_> Hangon
[16:11] <bratsche_> You mean how is it translating from the C# enum back into something when it talks to the native lib?
[16:12] <tedg> Yeah, or where is it getting the value for PROP_STATUS_S -- it's a #define in the C source.
[16:12] <tedg> I'm not sure if it's getting the value correctly.
[16:12] <tedg> Looking at the generated source I think it's trying to pass "PROP_STATUS_S" instead of "status" to GTK.
[16:12] <bratsche_> And "PROP_STATUS" is what, an int/enum?
[16:12] <tedg> #define
[16:13] <tedg> Oh, sorry, PROP_STATUS is an enum.
[16:13] <tedg> Actually, both of them are internal to the C file.
[16:13] <tedg> They're not even in a .h.
[16:14] <bratsche_> Maybe Status should be using PROP_STATUS instead of PROP_STATUS_S?
[16:14] <tedg> bratsche: Perhaps, I'm not sure how it should work.  But neither of those are exported.
[16:15] <bratsche> It doesn't matter if it's exported, it's a GObject property.
[16:15] <DBO> can someone give me the short version on whats broken?
[16:15] <bratsche> The world, dude.  The world.
[16:15] <tedg> DBO: Tomboy comes up hidden because it can't change the status from "passive" to "active"
[16:15] <DBO> okay, let me rephrase, can ted give me the short version
[16:15] <tedg> DBO: Gives and error about not being able to evaluate PROP_STATUS_S
[16:15] <DBO> ah
[16:16] <DBO> will fix
[16:16] <DBO> uhm, but I am in class all day today
[16:16] <DBO> try adding a rule to rename PROP_STATUS_S to PROP_STATUS
[16:16] <bratsche> Okay
[16:16] <bratsche> What about other stuff like PROP_CATEGORY_S?  Presumably they'll have the same problems?
[16:17] <DBO> potentially
[16:17] <DBO> I am looking at it all now
[16:17] <bratsche> The weird thing is I think we tested this stuff when we were adding the bindings.
[16:18] <DBO> oh *I* see whats going n
[16:18] <DBO> on
[16:18] <DBO> this is suck...
[16:18] <DBO> also, we can blame ted!
[16:18] <bratsche> heh
[16:18] <seb128> you can always blame ted
[16:18] <seb128> ;-)
[16:18] <DBO> basically, our bindings are a bit confused about how to set those properties because we provide them as GObject properties and as very well named method calls
[16:19] <DBO> which is ultimately causing some confusion
[16:19] <DBO> all we need to do is add some rules to the bindings to tell it to use the right things
[16:20] <DBO> bratsche, I think getting rid of the _S will provide a quick fix
[16:20] <DBO> however I'll need to straighten out the duplicate functionality
[16:20] <DBO> g2g
[16:21] <DBO> later
[16:21] <bratsche> Okay cool.
[16:21] <bratsche> Later dude.
[16:23] <didrocks> going to meet pitti at La Defense, bbl
[16:24] <seb128> didrocks, say hello
[16:24] <seb128> didrocks, have fun
[16:25] <bratsche> seb128: I think I've tracked down this gtk issue in totem a little further.  The stacktrace indicates that it's XSetBackgroundPixmap() generating the BadMatch, but when I commented that out then the very next X call generated the error instead.  Looking through xtrace it seems the last call was to GetInputFocus, which seems to be in the async code in csw which is why the bug goes away with GDK_NATIVE_WINDOWS set.  Still not sure yet why it
[16:25] <bratsche> 's only happening with rgba on though.
[16:25] <bratsche> Fun stuff.
[16:25] <seb128> seems so
[16:25] <bratsche> I'm going to switch over to libappindicator for a bit now, I need to finish up a patch there before I dig into this any more.
[16:25] <seb128> debugging async x calls is alway fun
[16:25] <seb128> ok
[16:26] <seb128> thanks for keeping me updated there
[16:31] <chrisccoulson> hey bratsche - i was thinking of putting together a session on debugging X errors for a future UDW. perhaps you have some knowledge to contribute there? ;)
[16:31] <bratsche> Uhh.. I think I need to attend such a session to learn more. :)
[16:32] <chrisccoulson> lol
[16:32] <chrisccoulson> nobody likes debugging them, but i ended up working on a few during karmic
[16:40] <bratsche> It's actually really interesting.  I used to debug some internal stuff in gtk's Win32 backend, but it wasn't so bad because MSDN is fucking amazing.  We don't have anything like that though, and I guess you have to start reading xserver code to get really deep.
[16:41] <bratsche> I guess this is why there are so few people who really know all the details about this kind of stuff.
[16:57] <chrisccoulson> bratsche - yeah, i had to read the xserver code a few times when investigating those types of issues
[16:57] <chrisccoulson> and i hav eno clue about Xorg really ;)
[16:59] <itorrey> djsiegel: I am getting Lucid up and running my main dev machine and have 9.10 installing as well. I installed Lucid (all of this in VMWare FUsion) on my MBP but Empathy didn't actually connect to any of my accounts so I'm going to work from 9.10 for the moment
[17:00] <djsiegel> itorrey: sounds fine, I am sure the differences as far as themeing empathy will be slight to none
[17:00] <djsiegel> itorrey: seg|ars in #ayatana said he will port your empathy theme to gwibber (twitter client shipping in Lucid)
[17:00] <djsiegel> so we will have a consistent messaging style across IM and microblogging
[17:00] <itorrey> Would you like me to take a crack at the color scheme?
[17:00] <itorrey> Oh nice
[17:01] <djsiegel> itorrey: I don't have the colors from our artists yet
[17:01] <djsiegel> kwwii: ^
[17:01] <djsiegel> kwwii: itorrey wants some color recommendations for the renkoo-inspired empathy theme
[17:06] <djsiegel> itorrey: you may want to create a launchpad account and assign this bug to yourself so you get mail about it: https://bugs.edge.launchpad.net/ubuntu/+source/empathy/+bug/392488
[17:50] <rickspencer3> kenvandine, hiya
[17:50] <kenvandine> hey rickspencer3
[17:51] <rickspencer3> what's the scoopage with the widget for microblogging through gwibber
[17:51] <rickspencer3> ?
[17:51] <rickspencer3> any progress?
[17:52] <kenvandine> humm... well sosocial works (i think)
[17:52] <kenvandine> not really a widget
[17:52] <kenvandine> seiflotfy_, says he has one
[17:52] <kenvandine> seiflotfy_, is that ready?
[17:52] <rickspencer3> so none built into gwibber atm?
[17:52] <rickspencer3> I can make one easily, so no worries
[17:52] <kenvandine> not yet
[17:52] <kenvandine> woot
[17:52] <kenvandine> :)
[17:52] <rickspencer3> I mean, make one for my app
[17:53] <rickspencer3> but I'll do it properly so you guys can snipe it if you want
[17:53]  * rickspencer3 derives from HBox
[17:54] <kenvandine> rickspencer3, sounds great
[17:57] <rickspencer3> kenvandine: http://bazaar.launchpad.net/~rick-rickspencer3/lolz/quickly_trunk/annotate/head%3A/lolz/MicroblogDialog.py
[17:57] <rickspencer3> I'll add that to quidgets for now
[17:58] <rickspencer3> nah, I'll just stick it in photobomb for now, and you guys can snip it
[18:01] <kenvandine> hehe
[18:01] <kenvandine> thx
[18:47] <djsiegel> ok rickspencer3
[18:48] <djsiegel> think we can set, as a goal for Lucid, that autologin users don't have to type their password to join a saved wifi network?
[18:49] <chrisccoulson> djsiegel - out of interest, how do you achieve that?
[18:49] <chrisccoulson> setting an empty keyring password?
[18:49] <djsiegel> pitti: ^ do you have and community guys you could recommend who might want to explore solutions for that?
[18:49] <djsiegel> chrisccoulson: apparently, one solution is to make a separate keyring for those passwords
[18:50] <djsiegel> and that separate keyring is practically always unlocked, IIRC
[18:50] <chrisccoulson> but the keyring would need to have no password right?
[18:50] <chrisccoulson> yeah
[18:50] <chrisccoulson> would you intend to do that for users who don't use autologin?
[18:50] <djsiegel> hmm
[18:50] <djsiegel> I'm not sure
[18:50] <chrisccoulson> because we may as well just not bother using the keyring in that case, and store the secrets in plaintext
[18:51] <chrisccoulson> it's a difficult one to solve ;)
[18:51] <djsiegel> yes, but it's also something that we should definitely tackle
[18:51] <chrisccoulson> users would like good security and convenience of entering no password
[18:51] <djsiegel> yeah
[18:52] <djsiegel> sorry, gtg
[18:52] <djsiegel> brb
[19:41] <DBO> tedg, did the PROP_STATUS_S hack work?
[19:41] <tedg> DBO: I'm not sure.  I don't know where to change it, sorry.
[19:42] <DBO> kay, I'll do it
[19:42] <tedg> DBO: I was waiting for you to get out of class. :)
[19:42] <DBO> im in class for a while still
[19:42] <DBO> did you see my email on the dx-team list?
[19:43] <tedg> DBO: Ah, okay.  With your schedule?
[19:44] <DBO> tedg, thats the one
[19:45] <tedg> DBO: Yeah, I saw it, but I didn't think to look at it in this case :)
[19:45] <DBO> tedg, you are only justifying my belief that I need only read the mailing list :P
[20:05] <milanbv> chrisccoulson: you have a new stb - liboobs - gst trinity ready for packaging ;-)
[20:12] <chrisccoulson> milanbv - thanks :)
[20:13] <chrisccoulson> i'll try and look at that this week sometime (perhaps after A2 now)
[20:18] <milanbv> I'm not in a hurry, just to let you know
[20:18] <milanbv> there are major changes in the backends in that release
[20:18] <milanbv> bugs might appear without very visible benefit for users :-p
[20:19] <milanbv> the major change is that we don't commit users as a whole, but one by one, which means we won't remove all users and groups form the computer as some bugs reported
[21:22] <seb128> hey
[21:24] <jcastro> hi seb
[21:24] <seb128> hey jcastro
[21:24] <seb128> how are you?
[21:30] <jcastro> seb128: good. same old same old.
[21:30] <seb128> did anybody try the new indicator-me with empathy?
[21:30] <baptistemm> www.piware.de down ?
[21:31] <seb128> baptistemm, dunno, it has no content but replies there
[21:31] <seb128> pitti, ^
[21:31] <jcastro> seb128: I can in about a minute now that my mirror is caught up
[21:32] <seb128> jcastro, thanks
[21:32] <baptistemm> chrome obfuscates the real error
[21:32] <baptistemm> seb128,  indicator-me is the applet  with the firstname?
[21:33] <seb128> it's the menu in lucid which has the im options
[21:33] <seb128> it has your username as title yes
[21:34] <baptistemm> because I just started empathy from the ubuntu notification applet and the action in  indicator-me are disabled
[21:35] <jcastro> seb128: me too
[21:35] <jcastro> they're grayed out
[21:35] <jcastro> the applet is there and looks right though
[21:35]  * baptistemm is pondering to buy a 160 intel SSD disk
[21:35] <seb128> jcastro, ok thanks
[21:35] <seb128> same here
[21:36] <seb128> "right" but useless...
[21:36] <seb128> kenvandine, ^
[21:36] <seb128> known issue?
[21:36] <kenvandine> hey seb128!
[21:36] <seb128> hey kenvandine ;-)
[21:36] <kenvandine> seb128, yeah... that isn't new behavior... there is a problem with watching mc5
[21:37] <kenvandine> meaning it has been broken since xmas :)
[21:37] <kenvandine> seb128, can you look at lp:~ubuntu-desktop/xchat-indicator/ubuntu ?
[21:37] <kenvandine> it should be ready
[21:37] <seb128> ok
[21:37] <seb128> speaking of which I've a bug with that one
[21:37] <kenvandine> oh?
[21:37] <seb128> right now the message indicator lists 2 entries for xchat
[21:38] <seb128> xchat-gnome rather
[21:38] <seb128> one with the subtitle and one without
[21:38] <kenvandine> it shouldn't
[21:38] <seb128> I guess it didn't detect I ran it or something
[21:38] <kenvandine> humm
[21:38] <kenvandine> are you running xchat-gnome from /usr/bin?
[21:38] <seb128> yes
[21:38] <kenvandine> then it should
[21:38] <seb128> I've started it using the run software alt-f2 dialog
[21:38] <kenvandine> humm
[21:39] <kenvandine> try starting it from the indicator
[21:39] <seb128> ok, I think that's the first time it happened
[21:39] <kenvandine> see if it behaves the same way
[21:39] <seb128> I will watch for it
[21:39] <kenvandine> the only case i know of that it should do that is if you run from a checkout or something
[21:39] <seb128> I started it and closed quickly by wrong click and restarted immediatly
[21:39] <seb128> there might be a race or something
[21:39] <kenvandine> yeah... could be
[21:39] <kenvandine> ted never has bugs in his code :)
[21:39] <kenvandine> wish he was here to tease :)
[21:39] <seb128> anyway I will review the package for upload
[21:39] <seb128> thanks
[21:39] <kenvandine> thx
[21:39] <seb128> hehe
[21:40] <kenvandine> seb128, i had hoped ted would fix the mc5 issue in indicator-me with the split
[21:40] <seb128> do you know if anybody plan to fix the mc5 issue for alpha2?
[21:40] <kenvandine> maybe i will look at it again tonight
[21:40] <seb128> it's visible
[21:40] <seb128> the menu is useless right now
[21:40] <kenvandine> let me see if it is something obvious
[21:40] <seb128> we can live with it for an alpha it's not end of world
[21:40] <seb128> ok thanks
[21:41] <kenvandine> it has been like this for a couple weeks already though
[21:41] <kenvandine> in indicator-session-applet
[21:41] <seb128> ok
[21:41] <seb128> I use pidgin
[21:41] <kenvandine> hehe :)
[21:41] <kenvandine> ok, i'll see what i can do
[21:41] <seb128> I just switched back to trying empathy this week
[21:41] <seb128> I might stay with it
[21:41] <seb128> though it has already failed me
[21:41] <kenvandine> i also just noticed i am not getting notifications on song change from rb
[21:41] <seb128> I add to start pidgin because a friend asked why I was not accepting a file transfert
[21:42] <seb128> which I never received in empathy
[21:42] <kenvandine> i suspect it might be related to appindicator
[21:42] <seb128> somebody opened a bug about the song thing today I think
[21:44] <seb128> bug #498588 too
[21:44] <chrisccoulson> good evening everyone
[21:44] <seb128> there is something weird there
[21:44] <seb128> "** (rhythmbox:3253): WARNING **: Unable to create Ayatana Watcher proxy!  Could not get owner of name 'org.ayatana.indicator.application': no such name"
[21:44] <seb128> I need to try what happens with rhythmbox if you don't have the indicators installed too
[21:44] <seb128> hey chrisccoulson
[21:44] <seb128> how are you?
[21:45] <seb128> did you manage to avoid traffic tonight?
[21:45] <chrisccoulson> seb128 - yeah, good thanks
[21:45] <chrisccoulson> i got home in normal time tonight :)
[21:48] <seb128> so who wants to do some updates?
[21:48] <seb128> 2.29.5 tarballs are there
[21:48] <seb128> tedg, !
[21:48] <tedg> Oh no.
[21:48] <seb128> oh, robert_ancell
[21:48] <tedg> :)
[21:48] <seb128> happy new year
[21:49] <seb128> tedg, indicator-me is not mc5 friendly apparently now
[21:49] <seb128> it works fine with pidgin though
[21:49] <seb128> tedg, is that something you think you will fix for alpha2? ;-)
[21:49] <robert_ancell> seb128, hey, hope you had a good holiday!
[21:49] <seb128> robert_ancell, excellent thanks!
[21:49] <seb128> robert_ancell, I checked emails 3 times in 2 weeks and that's about it for work things
[21:49] <tedg> seb128: Hmm, really?  It should now be using libtelepathy...
[21:49] <seb128> robert_ancell, got pretty nice and relaxing holidays
[21:49] <kenvandine> seb128, none of the rb notification code gets hit if HAVE_APP_INDICATOR is defined
[21:50] <kenvandine> tedg, remember we talked about this before xmas?
[21:50] <kenvandine> it works if you reload the applet after mc5 starts
[21:50] <seb128> tedg, does it work for you?
[21:50] <tedg> kenvandine: No, I don't remember :)
[21:50] <seb128> kenvandine, btw want to do the empathy update?
[21:50] <tedg> seb128: I'm still using Pidgin :)
[21:50] <seb128> tedg, me too ;-)
[21:51] <seb128> tedg, but I'm trying empathy this week
[21:51] <kenvandine> seb128, sure
[21:51] <seb128> to see how it is now
[21:51] <seb128> kenvandine, cool thanks!
[21:51] <kenvandine> tedg, it doesn't monitor dbus for the name change properly
[21:51] <kenvandine> like if the interface isn't up yet, it doesn't monitor it
[21:51] <kenvandine> if you reload the applet after starting empathy, it monitors it just fine
[21:52] <tedg> kenvandine: Hmm, okay.  I'll look into that.
[21:52] <kenvandine> tedg, thx
[21:52] <kenvandine> tedg, i might look at it in a few minutes :)
[21:52] <kenvandine> see if i can easily fix it for a2
[21:52] <kenvandine> tedg, any word on the mono bindings?
[21:53] <tedg> kenvandine: No, I talked to DBO about it for a minute.  He thinks he knows how to fix it.
[21:53]  * kenvandine looks at the clock
[21:54] <tedg> kenvandine: Are you guys seriously freezing the whole archive for 3 days?
[21:54] <kenvandine> yeah...
[21:54] <seb128> tedg, alpha are soft freezes
[21:54] <kenvandine> seb128, sometime tomorrow morning right?
[21:55] <seb128> but uploading is often not a good idea, it should be limited to alpha blockers
[21:55] <seb128> kenvandine, yes, they usually start building CDs around that time
[21:55] <seb128> doing small changes is often fine if they don't try to respin images
[21:56] <seb128> the archive has to be in a consistent state for that
[21:56] <seb128> let's see that bug fixes any time tomorrow should be ok
[21:56] <seb128> we just have to make sure they are not building images before uploading
[21:56] <robert_ancell> seb128, have you seen this gtk+ bug: https://bugzilla.gnome.org/show_bug.cgi?id=606143
[21:56] <seb128> ie spot the right time for the upload
[21:57] <seb128> robert_ancell, now I did
[21:57] <seb128> robert_ancell, they just rolled 2.29.3
[21:57] <seb128> I will sync when Debian updates
[21:57] <seb128> slomo is quick usually
[21:57] <seb128> so probably tomorrow morning european time
[21:58] <robert_ancell> seb128, just wondering if it should be backported
[21:58] <seb128> is it an issue in karmic?
[21:59] <baptistemm> good night everyone
[22:00] <seb128> 'night baptistemm
[22:00] <robert_ancell> report says gtk+ 2.18, Ubuntu 9.10
[22:00] <baptistemm> bye
[22:00] <seb128> robert_ancell, hum ok, seems worth a stable update to me yes
[22:00] <seb128> robert_ancell, what do you think?
[22:01] <robert_ancell> seb128, I'd say because it can crash X and the fix is one missing unref then yes.  I don't know if other applications can trigger it
[22:01] <seb128> do you want to work on it?
[22:02] <seb128> or should I add that to my list?
[22:02] <seb128> I hope you had good holidays
[22:02] <seb128> this new year seems to start as a busy one ;-)
[22:03] <seb128> robert_ancell, btw on what do you plan to focus now? oem work I guess?
[22:03] <robert_ancell> seb128, please add to your list if you can (and subscribe me to the bug).  I've got quite a bit to catch up on
[22:03] <seb128> robert_ancell, will you have some time for GNOME updates or login speed tasks?
[22:03] <robert_ancell> seb128, yes oem - I'm finding myself already too easily distracted with desktop things
[22:03] <seb128> robert_ancell, not that we need you for something special, just trying to know what to expect
[22:03] <seb128> ok
[22:04] <seb128> do you come a the distro sprint btw?
[22:04] <seb128> I guess not?
[22:04] <robert_ancell> seb128, at the moment I'm just working on the gdm stuff for dx.  Not coming to sprint :(
[22:04] <seb128> ok, sort of what I was expect
[22:04] <seb128> good luck for the gdm work!
[22:05] <seb128> expecting
[22:05] <robert_ancell> seb128, thanks
[22:10] <chrisccoulson> hey robert_ancell
[22:11] <chrisccoulson> it's easy to get distracted with desktop things ;)
[22:11] <robert_ancell> chrisccoulson, hey
[22:38] <robert_ancell> chrisccoulson, what was the result of the gnome-session delay investigation?
[22:39] <chrisccoulson> robert_ancell - mainly blocking on the gconf database being parsed, but also some delays starting DK-Power
[22:39] <robert_ancell> chrisccoulson, was there anything we can do about it?
[22:40] <chrisccoulson> robert_ancell - there are some packages in http://people.ubuntu.com/~chrisccoulson/desktop-startup-speed/
[22:40] <chrisccoulson> those improve the situation, but are quite experimental at the moment
[22:40] <chrisccoulson> we fixed the DK-Power delay already
[22:41] <robert_ancell> chrisccoulson, thanks, looking for things that can be backported safely to karmic for oem builds
[22:42] <chrisccoulson> for production use?
[22:43] <robert_ancell> chrisccoulson, ye
[22:43] <robert_ancell> s
[22:45] <chrisccoulson> robert_ancell - these patches would probably need a bit more testing yet. and they would also benefit from investigating what takes seahorse-daemon so long, as that seems to be the longest path in the initialization phase with these changes now
[23:05] <chrisccoulson> seb128 - i've got a fix for bug 505789 now, but the fix will only work in karmic for now due to a xorg regression in lucid. i'm not sure whether to upload to both lucid and karmic-proposed, or just karmic-proposed, or do i have to delay the SRU until it can be fixed properly in lucid?
[23:05] <seb128> just karmic sru
[23:05] <chrisccoulson> seb128 - thanks
[23:08] <seb128> np
[23:20] <geser> robert_ancell: Hi, as you did the recent uploads of clutter-gtk, have you time to review bug #498817?
[23:25] <robert_ancell> geser, looking...
[23:29] <geser> robert_ancell: the problem is that debian packaged clutter-gtk 0.10 as clutter-gtk-0.10 and we synced it and have now two source packages trying to build the same binary packages and the Debian one wins as it has a higher version number, so I tried to apply our changes on clutter-gtk to clutter-gtk-0.10 (so further builds of clutter-gtk won't fail with "Failed to upload")
[23:31] <robert_ancell> seb128, you there?  how do we remove clutter-gtk from the archive?
[23:32] <seb128> robert_ancell, open a bug asking for that and subscribe ubuntu-archive to it
[23:32] <robert_ancell> seb128, ok
[23:33] <geser> I planned to do that once the Ubuntu delta got applied to clutter-gtk-0.10 (else gir1.0-clutter-gtk-0.10 vanishes)
[23:35] <robert_ancell> hmm, is there a way I can just click to make the merge happen?
[23:38] <geser> someone with upload rights needs to sponsor it
[23:38] <robert_ancell> I guess I have to make a new clutter-gtk-0.10 repository.  Doing it now...
[23:49] <robert_ancell> geser, thanks for that - it is now uploaded
[23:49] <geser> thanks for sponsoring