=== racarr_ is now known as racarr === Jazzva_ is now known as Jazzva [05:51] pitti: you around? I've a few questions for you on bug 269509 [05:51] Launchpad bug 269509 in compiz "white screen on second session with compiz: pretends to have a second DRI capable head where it doesn't" [High,Fix released] https://launchpad.net/bugs/269509 [06:21] pitti: guess you're out; I'll ask on the bug [07:19] bryce_: right, I'll answer on the bug [07:38] morning o/ [07:46] hi mvo :) [07:50] hey didrocks! === tkamppeter_ is now known as tkamppeter [07:53] mvo: I have two gifts for you: [07:53] lp:~didrocks/+junk/totem [07:53] lp:~didrocks/+junk/totem-pl-parser [07:53] hope you will like them :) [07:53] what are those? [07:58] Tm_T: totem's gnome update, put in bzr [07:58] I see [07:59] what hew hotness I should look at? [07:59] thanks didrocks - geting them now [08:00] mvo: I made some dependency changes, nothing really risky but I think this is correct [08:01] Tm_T: for totem, you can look at the changelog, everything is in it. For other package, ask mvo & seb128 :) [08:36] didrocks: totem build fine, I'm checking the debdiff now (sorry that it took so long, got distracted) [08:37] mvo: when are you going to upload the python-apt with gtk stuff? :) [08:37] slomo: its in experimental already and in jaunty too - its not a ideal time for it in sid I think :/ [08:38] slomo: we still need some little backend script that can be run as like synaptic - so that we don't have to run the main gui as root. but thats trivial [08:38] ok :) but experimental is fine, i'll wait until that backend script exists ;) [08:39] slomo: I try to work on gnome-codec-install a bit every day, its a nice and fun project :) [08:39] thanks :) [08:40] and I seem to have figured bzr-svn enough to not have to bother you with every single commit (I hope) [08:41] i could add you to pkg-gstreamer if you want [08:42] slomo: if that is ok with the team I'm fine with that too [08:43] * mvo hugs glatzor [08:45] mvo: what's the name of your alioth account? [08:45] morning mvo and slomo [08:45] slomo: should be mvo [08:45] hi glatzor :) [08:50] mvo: no pb, take you time :) [08:53] mvo: added you [08:55] hello everybody there [08:55] pochu: there? any news about the libproxy 0ubuntu1 version? [08:55] hi seb128, slomo and glatzor ;) [08:56] hey didrocks, did you do the other updates yesterday? ;-) [09:02] go go go pitti ;-) [09:03] hey seb128 [09:03] (just got a apport retracer service email ;-) [09:03] seb128: :-) [09:03] hey pitti [09:03] seb128: I'm having the hardy and intrepid ones catch up first, before I start working on jaunty [09:03] I guess there is a long queue [09:03] seb128: I noticed that we can't send mail from ronne :( [09:04] will be the second flood of the day [09:04] I updated the RT for this, but not sure when it will be done [09:04] so the polling will need to continue for a while [09:04] the first one was bug watch updates, we got around 500 of those during the night on desktop bugs [09:04] ok [09:04] but I think until then we can work around this by adding a "ssh ronne test_if_running" into our .bashrc or so [09:04] ;-) [09:04] and look into the log what went wrong [09:05] yeah [09:07] seb128: yes, mvo is on it (lp:~didrocks/+junk/totem, lp:~didrocks/+junk/totem-pl-parser) [09:07] mvo: I am in a meeting. will be available in one hour :) [09:08] didrocks, mvo: ok, thanks guys [09:10] seb128: oh, indeed, I got a bug watch updater flood as well [09:11] seb128: totem is in progress, some smallish stuff needs attention first I think, including a Vcs-Bzr header ,) - should we put it under ~ubuntu-core-dev or ~ubuntu-desktop, what do you prefer? [09:12] mvo: ubuntu-desktop would be cool, what do you think? [09:12] seb128: yay for bug 207072 fixed upstream [09:12] Launchpad bug 207072 in gvfs "nautilus does not display samba shares for machines inside an ADS network." [High,In progress] https://launchpad.net/bugs/207072 [09:12] pitti: indeed! [09:12] pitti: will be a bit short for 8.04.2 though [09:12] lut huats [09:13] would really be nice, though, but yes [09:13] hello seb128 and pitti [09:13] seb128: fine with me, we just need to keep in mind that people added there will have write access to the bzr branche [09:13] hey huats [09:13] :) [09:13] mvo: the team has been created for that purpose in fact, we already had desktop-bugs for bug triagers [09:14] seb128: yeah, just checked the members, looks fine [09:14] seb128: would be nice if we could give ubuntu-core-dev implicit permission on the branches too [09:15] mvo: does launchpad allow to do that by setting one team as member of the other one or something? [09:16] I think it does, however I think its good asking first (#launchpad maybe) just to ensure it has no bad side-effects (like some sort of mail spamming or similar) [09:23] seb128: I have an answer for the gnome-keyring stuff (which is blocking for seahorse...) [09:23] huats: ah good, which one? [09:23] crevette: lut [09:23] it is a development stuff that upstream don't understand how we can have that [09:23] hello gentlemen [09:23] crevette: t'as corrigé ta maj de gedit? [09:24] so he asked me to debug a bit with him... [09:24] what I will do of course :) [09:24] huats: what do you mean? [09:24] seb128, non pas du tout [09:24] crevette: :-( [09:24] crevette: c'est une ligne à changer et tu bloques l'update [09:24] crevette: t'as commencé donc personne d'autre va la faire et elle est buggée donc peut pas être uploadée, ca serait bien de corriger ;-) [09:25] ah desolé [09:25] je pensais que tu pouvais le corriger [09:25] ce soir ca va ? [09:25] crevette: je peux le corriger si tu veux [09:25] crevette: oui [09:25] seb128, si tu peux le corriger c'est super [09:26] ok [09:26] let continue in english [09:27] I thought as you sent me the fix you were going to correct the package,sorry [09:27] :/ [09:27] huats: ok, I got the email [09:27] seb128: I have forwarded the email :) [09:27] crevette: that's ok, I was just telling you how to fix it so you can learn ;-) [09:29] seb128: if crevette is bit busy I can have a look :) [09:29] huats: there is other updates for you if you want to do some [09:29] hehe [09:29] ok :) [09:30] (i was saying that because I think I did a gedit update on my computer just before I realized that crevette already did it... but I am not that sure...) [09:33] huats: feel free to fix it, he opened a bug and did the changelog update but there is also a .install to update [09:34] seb128: no no [09:34] crevette: you need to learn :) [09:35] huats: want an another update to do? [09:35] hey tseliot [09:35] seb128: sure [09:35] :) [09:35] hey seb128 [09:36] (well on the other side I might finish the anjuta one first... since I have some stuffs related like libgda) [09:36] huats: about gnome-keyring it's probably only failing because we use -Wl,-z,defs which enforce proper building, you told that to upstream right? [09:36] yep [09:36] huats: you can try to comment the LDFLAGS in the rules and see if it builds otherwise [09:37] that was something I was about to do this morning :) [09:37] huats: as you want, I prefer to focus on the standard desktop first and then on side applications usually ;-) [09:37] ok [09:37] so I'll follow you order sir ;) [09:37] give me something to do :) [09:39] huats: [09:39] http://download.gnome.org/sources/deskbar-applet/2.25/deskbar-applet-2.25.4.tar.gz [09:39] ok [09:39] I am on it [09:40] btw seb128, have you worked on the 'new' desktop package page that norsetto initiated ? [09:40] (I was wondering that during holidays :)) [09:41] huats: not yet, but we should [09:41] seb128: ok :) [09:42] let's catch up on work and updates first and then we will work on the workflow ;-) [09:44] seb128: I was just asking :) [09:51] seb128: it gnome-keyring builds fine without that flags [09:51] ok, that was expected ;-) [09:51] yep [09:51] so I can tell him that it builds fine without that flags [09:55] seb128: what do I do ? [09:55] I put the package without that flags ? [09:55] or I work with upstream in order to have a package with the flags ? [09:55] huats: let's wait a bit on upstream to reply, the bug should be easy to fix [09:55] ok [09:56] huats: we use those flags for a reason ;-) [09:56] seb128: I know :) [09:56] so better to fix issues than to workaround [09:56] sure [09:56] (I was just asking) [09:56] thanks [10:07] huats, the thing is I can only do updates during the night, and at work I can just talk but not package. feel free to correct my package if you want [10:07] crevette: I understand [10:07] but master seb128 told you to learn, so learn ;) [10:08] I would never find how to fix the package myself [10:08] crevette: I am sure you will [10:10] huats, if you want to correct the package, seb told me to just remove the *.ui line in gedit.install, they get installed in gedit-common anyway now and it builds correctly === asac_ is now known as asac [10:49] "huats> that was something I was about to do this morning :)" -> fake job :p [10:50] LOL [10:50] thanks didrocks [10:50] y/w huats ! [10:50] :) [11:03] seb128: if you have any other update in the pipe (and bzr-ianisation to do) that I can do this evening, just shout :) [11:03] didrocks: just ask this evening, the list will move during the day [11:04] oki [12:24] seb128: morning :) here you have, please review it ;) http://emilio.pozuelo.org/~deb/libproxy_0.2.3-0ubuntu1.dsc [12:26] pochu: hey, thanks [12:26] pochu: want to do the mir for it too? ;-) [12:30] seb128: yeah I can do it, but later today [12:30] pochu: thanks [12:30] pochu: I've reviewed the package, good work [12:31] \o/ [12:31] thanks [12:31] pochu: I'll sponsor the upload and ask pitti to NEW it [12:31] so it has a second review === ember_ is now known as ember [12:31] seb128: I can upload it myself, btw ;) [12:31] but feel free to upload it :) [12:31] pochu: do it please then [12:31] ok [12:32] hum [12:32] it doesn't build [12:32] bah [12:33] it'll build on the buildds [12:33] I only built it in a Debian pbuilder [12:33] that's because it changes the configure and that triggers an autotools run [12:33] what's the error? [12:33] ../../libtool: line 818: X--tag=CC: command not found [12:33] classic libtool issue when autotools are not ran in the right order [12:33] and it won't trigger it in the buildd? [12:33] but that's only because automake is installed and got triggered [12:33] ah [12:33] ok [12:33] no, automake will not be installed there [12:34] ok, uploading [12:34] thanks [12:34] Successfully uploaded packages. [12:34] :) [12:37] pitti: can I get you to have a quick look to libproxy in NEW? I already checked it but there is one file not under a standard license and I would like to have your opinion on that [12:44] seb128, pitti: this is the thread from my ITP in Debian which lead to a few concerns from a security POV: http://lists.debian.org/debian-devel/2008/12/msg00730.html [12:44] hum [12:45] "mozjs.c:32:19: error: jsapi.h: No such file or directory [12:45] " [12:45] mvo: hi! you have mail :) [12:46] seb128: I'll look at it tonight, need to run to the university [12:47] * pochu waves at pedro_ :) [12:47] pochu: ok thanks, see you later [12:47] see you! [12:47] pochu: hello! [12:48] asac: there for a xulrunner question? [12:50] seb128: are you here? [12:50] soc: hi [12:51] ah cool [12:51] it's about #157398 [12:51] https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/157398 [12:51] Launchpad bug 157398 in gnome-control-center "GNOME default DPI doesn't match X default DPI" [Unknown,Fix released] [12:51] i found the root cause of the problem [12:52] the xrandr code is using 96 dpi [12:52] so when you have used the xrandr capplet you get 96 dpi used [12:52] https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/157398/comments/7 this is the comment i described the wrong behavior and https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/157398/comments/8 describe the problem [12:52] Launchpad bug 157398 in gnome-control-center "GNOME default DPI doesn't match X default DPI" [Unknown,Fix released] [12:52] that's not a bug [12:53] that gconf setting has been added back because there was too many bug configs [12:53] it's a bug that debian tries to hardcode it themselves [12:53] we tried to use the autodetected dpi some cycles ago [12:53] no it's not [12:53] because debian pathced the code in 2007 to handle that more gracefully [12:53] seb128: when did you try that? [12:54] because debian patched the code in 2007 to handle that more gracefully, i meant [12:54] so the debian code is duplicate [12:54] ? [12:54] they patched what? [12:54] and makes debugging more complex [12:54] debugging of what? [12:55] they try to detect the dpi and if the dpi is in an reasonable range they use, if not they hardcode 96 dpi [12:55] so it's useless to hardcode it in that debian file [12:55] because the first part will never get executed [12:55] we tried during the gutsy cycle [12:56] the issue is not "not reasonable range" [12:56] mhh, then what is the issue? [12:56] but 80 dpi listed when the screen is 96 dpi for example [12:56] because gnome thinks the value in that %gconf.xml is set by the user, it doesn't even try to get the dpi from the xserver [12:56] read bug #118745 [12:56] Launchpad bug 118745 in xorg-server "Font sizes in Gutsy are affected by bad X.org DPI detection" [Medium,Fix released] https://launchpad.net/bugs/118745 [12:57] soc: we did try the xorg way and rolled back due to the flood of bugs [12:57] soc: there is many configs where xorg just doesn't get it right [12:57] and then why use 96? [12:58] that's just a random value which is almost never right anymore [12:58] because it's near of a correct value and create less trouble for most users [12:58] we don't have many users complaining [12:58] from my testing at least nv, nvidia and radeonhd get it right [12:58] I don't think "almost never right" is a correct statement [12:58] i'm sure about it [12:59] seb128: yes [12:59] well, let's see xorg autodetection get it less right then [12:59] brb just restarting IRC to try something [13:00] seb: modern displays don't even have an integer dpi anymore, as well as they don't have the same dpi for the vertical and horicontal range [13:00] asac: pkg-config --cflags --libs mozilla-js lists -I/usr/include/xulrunner-1.9.0.5/stable is that normal? [13:00] soc: I'm not interested in this discussion, we get not complain using the current way, you tried your way you can read the bug and the number of duplicates [13:01] seb128: no complains? [13:01] soc: I don't really care what is right or not we do what is best to not annoy users [13:01] i see at last five different bug reports on that [13:01] and at least as many entries on brainstorm [13:01] soc: well, that's much smaller than the angry flood of users we had when trying the xorg way [13:01] it would be nice to maybe fix that issue once [13:02] asac: libproxy uses jsapi.h which is the unstable directory and pkg-config on mozilla-js, is that correct? [13:02] soc: what I got from the xorg team by then is that the issue can't be fixed on a lot of non modern hardware [13:03] soc: where the monitor doesn't communicate enough to the computer to get that value right [13:03] so then gnome falls back to 96 dpi, so what's the problem? [13:03] seb128: what is libproxy? [13:03] soc: I can raise the issue to the next desktop team meeting or discuss it on #ubuntu-x and we can probably try dropping the set value again and see users reactions, maybe xorg does a better job now [13:04] is that something (in future) important? [13:04] seb128: i'm sure that the situation has improved ... [13:04] asac: that's something GNOME 2.25 depends on, it's blocking GNOME updates in jaunty and my priority for this week now [13:04] could you point me to the file where it gets hardcoded? [13:04] i thought the file was in gconf2-common, but it wasn't [13:04] seb128: what elements of jsapi does it use? [13:05] just some constant or real abi? [13:05] soc: /usr/share/gconf/defaults/10_libgnome2-common [13:05] soc: i will prepare patches, so the team has some facts to discuss about [13:05] thanks [13:05] asac: dget http://emilio.pozuelo.org/~deb/libproxy_0.2.3-0ubuntu1.dsc [13:05] soc: patch? it's dropping one line in a .gconf-defaults [13:05] sure [13:05] seb128: what part of gnome depends on it? [13:05] soc: no need to bother, I did set the value and know how to unset it, it just needs to be discussed, but thanks [13:06] ok [13:06] asac: libsoup depends on it now, which is used by libgweather [13:06] another thing to think about would be the standard font size [13:06] asac: it's blocking the gvfs update which fix samba active directory browsing, libgweather, gnome-panel and some other things too [13:06] now, when the dpi is set correctly, it might be possible to set it to something "which sucks less"TM [13:06] :-P [13:07] soc: those discussions might be better placed on #ubuntu-x btw [13:07] btw, when is the next desktop team meeting? [13:07] soc: next tuesday at 16h30 utc [13:07] on this channel [13:08] so yesterday was the last meeting? [13:08] asac: the source using it is mozjs.c [13:08] soc: right, those are weekly meeting, usually at the same time but that might change after next one due to team reorganisations [13:09] ah k [13:10] seb128: btw, why is the current wallpaper called "warty......png"? [13:11] soc: because we usually don't touch user configuration on upgrade and changing the name would break a working configuration for users which have that filename set in their config [13:11] ah, ok interesting [13:11] pochu: thanks, was having lunch [13:11] that's one of the thing we might consider trying to fix in upgrade tools at some point though [13:12] we still have evolution-2.2.desktop for the same reason [13:12] mvo: we forgot to discuss that at UDS, maybe at the distro sprint or next UDS [13:12] pochu: so wpad will get disabled by default? [13:12] seb128: okay [13:13] pitti: danke [13:13] last thing to that dpi-problem: that dpi input box in gnome-appearance-properties would be better placed in the gnome-display-properties [13:13] because many people are bausing that dpi-setting to change the font-size ... [13:14] s/bausing/abusing [13:14] seb128: in exchange, I'd appreciate if you could review calibre, since I uploaded it and thus can't NEW it [13:14] soc: right, that's a good point, should probably be discussed upstream though [13:14] pitti: sure, will do [13:14] do you know if o maintainer of display-properties is around here? [13:15] distro maintainer or upstream hacker? [13:15] any one [13:15] the GNOME packages are team maintained, usually mvo or I do the gnome-control-center updates but that's distro work, not really upstream hacking [13:15] ah ok [13:15] upstream guys are on #control-center on irc.gnome.org [13:16] thanks [13:16] seb128: hm? evo2.2? [13:16] you're welcome [13:16] seb128: the license looks fine to me; what do you see wrong with it? [13:16] pochu: nice, thanks [13:16] seb128: pkg doesnt even build here at all :/ [13:16] pitti: nothing, I just wanted an another opinion, I'm never comfortable jugging licenses [13:17] seb128: it sounds fairly common (MIT license) [13:17] asac: libproxy? [13:17] yeah [13:17] ;) [13:17] seb128: it's just a slightly reworded MIT, yes [13:17] pitti: no need to have a COPYING for it or something right? [13:17] seb128: the license would need to be in src/plugins/xhasclient.c [13:17] pitti: is that required or not? [13:18] seb128: anyway. please do something in this spirit: http://paste.ubuntu.com/101643/ [13:18] seb128: also remove xul dep then [13:18] seb128: required, and it is there [13:18] mozjs is not a lib and cannot be supported [13:18] ups, closing wrong dialog [13:18] asac: url again please? ;-) [13:19] seb128: use irssi in a screen ;) [13:19] 14:18 < asac> seb128: anyway. please do something in this spirit: http://paste.ubuntu.com/101643/ [13:19] seb128: so all in all, package looks good to me [13:19] seb128: (accepted) [13:19] * pitti -> lunch, bbl [13:19] seb128: adjust build-deps accordingly. if there is an issue with disabling it ... we have to look/talk also with upstream [13:20] asac: http://people.ubuntu.com/~seb128/configure_check_for_dbus.patch.gz [13:20] from the build failure it looks like the package needs to be re-libtoolized or something [13:20] asac: updated patch if you want to build it [13:20] seb128: is that re-autostuff? [13:20] asac: the previous one fails if you have automake installed, that got run but it doesn't work correctly using the current libtool [13:21] asac: yeah, one configure.ac change (you get an error saying what to add if you run autoreconf and autoreconf run) [13:21] ok cool. will try. but mozjs is just a plugin so i guess it should be safe to disable for now [13:21] pitti: thanks [13:22] asac: ok thanks, yeah we don't need plugins, just the library [13:22] asac: it doesn't tell me if the bug is libproxy or a xulrunner one though ;-) [13:22] seb128: spidermonkey folks know about this issue (they didnt know a few weeks ago) and understand that they need to do ABI tracking to become a real lib [13:22] asac: ie if mozilla-js is not the correct thing to pkg-config [13:23] seb128: the bug is that libproxy tries to use a lib that isn't main-worthy [13:23] ok, fair enough [13:23] hence we dont ship it at a static location ... so -rpath wont work ... so we cannot allow mozjs things in [13:23] I will let those guys sort that then [13:24] tell them that spidermonkey folks know about that issue ... they can support them by asking for ABI/API policy and proper SONAME in bugzilla ;) [13:25] ok ;-) [13:25] asac: thanks for looking into the issue [13:26] welcome [14:16] vuntz: hey [14:16] vuntz: so gnome-panel 2.25.3 doesn't build ;-) [14:16] vuntz: clock.c:2737: undefined reference to `bonobo_ui_component_set_prop' [14:16] vuntz: known issue? [14:18] seb128: hrm. weird [14:18] it does build here [14:18] let me finish something and I'll look at it [14:19] vuntz: we use -Wl,-z,defs so you probably dropped the -llibbonobo but still use some symbols which is wrong [14:19] or -lbonoboui [14:20] or whatever defines the symbol you are using ;-) [14:25] seb128: libpanelapplet-2.0.pc contains libbonoboui-2.0 [14:25] hrm [14:25] vuntz: is that .pc used when building gnome-panel? [14:25] vuntz: circular depends? ;-) [14:27] seb128: well, I think libpanelapplet-2.0-uninstalled.pc is used when building gnome-panel, but it still contains libbonoboui-2.0 [14:27] so something is wrong somewhere [14:27] ah [14:27] I think I know [14:28] hum [14:29] just need to add LIBPANEL_APPLET_CFLAGS and LIBPANEL_APPLET_LIBS to all applets [14:29] vuntz: [14:29] PKG_CHECK_MODULES(CLOCK, pango >= $PANGO_REQUIRED gtk+-2.0 >= $GTK_REQUIRED glib-2.0 >= $GLIB_REQUIRED gio-2.0 >= $GLIB_REQUIRED $LIBECAL_REQUIREMENT libglade-2.0 >= $LIBGLADE_REQUIRED librsvg-2.0 dbus-glib-1 gweather >= $GWEATHER_REQUIRED) [14:29] vuntz: that would work [14:29] actually we already have LIBPANEL_APPLET_CFLAGS for the clock [14:30] vuntz: where? [14:30] ah [14:31] vuntz: right, you don't have the LIBS though [14:31] which is what create the ldd issue [14:32] yep, will commit the fix in one minute (building to make sure it's okay) [14:33] vuntz: thanks! [14:35] committed [14:35] thanks [14:36] vuntz: thank you ;-) [14:36] * seb128 hugs vuntz [14:36] vuntz: you don't have the patch handy somewhere by any chance? [14:37] sucks that viewvc doesn't have the changeset, you need to get the diff for each file there [14:37] seb128: http://svn.gnome.org/viewvc/gnome-panel?view=revision&revision=11435 [14:37]