=== tkamppeter_ is now known as tkamppeter === bluesmoke is now known as Amaranth === BugMaN1 is now known as BugMaN [08:34] morning everyone [08:36] morning huats [08:38] morning seb128 [08:39] lut huats [08:39] need to restart session brb [08:39] seb128: do you want that I take care of the gnome-keyring update ? [08:43] huats: do you want to do the gnome-keyring update or are you busy? [08:44] I just asked you before you left :) [08:44] Hi seb128 :) [08:44] I am officially not in my previous company :) [08:44] lut didrocks [08:44] so I think I can deal it :) [08:44] huats: oh, congrats [08:45] seb128: bugs #329800, #329832 (and don't forget #327933) :) [08:45] Launchpad bug 329800 in gnome-icon-theme "Please, sponsor gnome-icon-theme 2.25.90 to jaunty" [Undecided,Confirmed] https://launchpad.net/bugs/329800 [08:45] huats: well, I want this update today so just claim if you have time to do it today [08:45] Launchpad bug 329832 in seahorse-plugins "Please, sponsor seahorse-plugins 2.25.90 into jaunty" [Undecided,Triaged] https://launchpad.net/bugs/329832 [08:45] I'll take care of it right now [08:45] didrocks: thanks [08:45] huats: thanks [08:45] seb128: I can also take care of gtksourceview2 [08:45] huats: ok [09:11] My wife's gnome-panel has recently begun freezing from time to time on her Hardy laptop.. Any idea what could have caused that? [09:12] By "freezing" I mean she can't click on anything, the clock is frozen, the window list isn't updated... The rest of the desktop works fine. [09:12] soren: do you get the issue after clicking on the clock applet? [09:13] seb128: Hm... It's possible. [09:13] there is some gnome-panel bugs about that [09:13] seb128: I would have to ask her when she gets up. [09:13] You know, we recently added a Google calendar feed to her Evolution, so that might very well be it. [09:13] you can get an hang stacktrace maybe? [09:14] right, that's a known issue (ie we got quite some bugs about google calendar leading to such hangs) [09:14] seb128: I'll make sure to grab a dump next time it happens and then remove that feed. [09:14] seb128: Thanks for the hint :) [09:15] you're welcome [10:30] huats: so how are the updates going? ;-) [10:30] seb128: :) [10:32] seb128: remind me that I would never have you as my boss :) [10:32] huats: lol [10:33] huats: I'm not asking too much usually but gnome-keyring ssh agent is broken right now and I get pinged by all the people who use svn, ie active contributors who can't get work done in a normal way [10:33] yeah [10:33] I understand [10:33] it will be ready by 3pm [10:33] huats: that's what you get for claiming updates on basic components rather than let's say calculator ;-) [10:33] hey huats [10:33] huats: ok thanks [10:33] huats: congratulations to your MOTU badge! [10:34] pitti: thanks ! [10:34] seb128: LOL [10:36] seb128: I am creating my pbuilder env on my home computer (since I used to work on my office computer) [10:36] and I start to build [10:36] huats: you should be running jaunty [10:37] seb128: yeah... [10:37] I am thinking of that [10:37] but I have heard of problem with gnome-keyring :D [10:38] (and my gf won't be really happy with jaunty so far I think) [10:38] huats: why not? your gf bullying you about breakage is 100% pure dogfooding :) [10:38] :) [11:13] vuntz: hey [11:13] vuntz: gnome-session for you, it restarts automatically things which are in the session and exit which creates and interesting case when running nautilus with no draw_background set [11:14] vuntz: gnome-session keeps running nautilus which keeps exiting since there is nothing to do [11:14] is that a nautilus or a gnome-session issue? [11:14] should nautilus unregister by some way? [11:15] Would anyone like to attach before-and-after screenshots to bug 328954? [11:15] Launchpad bug 328954 in gnome-control-center "gnome-about-me does not fit in 1024x600 screen" [Wishlist,Confirmed] https://launchpad.net/bugs/328954 [11:16] mpt: can you add a comment in the bug requesting for that? I guess whoever is suggesting the change can do that ;-) [11:17] fine fine [11:17] :-P [11:30] seb128: why does nautilus exit? [11:30] seb128: shouldn't it still run even if there's no background? (don't know) [11:30] vuntz: because there is no dialog open [11:30] vuntz: no [11:30] hrm [11:30] vuntz: there is no server mode [11:30] vuntz: same if you try to nautilus --quit to debug [11:30] gnome-session assumes that it should always run [11:31] wrong assumption [11:31] seb128: that's the meaning of the thing in the .desktop file [11:31] so nautilus bug [11:31] the autorestart? [11:31] it should put that in .desktop file and it should directly control if it gets restarted [11:31] yes [11:31] the panel does this [11:32] well, it should autorestart when running [11:32] not when not running [11:32] seb128: gnome-session starts nautilus. nautilus exits. Then gnome-session restarts it, as indicated by the .desktop file [11:33] vuntz: can you join #nautilus? [11:46] asac: gnome bug #571423 upstream is responsive but needs testing if you want to subscribe and maybe comment [11:46] Gnome bug 571423 in ask dialog "grabbing the keyboard while a menu is open can lock the session" [Normal,Unconfirmed] http://bugzilla.gnome.org/show_bug.cgi?id=571423 [11:48] seb128: cool. i will test it asap [11:48] hopefully before lunch [11:48] thanks [11:54] ok running testcase now [12:03] seb128: LOCK up ;) [12:03] asac: using the testcase? [12:03] i also posted a more bad lockup to the bug [12:03] seb128: yes [12:03] cool [12:03] seb128: just try multiple times [12:03] thanks [12:03] at some point you will end up in the deadlock grab situation [12:04] seb128: as i posted i even get worse situations in combination with gtk-pinentry ... even ctrl-alt-F1 doesnt work [12:04] you need to stop gdm to fix it? [12:04] yesterday i had to hit power button for two things [12:04] killing the testcase is not enough? [12:04] seb128: well. i didnt try killing the testcase. i assume that works ... i can try [12:05] I will try later [12:05] now is lunch time and I don't want to have to restart my session now [12:06] . o O { Use the guest session, Luke! } [12:07] the box tends to freeze a few minutes after switching between xorg sessions [12:07] I didn't try since the sprint though maybe that's fixed now [12:07] hm, I get that effect after hibernate [12:07] but the previous time I used gdmflexiserver to start and another session and closed it the computer locked not too long after that [12:08] it gets locked on /dev/input/events0 [12:09] seb128: ok. so killling test binardy doesnt help [12:09] seb128: updated bug with that info [12:09] seems to be a stale lock in X somewhere i guess [12:09] weird bug [12:15] it sounds a bit like the the grabbing requests are not cancelled in X even though the function returns with FALSE [12:15] in that case its easy to understand why you end up in a deadlock [12:16] e.g. gtk does a two staged grab for popup: 1st. mouse grab; 2nd keyboard grab [12:16] so if someone grabs keyboard in between and then tries to grab mouse you will end up in a deadlock [12:17] but since the gtk functions are supposed to not block it would be something in X that does that. but lets listen to upstream ideas ; [12:20] anyone knows the IRC nick of "Marco d'Itri" (debian)? [12:20] * asac ponders db.debian.org [12:21] ok seems like "Md" [12:21] but isnt online [12:47] vuntz: is "vertical gnome-panel displays only one notification area icon" a known issue? === seb128_ is now known as seb128 [12:49] seb128: no [12:50] vuntz: ok, you will get bug then ;-) [12:50] seb128: or rather "there might be a bug, but I didn't read it if it exists" [12:50] I've looked on bugzilla and didn't find one [12:50] (too many panel bug mails) [12:55] seb128: hey, looks like bug http://bugzilla.gnome.org/show_bug.cgi?id=531371 [12:55] Gnome bug 531371 in notification area "Bad icons arrangement in vertical mode." [Normal,Unconfirmed] [12:55] seb128: it uses one line for all the icons on the notification area [12:55] if you increase the size you'll see the others icons [12:55] ah ok [12:56] pedro_: bug #329537 [12:56] Launchpad bug 329537 in gnome-panel "tray show only one icon on vertical panel" [Low,New] https://launchpad.net/bugs/329537 [12:56] seb128: yup we have that one as well [12:57] wait bug 322252 [12:57] Launchpad bug 322252 in gnome-panel "notification area draws incorrectly on vertical panel" [Low,Triaged] https://launchpad.net/bugs/322252 [12:58] seb128: btw, can you try... [12:58] http://bugzilla.gnome.org/show_bug.cgi?id=571041 [12:58] there's a patch [12:58] Gnome bug 571041 in notification area "remove obox" [Normal,Unconfirmed] [12:58] it might fix it [12:59] vuntz: would testing be useful to you? [13:00] ie I'm being lazy and will not test if that's not useful but if you want to know if that fixes it or I can do that [13:02] seb128: well. If it avoids opening an upstream bug... ;-) [13:03] vuntz: do you intend to commit this change before rolling new tarballs today? ;-) [13:03] seb128: the patch is good, so I'll likely commit it if chpe doesn't commit it [13:03] seb128: so, deal: don't open the bug and wait for the new tarball? [13:03] :-) [13:03] ok, so I will wait for the new tarball to try [13:03] ok [13:03] deal! [13:17] pochu do we still need the procs change on tracker? [14:01] seb128: I am a little late on my schedule [14:01] huats: I noticed! [14:01] I am installing again my jaunty vm [14:01] and once it is done, I can testrun the update.. [14:01] is the update technically ready? [14:01] yep [14:01] I can review and test it if you want [14:02] sure [14:02] seb128: let me put it somewhere [14:02] open a normal sponsoring bug? [14:02] ok [14:08] seb128, about bug #217908, I've responded to your concerns in the bug tracker. I thought it might be easier to discuss this on IRC. [14:08] Launchpad bug 217908 in cairo "Pixellated Images in Firefox/Opera due to incorrect EXTEND_PAD implementation in several video drivers" [High,Fix released] https://launchpad.net/bugs/217908 [14:08] TomJaeger: hi, I was just reading your comment [14:09] TomJaeger: the issue is simple we don't want to carry changes when not really required, if that change is good is should go upstream if they have a reason to not want it we should probably not ship it either [14:09] TomJaeger: having distro diverting from upstream create distro specific bugs and tension with uostream and is usually not a good thing [14:09] As I said, upstream can't ship the change yet, because they can't be sure the drivers are fixed at this point [14:10] how can we be sure if they are not? [14:10] this is what this whole bug is about [14:10] no, that bug is about fixing the drivers we have control over [14:11] the freedesktop guys could clearly do the same [14:12] Some projects are slow to respond to bug reports, but these changes are going to happen upstream eventually [14:12] and I would argue that this bug is open for almost a year and has no duplicate so it's not a real issue for our users and probably not worth carrying this delta for cairo [14:12] I think it's an important issue. The browser is one of the first programs any user is likely to use [14:13] well nobody seems to notice or care [14:13] I for one have no issue with the current rendering [14:13] And people do notice that scaled images look fine on Windows and look like shit on ubuntu [14:13] People do care [14:13] seb128: bug 330096 [14:14] Launchpad bug 330096 in gnome-keyring "Please sponsor gnome-keyring 2.25.91 into jaunty" [Wishlist,New] https://launchpad.net/bugs/330096 [14:14] huats: thanks [14:14] no pb (sorry I have been on the phone...) [14:14] that's ok [14:14] seb128: I don't want you to think that I need 10 minutes to put on LP :=) [14:14] :) [14:14] seb128, especially with high-resolution screens being more common on laptops these days [14:15] I am not as slow than didrocks on mariokart :P [14:15] TomJaeger: ok, can we get an upstream bug where upstream state they agree with the changes and will apply those once drivers are fixed then? [14:15] huats: ;-) [14:15] seb128, this is more or less what Carl stated in that intel driver commit message [14:15] TomJaeger: we already had unhappy upstream due to distro changes and I would like to avoid that if not required [14:16] I'm sure upstream is going to appreciate the work we are doing here [14:17] the commit message has a "(due to various bugs and workarounds in cairo and pixman)" mentions [14:17] do you have details on that? [14:17] the bug was in pixman, the workarounds are in cairo [14:17] have those issues been addressed in jaunty? [14:18] The pixman issue was fixed here: http://cgit.freedesktop.org/pixman/commit/?id=2d9c7cd84b276ebe2ff72d03c34a2d7f4f98b9f9 [14:18] This is not in jaunty as I don't think EXTEND_REFLECT is very important [14:20] ok [14:20] you seem to know what you are doing let's keep things this way for now [14:21] thanks [14:21] sorry for the trouble but I'm trying to avoid adding random changes because somebody stated that was a good idea [14:22] we got bitten by such things turning to be not so great idea and make upstream not happy with ubuntu for shipping those changes [14:22] so it's always good to have an upstream bug stating that agree with the change when possible ;-) [14:23] I'm kind of interested now, what was that change that upstream was unhappy about? [14:24] that's not especially on cairo [14:24] they were unhappy with the lcdfilter changes we have though [14:25] brb trying the new gvfs version [14:28] ok, works correctly [14:34] seb128, Thanks, I'll take another shot at getting the remaining driver fixes accepted upstream, and as soon as that has happened, I'll bring up the issue on the cairo mailing list again. [14:34] TomJaeger: thank you for your work and being responsive to my comments! [14:35] You're welcome [14:38] huats: usually users enjoy reading the NEWS entry in the debian changelog if you can copy it there ;-) [14:38] seb128: hum... [14:38] that is true [14:39] just a detail but I mention it [14:39] you are right [14:39] it's handy to close bugs and nice to read [14:39] huats: I prefer doing better packages than playing mario kart :p [14:40] * didrocks needs a real revenge on MK :) [14:40] seb128: can you imagine, that didrocks has willingly forgotten his nintendo DS at home during the fosdem, to avoid playing MK with me ??? [14:40] oh, is that the current game? I still live in the frozen bubble world [14:40] lol [14:40] seb128: that's false. I had my DS, huats not :) [14:41] well he forgot to tell me : bring your, I'll have mine... [14:42] huats: that's pretty different from what you were saying ;) [14:44] pitti: maria kart is quite old game though they do new versions for new machines ;-) [14:44] I've not played it for 15 years or so [14:45] ember: do you mean the change from 0.6.6-1ubuntu4 ? [14:47] :) [14:47] seb128: come to toulouse to do a conference :) [14:47] and you'll be able to play :) [14:47] lol [14:48] ;) [14:48] pochu yes [14:48] seb128: I will be there an next ubuntu party in Toulouse, please come so that I feel not lonely when loosing :) [14:48] ember: no idea, kees did that change [15:18] huats: you need to update the libgcr0 shlibs too [15:18] pfff [15:18] I gave you the wrong stuff [15:18] lol [15:18] yeah yeah [15:19] (yeah that sounds weird but I am on 2 computer this afternoon..) [15:19] and I did the update on both [15:19] pitti: ping [15:23] huats: the new gnome-keyring works correctly here [15:23] ok [15:23] great [15:25] huats: so you can update the changelog to list the change and close bugs and update the shlibs? then I can sponsor the upload ;-) [15:25] ok [15:25] no pb [15:25] I'll [15:26] thanks [15:54] rickspencer3: pong [16:01] Keybuk there? [16:01] yup [16:01] i was talking with kees about a inotify change in tracker [16:02] ubuntu as been using fs.inotify.max_user_watches = 524288 [16:02] right [16:02] debian added the change and increase to fs.inotify.max_user_watches = 65536 [16:02] that's a tenth of our value? [16:03] so i should keep the ubuntu change or drop it? [16:07] keep it [16:07] ok, thanks. [16:45] hello guys [16:46] I packaged abiword 2.6.6 which fixes a lot of annoying bugs [16:46] I would like to get it in before feature freeze [16:47] could someone review my package attached to bug #318444 ? [16:47] Launchpad bug 318444 in abiword "[need-update] abiword to latest stable version 2.6.6 in Ubuntu 9.04" [Wishlist,Triaged] https://launchpad.net/bugs/318444 [16:47] jeromeg: can you please sub ubuntu-main-sponsorss? [16:47] jeromeg: btw, that doesn't sound like a FF issue, if it's mostly bug fixes [16:47] jeromeg: so we can get it in a bit later, but either way, we'll try to look at it ASAP [16:47] jeromeg: thanks a lot for the update! [16:48] pitti: unfortunately, I won't be available a lot in the next fex days, so I would have liked to have someone look at it today [16:48] so I can fix things if I made some stupid mistakes [16:49] jeromeg: understandable; I just have to leave in about 15 mins, and still working on something :( [16:50] pitti: ok, no problem [16:50] jeromeg: judging by the changelog it looks alright [16:51] jeromeg: btw, please don't attach orig.tar.gz's to bug reports, an URL to the upstream location suffices :) [16:51] (and we'll download that one anyway) [16:51] pitti: the tarball is repackaged [16:51] or did you repack the upstream tarball? [16:51] ah [16:51] what changes, out of interst? [16:51] I'm not the one who started this, debian does it too [16:51] pitti: it's a merge of four tarballs [16:51] right, I just don't remember why it's necessary - some nonfree bits? [16:52] ah, that [16:52] abiword, abiword-help, abiword-plugins, abiword-extras [16:52] jeromeg: does this have a debian/rules get-orig-source? [16:52] there is a README.source at the root of the tarball [16:53] pitti: I found 3 or 4 additionnal LP bugs closed by this upgrade, shall I update the changelog, or closing them by hand after the upload is ok ? [16:54] jeromeg: closing by changelog is always nice, for keeping a permanent cross-ref [16:54] ok, I'll attach the updated package then [16:54] jeromeg: awesome, thank you [16:58] huats: hello? ;-) [17:06] seb128: I am here.. [17:06] seb128: I will put that in 5 minutes [17:06] I was away [17:07] huats: ok, sorry for pinging on this one, I will be cool again on the next ones ;-) [17:07] no pb [17:08] huats: you signed up for some responsability you get the pressure going with those ;-) [17:08] I start to know how you are :) [17:09] huats: didn't know seb128's whip before? :-) [17:09] nope [17:09] PHEAR [17:09] ... i should have been more careful... [17:09] * pitti hugs seb128 and huats [17:10] :) [17:10] pitti: I try to not scare them too early, now that they joined motu though ... ;-) [17:10] * seb128 hugs pitti [17:10] seb128: ... there's NO way back!!11! [17:10] * seb128 hugs huats [17:11] * huats hugs both seb128 and pitti [17:12] huats: seriously, the Ubuntu user crowd will appreciate your help [17:12] :) [17:12] for what ? getting whipped by seb128 :) [17:13] better you than them no? ;-) [17:13] ahahah ;-) [17:13] ;) [17:13] see what happens when I get bored because contributors claims all upgrades but don't give me something to review ;-) [17:15] seb128: I am having trouble to associate the various bug fixes to the elements of the NEWS file [17:21] huats: use https://bugs.launchpad.net/bugs/bugtrackers/gnome-bugs/nnnnn ? [17:21] seb128 if you so bored there's a tomboy update awaiting to be sponsored :o [17:21] * ember hides [17:21] huats: where nnnn is the gnome bug number, it will give you the ubuntu bug if there is one [17:21] ok [17:22] ember: I try not touching monon when I don't have to [17:22] seb128: the thing is that all bug linked from LP are still not marked as resloved upstream [17:22] and I'm not really bored ;-) I might have a look to sponsoring when I'm done looking at some evolution changes though [17:23] seb128: let's no close bugs automatically [17:23] huats: ok [17:23] and I'll close them manually [17:23] (I'd rather have an opened bug in LP instead than a false close one... well I think it is better) [17:23] the only "monon" i touch is tomboy [17:23] (but I might be wrong) [17:24] huats: right, I though they had fixed the fix commited bug before rolling the tarball but apparently not [17:25] brb [17:27] you're crazy guys ;) [17:30] huats: if you want, I think I can whip seb128 for sponsoring too. He owns me 3 :) [17:31] huats: hum no… that's true that you are always putting my leg about mario kart, so I won't :p [17:31] didrocks: I'm doing sponsoring next [17:31] seb128: just kidding, no emergency ^^ [17:32] as all those packages will have FFe, I think :) [17:32] I know there is no hurry, I would have sponsored those already otherwise ;-) [17:32] didrocks: right, there is no freeze for GNOME [17:32] seb128: as huat's one, for instance? :p [17:32] yes [17:32] getting the ssh agent fixed would stop angry people who can't commit to svn due to that [17:32] or rather who have to type their password a zillion time a day [17:33] it's understandable ^^ [17:34] btw, I have to ping ubuntu-server team to know why there is no ssh-agent by default on server (it can be sometimes useful) [17:34] seb128: it is on LP [17:35] huats: thanks [17:37] didrocks: btw there is a new gnome-python-extras version for you [17:37] didrocks: and gnome-python-desktop too [17:37] seb128: some work to do, so, I'm on it [17:38] :) [17:38] ;-) [17:38] didrocks: there is also vino and vinagre if you want to do those [17:38] seb128: I put them on my schedule too :) [17:43] seb128: is it normal that gnome-python-desktop is not in bzr for ~desktop-team? [17:43] didrocks: it was supposed to be there? is there still a sponsoring request pending for it that I forgot about because it's not on the list? [17:44] hum, let me check [17:45] huats: the shlibs to update is the libgcr0 one and not the libgnome-keyring one [17:45] seb128: there is a shlibs for libgnome-keyring [17:45] seb128: gnome-python-desktop was sponsored and I attached the bzr branch [17:45] huats: and now you need one for libgcr0 [17:46] didrocks: ok so I didn't push it probably, where is it? [17:47] seb128: https://code.edge.launchpad.net/~didrocks/+junk/gnome-python-desktop but you can push it next time :) [17:47] huats: no .shlibs means there is no version specified, which was correct for libgcr since that's a new lib [17:47] didrocks: ok, will do that then [17:47] seb128: I used +junk because there is no gnome-python-desktop project in LP [17:48] didrocks: https://edge.launchpad.net/gnome-python-desktop ? [17:49] that's strange, it refused it to me. I will try again to push the branch later [17:49] didrocks: I have the same problem for my packaging [17:50] crevette: even with project that are on LP [17:50] I tried to push my own branch for obex-data-server but I wasn't allowed to, wo Ipushed to +junk [17:50] crevette: you need to have a product using the same name on launchpad, if your packaging is nautilus-sendto-universe that's normal [17:50] seb128: it's ok now [17:50] seb128: no obex-data-server [17:50] seb128: Registered [17:50] 2009-01-27 [17:50] :) [17:51] seb128: ok [17:51] didrocks: yes, I pinged jcastro recently about it I think [17:51] didrocks: but your request is not waiting for 3 weeks is it? [17:51] crevette: weird, https://edge.launchpad.net/obex-data-server [17:51] seb128: I think I created the branch in ~didrocks before the creation [17:51] of the project [17:51] ok [17:52] seb128: (it is corrected) [17:53] so if I understood you well [17:54] there was no need for the 2.25.90 since the lib was new in that release, but now we need it, since there was a .shlibs in the package [17:54] ? [17:54] huats: almost good, the libgnome-keyring shlibs doesn't need an update [17:55] just libgcr [17:55] the shlibs need to be updated when there is an api addition [17:55] libgcr was new so there was no api addition in a specific version so no need to specify one [17:55]