=== asac_ is now known as asac [03:04] hmm the new notify-osd breaks the synchronous notifications in gsd and gpm [03:07] how do you mean? [03:09] LaserJock: 0.8 had a capability called private-canonical-1 and private-canonical-2. the patches for synchronous notifications in gsd and gpm both search for those capabilities [03:09] LaserJock: 0.9 removed both private-* capabilities, and added one new one -- private-synchronous [03:11] LaserJock: correction -- gsd and gpm both search for canonical-private-1 [03:48] who's maintaining the gsd and gpm patches for notify-osd? [06:47] morning === tjaalton_ is now known as tjaalton [07:34] Good morning [07:41] hey pitti o/ [07:42] pitti: it has already been sponsored, but I only want your opinion in this workflow: https://code.edge.launchpad.net/~didrocks/glibmm2.4/ubuntu [07:42] I hope I followed successfully what you told me yesterday :) [07:44] didrocks: by and large, yes, great! [07:44] comment to 5 http://bazaar.launchpad.net/%7Edidrocks/glibmm2.4/ubuntu/revision/5 [07:44] didrocks: usually the changelog should be in the "new upstream release" commit, but that's only a nit, and it's okay [07:45] pitti: you mean the "* New upstream release" line? [07:45] didrocks: yes, in above commit you added the description of the new upstream release [07:46] pitti: ok, I just added "* New upstream release", but not the full description of the release. But I can add "* New upstream release" in the last commit as well :) [08:04] didrocks: no, don't [08:05] didrocks: the commit where you actually upgrade to the new upstream release should also have that changelog [08:30] pitti: so, if I understood well, you prefer having the full changelog of the new releasing (typically the content of NEWS file) in the first commit, with "* New upstream release", right? [08:31] hi seb128 [08:31] hello didrocks [08:31] didrocks: yes, it's a bit cleaner; but as I said, it's really just a minor nit, the way you did it works, too [08:31] * seb128 didn't sleep enough again [08:31] seb128: you went to bed so late? [08:32] 2:30am [08:32] pitti: ok, thanks, I will update the desktop bzr wiki page so :) [08:32] dunno if that's so late but that's a bit of a short night for my taste ;-) [08:33] pitti: guten tag! [08:33] didrocks: a slightly better way would be to commit the new changelog separately as "add upstream news to changelog", debcommit, and then dch -r/debcommit -r [08:33] seb128: bonjour Monsieur! [08:33] pitti: I sponsored kenvandine_wk's change for the evolution indicator and the oem scrollbars changes too [08:34] seb128: I saw the evo changelog; you rock [08:35] seb128: ourgh, yeah... you slept more than me but it's not so much... (Personnaly, I have to wake up at 6:00 AM to go to my company, with no salary raise for anybody this year, even if it the objectives have been reached. You can feel my mood now :/) [08:35] pitti: ok, will try that [08:35] didrocks: yeah ... [08:38] didrocks: you can do the gnome-games update later if you want btw [08:38] seb128: ok, I am used to this package now :) [08:38] ;-) [08:40] lut crevette [08:40] bonjour [08:40] didrocks: btw to count sleep I got up at 8am not when joining IRC ;-) [08:42] seb128: oh ok, so I understand 5h30 -> same than me \o/ [08:42] that's french standards? ;-) [08:43] seb128: we have to ask to huats too ^^ [08:44] didrocks: he seems to be busy for a week now, I've not seem him around a lot, I'm wondering if I should assign the gcalctool update to somebody else [08:45] lool: hello [08:45] seb128: Hi [08:46] lool: your gtk changes means we can relibtoolize using libtool2 now? ;-) [08:46] seb128: What used to break for you? [08:47] seb128: I completed full builds after the po-properties fixes, from SVN; so I think jaunty's toolchain should work ATM [08:47] lool: "ignoring invalid character `\001' in script" [08:47] seb128: Yes, that's what was fixed, it should work again now [08:47] lool: that you mentioned in bug #332840 [08:47] Launchpad bug 332840 in gnulib "$(SHELL) config.status broken" [Undecided,In progress] https://launchpad.net/bugs/332840 [08:47] lool: ok good, thanks a lot for tracking since [08:47] seb128: he was ill last week and very busy yes. I talked a little bit with him yesterday (I really have to call him) and his schedule is tight. If you want, I can do this update (I will just talk to him before, if it's the case). As you wish :) [08:47] lool: I was still using libtool 1.5 to relibtoolize gtk to workaround this error [08:47] seb128: It's unfortunate we didn't notice earlier, it seems intrepid is affected as well :-/ [08:48] didrocks: ok feel free to ask him when you have him on the phone there is no hurry [08:48] seb128: no pb [08:48] seb128: You know I'm really happy to know what broke it (libtool) because I really couldn't figure out; I suspected autoconf and dash! [08:48] lool: I did notice and asked Keybuk but never spend the required hours to figure what was the issue [08:48] It's not libtool's fault at all, but some update had exposed the breakage, I had no idea which one; now I know it was libtool :) [08:49] I could have told that :-p [08:49] seb128: Turned out to be a common bug; and you can easily hit it with almost all GNOME packages [08:49] I do downgrade libtool to 1.5 to workaround the issue for a while ;-) [08:49] never got it in other packages [08:49] seb128: Something like touch po/POTFILES.in in any GNOME package after configure and you will break the build there too [08:49] but we don't relibtoolize glib for example [08:49] So if you e.g. patch a lang in, you might hit it again [08:50] And the only way to fix it is to wait for all projects to release again with a newer glib-gettext + newer intltool [08:50] (The borken Makefile.in.in is copied in all GNOME tarballs) [08:55] seb128: Hmm there's something broken with the remote bug watches isn't it? The bug has a gtk+ task linked to a bug which has been resolved on GNOME's side, but the launchpad status still says "Unknown" [08:55] yes, they are not updated often enough [08:56] I didn't bother yet but somebody should ping #launchpad I guess [09:09] morning everyone [09:10] lut huats [09:10] hey seb128 [09:10] huats: how are you? I was just asking about you to didrocks ;-) [09:10] even if I am running out of time, I will at least do the gcalctool update ;) [09:10] I am getting better [09:10] thanks ! [09:10] how are you ? [09:11] good thank you! [09:11] no pb [09:11] didrocks: ^ he will do the update [09:12] I also have anjuta to finish (I had a running 2.25.902 but the 2.25.903 is out so I will update it) [09:13] ok [09:13] I hope that later this week I will have ore time to do packaging stuffs... [09:13] (I will) [09:13] better to get what you have uploaded and then work on the next update than getting lot of version changes late in the cycle [09:13] exactly [09:13] ok [09:13] I will do that then [09:17] seb128: and btw thanks for taking care of gnome-keyring and seahorse yesterday... [09:19] Does anyone can remember me URL of the documentation to put a package into bzr ? [09:19] huats: didrocks does for sure and you are welcome for the updates ;-) [09:20] huats: you have some stuff to do to ubuntu-fr too :p [09:20] I am sure that didrocks knows that ... but he didn't asnwered me privately [09:20] :) [09:20] seb128: yep, noted. I will try to tackle gnome-games within the day :) [09:20] didrocks: I am sure I have [09:20] I will take care of them too [09:20] huats: maybe you need to ask nicely? ;-) [09:21] huats: I have a work too :) [09:21] didrocks: luckly you, I don't :P [09:21] huats: https://wiki.ubuntu.com/DesktopTeam/Bzr, Vcs-Bzr: https://code.launchpad.net/~ubuntu-desktop//ubuntu [09:21] well sort of :) [09:22] huats: you choose :p [09:22] thanks didrocks [09:22] you're welcome [09:24] seb128: there were no "please" in the sentence. I have a filter :p (cf ML discussion) [09:24] you mean "there is huats in the sentence and you have a filter for that too"? ;-) [09:25] :) [09:25] seb128: exactly :) [09:40] seb128: I think I must avoid to update things after midnight (typo & SHVER ;)) [09:41] didrocks: yeah ;-) [09:41] hello MacSlow mvo_ [09:43] yo funky bunch! [09:43] seb128, mvo's tail is showing ;) [09:55] hey seb128 [09:57] * pitti hugs MacSlow and mvo [09:57] pitti, alter Schwede! [09:58] pitti, you and dbarth were busy getting the latest notify-osd going :) [09:58] I never will underestimate to land code in a package! [10:01] heh [11:15] does anyone know how I can prevent a window from getting a close button? [11:16] gtk_window_set_deletable (GTK_WINDOW (unmount_flush_window), FALSE); [11:16] I tried that, but it doesn't work [11:16] I also tried [11:16] gdk_window_set_decorations (unmount_flush_window->window, GDK_DECOR_BORDER|GDK_DECOR_TITLE); [11:16] but that says that window is not a GdkWindow [11:17] (gnome-mount:3944): Gdk-CRITICAL **: gdk_window_set_decorations: assertion `GDK_IS_WINDOW (window)' failed [11:17] that in particular [11:17] why do you want to do that? [11:17] seb128: https://wiki.ubuntu.com/NotifyOSD#gnome-mount [11:17] for now I used gtk_window_set_decorated(), but then I don't have a title bar at all [11:17] which looks fine, too, though [11:18] there is nothing there which says the dialog shouldn't be closed? [11:19] I'm not sure why you want limit that user choice [11:19] pitti: gdk_window_set_functions() [11:20] mvo_: won't that have teh same GDK_IS_WINDOW (window)problem? [11:20] mpt: help [11:20] pitti: have you run "gtk_widget_realize()" on it (or _show()) before you run the gdk_ function? [11:21] mvo_: not ATM [11:21] "Depending on the system, this function may not have any effect when called on a window that is already visible, so you should call it before calling gtk_window_show()." [11:21] oops, that's for set_deletable() [11:21] pitti: please try that then, gtk creates the gdk window only on first show or relaize [11:22] mvo_: moved; it doesn't barf any more, but doesn't work either [11:22] * pitti tries set_functions instead of set_decorations [11:22] pitti: which one, the "set_functions()" does not have any effect or the "set_decoration()" (or both) ? [11:22] aha [11:23] :) [11:23] . o O { that looks quite redundant.. } [11:24] a-haa [11:24] * pitti hugs mvo [11:24] thanks [11:24] cheers :) [11:24] * mvo_ is still desktop team material ;) [11:28] hey pitti, you're taking the gnome-mount changes? [11:28] davidbarth: yes, currently working on them [11:28] pitti: great! [11:28] I'll followup on the bug [11:28] davidbarth: I won't change all strings yet, though, that should really be coordinated with upstream [11:28] anyway, discussion -> bug [11:47] * pitti finds it utterly weird though, that we invest many resources in writing proper notifications, and then invest resources in rewriting programs to not use them any more.. [12:02] james_w: I don't want to nag, but is there anything new in the bzr-buildpackage act odd with python2.6 bug? anything I can do to help? [12:03] mvo_: I have a fix, just preparing the stuff for an FFe [12:03] I didn't want to take time out to upload a fix [12:03] I can do it if it is urgent [12:03] james_w: if its in a bzr tree somewhere thats fine [12:04] you probably don't need an exception for bug fix changes [12:04] james_w: then I will just check it out myself [12:04] seb128: I've been busy :-) [12:04] heh :) [12:05] james_w: https://code.edge.launchpad.net/bzr-builddeb shows all branches are a couple of days old, is the fix not pushed yet? [12:05] mvo_: just pushed to lp:~james-w/bzr-builddeb/2.1 [12:05] james_w: excellent, thanks again [12:07] mvo_: want to do the new g-c-c version update? ;-) if you are busy don't bother I will do it after lunch [12:09] seb128: I'm going for lucnh now/soon too and I'm pretty busy with some other stuff. I could try to queeze it in though [12:09] pitti, either "ironic" or "tasteful", take your pick :-) [12:10] Programs were overusing notification bubbles [12:10] mvo_: no that's ok if you are busy I will do it [12:14] james_w: can you give me a overview about the pristine tar stuff? is that what we should use for the non-native branches (e.g. the gnome-control-center branch etc)? [12:15] mvo_: is it debian/ only? [12:15] mvo_: if you do g-c-c it's on ubuntu-desktop now [12:16] james_w: yes [12:16] seb128: thanks [12:16] mpt: okay, I uploaded the first patch, added comments to the LP bug and also forwarded it upstream (maybe David considers adopting it, which would ease matters a lot) [12:16] mvo_: then you lose :-) [12:16] james_w: hm [12:16] mpt: it's not perfect yet, but at least fixes the immediate problem with getting a dialog with buttons [12:16] pitti: what is wrong with having buttons? [12:17] pitti: if you display a dialog I can't close I'm going to be unhappy with you ;-) [12:17] pitti, excellent [12:17] mvo_: there is nowhere tasteful to store the pristine tar data for debian only really. It would be possible, but it would either be binary files in the working tree, or craziness in the revision graph. [12:17] seb128, don't worry, it's not a dialog, it's a progress window ;-) [12:17] seb128: because here https://wiki.ubuntu.com/NotifyOSD?action=AttachFile&do=get&target=gnome-mount-unmounting.png it doesn't make any sense at all [12:17] mpt: same difference, anything which open and I can't close is going to make me unhappy [12:17] seb128: I shouldn't have to close this progress window [12:17] why not? [12:18] if I want to get it out of my way [12:18] seb128: "have to" != "can't" [12:18] seb128: it should auto-close [12:18] seb128, it closes itself after a few seconds, and you can minimize it if you're really impatient. [12:18] when it's donw [12:18] james_w: hm, thanks. I guess I misunderstood the use-case for it then [12:18] mpt: what is wrong with letting user the choise to close things he doesn't want now? [12:18] seb128: I'm absolutely open to adding back the close decoration [12:18] that start being dictating users what to do I and don't like that at all [12:18] seb128: but we shuoldn't have above fallback dialog from notify-osd, since that's just plain wrong [12:18] mvo_: oh, you got the use case correct, it's just hard to implement in this case [12:19] mvo_: it currently only works for full-source branches [12:19] pitti: right, I'm fine with that design, I just don't get why you want to prevent users who want to close the dialog to do so [12:19] seb128, because that would falsely imply you were cancelling the unmount when you can't. [12:19] you do extra efforts to get in the user way [12:19] mpt: no that would, that would imply I know it's syncing and I want it out of my screen because it's noise [12:19] wouldn't [12:20] my ipod screen change when I can unplug it I don't need a dialog on my computer screen too [12:20] seb128: would you still want the next window which says that you can remove it? [12:20] no [12:20] I look at the ipod before unplugging not the computer [12:20] right, I agree [12:20] so *if* we make the dialog close-able, it shouldn't present the followup window either [12:21] I can't think of people who would assume that closing the window would cancel the unmount, but I let myself convince otherwise of course from user-testing data [12:21] iPod's are unusual in that they prominently show mounted/unmounted state. [12:21] but I leave the decision of that "if" to someone else [12:21] er, iPods I mean. [12:21] Most hotpluggable devices don't. [12:21] well, still when the led stops flashing it's ok [12:21] * pitti wishes that all this mess wouldn't be necessary in the first place, and the kernel would offer a sane flushing algorithm [12:21] if I want to close that dialog I should be able to do so [12:24] anyway let's see how it goes but I don't think starting to dictate user their workflow is nice and will work for everybody [12:24] seb128: minimizing isn't enough for you? [12:24] it's still in my way, ie in the tasks list, in the alt-tab list, etc [12:25] I'm not sure what we win by removing the flexibility there [12:26] pitti: and please tell me that I will not have to click on a "ok" button to close the dialog that say than I can unplug my device now ;-) [12:26] seb128: no, that's the very bug I was fixing :) [12:26] ok good [12:26] seb128: right now it looks like https://wiki.ubuntu.com/NotifyOSD?action=AttachFile&do=get&target=gnome-mount-unmounting.png [12:26] seb128: which you *have* to close, and that's totally wrong [12:26] agreed [12:27] seb128: now it looks like http://launchpadlibrarian.net/23359790/cache-flushing.png [12:28] ooh, nice [12:28] pitti: nice indeed [12:28] james_w: I use your branch now, its currently a bit unhappy, http://paste.ubuntu.com/125743/ helped with the compiz tree a bit, but its still not happy [12:28] I like the nautilus way better though [12:28] (modulo that annoying GTK text wrapping bug) [12:28] you can close the copy dialog, it just goes to the notification area ;-) [12:28] seb128: yeah, that's nice, too [12:29] I'm wondering if GNOME has any dialog you can't close right now [12:30] mvo_: thanks, please pull [12:30] pitti, looks like the gap between the progress bar and the "To prevent..." text is a bit large [12:30] mpt: right; that needs some work (it's not that easy to get the exact spacing) [12:31] I don't envy you, Glade annoys me :-) [12:31] pitti, hey, that progress bar is determinate! Did you find a way of calculating the proportion done? [12:31] mpt: but that's not critical for UIF, and I have some other things (like usplash) which are [12:31] mpt: no, it's just a bouncing one [12:31] oh [12:32] see, that's why indeterminate progress bars shouldn't be themed to bounce -- it makes them look unnecessarily similar to determinate ones [12:32] pitti: btw while you are uploading gnome-mount change there is a pending sponsoring request for a typo fix waiting [12:32] seb128: oh, will do that next time (I'm sure I have to touch gnome-mount again soon enough :) ) [12:32] thanks [12:32] * pitti already uploaded, and is now sending his weekly report [12:32] doh, weekly report [12:32] did we get reminder emails? [12:33] not this week apparently [12:33] I didn't, I'm wondering if my spam filtering is too efficient or something [12:33] ok good [12:34] pitti: the current dialog autoclose right? so if you get a flush which takes 0.1 seconds you will see a dialog jumping and vanishing directly? [12:35] james_w: works great now, thanks! [12:35] mvo_: thank you [12:35] seb128: it only starts after 0.75 seconds [12:35] seb128: just like the notification [12:35] ah good [12:35] seb128: so for fast/no flush you don't see anything [12:35] * seb128 hugs pitti [12:35] and for long ones it autocloses, yes [12:36] if you flush takes 0.9 seconds, it looks ugly indeed [12:36] but that's not new, same problem with the notification [12:36] right I was just wondeing if there was a way to estimate the flush time before [12:37] pitti: maybe you can add an artificial timeout to let the user see the dialog? [12:37] let's see how it goes already like this we can do tweaking later [12:37] pitti: when the flush timeout occurs, add an additional 2s timeout [12:37] davidbarth: that's possible [12:38] davidbarth: well, only if the flush took less than 1 second or so [12:38] pitti: for quick flushes, you will only be disturbed for 2s (but will have the time to actually see what's happening) [12:38] pitti: and for longer flushes, you have to wait anyway... [12:38] if it already takes 5, then there's no reason to have an extra 2 [12:38] davidbarth: in fact I used that extra delay for testing :) [12:39] I already have the patch [12:39] pitti: right, so you need to account for the time the dialog has been up [12:39] pitti: hehe, nice [13:08] * kenvandine_wk waves [13:09] morning kenvandine_wk [13:23] hey kenvandine_wk [13:23] hey seb128 [13:23] kenvandine_wk: I uploaded the new evolution version and included your changes [13:23] great [13:23] both bugs? [13:23] kenvandine_wk: yes [13:23] excellent [13:23] thx [13:24] kenvandine_wk: could you open a bug upstream about the action change though? [13:24] you're welcome [13:24] * kenvandine_wk was going to create a debdiff for those today [13:24] yes [13:24] thanks [13:24] * kenvandine_wk does that now [13:38] mvo_: did you or do work on g-c-c? [13:39] mvo_: just asking before doing the update to not conflict [13:44] seb128, evolution still shows me popups instead of nice notifs, do I need to add something? [13:45] fta2: hello [13:45] fta2: did you upgrade and did you restart it? [13:46] both [13:46] so talk to kenvandine_wk who wrote the change [13:46] it works for me [13:46] humm [13:46] i remember you asked me to uncheck a pref last week [13:46] no I didn't [13:46] I said you can disable the upstream one if you want [13:47] fta2: the preference shouldn't matter in the latest [13:47] so it doesn't work for me. i see the ok / cancel dialog [13:48] fta2: echo $GDMSESSION [13:48] oh, just rechecked the pref, now, i have both the dialog and the notif [13:49] kenvandine_wk, default [13:49] default is what it returns? [13:49] fta2: dpkg -l | grep evolution-? [13:49] is there a planned upload of eel2 in the near future? as libeel2-dev is missing a dependency on libgail-dev (gail is referenced in eel-2.0.pc) [13:49] geser: no [13:49] http://paste.ubuntu.com/125773/ [13:50] seb128: no, I was doing compiz (and still am) [13:50] geser: that libary is deprecated and not used in GNOME (or should not it's still there for compatibility reasons) [13:50] mvo_: ok, I will do the g-c-c update then [13:51] fta2: actually, when you configure the mail-notification plugin in evolution, you shouldn't even have an interface to enable the icon anymore [13:52] kenvandine_wk: his issue seems to be the action part and not the icon though [13:52] kenvandine_wk, http://www.sofaraway.org/ubuntu/tmp/Screenshot-evolution-indicator.png [13:52] seb128: I tried to rebuild nautilus-python for the python 2.6 transition and it failed due to this missing dependency [13:52] seb128: but he shouldn't even get that action if he is in the right session [13:53] seb128: okay for me to sponsor bug 329245? [13:53] Launchpad bug 329245 in gnome-settings-daemon "gnome-settings-daemon could use the new notification service" [Wishlist,In progress] https://launchpad.net/bugs/329245 [13:53] geser: could you look at fixing it, do a debdiff and subscribe the sponsor team to the bug? [13:53] seb128: (updated patch by davidbarth) [13:53] pitti: I was going to do this one but sure, make sure to take the version I uploaded before lunch as basis [13:53] seb128: yes, downloading from LP directlry [13:54] pitti: ok, go for it then [13:55] kenvandine_wk: maybe notify-osd broken in the recent update and capability query doesn't work correctly? [13:55] broken -> broke [13:55] works here... [13:55] * kenvandine_wk just updated to make sure [13:56] worked for me too when I tried yesterday, I didn't upgrade my laptop yet so I can't test now [13:56] i just verified the version you uploaded works... seems fine [13:56] fta2: do you get the flashing notification icon? or just the dialog? [13:56] fta2: run evolution from a console [13:56] then go into the plugin configuration and pastebin what is printed on the console [13:57] kenvandine_wk: btw on bugs you can click the also affects project link below the table to add upstream tasks [13:57] kenvandine_wk: could you do it on bug #328596? [13:57] Launchpad bug 328596 in evolution "evolution shouldn't use notifications with actions" [Wishlist,Fix released] https://launchpad.net/bugs/328596 [13:58] what else does it affect? [13:58] upstream evolution [13:58] oh... i see [13:58] adding an upstream tasks will monitor the bugzilla bug status [13:58] cool feature :) [13:58] indeed [13:58] it automatically picked up the watch for it...which i thought was cool [13:58] the upstream task will change when they close or needinfo the bug [13:59] ;-) [13:59] awesome [13:59] seb128: re: notify-osd and gnome-settings-daemon, is this fixed in the next release? https://bugs.launchpad.net/notify-osd/+bug/334292 [13:59] Launchpad bug 334292 in gnome-settings-daemon "New osd-notify notifications should not have an empty title" [Undecided,New] [13:59] eeejay: read what pitti said around 15 ago? [14:00] * eeejay scrolls [14:00] me? [14:00] pitti: I think that's about the fix you want to sponsor [14:00] oh, I've been misleaded by the title [14:00] seb128: the patches I upload (g-p-m and g-settings-daemon) fix the notifications for the new hint names [14:00] and for the eject key [14:00] eeejay: ask MacSlow or davidbarth about notify-osd issues [14:01] eeejay: that doesn't seem to be a bug but a design decision [14:01] pitti: yeah, sorry I have been confused by the title [14:01] * pitti hugs seb128 [14:01] * seb128 hugs pitti [14:02] seb128: they know about the issue, it is needed for correct ATK exposure, MacSlow agreed: https://bugs.launchpad.net/notify-osd/+bug/334292/comments/2 [14:02] Launchpad bug 334292 in gnome-settings-daemon "New osd-notify notifications should not have an empty title" [Undecided,New] [14:03] eeejay: so why do you ask to me? I'm not working on notify-osd [14:03] seb128: because the fix is needed in gst, (ie. the title _("Volume") is needed instead of " ")). [14:04] eeejay: doesn't change the fact that I'm not working on those notify-osd changes [14:05] eeejay: you want to talk to davidbarth or MacSlow really [14:05] MacSlow: davidbarth: could you please bless bug 334292? [14:05] Launchpad bug 334292 in gnome-settings-daemon "New osd-notify notifications should not have an empty title" [Undecided,New] https://launchpad.net/bugs/334292 [14:07] eeejay, there you go [14:09] MacSlow: thanks! i'll do the same for gpm.. [14:09] kenvandine_wk, http://paste.ubuntu.com/125782/ [14:10] davidbarth: hm, the eject notification works now, but it doesn't actually eject; does that work for you? [14:10] fta2: weird... i see more output than that :) [14:11] fta2: the gvfs warning are because you upgraded gvfs but didn't restart your session [14:11] fta2: do you see the mail notification icon in the notification area? [14:11] hey rickspencer3 [14:11] as well as the indicator applet? [14:11] pitti: not sure, i have not test the result of the command [14:11] morning rickspencer3 [14:11] hey rickspencer3 [14:11] kenvandine_wk, no [14:11] good morning seb128 and kenvandine_wk [14:11] fta2: ok... that is really weird [14:11] pitti: but i haven't changed that part of the code and i think i do not exit prematurely [14:11] rickspencer3: FYI, I added my activity report/work items directly to the wiki [14:11] pitti: maybe the code is old and does not work properly [14:11] * davidbarth -> quick lunch [14:12] maddness! [14:12] pitti: eject is buggy for me since a while, I get gnome-mount error dialogs when pressing the eject button on the CD drive usually [14:12] seb128: I mean if I press the eject hotkey [14:12] which is still F12 for me [14:12] looks like seb128 pitti and mvo have been quite busy while I was sleeping this morning! [14:12] which annoys me a lot, but is nice for testing this particualr fix :) [14:13]