[00:00] bryce: looking into it today, I'm not 100% sure about the blacklisting as I haven't worked on that previously [00:01] ok no prob, I can send mvo a wishlist bug, should be straightforward [00:15] hey bryce [00:16] bryce: care to take a quick look at bug #383396 and see if you recognize anything obvious in the logs? I /just/ did an updated on this machine today and it started happening [00:16] Launchpad bug 383396 in xorg "X crashes when screensaver activates" [Undecided,New] https://launchpad.net/bugs/383396 [00:21] bryce: mvo already un-blacklisted at least GM965 [00:21] in bzr === asac_ is now known as asac [01:42] Hmm. Since the gtk+2.0 update, ssh-askpass is now reporting 'gdk_x11_atom_to_xatom_for_display: assertion tom != GDK_NONE' failed' [01:43] s/tom/`atom/ (my screen session ate the `a) === bluesmoke_ is now known as Amaranth === ajmitch_ is now known as ajmitch [08:30] morning everyone ! [08:41] pitti - do you think bug 361689 is worth a SRU? some reporters have resorted to installing the karmic hal binary with its karmic dependencies (libblkid) on their jaunty systems, causing issues for them (and lots of bug noise) [08:41] Launchpad bug 361689 in hal "hald crashed with SIGSEGV in hotplug_event_begin_add_blockdev when assembling mdraid devices" [Medium,Fix released] https://launchpad.net/bugs/361689 [08:41] hey huats [08:41] chrisccoulson: if there's someone who would test the update, sure [08:41] hello pitti ! [08:42] there seems to be plenty of people willing to test the update. if you think its SRU worthy, would you mind adding a jaunty task (and assigning it to me), and I'll work on that [08:43] i dont think that code changed so the patch should easily port to the jaunty version [08:48] chrisccoulson: no, hal doesn't change a lot any more [08:49] chrisccoulson: done, and marked as regression [08:49] pitti - thanks:) [09:03] hi all [09:05] seb128: pitti: What needs to be done to get mono synced to the debian unstable version? [09:05] robert_ancell: use requestsync [09:05] and explain why our changes can be dropped [09:05] hey robert_ancell [09:05] there sure are a lot of little ubuntu tools installed :) [09:06] that is in ubuntu-dev-tools [09:06] I'm not sure what the changes are but I was looking at MOM and it is a candidate for updating [09:06] hey pitti [09:07] also, why is only a subset of packages shown in MOM? [09:07] robert_ancell: you might want to talk to the guy who were doing the mono update... They have done quite a good work lately so I think they might help you [09:07] robert_ancell: right, talk to directhex about this [09:08] robert_ancell: it only shows packages which Ubuntu has modified [09:09] huats: some of the previous releases were done by "Ubuntu Archive Auto-Sync" - aside from that I couldn't tell if there is a standard mono packager [09:14] robert_ancell: we do autosync for packages without changes regularly [09:14] ie nothing required for those [09:14] robert_ancell: ok [09:14] seb128: so is mono still on the autosync queue. Or did the last change knock it off that? [09:15] robert_ancell: mono | 2.0.1-6ubuntu1 | http://archive.ubuntu.com karmic/main Sources [09:15] is has a "ubuntu1" version [09:15] which means it has ubuntu changes, needs to be done manually [09:16] seb128: the change is "to try and bring Ubuntu into line with Debian". I'm guessing that has been applied to the unstable version. If that is the case do I just request a sync? [09:17] try not guessing but checking but it that's the case yes ;-) [09:18] ie, it could have been applied to their package vcs and not uploaded [09:18] also you can try pinging directhex about it, debian seems to have 2.4 now, ie a new version, just to make sure they are not planning a transition or something [09:18] seb128: I was guessing but I hadn't investigated yet :) [09:19] ok, who is directhex? [09:19] robert_ancell: in #ubuntu-devel [09:21] robert_ancell: Jo Shield, he works on mono in debian and ubuntu [09:21] thanks [09:22] robert_ancell: when you do work on a bug don't forget to change it back to new or confirmed [09:22] robert_ancell: so it's listed on the sponsoring queue [09:22] "I assume that common has to also be versioned to have both installable? It wasn't previously." [09:22] no, we usually don't bother [09:23] the -common usually have translations and documentation [09:23] so having the new version doesn't break the old library version [09:23] seb128: ah, I wasn't sure about that. I'll do that in future [09:23] we really aim at having the old library installed for the time we rebuild everything [09:24] robert_ancell: same for the -dev package, no need to version it [09:25] regarding gdl - if you have both libgdl-1-0 and libgdl-1-2 installed they both depend on libgdl-1-common (= ${source:Version}} [09:25] isn't that impossible? [09:26] we usually use >= ${source:Version} [09:27] ok, well the existing package has been built with '=' so what can we do? [09:27] screw libgdl [09:28] LOL [09:28] What situation is trying to install both libgdl-1-0 and libgdl-1-2? [09:28] the rdepends list is tiny, we can rebuild that in one publisher run [09:28] seb128: Not right now we can't, there's buildd queues since draining [09:28] StevenK: I was trying to take it as an example to explain why we rename binaries so that both lib versions are installable together [09:29] anyway [09:29] * StevenK picks on libuser0 and libuser1 for that. [09:29] Just don't think about the ld flags for that library [09:31] robert_ancell: anjuta gdl gnome-build gnome-python-extras gtranslator [09:31] that's the list of everything using it [09:32] so basically the transition will be short we don't need to have both installable [09:32] that's not the case when libwnck change soname for example [09:32] Both installable is a nice to have -- but can lead to interesting bugs [09:32] right [09:33] robert_ancell: ok, so your task for tomorrow, finish this gdl update (just rename the lib and the dbg) [09:33] ok [09:33] then make sure that gnome-build anjuta and gnome-python-extras build with the new version [09:33] so we can upload those in the same day [09:33] robert_ancell: If you have packaging questions during your workday, grab me [09:33] anjuta not being installable for a few is no issue [09:34] Like anyone uses anjuta [09:34] StevenK: sure, thanks [09:34] but gnome-python-extras should be working [09:35] robert_ancell: also could you have a look at merging gnome-control-center tomorrow? [09:35] * seb128 aways for a few minutes, brb [09:35] seb128: sure [09:40] Feedback requested regarding a user page for people with Compiz problems: https://wiki.ubuntu.com/VisualEffects [09:40] mvo: ^ [09:40] hello [09:41] hello [09:42] hey robert_ancell [09:45] robert_ancell: reading [09:54] robert_ancell: looks good, thanks! [09:55] seb128: could you please sync gnome-bluetooth from debian so we get get a new baseline for the changes crevette has in his suggested merge? [09:56] mvo: cool, now I have somewhere to reporters to :) [09:56] to push [09:56] :) [09:56] asac, you're assigned to care about bluetooth, or this is because it has tied relation with NM now? [09:56] crevette: well ... the spec is somewhat on my plate [09:57] pitti: should we rename gnome-control-center? The upstream is called that and it's more generic [09:57] crevette: we will see how well it works out [09:57] asac, gnome-bluetooth works nicely with bluetooth audio device now [09:57] I can connect to it and swith my audio to my bluetooth gateway [09:57] yeah thats why i want this in the archive. just think we should first sync and then upload just your notification change [09:58] crevette: does bluetooth-source also work with pulseaudio now in karmic? [09:58] robert_ancell: fine for me, especially if we merge it with Debian [09:58] so i can use my headset without messing with .asoundrc [09:58] ;) [09:58] I didn't tested source, but my audio gateway foes both, I sould certainly give a that a try [09:58] cool [09:59] pitti: weird, I'm not sure what Debian is doing. They have http://packages.debian.org/sid/gnome-control-center but no http://packages.qa.debian.org/g/gnome-control-center.html. Instead they have http://packages.qa.debian.org/c/control-center.html [09:59] crevette: what do you think about modems wrt bluetooth + wizards [09:59] pitti: duh, source vs binary... [09:59] crevette: shouldnt gnome-bluetooth provide the next step as well? e.g. binding DUN [09:59] re [10:00] robert_ancell: right, packages.qa is source package [10:00] asac: ok [10:00] seb128: thanks! [10:00] robert_ancell: it's already named gnome-control-center [10:00] it used to be called control-center [10:00] but we renamed it some cycles ago [10:01] seb128: right, so how can we convince debian this is a good idea? :) [10:01] do we care about the name they use? [10:02] Keybuk: why does gnome-control-center not show up in MoM? Is it because the Debian source package is called control-center? [10:02] seb128: ^ [10:02] robert_ancell: yes [10:02] robert_ancell: yes [10:02] asac, (I'm on phone) [10:03] Keybuk: can we get MoM to handle that? [10:03] robert_ancell: btw for gdl you probably need to rename the .install too [10:04] seb128: yes] [10:04] asac: synced [10:05] gratias [10:05] de nada [10:06] robert_ancell: the source package name appears all over the package [10:06] every import would be conflict-hell [10:06] so no [10:07] Keybuk: ok [10:08] crevette: any clue if the notification patch send upstream? [10:09] seb128: regarding libgdl-1-dev - does a -dev package _always_ point to the latest version? [10:10] hey seb128, any news from Pedro? [10:10] robert_ancell: usually ues [10:10] yes [10:10] robert_ancell: I will not say always, it gtk1.2 and gtk2 for example are all versioned [10:11] but that's when there is a reason to keep the old version available for build for a while [10:11] there we can count the rdepends on an hand so no need to bother [10:11] rodrigo_: no ... [10:17] do we use some special syntax/place for desktop specs in the ubuntu wiki? [10:17] asac: https://wiki.ubuntu.com/DesktopTeam/Specs/Karmic/FooBar [10:17] ah found DesktopTeam/Specs [10:17] great. [10:19] seb128: oh, I remember I have tomorrow off so I'll look at g-c-c on monday [10:19] cool, no hurry [10:20] I wanted to take a swap day tomorrow too but with this ubuflu I can as well work, I'm not feeling good enough to do outside activities etc [10:20] enjoy your weekend! [10:21] seb128: take a swap day on Monday thaen? [10:21] robert_ancell: enjoy the long weekend! [10:21] pitti: I will see how I feel but I think I will probably take next friday instead [10:22] cheers I will (going to Adelaide for the weekend) [10:23] asac, for the notification, I wondered the same question, perahps kenvandine would know [10:23] (on the phone) [10:24] see you all next week [10:41] hey thanks for the merge [10:56] would be nice to have https://fedoraproject.org/wiki/Features/Fingerprint [10:56] at lease fingerprint enrollment in about-me of gnome-cc [11:02] crevette: do you have any config using that? I though that was not a secure way to do authentification? [11:04] seb128, you're concerned that someone could enroll its fingerprint as another user? [11:04] no, I basically don't know about this thing and don't really care [11:04] :) [11:04] but the comments I read were saying that was not really a secure way to do authentification [11:05] neither I do, I did try fingerprint authentication with my laptop and it worked, I just thoughthaving it integrated in a graphical interface would be better. [12:10] hmmm, I would need to have a kernel module loaded for bluez in order to have a better experience for bluetooth like headser, how should I do? [12:10] should I put a modprobe in the init script? [12:38] crevette: dunno, maybe Keybuk does know about that though [12:38] seb128, thanks [12:38] pitti: there to speak about the new gdm and karmic? [12:38] hey seb128 [12:38] hey pitti ;-) [12:38] seb128: about to leave for lunch, but I can stall that for a bit [12:38] pitti: so I was wondering, if we upload now we will get no fusa nor guest session [12:38] crevette: what's the kernel module? [12:39] do we want to break those or wait until those are ported to upload? [12:39] Keybuk, uinput [12:39] pitti: no hurry [12:39] seb128: let's say I'd be more motivated to fix it if it gets broken :) [12:39] pitti: enjoy your lunch, we can discuss that later [12:39] seb128: (For guest session) [12:39] seb128: however, why does fusa get broken? I thought upstream gdm would have this? [12:40] Keybuk, apparently it makes buttons on bluetooth headset working [12:40] they have a fusa [12:40] seb128: of course we have to live with not having our modifications for a while, but *shrug* [12:40] but it's doesn't have the ubuntu changes [12:40] ie doesn't control the im status [12:40] and doesn't have the session actions [12:40] crevette: the driver is missing details about what hardware it works with [12:40] it just does user switching [12:40] oh, it's the uinput thing [12:40] sorry, I didn't even *read* the name of the module before running modinfo on it [12:40] seb128: right, that should be fine [12:41] seb128: I have no objection to breaking those changes [12:41] seb128: it'll encourage more people to contribute to getting them back :-P [12:41] pitti: ok, I guess we want to drop the gnome-panel patch dynamically removing menu items meanwhile then [12:41] otherwise no way to reboot, etc [12:41] seb128: that depended on the new fusa? [12:41] seb128: ah, indeed [12:41] pitti: thanks, I will work on that [12:41] * pitti hugs seb128, thanks! [12:41] pitti: well, the new fusa will not have session actions [12:41] right [12:42] I will probably get the current version ready in the ubuntu-desktop ppa and ask for some testing [12:42] crevette: one option is whatever talks to that driver is responsible for loading it [12:42] it falls into that tricky crack that things like devmapper sit in right now [12:42] pitti: I will work on that now, enjoy your lunch, I will ask you to test the gdm upgrade from the ppa later if that's ok [12:42] sure [12:42] and upload if I get some confirmation about it being ok [12:42] thanks [12:42] * seb128 hugs pitti [12:42] pitti: enjoy your lunch! [12:42] crevette: but since it's a "feature" it's almost at the level I say shouldn't be a module but built-in [12:42] * pitti will just finish his libgphoto udevification [12:44] Keybuk, I don't know for the policy about module (but if you have documentI can look at I willing to read it :), but I wanted to know how can I load them properly, can I use inti script for that? [12:44] crevette: add it to /etc/modules [12:44] but for the packaging? [12:45] crevette: /etc/modules is not a conffile, you can edit it [12:45] though obviously take care you don't add dups ;) [12:46] yeah, I'll look to another package to be inspired [13:28] crevette: did you see that asac synced gnome-bluetooth? Were there any additional changes that you wanted to be made over Debian? [13:29] Laney, yah I see, we need the notification patch from bluez-gnome which I already updated for the new code [13:29] I need to see with the author if the code if it worths sending it upstream [13:29] crevette: please make a debdiff against 2.27.5-1 then [13:29] yep [13:30] and send it to both Debian and upstream to see if we can sync straight in future [13:30] crevette Laney: thats ok. i wanted to get a new baseline in the archive first. now we can add the notification patch [13:30] asac: yeah sure, no worries [13:31] crevette: can you check if your diff.gz gives us a minimal debdiff still? [13:31] crevette: by the way, for a merge the best patch to submit is a debdiff between what Debian has and what you want to upload [13:31] and while doing that send patch upstream and debian [13:32] Laney, 2.27.5 was not in unstable yesterday [13:32] so I wasn unable to produce a debdiff [13:32] all fine ;) [13:32] (at least from my side) [13:32] it was uploaded on the 31st [13:32] unless it was NEW or something [13:33] hmm, I didn't see it in packages.debian.org [13:33] http://packages.qa.debian.org/g/gnome-bluetooth.html [13:33] it definitly was binary NEW ... cant remember if debian does that manually though [13:33] pts is the best [13:33] binary NEW is manual but usually fast [13:33] (afaik) [13:33] yeah. so it might have been stuck there for a it [13:33] bit [13:34] yeah [13:34] ok, got a meeting [13:34] I'll produce the debdiff tonight once I'll be at home [13:34] i'll sponsor the patch later if you get it done [13:34] bye bye [13:34] thx Laney === ember_ is now known as ember [14:25] tedg: :) eventually! [14:25] Mark__T: ? [14:27] tedg: I tried to ask you some things about indicator-applet, but you're always offline when I'm here. So I sent you a mail [14:27] Mark__T: Ah, downloading mail now... [14:29] tedg: It's kind of obsolete now, since I have a working xfce4-indicator-plugin here now: http://www.foresightlinux.org/hg/xfce/xfce4-indicator-plugin [14:31] Mark__T: Cool, any screenshots? [14:31] doesn't lookt that different from the original one [14:32] Can we convince kenvandine to package it for Xubuntu? ;) [14:32] hehe [14:32] pitti: have you all discussed Till's proposed SRU? [14:32] tedg: is 0.2 already in karmic? [14:32] tedg: I need to convince him to package 0.2 of i-a for fl in his spare time first .-P [14:33] rickspencer3: for changing gs->poppler in jaunty? only quickly, I asked him to start a discussion on the ML [14:33] kenvandine: I don't believe so, I've kept the packaging branch (local) up to date with the snapshots though. [14:33] okay [14:33] hey rickspencer3, kenvandine, tedg [14:33] kenvandine: Honestly, I'm a little confused on when that should go into Karmic. I don't consider it stable as of yet, but really, neither is most of karmic ;) [14:33] hey seb128 [14:33] hi seb128 [14:34] tedg: perhaps you can do a 0.2 release [14:34] and later 0.3, etc [14:34] seb128: Howdy! [14:34] tedg: i think the sooner the better [14:34] kenvandine: I was trying to make "0.1" Jaunty and "0.2" Karmic type of thing. Though, it seems like version numbers are kind of a problem... [14:34] tedg: I'm about to upload the new gdm to karmic today, do you plan to work on the fusa changes soon? ;-) [14:35] seb128: is that a hint? :-D [14:35] tedg: seems kind of arbitrary :) [14:35] tedg: perhaps 0.1.90 [14:35] no, just standard information ;-) [14:35] and build up to 0.2 [14:35] seb128: Heh, yes. But, I don't have it done today ;) [14:36] seb128: i have fixed up the indicator patch for empathy [14:36] tedg: not today, so for yesterday? ;-) [14:36] kenvandine: good! [14:36] Perhaps we should just version things by letter. So this release would be "k.0.1" or something like that. I'd probably make more sense. [14:36] seb128: making a couple improvements now [14:37] tedg: doesn't help other distros :) [14:37] tedg: Mark__T wants me to get 0.2 into foresight so he can package the xfce plugin for the indicator [14:37] kenvandine: Other distros? I've heard of those before ;) [14:37] hehe [14:38] hello Mark__T :) [14:39] tedg: more distros that use it makes the fdo thing easier [14:40] kenvandine: seb128: Is there any plan to propose indicator as GNOME external dep? === rickspencer3 is now known as rickspencer3-afk [14:40] that is more a tedg question, but afaik yes [14:41] more DEs usable with it is helping too I think [14:41] Mark__T: Yeah, I honestly think that DEs is more important for FDo than distros, but yes, both would be good. [14:41] kenvandine: seb128: To be honest I really think we need something for that kind of stuff, libnotify is just not enough. But I'm a bit worried by project maintained by distro $FOO that will never get really upstreamed and dies as quick as it is born [14:41] tedg: i think it is equal [14:42] Zdra: other distros do it :) [14:43] Zdra: GNOME external deps kinda have a chicken and egg problem, in that apps need to be using them before they usually get accepted, but many app maintainers don't want them until they're accepted as external deps. Hopefully I'll wow a bunch of app developers at GUADEC to use it, to seed that problem :) /me needs to work on talk... [14:43] kenvandine: note that I have nothing against indicator itself, I didn't look to it yet. I just think that such think MUST be discussed upstream early, otherwise the experience show that it dies very fast [14:44] Mark__T, stupid question : is it an svn, git, bzr you're using ? how can i grab the code please ? [14:44] tedg: even if it's not accepted, proposing it is good [14:44] tedg: kenvandine: http://picasaweb.google.com/mark.trompell/Xfce# [14:44] tedg: because it shows to everybody you are working on it, what you do, etc [14:44] and you get (hopefully) constructive critics [14:45] Sidi it's hg [14:45] and whats the magic command then please ? :/ [14:45] hg clone http://www.foresightlinux.org/hg/xfce/xfce4-indicator-plugin [14:45] thanks [14:45] Mark__T: Cool! [14:45] tedg: silently adding optional support to Empathy is not going to do the buzz needed to get people involved, IMO [14:46] Mark__T: excellent [14:47] hm, the icon doesn't scale if I change the panel size [14:47] Zdra: I promise, if you accept the Empathy patches, I won't be silent about it ;) [14:48] Mark__T, ask the XFCE guys about that, i think they use a particular xfce api [14:48] tedg: is there a chance to get claws and thunderbird to support it? [14:48] Zdra: i just updated the patch again [14:49] i think it should be good now [14:49] :) [14:49] Mark__T, for TB i suppose it'll be a bit of fight, but for claws why not ? Mark__T check the xubuntu spec for default mailing client btw [14:49] Zdra: criticism welcome [14:49] SiDi: there is a size changed callback, need to find out how to access that icon though [14:50] kenvandine: I'll try to find time to review, thanks for your work ;) [14:50] thanks for reviewing :) [14:50] * kenvandine considers removing pidgin from his laptop now [14:50] btw Mark__T, i know its a bit of trolling, but shouldnt you name it indicator-applet-xfce ? usually the xfce4-* names are for the upstream xfce packages [14:51] oh... yeah that jabber bug... damn [14:51] if it only would be better with irc [14:51] kenvandine: ubuntu jaunty has the needed deps for running your patch? [14:51] yes [14:51] great :) [14:51] i haven't tested it on jaunty... but it has everything [14:52] SiDi: I could probably create a goodie and make it upstream, but for know I want hg instead of svn :-) [14:52] Mark__T, they use git now anyways ;p [14:52] SiDi: not yet, but they are close [14:53] but if you can get it upstream then go for it :) === rickspencer3-afk is now known as rickspencer3 [14:53] SiDi: it was so easy with hg serve to just create a package to install and test [14:54] Mark__T, dunno, never used it :/ [14:55] hg serve on my box and r.addMercurialSnapshot('http:/localhost:8000') in my conary recipe :) [14:56] hehe [14:56] kenvandine: I can't expect from you to do that :-P [14:57] SiDi: anyway the plan always was to get it to the goodies at one point [15:02] :) [15:11] kenvandine, are you the one who wrote the notification patch for bluez-gnome? [15:11] bratcshe wrote it, i might have cleaned it up a little [15:11] why? [15:12] because I had to port it for gnome-bluetooth (bluez-gnome's fork) [15:12] cool [15:12] pitti: I see I'm set for approver on automagic python build system, I'm wondering if seb128 or asac would be more useful for you in that role. Thoughts? [15:13] 1) it didn't contain any header with the author 2) I wanted to know if it could be interesting for upstream? [15:13] we sent it upstream [15:13] not sure if they accepted it [15:14] to bluez-gnome I guess [15:14] yes [15:14] noone look to it [15:14] we definately want it upstream for gnome-bluetooth [15:14] oky docky [15:14] thx! [15:16] the notification patch as written to supported notifcation daemon that doesn't support action, right ?(/me needs to understand) [15:16] s/as/was/ [15:31] rickspencer3: well, the design is primarily for you (quickly), I'm happy for the technical bits to be reviewed by someone else [15:33] speaking of blueprints... i have absolutely no idea at all how that process is supposed to work :) [15:33] crevette: you think you can find the bug submitted by kenvandine upstream? [15:33] asac: it was an email to the mailing list [15:33] they have not bug tracker [15:33] kenvandine, ah okay [15:34] should be in the archive though [15:34] anywau it is outdated [15:34] it won't applis on gnome-bluetooth code which was refactored [15:34] applies [15:34] pitti: ack [15:35] I'll review it for the requirements for quickly [15:35] aha, bluez-gnome was dropped from bugs.gnome.org [15:38] pfft === thunderstruck is now known as gnomefreak [15:47] seb128 - i haven't read the whole conversation here, but i saw you discussing FUSA with pitti earlier. do the IM status changes need to be ported across? The new GDM switcher already supports presence using the new gnome-session presence API [15:48] perhaps the default IM client should also support this API? [15:48] chrisccoulson: better to talk to ted [15:48] I'm not sure what presence api they want to use [15:49] I'm not sure there has been an agreement that gnome-session is the right place for that [15:49] especially that telepathy already had similar solutions [15:49] yeah, i'm not sure [15:49] just a thought ;) [15:50] and I don't think the gnome-session thing is functional right now [15:50] it's a first code drop but not doing anything useful [15:50] is it not? i'm not sure any application uses it yet (gnome-power-manager uses it i think) [15:51] asac: aren't you the right person to bug to take care of indicator support for thunderbird/icedove :-P [15:53] chrisccoulson: pidgin doesn't seem to react to such changes for example though [15:54] yeah, it doesn't have support for that API. i don't know how easy it would be to do that [15:54] Mark__T: in general yes, for now there are a few political and technical things left before this can happen properly (this definitly has to happen upstream). Maybe we can look into using some tbird extension in ubuntu as a temporary solution. [15:54] that's something we have now though [15:54] so we need to get it by some way in the new gdm [15:54] ie the patch porting working [15:54] working -> work [15:56] brb === mvo_ is now known as mvo [16:03]