[00:00] let those for now and we will see if somebody complains [00:00] to change then: [00:00] - unsplit the C locale [00:00] - use replaces to avoid file conflicts error on upgrade [00:00] - do the 2.25.91 upgrade [00:01] thanks again for your work ;-) [00:01] no problem, I'll include the split with the 2.25.91 upgrade [01:20] chrisccoulson: you referring to 160_log_timestamping.patch? [01:23] does that patch add timestamps then? the only reason i asked is because i was looking at a bug report where the user couldn't open a second session via FUSA. the reporter already provided a Xorg.0.log, but it didn't contain anything useful, so i asked them to attach their Xorg.20.log too. That didn't have any trace of what went wrong either, andt it wasn't clear from the log when it was created, as there was no timestamp [01:23] the log they provided might have been several months old ;) [01:31] i've just noticed the timestamps in my own log actually [01:32] chrisccoulson: you're welcome ;-) [01:32] actually they're time since server start, so may not solve the issue in this particular case [01:32] the only thing that is missing though is the time that the server actually started [01:33] chrisccoulson: I'd accept a patch to add that if you'd be up for taking a shot at it; probably a 1-liner [01:33] i might be able to have a look at that. probably tomorrow though as it's getting quite late here now [01:33] cool [01:34] probably make sense to slot it in right after the Build Date line [01:34] oh hang on [01:35] [ 0.000982] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Feb 13 11:54:14 2009 [01:35] isn't that it there? [01:39] ah yes, it is there in my log too [01:39] d'oh! i should probably get some sleep [01:41] :-) [02:40] glatzor? [02:41] bryce, hi how i can see the displayconfig-gtj dependences ? [02:41] s/gtj/gtk === bluesmoke is now known as Amaranth === bluesmoke_ is now known as Amaranth [08:18] hello [08:23] mvo: hello! [08:23] hey seb128 [08:28] seb128: I take brasero and gnome-terminal for a start [08:28] mvo: danke [08:28] I take evolution-data-server and evolution [08:28] lut crevette [08:28] salut [08:28] didrocks: hello, want some work? I got libs updates for you ;-) [08:32] seb128: hi :) and yes ;) [08:32] seb128: thanks for all the sponsoring you did yesterday but you have to sleep, you know :) [08:33] seb128: I think you forgot gnome-python (just pass it to whishlist) [08:33] and gnome-python-extra is waiting for libgda [08:33] talking about libgda :p, hey huats! [08:33] didrocks: no I didn't, I was not sure if you moved it to the right component or was still junk to use [08:33] morning everyone [08:33] I knew you were talking about me... [08:33] lut huats [08:34] hey seb128 and didrocks [08:34] huats: in a bad way, of course :) [08:34] the gda update is ready just need to test it (which is not obvious) [08:34] didrocks: because you can say nice word about me ? [08:34] huats: as usually :) [08:34] seb128: gtksourceview2, gucharmap and gnome-syste-monitor are on they way too.... [08:34] usual* [08:35] (well if you haven't done one of them...) [08:35] seb128: let me check for gnome-python [08:35] huats: I did upload gucharmap and gnome-system-monitor yesterday night [08:35] ok === BugMaN1 is now known as BugMaN [08:35] huats: did you start on those? [08:35] seb128: I was trying to find you yesterday but I didn't... [08:36] yeah but it is not a big deal... I didn't spend a lot of time... (it was more a parallele task) [08:37] seb128: don't worry I'll take care of the gcalctool this morning in order to dry my tears :P [08:37] didrocks: there is also gnome-games if you want [08:37] huats: want other updates? [08:37] why not... [08:39] didrocks: yes, I can handle it, and what about the lib updates? [08:39] seb128: there is no gnome-python project [08:39] bzr: ERROR: Invalid url supplied to transport: "lp:~didrocks/gnome-python/ubuntu": No such project: gnome-python [08:40] seb128: just a question you had to do a MIR for libgirepository right ? [08:40] huats: that doesn't seem ot be a convinced ping, just let me know when you are done with your updates and you want new ones [08:40] huats: no, why? [08:41] no no I was kidding... give me some updates :) [08:41] didrocks: we should ping jcastro do fix that ;-) [08:41] jcastro: hello? [08:41] because it seems to me that it was a bdeps of one of the update (gucharmap or gnome-system-monitor) [08:41] (something new) [08:42] huats: gucharmap can build bindings using gir but that's not a requirement [08:42] seb128: you joined at 9:18. Tsss. That's so late! [08:43] vuntz: do you ever sleep? you uploaded tarballs until 6am [08:43] vuntz: seb128 sponsored a lot of work very late, you know? :) [08:43] * vuntz should really roll his panel tarball [08:43] seb128: ok [08:43] seb128: I decided to not answer this question today ;-) [08:43] ok, not at 6am :p [08:43] vuntz: I'm a bit disapointed that neither session storing or the session dialog theming have been fixed though, stop slacking! [08:43] like I said I had a rought look at it.... [08:43] seb128: session storing: I'm pinging lucasr for his patch [08:44] seb128: session dialog theming: well, you know who to ask... [08:45] vuntz: I pinged him on IRC but got no reply, will try again ;-) [08:45] vuntz: did you find mvo for your gconf question yesterday? [08:46] didrocks, huats: btw, congrats for the MOTU promotion! [08:46] seb128: so what about those updates ? ;) [08:46] vuntz: thanks ! [08:46] huats: http://download.gnome.org/sources/eog/2.25/eog-2.25.91.tar.gz [08:46] ok seb128 [08:46] seb128: hrm, no. But I think you guys should patch the code to not use gconf.xml.system and use gconf.xml.defaults (since they are both for the exact same use case) [08:46] didrocks: http://download.gnome.org/sources/libgtop/2.25/libgtop-2.25.91.tar.gz [08:46] huats: [08:47] http://download.gnome.org/sources/gtk-engines/2.17/gtk-engines-2.17.3.tar.gz [08:47] seb128: (and because you're stuck with gconf.xml.defaults forever for compatibility) [08:47] vuntz: you know it is mainly thanks to the whip of seb128.... [08:47] huats: and then people will say again and again that french people love whips... [08:47] :) [08:47] seb128: ok. I will do it once gnome-games is ok [08:47] vuntz: I think we misunderstood the way it was supposed to work [08:48] vuntz: to what change did you look exactly yesterday? to the gconf path we are using? [08:48] vuntz: anyway having extra paths in the list doesn't cost much I think [08:48] vuntz: and thanks ;) [08:48] seb128: yeah, looking at your gconf path. It all looks fine. We do the same thing in openSUSE [08:48] seb128: it's just meaningless to have both gconf.xml.system and gconf.xml.defaults [08:49] right [08:49] (potentially harmful too since it's confusing for a sysadmin) [08:49] I was discussing with halfline yesterday on how to move all this upstream [08:50] so the code now uses gconf.xml.defaults? [08:50] seb128: no, the code uses gconf.xml.system. That's a fedora-ism, because it was developed by a fedora hacker [08:50] seb128: if you or I had written the code, we'd have used gconf.xml.defaults [08:51] seb128: because that's how our gconf path is set [08:51] I see [08:51] we need dconf ;-) [08:51] anyway, you can do whatever you want. I know I will patch gconf.xml.system out in openSUSE ;-) [08:51] I'm pondering what to do now due to upgrades [08:52] well, since the only user of the gconf PK stuff in 2.24 was gnome-power-manager, and since it was broken (!), nobody was able to use gconf.xml.system [08:52] so it's still time to kill it ;-) [08:53] not in ubuntu [08:53] the gconf was added by mvo because he used that to set the system proxy key [08:53] bad him [08:53] slap him hard [08:53] lol [08:53] * seb128 hugs mvo [08:54] mvo: I still love you, of course [08:54] vuntz: oh, was that not the right way to do it? [08:55] huats: undo gtk-engines it has been done already by somebody else [08:55] * mvo reads backlog [08:55] seb128: ok [08:58] hmm; when linking libindicate, I get [08:58] /home/martin/ubuntu/dx/indicator-applet-ubuntu/libindicate/listener.c:699: undefined reference to `g_memory_input_stream_new_from_data' [08:59] do I explicitly need to -lgio? [08:59] PKG_CHECK_MODULES(LIBINDICATE, glib-2.0 >= $GLIB_REQUIRED_VERSION [08:59] gio-2.0 >= $GIO_REQUIRED_VERSION [09:00] so that should be ok, in theory? [09:01] pitti: in theory you need to add the flags in your makefiles too [09:01] hm, somehow this is totally wrecked, nevermind for now [09:01] vuntz: I'm pretty sure that when I did that change, our default config would not allow me to do system settings modification. I use the dbus "org.gnome.gconf.defaults.set-system" stuff for it [09:01] vuntz: might be a issue with a early implementation of this interface of course :/ [09:01] mvo: sure. The thing is that in an ideal world, you should have patched the PK helper to use gconf.xml.defaults instead of gconf.xml.system [09:02] mvo: (which is hard to know, I'll admit ;-)) [09:02] vuntz: thanks for this information :) [09:03] mvo: now the questions are "is it too late? Does that matter now that we have one release with it?" [09:03] mvo: and I'll let you decide [09:03] pitti: do you have a -lglib2.0 on the ld line? [09:03] seb128: fwiw, I forgot to explicitly mention it in NEWS, but the change in libgweather is because of tzdata 2009a. Don't know if you have it in jaunty [09:04] seb128: no, but /usr/lib/libglib-2.0.so (totally wrecked) [09:04] seb128: I think that's probably it [09:05] seb128: oh, hang on, it is there for the libtool call [09:05] /bin/bash ../libtool --tag=CC --mode=link cc -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -g -O2 -g -Wall -O2 -version-info 0:1:0 -no-undefined -export-symbols-regex "^[^_].*" -Wl,-Bsymbolic-functions -Wl,-z,defs -Wl,--as-needed -o libindicate.la -rpath /usr/lib libindicate_la-server.lo libindicate_la-listener.lo [09:05] libindicate_la-listener-marshal.lo libindicate_la-indicator.lo libindicate_la-indicator-message.lo -L//lib -lgdk_pixbuf-2.0 -lm -lgmodule-2.0 -ldbus-glib-1 -ldbus-1 -lgobject-2.0 -lglib-2.0 [09:05] seb128: I think that's just missing a -lgio then ? [09:05] vuntz: I check it out, thanks again [09:06] pitti: right [09:06] pitti: you need to use $(LIBINDICATE_LIBS) somewhere in your Makefile.am I think [09:07] pitti: and $(LIBINDICATE_CFLAGS) maybe too [09:07] libindicate_la_LIBADD = \ [09:07] $(LIBINDICATE_LIBS) [09:08] it does [09:08] * pitti just appends -lgio-2.0 and leaves the proper fix to ted [09:09] pitti: grep LIBINDICATE_LIBS Makefile.in? [09:09] pitti: is the source downloadable somewhere? [09:09] vuntz: hm, I may be a bit slow, but do I need to change this in our code or in the gconf wrapper? because afaics all I do is using org.gnome.GConf.Defaults and calling "SetSystem" on it? I don't see (currently) that I can do it from my code [09:10] seb128: https://edge.launchpad.net/indicator-applet/+download, indicator-applet [09:10] seb128: nevermind for now, I'll apply the quickfix and ask Ted [09:10] works now [09:12] mvo: https://api.opensuse.org/public/source/GNOME:Factory/gconf2/gconf2-pk-default-path.patch?rev=c9daf410c2d59d940c81b060cdaa9238 [09:12] mvo: that's the patch I have in openSUSE [09:12] cool, thanks vuntz [09:13] vuntz: will that go upsteam too? [09:13] mvo: and if you need to double check, /etc/gconf/2/path is changed like this: https://api.opensuse.org/public/source/GNOME:Factory/gconf2/gconf2-schemas-path.patch?rev=c9daf410c2d59d940c81b060cdaa9238 [09:13] mvo: I've talked with halfline yesterday about it [09:13] IIRC mclassen wrote the gconf interface, no? [09:14] mvo: I think he's more or less convinced that upstream should adopt what Debian/openSUSE/Ubuntu are doing (since we're doing the same thing) [09:14] heh .) [09:14] good [09:14] mvo: so this will hopefully end up upstream. But in 2.27 [09:14] I think I apply the patch, I will just need the old location until the next LTS :/ [09:14] (for backward compat) [09:15] mvo: well. It's really up to you. Maybe it's simpler for you now to not use this patch. I'd say it's broken, but most people won't notice anyway [09:15] "most people" as in "99.9999%" [09:15] pitti: builds fine for me [09:15] okay, make that "99.99%" [09:16] vuntz: heh .) ok [09:16] * mvo scratches his head about it [09:17] mvo: if it helps you: if I were you, I'd use the patch to try killing gconf.xml.system harder. It's a one-line patch used by at least one other distro. [09:17] mvo: but I'm not you ;-) [09:17] and I'm biased [09:22] pitti: dunno where you got your pkg_config line, the tarball has [09:22] PKG_CHECK_MODULES(LIBINDICATE, glib-2.0 >= $GLIB_REQUIRED_VERSION [09:22] gdk-pixbuf-2.0 >= $GDK_PIXBUF_REQUIRED_VERSION [09:22] dbus-glib-1 >= $DBUS_REQUIRED_VERSION) [09:23] seb128: weird, I have gio-2.0 there, too [09:23] pitti: adding a gio-2.0 line in there fixes the issue [09:24] pitti: ok so we don't have the same version, I did add gio line, ran autoconf and automake and now the Makefile.in LIBINDICATE_LIBS lists -lgio-2.0 [09:24] seb128: aaah [09:24] seb128: that change is in the packaging branch, but not in the tar.gz [09:24] seb128: so a mere autoreconf should do it [09:24] pitti: you probably need to run autoconf and automake then [09:24] pitti: right [09:27] vuntz: I trust you (famous last words ;) [09:27] seb128: new gconf is comming [09:27] mvo: thanks! [09:27] * mvo hugs vuntz [09:33] "debian/patches/05_from_vuntz_gconf2-pk-default-path.patch" [09:33] :) [09:35] ahah [09:36] positive way to see it: "yay, I get the credit!" [09:36] negative way to see it: "if it's wrong, everybody will know it's my fault" [09:36] vuntz: everybody knows that GNOME being broken is your fault anyway [09:41] waouh [09:41] the new title edition in launchpad is cool ;-) [09:44] seb128: yeah it's really fun :) [09:44] new title edition ? [09:44] crevette: try to edit a bug title, for instance [09:44] (on edge) [09:45] seb128: is it inline edition? [09:45] vuntz: yes [09:45] ah okay [09:45] vuntz: how do you know? ;-) [09:45] I look the little red animation when you cancel the edition :) [09:46] seb128: don't know. Just makes sense. [10:05] seb128: indicator-applet uploaded to NEW [10:06] pitti: do you want me to do review? [10:06] seb128: if you have some time, that'd be great [10:06] pitti: ok, doing that next [10:09] pitti: I managed to fix two additionnal bugs in abiword's packaging which made documentation unusable [10:09] I'm doing a last test build and will attach to LP [10:10] jeromeg: cool, thanks [10:10] I will forward my fix to debian later, so that we don't divert too much [10:12] pitti: ENOTINTHEQUEUE [10:13] pitti: are you reviewing the abiword update? I was going to give it a look but I don't want to dup work [10:14] seb128: I'm doing a last test build and will attach and improved package fixing 3 additionnal bugs [10:14] jeromeg: ok [10:14] seb128: abiword> not today, I'm afraid; dx team packaging, meeting, 8th anniversary with my wife this evening.. [10:14] pitti: oh, happy anniversary ;-) [10:14] pitti: yeah, busy day for me too, new GNOME, dx team, meeting ... doh need to send activity report! [10:15] seb128: queue> weird, I uploaded it, and no reject mail so far [10:15] pitti: still not there but there is one less item now so maybe somebody else is cleaning [10:15] well, I should have gotten a NEW mail [10:15] ah, there it is [10:16] got caught in the :15 run [10:16] ok, it's in the queue [10:16] * seb128 fetchs it [10:20] mpt: hello, could you give me your opinion on the "auto_launch" update-manager feature. how should it behave on the development release? should we have a "7 days for regular updates until its started" policy here too? [10:21] pitti: ok, package looks all fine to me, accepted [10:22] mvo, that's more of a managerial sort of decision [10:22] seb128: thanks [10:22] pitti: the .schemas is weird but I will ask ted about that later that's a detail [10:22] mvo, because if you have the 7-days-between-updates working during the alpha/beta, testers aren't receiving updates as often as they probably want to [10:22] * mvo looks up "managerial" [10:22] ok [10:22] seb128: could you possibly move xfce4-notifyd and xfswitch-plugin out of new ? [10:23] mvo, but if you have daily updates during the alpha/beta, you won't get testing of the code that tests that updates during the release are weekly :-) [10:23] yeah :) [10:23] I guess I make it two days for now [10:23] jeromeg: I don't plan to spend too much time on NEW today I've lot to do, let me have a quick look to see if those are easy ones [10:23] mvo, so if you're quite confident of the code that makes updates weekly, then make it daily during the testing period [10:23] so that the interval codes get testing [10:23] ah, good idea [10:24] seb128: we took them from debian svn, it should be safe [10:24] do you think we should treat outside updates (from external repository) different? or just apply the same interval on them as well (on a stable release) ? [10:24] mvo, and set yourself at least one reminder alarm to change that period before the freeze :-) [10:24] seb128: Corsac will upload them to debian in the next few days [10:25] mpt: reminder> yes [10:25] mvo, I don't know. Are there examples of external repositories that change very often? I suppose heavily-in-development PPAs might. [10:26] mpt: I'm not sure, I guess there are some but I don't know how much flux there is. sounds like something I should ask on ubuntu-devel-discuss or ubuntu-devel [10:26] mpt: to gather some data on it [10:27] jeromeg: xfswitch-plugin accepted, xfce4-notifyd is not good [10:27] jeromeg: xfce4-notifyd sources a GPL2 and the COPYING in GPL3 [10:27] a -> are [10:28] arg [10:28] " * This program is free software; you can redistribute it and/or modify [10:28] * it under the terms of the GNU General Public License as published by [10:28] * the Free Software Foundation; version 2 of the License ONLY." [10:28] seb128: ok, thank you very much for the review [10:28] you're welcome [10:28] I'll fix this asap [10:28] thanks [10:30] tseliot: SimpleGladeApp.py is LGPL in xorg-options-editor-gtk and the tarball has no LGPL copy and the debian copyright doesn't list this one [10:39] bryce: 330108 -> please ack this sponsoring [10:48] seb128: what do you suggest that I do? Shall I add another license file or simply add LGPL to the current COPYING file? [10:48] seb128: and maybe explain it all in the README? [10:49] tseliot: add a COPYING.LIB or similar which has the LGPL copy and list in the debian copyright [10:49] tseliot: you need to ship the texts for the license you use and the copyright needs to list those [10:50] seb128: ok, I'll do it and I'll update my bzr branch [10:51] thanks [12:13] seb128: about xfce4-notifyd, if I patch COPYING with upstream's agreement, is that enough ? [12:17] jeromeg: can't you get them to roll a new tarball with a fixed license? [12:18] seb128: I'll see what I can do [12:18] jeromeg: if they fix it to their vcs I guess patching for the current version until the next tarball come is ok [12:18] ok, that should be easier :D [12:19] well if they want their software distributed they should be conciliant and roll a new tarball ;-) [12:20] pitti: is your ssh agent working again with the gnome-keyring uploaded yesterday? [12:20] seb128: sure [12:23] seb128, thanks for gwibber. i'll clarify that with upstream [12:23] fta2: you're welcome [12:24] seb128, could I re-up with a fixed tarball but using the same upstream version? or will it be rejected because of md5 mismatch? [12:26] seb128: "again"? It never stopped working [12:26] pitti: I though it broke for you during the sprint when I uploaded the version which fixed the timeout issue [12:27] pitti: we got several bugs about the ssh agent being broken in 2.25.90 [12:27] asac: ^ does it work for you now? [12:27] fta2: you can reupload the same version, the other one has not been accepted or published [12:28] seb128: dont have 64bit system at hand right now. dholbach also saw this [12:28] asac: that was 64b specific? [12:28] it always worked on 32bit [12:28] seb128: yes i think so [12:29] asac: ok, you didn't tell me that or I didn't note the information ;-) [12:29] seb128: oh, during the sprint, yes [12:29] seb128: it has worked again for a long time [12:29] seb128: sorry. i think dholbach noted that in the bug [12:30] pitti: ok [12:31] asac: I've pinged dholbach and mdz who had the issue too [12:34] mpt: everything should auto-launch, no notification area applets at all? so apport will auto-launch on login (if needed) and reboot required comes up too? [12:35] mvo, the "restart required" is update-notifier, correct? that should come up automatically [12:35] Does apport use notification bubbles? [12:35] I didn't notice that [12:38] mpt: apport uses a notiifcation icon for crashes that happened for system processes [12:38] mpt: or that happend while noone was logged in [12:39] mvo, just an icon and no bubble? That's fine for now [12:39] mpt: so when the user clicks on it he may get a gksu style dialog first to access the crash [12:39] mpt: it also contains a bubble that just tells about the crash report [12:40] ergh [12:40] What's the exact text of the bubble? [12:40] (Thanks for thinking of that case!) [12:40] http://paste.ubuntu.com/119190/ [12:41] "Click on the notification icon to " [12:41] rats [12:42] And we can't stuff explanatory text into the gksu dialog, can we? [12:42] you are not suggesting auto-opening a gksu dialog right? [12:42] probably not :-) [12:43] ok good ;-) [12:43] mpt: I guess we could but it would be a bit inconvinent to login and get a dimmed screen [12:43] exactly [12:44] hm [12:46] mvo, what would be the impact of nuking both the icon and the bubble? [12:47] -> not providing graphical access to crash reports of system processes [12:47] -> ...? Who uses that? [12:47] mpt: nuking the bubble woudl make it less discoverable, nuking the icon means we don't get bugreports for this type of crashes anymore [12:47] lot of users looking at launchpad [12:47] all the installation issues are reported this way [12:48] hm, ok [12:48] mvo: I would not say no to less installation issues bugs though ;-) [12:49] * seb128 runs away from mvo quickly [12:49] * mpt thinks seb128 is confusing bugs with bug reports ;-) [12:49] I guess it should be a preliminary alert that segues into the gksu one, ugh [12:49] until we have a nice Crash Reporter utility thingy [12:50] ok, I'll write this up [12:53] mpt: that may not make it to FF, I mean, there is *very* little time already and I need to finish more than just the UX team changes. adding more code is going to make it even more difficult (unless I get a FF expection for this) [12:54] mvo, do you have an alternative suggestion? [12:54] mpt: just showing the icon and not the bubble and hoping the user discovers it on his own (sorry, not a very good one I guess) [12:55] mpt: please still draw the suggestion you have, but its going to be difficult to meet the deadline [12:55] mvo, ok, the icon only would be tolerable [12:55] I'll mock up the alert now [12:56] thanks [13:02] mvo, maybe bratsche could take care of apport instead [13:06] mvo: so does the user see partner apps in update-manater? [13:06] asac: sure, why not? [13:08] mpt: sure, the code is in update-notifier bzr: src/crash.c - the recent commits should be good templates in what needs to be changed [13:08] mpt: I will leave that change out and upload what I have now and let him add the required code [13:09] thanks mvo [13:09] mpt: will you be able to write a mail to ubuntu-devel asking for opinions about if we need a special interval for third party repos (like PPAs) or if 7 days is good for those as well [13:09] ? [13:09] mvo, wait, src/crash.c is in update-notifier? Not in apport? [13:10] mpt: correct, update-notifier acts as the messanger, it detects the files and calls apport [13:11] (update-notifier should really be named event-notifier) [13:11] ok [13:17] mvo: i am not sure why not. because its not enabled? [13:17] mvo: so are the partner apps visible in update-manager or not? ;) [13:20] asac: partner apps are only visable when the partner repo is enabled and a partner app is installed [13:20] asac: but then they will show up just fine [13:20] mvo: ok [14:12] seb128: looking for me? [14:13] jcastro: hello [14:13] jcastro: could you create a gnome-python component on launchpad? ;-) [14:14] yessir! [14:14] thanks ;-) [14:14] I have something for you seb128 [14:14] https://code.edge.launchpad.net/lp-upstream-tools [14:14] I am announcing this on the bugs list later today [14:15] it will let you mass open upstream tasks [14:16] cool, will try that later [14:16] I'm busy with GNOME updates right now [14:16] no worries [14:17] hey tedg [14:17] seb128: Good morning. [14:17] tedg: I cc-ed you on a sponsoring request for fast-user-switch-applet, the change seems to be quite some good work if you could give it a review [14:17] seb128: Cool. I'll look at it. [14:17] thanks [15:04] hey tedg [15:05] pitti: Morning, going through your mail :) [15:22] vuntz: gnome-panel 2.25.91 fixes the vertical notification area issue (and a similar one with the clock applet when showing the weather) [15:24] seb128: is there a known issue with gnome panel locking up when attempting to access the clock applet? [15:24] seb128: its happening to me all the time :\ [15:24] calc: yes, http://bugzilla.gnome.org/show_bug.cgi?id=570765 [15:24] Gnome bug 570765 in Calendar "gnome panel hangs after clicked on the clock applet" [Critical,New] [15:24] seb128: ok thanks [15:25] calc: you are welcome to try the patch one the bug if you get the bug all the time and tell us if it fixes the issue [15:25] calc: that's a one line and I will probably upload to jaunty later today [15:25] vuntz: ^ do something! [15:27] seb128: ok, i'm pretty busy today but if i have a chanse before its uploaded i will look at it [15:33] hey calc [15:36] ugh, our gpm package is a patch swamp [15:36] seb128: what can I do if it's an eds bug? [15:38] vuntz: well whatever e-d-s do the clock should not hang, no? [15:38] vuntz: there is an e-d-s bug for sure but the clock not handling e-d-s crashes is a bug too [15:38] pitti: talk to tedg ;-) [15:40]