=== asac_ is now known as asac [06:58] Hello everyone, who do I need to speak to about Lucid CD contents? [07:25] no one? [07:30] good morning o/ [07:44] hi [07:44] morning oni [07:44] anyone tryed to use 9.10 on intel i5-clarkdale [07:45] it is booting fine but when gnome starts in suddenly hangs any idea? [07:48] 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] in #ubuntu nobody could help so i tryed here [07:49] oni: you didn't find anything related on LP or on ubuntuforums? [07:50] no i think clarkdale is a bit to new [07:50] maybe disabling 3D acceleration on the driver is a start. I have no other clue, sorry :/ [07:51] ok thanks i will try it [07:57] 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] whole page of info, including bug reports [08:00] lot of it not specific to ubuntu-branded - but definitely linux hits [08:02] my google(german) just finds reviews [08:03] try putting it in this way in a search window - "ubuntu + intel i5-clarkdale" without the quote marks [08:04] thats exactly what your link is doing [08:06] may i should put a detailt bug report to LP [08:10] join #quickly [08:10] hey rickspencer3 :) [08:10] didrocks, good morning, welcome to the desktop team!! [08:10] thanks a lot rickspencer3 :) [08:14] 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] oni: maybe you will need to try that, after disabling 3D acceleration, as didrocks advised above. [08:17] these posts are about the "old" i5 series [08:21] oni: no problem - then recommend do as suggested, and if nothing works, file a detailed bug report then [08:22] ok thanks [08:39] good morning there [08:39] hey seb128, how are you? [08:39] hey chrisccoulson_g1, it's monday morning and I'm not fully awake yet but good I think [08:39] what about you? [08:40] yeah, I'm good thanks. but stuck in a long queue of traffic in my car at the moment [08:41] oh :-( [08:41] still due to the winter weather? [08:42] I'm not too sure yet. I think there must have been an accident somewhere on my route [08:42] the weather isn't too bad now though [08:43] hello [08:43] hey baptistemm [08:43] chrisccoulson_g1, did you have any chance to look at g-c-c yet? [08:44] it should be rebuilt for tomorrow if we want to get the libgnome-desktop soname transition done for alpha2 [08:44] seb128 - I did it last night, and pushed to bzr [08:45] nice [08:45] any reason you didn't upload? [08:45] I haven't had a chance to make sure everything still works though [08:45] gcc is in desktop-core package set, so I can't upload [08:46] oh ok [08:46] if there is no breakage that's ok nowadays since g-c-c is only capplets [08:46] g-s-d is the session visible component [08:46] but I will give it a try later, thanks [08:46] I'm getting coffee first! [08:47] coffee sounds good! [08:47] hi seb128 [08:48] salut rickspencer3 [08:48] comment ça va ? [08:48] bien arrivé en France ? [08:49] bon [08:49] uh, don't know "yesterday" :( [08:49] oops, running out of power [08:49] * rickspencer3 runs to fnac to get a covnerter [08:49] "hier" [08:50] see you later! [08:50] I don't think not having a ground plug is an issue btw [08:51] davidbarth, hey, I told you that upload on friday was not a good thing ;-) [08:52] rickspencer3: see you later [08:52] I had to do fixing on saturday evening since things got screwed and all indicators were just crashing [08:52] bbiab [08:53] seb128: what happened? [08:53] hey chrisccoulson_g1 and baptistemm [08:53] * davidbarth reads up the log [08:59] davidbarth, new libdbusmenu-gk required new libdbusmenu-glib without saying so [08:59] davidbarth, and the new libdbusmenu-glib used a Breaks on indicators packages that need an update [08:59] hey didrocks, how are you? [09:00] davidbarth, which leaded to have the gtk version update and not the glib one and things crashing on lack of symbols [09:00] I wish I had got some coffee in my car [09:01] seb128: well, i told kenvandine that you did not recommend uploads on Friday, so what happened? [09:01] he did upload anyway [09:01] and things broke [09:01] anyway no real issue I sorted that [09:01] seb128: sure, but sorry for the issue [09:02] 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] seb128: ok, i'll try to clarify that during our integration call today [09:04] davidbarth, don't bother that's a distro issue, I will talk to kenvandine when he's around [09:04] nothing your team did wrong [09:04] out of delays tarball to friday which leaded to the conflict ;-) [09:04] but that happens [09:05] chrisccoulson_g1: fine thanks. Concerning the coffee, I'm sure you'll take some in a bottle for the return path :) [09:07] didrocks - yeah, I think I need to invest in a flask for coffee [09:08] I'm tempted to turn around, I've only moved 1 mile in the last hour [09:08] you can get out? [09:08] or you are stucked on a one way road? [09:09] hum, too bad… good luck :/ [09:09] seb128 - fortunately, its not 1 way. I could turn around if I don't move much soon [09:09] that's something [09:36] cassidy, hey [09:36] cassidy, bug #399039, do you know if that will be backport to telepathy-gabble 0.8? [09:36] Launchpad bug 399039 in empathy "Typing notification in empathy doesn't work for XMPP (google talk and jabber)" [Low,Triaged] https://launchpad.net/bugs/399039 [09:37] or if 0.9 is what we should use in lucid? [09:39] wb rickspencer3 [09:39] did you found what you needed? [09:39] thanks seb128 [09:39] seb128, yes [09:39] people in Paris are quite helpful so far [09:39] despite that I have the communication powers of a chimp here [09:39] you seem to be surprised :) [09:40] didrocks, not surprised [09:40] didrocks, did you get onto wiki.canonical yet? [09:41] rickspencer3: no, Alice sent me an email and I told her I've still no access to the wiki [09:41] hmmm' [09:41] well, you are on irc.canonical [09:41] so go to #rt [09:41] I'll meet you there [09:44] rickspencer3, communication: it's a good way to measure your french skills and to learn some extra bits too ;-) [09:44] seb128, yup [09:44] I still can't parse anything anyone says to me [09:44] but occasionally vocabulary words pop [09:45] or I'll hear someone say something I understand, but never to me ;) [09:45] rickspencer3: you're already presenting you in French "Bonjour, je m'appelle…". I think this is well appreciated :-) [09:46] didrocks, right, then they reply in French, and I look totally confused .. and they say "are you speaking English?" [09:46] ;) [09:46] ahah :) [09:46] hehe ;-) [09:47] I can say "merci" as well [09:47] I think also appreciated [09:47] right [09:47] and d'accord ;) [09:47] and chouette? :-) [09:48] lol [10:15] didrocks, want to come into town and meet up for some lunch? [10:15] re [10:15] I'm getting some wifi troubles recently [10:15] I'm wondering if that the lucid driver or the laptop card having issues === seb128_ is now known as seb128 [10:16] seb128, I think we should probably switch to 0.9 for Lucid yeah [10:16] rickspencer3: yes, what time and where is the best for you? [10:17] seb128, I'll ask to the Gabble guys what they think and I'll let you know [10:17] didrocks, any time starting now [10:18] rickspencer3: let me check for trains [10:18] cassidy, can you check if we will get a 1.0 or 0.9 stable on schedule? [10:20] oki [10:20] 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] didrocks, poifect [10:22] cassidy, ok thanks [10:22] cassidy, no hurry! [10:22] sure [10:32] rickspencer3: leaving now. I'll find you at the hotel lobby [10:33] didrocks, great [10:33] bon voyage [10:45] excellent, I've finally arrive at work! [10:45] it only took me 3 hours! [10:45] chrisccoulson_g1, took you only 3 hours? [10:45] lol [10:45] * seb128 hugs chrisccoulson_g1 [10:45] not the best week to start the week [10:46] * chrisccoulson_g1 hugs seb128 [10:46] I'm quite tired now - I've normally had 3 coffees by now [10:47] hehe [10:48] davidbarth, do you know what's going on with the indicator-me options? [10:48] like im status, etc [10:48] is that a new source? is it expected to land this week? [10:48] the current session applet dropped those [11:01] seb128: atm the indicator-me code contains what was in the status sub-menu of the session menu [11:01] seb128: it will be enhanced to support more of the features that are now defined (and approved) in the "me menu" spec [11:02] what is indicator-me? a new source? [11:02] will it be available before beta2? [11:02] seb128: the me menu is part of the a2 delivery [11:02] alpha2 I mean [11:02] ok [11:02] seb128: it's a new source yes, with a separate package [11:02] it's not there atm and freeze is tomorrow [11:02] I guess it's rather a ted and kenvandine's question though [11:02] I will sort that with them when they are around [11:02] seb128: so, that was part of the "don't release of friday" [11:02] seb128: or i don't know [11:03] the point I tried to make is "don't make half baked broken changes before running away for the weekend" [11:03] 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] ie either do everything in a tested way or wait monday ;-) [11:03] thanks [11:04] I will sort that with ken and ted [11:20] seb128 - i wasn't the last person to arrive at work ;) [11:20] someone else has just arrived now [11:20] lol [11:20] in time for lunch! [11:20] oh, not yet, it's one hour earlier for you guys [11:23] heh, i'm definately ready for lunch now [12:38] seb128, the chat state bug has been fixed in 0.8 [12:39] cassidy, oh ok, the GNOME bug comments stated in didn't, thanks [12:39] It did now. We just backported the patch :) Adding a comment [12:40] thank you! [12:40] so you recommend staying on 0.8? [12:41] for now yes. I think 0.9 still have few regressions [12:41] we should hopefully get rid of them soon [12:41] ok thanks === MacSlow is now known as MacSlow|lunch [13:02] seb128: hi [13:02] re [13:02] hey mvo [13:03] seb128: a quick question, we used to have a "text" option on boot that prevetned gdm from starting [13:03] I should sort that autoconnect and ip change issue [13:03] it tends to make my client bounce on session start [13:03] seb128: this seems to be gone again with the convert to a job file? [13:03] it should not [13:04] so that should still work? I have a look then [13:05] case "${ARG}" in [13:05] text|-s|s|S|single) [13:05] exit 0 [13:05] mvo, ^ that's the upstart job [13:05] do [13:06] ups [13:06] wehre [13:06] # Check kernel command-line for inhibitors [13:06] for ARG in $(cat /proc/cmdline) [13:06] seb128: thanks. odd. I double check, maybe I did a typo or something with grub was odd [13:07] or maybe the job file is buggy in some way [13:07] but it has not been intentionally dropped [13:10] hey pitti, are you around? [13:11] chrisccoulson, he was around but stopped IRC, he said it's not stable enough in the train [13:12] but he reads scrollback every now and then apparently [13:12] seb128 - thanks [13:12] so better to just ask your question [13:12] seb128 - could you add a karmic task to bug 505789? [13:12] Launchpad bug 505789 in gnome-screensaver "gnome-screensaver-command -p triggers keyboard event" [High,Confirmed] https://launchpad.net/bugs/505789 [13:12] it seems to be a regression caused by a previous SRU [13:12] you can probably do that no? did you try? [13:13] seb128 - i just tried that, but i can't do it [13:14] chrisccoulson, you managed to suggest it for nomination but not nominate it right [13:14] chrisccoulson, I've accepted it now [13:15] seb128 - thanks [13:15] np [13:58] hey tedg [13:59] Good morning seb128 [13:59] Looks like some work to do from Friday's upload :( [13:59] yeah [13:59] first we don't have im actions anymore now [14:00] but that apparently waits on a new source? [14:00] Yes, it was split out into the "indicator-me" package. [14:00] tedg, the rhythmbox menu looks weird now, previous and next got broken icons [14:00] and the power icon on the shutdown line is weird too, especially shifted [14:00] 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] GTK does that internally, but we need to do it somewhat externally. [14:01] ok [14:01] 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] tedg, you guys screwed the update by not update the shlibs version for libdbusmenu btw [14:01] There isn't enough spacing there, but that's a simpler fix :) [14:02] tedg, libdbusmenu-glib got blocked while -gtk got updated which leaded to crashland [14:02] So -gtk should depend on -glib? (I saw the bug, but I'm not sure I understood) [14:03] it does use symbols from it since it was crashing on a not found symbol there [14:03] so yes, it should depends on the version which has all the symbols it needs [14:03] that's done usually by updating the shlibs number in the package when api are added [14:04] the current package has a shlib version for -gtk in its rules [14:04] but none for -glib [14:04] Why wouldn't we have -gtk depend on the exact version, as they'll always get updated together? [14:04] they didn't [14:04] which leaded to crash land [14:04] they are different binary [14:05] somebody made the new -glib Breaks the old indicators [14:05] which made -glib in hold until the indicators were updated [14:05] but nothing blocked the -gtk update [14:05] which leaded to new -gtk installed with all -glib [14:05] and the version mismatch doesn't work so well [14:05] Okay, so in the libdbusmenu-gtk0 should have "Depends: libdbusmenu-glib (= ${binary:Version}) [14:05] >= should do [14:05] but yes [14:06] the shlibs system should take care of such depends [14:06] if you use a shlib [14:06] "shlib" means "the version required to have the current complete api set" [14:06] But since they're built together, wouldn't it not go through that? [14:07] the debian tools add a depends on the lib by going through ldd list basically [14:07] ldd library.so [14:07] and it add the package containing the lib (>= versin_shlib) [14:07] in this case you get -gtk depends on -glib (>= 0) [14:07] since you didn't set a shlib [14:08] it also means that right now that something building against libdbusmenu-glib0 will get a depends on it with no version [14:09] shlibs is a trick to make sure you get a least the api you built against [14:09] it doesn't do symbol granularity [14:09] seb128, eww... [14:09] it just says "I built against version of this lib so I will depends on that version because I know it's working" [14:10] you can't know that version n-1 would work too [14:10] slightly tweaked to make that "depends on the version which has the current api" [14:10] Do you know a good package to look at to see how to set it up? [14:11] ie if the api has no addition between 0.2 and 0.3 the shlib stays to 0.2 [14:11] libdbusmenu? [14:11] as said the rules has the line which set it for -gtk [14:11] but not for -glib [14:11] you need to add the same line for that one [14:11] Ah, I see. [14:11] and make sure you update the versions when you add things to the api [14:12] or use .symbols [14:12] which is the modern way [14:12] it lists all symbols and the version they have been added to [14:12] so you know from the symbols you use what version you need [14:13] Is there a tool to do that, or by hand? [14:14] dpkg-gensymbols is the tools used for those [14:14] once set up you don't have to do anything [14:14] typically build will break when it run into symbols not listed [14:14] and give you a diff with those listed as being added in the version you try to build [14:14] so you just apply the diff and rebuild [14:15] no need to do history [14:15] you can start by making a list of all symbols and say they have been added in the current version [14:15] and work incremental from there [14:16] kenvandine, hey, can you summarize where we stand now, what needs sponsoring, seeding, adding, etc? [14:16] kenvandine, the alpha2 freeze is tomorrow [14:16] and pitti is travelling today which somewhat limit you main promotion, newing etc speed [14:17] seb128, cjwatson fixed the upload perms [14:17] i got that stuff uploaded [14:17] only current issue i know of is jockey [14:17] which one? [14:17] there is no im menu anymore in current lucid [14:17] won't build, because of a regression in a kde lib [14:18] that's a new source no? [14:18] has that been uploaded? [14:18] yeah [14:18] one sec [14:18] pitti and i traded a couple emails this morning [14:18] kenvandine, btw next time avoid disruptive change on friday evening if you can, I told davidbarth to not to it... [14:18] ok [14:19] pykdeuic4 calls kde_i18n_string.escape() which doesn't exist any more [14:19] http://launchpadlibrarian.net/37627198/buildlog_ubuntu-lucid-i386.jockey_0.5.5-0ubuntu6_FAILEDTOBUILD.txt.gz [14:19] oh, you speak about jockey [14:19] good to know but I think if it's not in alpha2 that's ok [14:19] and the mono bindings to libappindicator are broken [14:19] I'm rather concerned about the new source [14:19] with the im status, etc [14:19] ah, just indicator-me then [14:20] yes [14:20] which isn't uploaded yet [14:20] as said before freeze is tomorrow [14:20] i need you for that :) [14:20] and our main promotion, newing etc will not be as efficient with pitti travelling [14:20] is it ready to be sponsored? [14:20] i think so, let me look at it one more time [14:20] thanks [14:22] tedg, ok... after updating this morning and rebooting the app indicator is working again [14:23] but not for mono [14:23] tedg, we really need that fixed asap... [14:23] * kenvandine files a bug [14:25] seb128, lp:~ubuntu-desktop/indicator-me/ubuntu is ready to be sponsored [14:25] kenvandine, looking [14:25] kenvandine: No one uses Mono ;) [14:26] kenvandine: Did you file a bug? [14:26] tedg in a troll mood today? ;-) [14:26] seb128: No, I'm applying for moderator on boycottnovell.com ;) [14:27] heh [14:28] tedg, why do you distribute a LGPL copy in the indicator-me source if there is only GPL code there? [14:28] kenvandine, ^ [14:28] seb128: Uhm, good question? :) [14:29] tedg, bug 505923 [14:29] Launchpad bug 505923 in indicator-application "mono bindings doesn't show indicator" [Undecided,New] https://launchpad.net/bugs/505923 [14:29] tedg, please remove the crufty license file :) [14:29] 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] 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] it's a new source from dxteam and should be fairly trivial [14:31] I just had a quick look and it seems ok [14:31] seb128: Looking [14:31] lool, thanks [14:31] lool, and it isn't really much "new" code... just split out for indicator-session [14:31] jcastro was rather disappointed it wasn't all the "bling" we saw at UDS :) [14:32] 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] kenvandine: I don't know, it seems like they should have been regenerated in the build. [14:33] kenvandine: Did you run Tomboy on the command line? [14:33] kenvandine: I'm curious if the error means something more to you :) [14:33] (tomboy:24379): GLib-GObject-WARNING **: IA__g_object_set_property: object class `AppIndicator' has no property named `PROP_STATUS_S' [14:33] tedg, are the broken previous and next icons in rhythmbox a rhythmbox patch issue? [14:33] that isn't a new message [14:34] seb128: They're a libappindicator issue. [14:34] tedg, ok thanks [14:34] 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] kenvandine: Yeah, but that's why it's broken now :) It's not setting the status. [14:34] does that need to be in the bindings or does the tomboy patch need to do that? [14:34] kenvandine: Before we ignored the status, so it didn't matter. Now we're listening to applications :) [14:35] oh, nice to see that fixed [14:35] it means I could do the nautilus change now ;-) [14:35] 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] tedg: POLKIT_REQUIRED_VERSION=0.92 in configure.ac isn't used [14:36] tedg, but does tomboy need to set that? [14:36] lool: Yup. Deleted it just now. :) [14:36] tedg, i am just wondering if we need to change the tomboy patch or mono bindings in libappindicator :) [14:36] kenvandine: Yes. But, I'm not sure how. If it's part of the "new" function or if it's explicit. [14:36] what is the C function? [14:36] 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] that should be 0.2.0... [14:37] 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] 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] tedg, app_indicator_set_status? [14:38] indicator.Status = Status.Active; [14:38] lool: Oh, cool. I didn't realize they do that now. [14:38] It has been so forever but apparently not a lot of people know [14:41] tedg, seb128: uploaded [14:41] lool, thanks [14:41] * seb128 hugs lool [14:42] lool: Thanks, I've got a branch with those comments in it. [14:43] tedg: Also, 4-spaces tabs are a crime!! ;-) [14:43] indicator >= $INDICATOR_REQUIRED_VERSION [14:43] >------->------->------->------->------->------- dbusmenu-gtk >= $DBUSMENUGTK_REQUIRED_VERSION) [14:49] 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] tedg, kenvandine: indicator-me newed to main [14:50] thx [14:51] seb128: Thanks! [14:51] thanks to lool who sponsored it so I can NEW it now ;-) [14:51] NB: I didn't test build it (lalala) [14:52] But you guys write perfect code anyway [14:52] it's in a ppa so it should be build tested [14:52] i built it in pbuilder too [14:52] Yeah, but I'm always scared of the bzr bd -S export thing with the tarball; it should just work, but yaknow [14:53] It just feels scary ;) [14:53] james_w: It seems to be merge@code.launchpad.net -- haven't gotten an error yet :) [14:53]