[03:04] <hypera1r> hmm the new notify-osd breaks the synchronous notifications in gsd and gpm
[03:07] <LaserJock> how do you mean?
[03:09] <hypera1r> 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] <hypera1r> LaserJock: 0.9 removed both private-* capabilities, and added one new one -- private-synchronous
[03:11] <hypera1r> LaserJock: correction -- gsd and gpm both search for canonical-private-1
[03:48] <hypera1r> who's maintaining the gsd and gpm patches for notify-osd?
[06:47] <didrocks> morning
[07:34] <pitti> Good morning
[07:41] <didrocks> hey pitti o/
[07:42] <didrocks> 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] <didrocks> I hope I followed successfully what you told me yesterday :)
[07:44] <pitti> didrocks: by and large, yes, great!
[07:44] <pitti> comment to 5 http://bazaar.launchpad.net/%7Edidrocks/glibmm2.4/ubuntu/revision/5
[07:44] <pitti> didrocks: usually the changelog should be in the "new upstream release" commit, but that's only a nit, and it's okay
[07:45] <didrocks> pitti: you mean the "* New upstream release" line?
[07:45] <pitti> didrocks: yes, in above commit you added the description of the new upstream release
[07:46] <didrocks> 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] <pitti> didrocks: no, don't
[08:05] <pitti> didrocks: the commit where you actually upgrade to the new upstream release should also have that changelog
[08:30] <didrocks> 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] <didrocks> hi seb128
[08:31] <seb128> hello didrocks
[08:31] <pitti> 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] <didrocks> seb128: you went to bed so late?
[08:32] <seb128> 2:30am
[08:32] <didrocks> pitti: ok, thanks, I will update the desktop bzr wiki page so :)
[08:32] <seb128> dunno if that's so late but that's a bit of a short night for my taste ;-)
[08:33] <seb128> pitti: guten tag!
[08:33] <pitti> 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] <pitti> seb128: bonjour Monsieur!
[08:33] <seb128> pitti: I sponsored kenvandine_wk's change for the evolution indicator and the oem scrollbars changes too
[08:34] <pitti> seb128: I saw the evo changelog; you rock
[08:35] <didrocks> 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] <didrocks> pitti: ok, will try that
[08:35] <seb128> didrocks: yeah ...
[08:38] <seb128> didrocks: you can do the gnome-games update later if you want btw
[08:38] <didrocks> seb128: ok, I am used to this package now :)
[08:38] <seb128> ;-)
[08:40] <seb128> lut crevette
[08:40] <crevette> bonjour
[08:40] <seb128> didrocks: btw to count sleep I got up at 8am not when joining IRC ;-)
[08:42] <didrocks> seb128: oh ok, so I understand 5h30 -> same than me \o/
[08:42] <seb128> that's french standards? ;-)
[08:43] <didrocks> seb128: we have to ask to huats too ^^
[08:44] <seb128> 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] <seb128> lool: hello
[08:45] <lool> seb128: Hi
[08:46] <seb128> lool: your gtk changes means we can relibtoolize using libtool2 now? ;-)
[08:46] <lool> seb128: What used to break for you?
[08:47] <lool> seb128: I completed full builds after the po-properties fixes, from SVN; so I think jaunty's toolchain should work ATM
[08:47] <seb128> lool: "ignoring invalid character `\001' in script"
[08:47] <lool> seb128: Yes, that's what was fixed, it should work again now
[08:47] <seb128> lool: that you mentioned in bug #332840
[08:47] <seb128> lool: ok good, thanks a lot for tracking since
[08:47] <didrocks> 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] <seb128> lool: I was still using libtool 1.5 to relibtoolize gtk to workaround this error
[08:47] <lool> seb128: It's unfortunate we didn't notice earlier, it seems intrepid is affected as well  :-/
[08:48] <seb128> didrocks: ok feel free to ask him when you have him on the phone there is no hurry
[08:48] <didrocks> seb128: no pb
[08:48] <lool> 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] <seb128> lool: I did notice and asked Keybuk but never spend the required hours to figure what was the issue
[08:48] <lool> 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] <seb128> I could have told that :-p
[08:49] <lool> seb128: Turned out to be a common bug; and you can easily hit it with almost all GNOME packages
[08:49] <seb128> I do downgrade libtool to 1.5 to workaround the issue for a while ;-)
[08:49] <seb128> never got it in other packages
[08:49] <lool> seb128: Something like touch po/POTFILES.in in any GNOME package after configure and you will break the build there too
[08:49] <seb128> but we don't relibtoolize glib for example
[08:49] <lool> So if you e.g. patch a lang in, you might hit it again
[08:50] <lool> 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] <lool> (The borken Makefile.in.in is copied in all GNOME tarballs)
[08:55] <lool> 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] <seb128> yes, they are not updated often enough
[08:56] <seb128> I didn't bother yet but somebody should ping #launchpad I guess
[09:09] <huats> morning everyone
[09:10] <seb128> lut huats
[09:10] <huats> hey seb128
[09:10] <seb128> huats: how are you? I was just asking about you to didrocks ;-)
[09:10] <huats> even if I am running out of time, I will at least do the gcalctool update ;)
[09:10] <huats> I am getting better
[09:10] <huats> thanks !
[09:10] <huats> how are you ?
[09:11] <seb128> good thank you!
[09:11] <huats> no pb
[09:11] <seb128> didrocks: ^ he will do the update
[09:12] <huats> 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] <seb128> ok
[09:13] <huats> I hope that later this week I will have ore time to do packaging stuffs...
[09:13] <huats> (I will)
[09:13] <seb128> 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] <huats> exactly
[09:13] <huats> ok
[09:13] <huats> I will do that then
[09:17] <huats> seb128: and btw thanks for taking care of gnome-keyring and seahorse yesterday...
[09:19] <huats> Does anyone can remember me URL of the documentation to put a package into bzr ?
[09:19] <seb128> huats: didrocks does for sure and you are welcome for the updates ;-)
[09:20] <didrocks> huats: you have some stuff to do to ubuntu-fr too :p
[09:20] <huats> I am sure that didrocks knows that ... but he didn't asnwered me privately
[09:20] <huats> :)
[09:20] <didrocks> seb128: yep, noted. I will try to tackle gnome-games within the day :)
[09:20] <huats> didrocks: I am sure I have
[09:20] <huats> I will take care of them too
[09:20] <seb128> huats: maybe you need to ask nicely? ;-)
[09:21] <didrocks> huats: I have a work too :)
[09:21] <huats> didrocks: luckly you, I don't :P
[09:21] <didrocks> huats: https://wiki.ubuntu.com/DesktopTeam/Bzr, Vcs-Bzr: https://code.launchpad.net/~ubuntu-desktop/<package_name>/ubuntu
[09:21] <huats> well sort of :)
[09:22] <didrocks> huats: you choose :p
[09:22] <huats> thanks didrocks
[09:22] <didrocks> you're welcome
[09:24] <didrocks> seb128: there were no "please" in the sentence. I have a filter :p (cf ML discussion)
[09:24] <seb128> you mean "there is huats in the sentence and you have a filter for that too"? ;-)
[09:25] <huats> :)
[09:25] <didrocks> seb128: exactly :)
[09:40] <didrocks> seb128: I think I must avoid to update things after midnight (typo & SHVER ;))
[09:41] <seb128> didrocks: yeah ;-)
[09:41] <seb128> hello MacSlow mvo_
[09:43] <MacSlow> yo funky bunch!
[09:43] <MacSlow> seb128, mvo's tail is showing ;)
[09:55] <mvo_> hey seb128
[09:57]  * pitti hugs MacSlow and mvo
[09:57] <MacSlow> pitti, alter Schwede!
[09:58] <MacSlow> pitti, you and dbarth were busy getting the latest notify-osd going :)
[09:58] <MacSlow> I never will underestimate to land code in a package!
[10:01] <pitti> heh
[11:15] <pitti> does anyone know how I can prevent a window from getting a close button?
[11:16] <pitti> gtk_window_set_deletable (GTK_WINDOW (unmount_flush_window), FALSE);
[11:16] <pitti> I tried that, but it doesn't work
[11:16] <pitti> I also tried
[11:16] <pitti> gdk_window_set_decorations (unmount_flush_window->window, GDK_DECOR_BORDER|GDK_DECOR_TITLE);
[11:16] <pitti> but that says that window is not a GdkWindow
[11:17] <pitti> (gnome-mount:3944): Gdk-CRITICAL **: gdk_window_set_decorations: assertion `GDK_IS_WINDOW (window)' failed
[11:17] <pitti> that in particular
[11:17] <seb128> why do you want to do that?
[11:17] <pitti> seb128: https://wiki.ubuntu.com/NotifyOSD#gnome-mount
[11:17] <pitti> for now I used gtk_window_set_decorated(), but then I don't have a title bar at all
[11:17] <pitti> which looks fine, too, though
[11:18] <seb128> there is nothing there which says the dialog shouldn't be closed?
[11:19] <seb128> I'm not sure why you want limit that user choice
[11:19] <mvo_> pitti: gdk_window_set_functions()
[11:20] <pitti> mvo_: won't that have teh same GDK_IS_WINDOW (window)problem?
[11:20] <pitti> mpt: help
[11:20] <mvo_> pitti: have you run "gtk_widget_realize()" on it (or _show()) before you run the gdk_ function?
[11:21] <pitti> mvo_: not ATM
[11:21] <pitti> "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] <pitti> oops, that's for set_deletable()
[11:21] <mvo_> pitti: please try that then, gtk creates the gdk window only on first show or relaize
[11:22] <pitti> 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] <mvo_> pitti: which one, the "set_functions()" does not have any effect or the "set_decoration()" (or both) ?
[11:22] <mvo_> aha
[11:23] <mvo_> :)
[11:23] <pitti> . o O { that looks quite redundant..  }
[11:24] <pitti> a-haa
[11:24]  * pitti hugs mvo
[11:24] <pitti> thanks
[11:24] <mvo_> cheers :)
[11:24]  * mvo_ is still desktop team material ;)
[11:28] <davidbarth> hey pitti, you're taking the gnome-mount changes?
[11:28] <pitti> davidbarth: yes, currently working on them
[11:28] <davidbarth> pitti: great!
[11:28] <pitti> I'll followup on the bug
[11:28] <pitti> davidbarth: I won't change all strings yet, though, that should really be coordinated with upstream
[11:28] <pitti> 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] <mvo_> 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] <james_w> mvo_: I have a fix, just preparing the stuff for an FFe
[12:03] <james_w> I didn't want to take time out to upload a fix
[12:03] <james_w> I can do it if it is urgent
[12:03] <mvo_> james_w: if its in a bzr tree somewhere thats fine
[12:04] <seb128> you probably don't need an exception for bug fix changes
[12:04] <mvo_> james_w: then I will just check it out myself
[12:04] <james_w> seb128: I've been busy :-)
[12:04] <mvo_> heh :)
[12:05] <mvo_> 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] <james_w> mvo_: just pushed to lp:~james-w/bzr-builddeb/2.1
[12:05] <mvo_> james_w: excellent, thanks again
[12:07] <seb128> 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] <mvo_> 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] <mpt> pitti, either "ironic" or "tasteful", take your pick :-)
[12:10] <mpt> Programs were overusing notification bubbles
[12:10] <seb128> mvo_: no that's ok if you are busy I will do it
[12:14] <mvo_> 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] <james_w> mvo_: is it debian/ only?
[12:15] <seb128> mvo_: if you do g-c-c it's on ubuntu-desktop now
[12:16] <mvo_> james_w: yes
[12:16] <mvo_> seb128: thanks
[12:16] <pitti> 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] <james_w> mvo_: then you lose :-)
[12:16] <mvo_> james_w: hm
[12:16] <pitti> mpt: it's not perfect yet, but at least fixes the immediate problem with getting a dialog with buttons
[12:16] <seb128> pitti: what is wrong with having buttons?
[12:17] <seb128> pitti: if you display a dialog I can't close I'm going to be unhappy with you ;-)
[12:17] <mpt> pitti, excellent
[12:17] <james_w> 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] <mpt> seb128, don't worry, it's not a dialog, it's a progress window ;-)
[12:17] <pitti> 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] <seb128> mpt: same difference, anything which open and I can't close is going to make me unhappy
[12:17] <pitti> seb128: I shouldn't have to close this progress window
[12:17] <seb128> why not?
[12:18] <seb128> if I want to get it out of my way
[12:18] <pitti> seb128: "have to" != "can't"
[12:18] <pitti> seb128: it should auto-close
[12:18] <mpt> seb128, it closes itself after a few seconds, and you can minimize it if you're really impatient.
[12:18] <pitti> when it's donw
[12:18] <mvo_> james_w: hm, thanks. I guess I misunderstood the use-case for it then
[12:18] <seb128> mpt: what is wrong with letting user the choise to close things he doesn't want now?
[12:18] <pitti> seb128: I'm absolutely open to adding back the close decoration
[12:18] <seb128> that start being dictating users what to do I and don't like that at all
[12:18] <pitti> seb128: but we shuoldn't have above fallback dialog from notify-osd, since that's just plain wrong
[12:18] <james_w> mvo_: oh, you got the use case correct, it's just hard to implement in this case
[12:19] <james_w> mvo_: it currently only works for full-source branches
[12:19] <seb128> 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] <mpt> seb128, because that would falsely imply you were cancelling the unmount when you can't.
[12:19] <seb128> you do extra efforts to get in the user way
[12:19] <seb128> 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] <seb128> wouldn't
[12:20] <seb128> my ipod screen change when I can unplug it I don't need a dialog on my computer screen too
[12:20] <pitti> seb128: would you still want the next window which says that you can remove it?
[12:20] <seb128> no
[12:20] <seb128> I look at the ipod before unplugging not the computer
[12:20] <pitti> right, I agree
[12:20] <pitti> so *if* we make the dialog close-able, it shouldn't present the followup window either
[12:21] <mvo_> 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] <mpt> iPod's are unusual in that they prominently show mounted/unmounted state.
[12:21] <pitti> but I leave the decision of that "if" to someone else
[12:21] <mpt> er, iPods I mean.
[12:21] <mpt> Most hotpluggable devices don't.
[12:21] <seb128> 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] <seb128> if I want to close that dialog I should be able to do so
[12:24] <seb128> 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] <pitti> seb128: minimizing isn't enough for you?
[12:24] <seb128> it's still in my way, ie in the tasks list, in the alt-tab list, etc
[12:25] <seb128> I'm not sure what we win by removing the flexibility there
[12:26] <seb128> 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] <pitti> seb128: no, that's the very bug I was fixing :)
[12:26] <seb128> ok good
[12:26] <pitti> seb128: right now it looks like https://wiki.ubuntu.com/NotifyOSD?action=AttachFile&do=get&target=gnome-mount-unmounting.png
[12:26] <pitti> seb128: which you *have* to close, and that's totally wrong
[12:26] <seb128> agreed
[12:27] <pitti> seb128: now it looks like http://launchpadlibrarian.net/23359790/cache-flushing.png
[12:28] <mpt> ooh, nice
[12:28] <seb128> pitti: nice indeed
[12:28] <mvo_> 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] <seb128> I like the nautilus way better though
[12:28] <mpt> (modulo that annoying GTK text wrapping bug)
[12:28] <seb128> you can close the copy dialog, it just goes to the notification area ;-)
[12:28] <pitti> seb128: yeah, that's nice, too
[12:29] <seb128> I'm wondering if GNOME has any dialog you can't close right now
[12:30] <james_w> mvo_: thanks, please pull
[12:30] <mpt> pitti, looks like the gap between the progress bar and the "To prevent..." text is a bit large
[12:30] <pitti> mpt: right; that needs some work (it's not that easy to get the exact spacing)
[12:31] <mpt> I don't envy you, Glade annoys me :-)
[12:31] <mpt> pitti, hey, that progress bar is determinate! Did you find a way of calculating the proportion done?
[12:31] <pitti> mpt: but that's not critical for UIF, and I have some other things (like usplash) which are
[12:31] <pitti> mpt: no, it's just a bouncing one
[12:31] <mpt> oh
[12:32] <mpt> see, that's why indeterminate progress bars shouldn't be themed to bounce -- it makes them look unnecessarily similar to determinate ones
[12:32] <seb128> pitti: btw while you are uploading gnome-mount change there is a pending sponsoring request for a typo fix waiting
[12:32] <pitti> seb128: oh, will do that next time (I'm sure I have to touch gnome-mount again soon enough :) )
[12:32] <seb128> thanks
[12:32]  * pitti already uploaded, and is now sending his weekly report
[12:32] <seb128> doh, weekly report
[12:32] <seb128> did we get reminder emails?
[12:33] <pitti> not this week apparently
[12:33] <seb128> I didn't, I'm wondering if my spam filtering is too efficient or something
[12:33] <seb128> ok good
[12:34] <seb128> 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] <mvo_> james_w: works great now, thanks!
[12:35] <james_w> mvo_: thank you
[12:35] <pitti> seb128: it only starts after 0.75 seconds
[12:35] <pitti> seb128: just like the notification
[12:35] <seb128> ah good
[12:35] <pitti> seb128: so for fast/no flush you don't see anything
[12:35]  * seb128 hugs pitti
[12:35] <pitti> and for long ones it autocloses, yes
[12:36] <pitti> if you flush takes 0.9 seconds, it looks ugly indeed
[12:36] <pitti> but that's not new, same problem with the notification
[12:36] <seb128> right I was just wondeing if there was a way to estimate the flush time before
[12:37] <davidbarth> pitti: maybe you can add an artificial timeout to let the user see the dialog?
[12:37] <seb128> let's see how it goes already like this we can do tweaking later
[12:37] <davidbarth> pitti: when the flush timeout occurs, add an additional 2s timeout
[12:37] <pitti> davidbarth: that's possible
[12:38] <pitti> davidbarth: well, only if the flush took less than 1 second or so
[12:38] <davidbarth> pitti: for quick flushes, you will only be disturbed for 2s (but will have the time to actually see what's happening)
[12:38] <davidbarth> pitti: and for longer flushes, you have to wait anyway...
[12:38] <pitti> if it already takes 5, then there's no reason to have an extra 2
[12:38] <pitti> davidbarth: in fact I used that extra delay for testing :)
[12:39] <pitti> I already have the patch
[12:39] <davidbarth> pitti: right, so you need to account for the time the dialog has been up
[12:39] <davidbarth> pitti: hehe, nice
[13:08]  * kenvandine_wk waves
[13:09] <james_w> morning kenvandine_wk
[13:23] <seb128> hey kenvandine_wk
[13:23] <kenvandine_wk> hey seb128
[13:23] <seb128> kenvandine_wk: I uploaded the new evolution version and included your changes
[13:23] <kenvandine_wk> great
[13:23] <kenvandine_wk> both bugs?
[13:23] <seb128> kenvandine_wk: yes
[13:23] <kenvandine_wk> excellent
[13:23] <kenvandine_wk> thx
[13:24] <seb128> kenvandine_wk: could you open a bug upstream about the action change though?
[13:24] <seb128> you're welcome
[13:24]  * kenvandine_wk was going to create a debdiff for those today
[13:24] <kenvandine_wk> yes
[13:24] <seb128> thanks
[13:24]  * kenvandine_wk does that now
[13:38] <seb128> mvo_: did you or do work on g-c-c?
[13:39] <seb128> mvo_: just asking before doing the update to not conflict
[13:44] <fta2> seb128, evolution still shows me popups instead of nice notifs, do I need to add something?
[13:45] <seb128> fta2: hello
[13:45] <seb128> fta2: did you upgrade and did you restart it?
[13:46] <fta2> both
[13:46] <seb128> so talk to kenvandine_wk who wrote the change
[13:46] <seb128> it works for me
[13:46] <kenvandine_wk> humm
[13:46] <fta2> i remember you asked me to uncheck a pref last week
[13:46] <seb128> no I didn't
[13:46] <seb128> I said you can disable the upstream one if you want
[13:47] <kenvandine_wk> fta2: the preference shouldn't matter in the latest
[13:47] <fta2> so it doesn't work for me. i see the ok / cancel dialog
[13:48] <kenvandine_wk> fta2: echo $GDMSESSION
[13:48] <fta2> oh, just rechecked the pref, now, i have both the dialog and the notif
[13:49] <fta2> kenvandine_wk, default
[13:49] <kenvandine_wk> default is what it returns?
[13:49] <seb128> fta2: dpkg -l | grep evolution-?
[13:49] <geser> 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] <seb128> geser: no
[13:49] <fta2> http://paste.ubuntu.com/125773/
[13:50] <mvo_> seb128: no, I was doing compiz (and still am)
[13:50] <seb128> geser: that libary is deprecated and not used in GNOME (or should not it's still there for compatibility reasons)
[13:50] <seb128> mvo_: ok, I will do the g-c-c update then
[13:51] <kenvandine_wk> 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] <seb128> kenvandine_wk: his issue seems to be the action part and not the icon though
[13:52] <fta2> kenvandine_wk, http://www.sofaraway.org/ubuntu/tmp/Screenshot-evolution-indicator.png
[13:52] <geser> seb128: I tried to rebuild nautilus-python for the python 2.6 transition and it failed due to this missing dependency
[13:52] <kenvandine_wk> seb128: but he shouldn't even get that action if he is in the right session
[13:53] <pitti> seb128: okay for me to sponsor bug 329245?
[13:53] <seb128> geser: could you look at fixing it, do a debdiff and subscribe the sponsor team to the bug?
[13:53] <pitti> seb128: (updated patch by davidbarth)
[13:53] <seb128> pitti: I was going to do this one but sure, make sure to take the version I uploaded before lunch as basis
[13:53] <pitti> seb128: yes, downloading from LP directlry
[13:54] <seb128> pitti: ok, go for it then
[13:55] <seb128> kenvandine_wk: maybe notify-osd broken in the recent update and capability query doesn't work correctly?
[13:55] <seb128> broken -> broke
[13:55] <kenvandine_wk> works here...
[13:55]  * kenvandine_wk just updated to make sure
[13:56] <seb128> worked for me too when I tried yesterday, I didn't upgrade my laptop yet so I can't test now
[13:56] <kenvandine_wk> i just verified the version  you uploaded works... seems fine
[13:56] <seb128> fta2: do you get the flashing notification icon? or just the dialog?
[13:56] <kenvandine_wk> fta2: run evolution from a console
[13:56] <kenvandine_wk> then go into the plugin configuration and pastebin what is printed on the console
[13:57] <seb128> kenvandine_wk: btw on bugs you can click the also affects project link below the table to add upstream tasks
[13:57] <seb128> kenvandine_wk: could you do it on bug #328596?
[13:58] <kenvandine_wk> what else does it affect?
[13:58] <seb128> upstream evolution
[13:58] <kenvandine_wk> oh... i see
[13:58] <seb128> adding an upstream tasks will monitor the bugzilla bug status
[13:58] <kenvandine_wk> cool feature :)
[13:58] <seb128> indeed
[13:58] <kenvandine_wk> it automatically picked up the watch for it...which i thought was cool
[13:58] <seb128> the upstream task will change when they close or needinfo the bug
[13:59] <seb128> ;-)
[13:59] <kenvandine_wk> awesome
[13:59] <eeejay> 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] <seb128> eeejay: read what pitti said around 15 ago?
[14:00]  * eeejay scrolls
[14:00] <pitti> me?
[14:00] <seb128> pitti: I think that's about the fix you want to sponsor
[14:00] <seb128> oh, I've been misleaded by the title
[14:00] <pitti> seb128: the patches I upload (g-p-m and g-settings-daemon) fix the notifications for the new hint names
[14:00] <pitti> and for the eject key
[14:00] <seb128> eeejay: ask MacSlow or davidbarth about notify-osd issues
[14:01] <seb128> eeejay: that doesn't seem to be a bug but a design decision
[14:01] <seb128> pitti: yeah, sorry I have been confused by the title
[14:01]  * pitti hugs seb128
[14:01]  * seb128 hugs pitti
[14:02] <eeejay> 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:03] <seb128> eeejay: so why do you ask to me? I'm not working on notify-osd
[14:03] <eeejay> seb128: because the fix is needed in gst, (ie. the title _("Volume") is needed instead of " ")).
[14:04] <seb128> eeejay: doesn't change the fact that I'm not working on those notify-osd changes
[14:05] <seb128> eeejay: you want to talk to davidbarth or MacSlow really
[14:05] <eeejay> MacSlow: davidbarth: could you please bless bug 334292?
[14:07] <MacSlow> eeejay, there you go
[14:09] <eeejay> MacSlow: thanks! i'll do the same for gpm..
[14:09] <fta2> kenvandine_wk, http://paste.ubuntu.com/125782/
[14:10] <pitti> davidbarth: hm, the eject notification works now, but it doesn't actually eject; does that work for you?
[14:10] <kenvandine_wk> fta2: weird... i see more output than that :)
[14:11] <seb128> fta2: the gvfs warning are because you upgraded gvfs but didn't restart your session
[14:11] <kenvandine_wk> fta2: do you see the mail notification icon in the notification area?
[14:11] <seb128> hey rickspencer3
[14:11] <kenvandine_wk> as well as the indicator applet?
[14:11] <davidbarth> pitti: not sure, i have not test the result of the command
[14:11] <kenvandine_wk> morning rickspencer3
[14:11] <pitti> hey rickspencer3
[14:11] <fta2> kenvandine_wk, no
[14:11] <rickspencer3> good morning seb128 and kenvandine_wk
[14:11] <kenvandine_wk> fta2: ok... that is really weird
[14:11] <davidbarth> pitti: but i haven't changed that part of the code and i think i do not exit prematurely
[14:11] <pitti> rickspencer3: FYI, I added my activity report/work items directly to the wiki
[14:11] <davidbarth> pitti: maybe the code is old and does not work properly
[14:11]  * davidbarth -> quick lunch
[14:12] <rickspencer3> maddness!
[14:12] <seb128> 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] <pitti> seb128: I mean if I press the eject hotkey
[14:12] <pitti> which is still F12 for me
[14:12] <rickspencer3> looks like seb128 pitti and mvo have been quite busy while I was sleeping this morning!
[14:12] <pitti> which annoys me a lot, but is nice for testing this particualr fix :)
[14:13] <pitti> :)
[14:13] <seb128> I get a
[14:13] <seb128> org.freedesktop.Hal.Device.Volume.UnknownFailure
[14:13] <seb128> "eject : tentative d'utilisation de `/media/cdrom0' comme nom de périphérique mais il ne s'agit pas d'un périphérique"
[14:14] <seb128> which basically means "try to use cdrom0 as device name but that's not a device"
[14:14] <seb128> weird error
[14:14]  * kenvandine_wk logs out to test something
[14:14] <davidbarth> pitti: but i can work on that later today, as i still have to add support for media keys
[14:15] <davidbarth> yeah, i was getting I/O errors, which were normal as i didn't have any media inserted
[14:15] <seb128> knowing that the disk is mounted as cdrom0 and it does unmount it before displaying the rror
[14:15]  * davidbarth is trying
[14:15] <pitti> davidbarth: hm, indeed, if I downgrade it doesn't work either
[14:15] <seb128> pitti: btw could you try if you still get your camera duplicated devices issue running gvfs 0.1.7?
[14:15] <pitti> davidbarth: so it's probably not due to your patch
[14:16] <davidbarth> pitti: i hope so! ;)
[14:16] <pitti> erm, *blush*
[14:16] <davidbarth> just fyi, it's ejecting the cdrom i inserted here
[14:16] <pitti> the tray was already open..
[14:16] <davidbarth> pitti: bug fixed then?
[14:17] <pitti> works
[14:17] <davidbarth> k
[14:17] <pitti> sorry for the noise :)
[14:20]  * kenvandine_wk waits for his 30 launchpad tabs load after a browser restart... can anyone say DOS :)
[14:21] <seb128> tseliot: hey, could you have a look at updating your 109_screen_resolution_extra.patch changes to http://download.gnome.org/sources/gnome-control-center/2.25/gnome-control-center-2.25.92.tar.gz?
[14:22] <fta2> kenvandine_wk, in fact, i see nothing related to evo in the notification area
[14:22] <tseliot> seb128: yes, I can but I'm working on a bug which has a high priority for my team. I promise to do it soon
[14:22] <seb128> tseliot: thanks
[14:23] <tseliot> np
[14:24] <vuntz> guys, you're not fun. I stop reading ubuntu-devel for a few days and now there are tons of mails on (I guess) notify osd ;-)
[14:24]  * vuntz wonders if he should read that
[14:25] <seb128> vuntz: hey, good to see you are still around ;-)
[14:26] <kenvandine_wk> hey vuntz
[14:27] <vuntz> I guess I'll read that later, with some pop-corn
[14:28] <kenvandine_wk> haha
[14:30] <andreasn> vuntz, almost as funny as desktop-devel you know
[14:31] <andreasn> except that the wall-of-hate doesn't consist of core contributors
[14:50] <davmor2> Guys is this a bug or design flaw or is it meant to be like this http://www.davmor2.co.uk/evosetup.png
[14:51] <kenvandine_wk> sounds like a bug
[14:51]  * kenvandine_wk tries to repro
[14:51] <seb128> what screen resolution do you use?
[14:52] <davmor2> seb128: 1440x900
[14:52] <seb128> that's a bug and that's what you get for uploading eom changes
[14:52] <seb128> please file a bug and I will try to get those guys to look into the issue
[14:53] <kenvandine_wk> i reproduced it
[14:53] <kenvandine_wk> i didn't do it in 2.25.91
[14:53] <davmor2> seb128: It was more the fact that most of the window is blank.  It's only on sending email too and not receiving which is really weird :)
[14:53] <seb128> right, I included the oem changes
[14:54] <seb128> "only on sending email too"? that is not clear
[14:54] <kenvandine_wk> the sending email screen
[14:54] <kenvandine_wk> the receiving screen is fine
[14:55] <davmor2> seb128: there are 2 config screens that are similar sending and receiving.  Sending is screwy receiving is fine
[14:56] <seb128> ok, please open a bug now and I will get somebody to look into it
[14:56] <davmor2> seb128: I'll do the bug as soon as I have finished the write up on how to setup evo shouldn't be long
[15:09]  * pitti hugs davmor2 for spotting regressions so fast
[15:10] <davmor2> that's my job :)
[15:14] <davmor2> seb128: bug 337264
[15:14] <seb128> thanks
[15:22] <davmor2> When you click on the panel calendar and it pulls down the monthly view and you double click on a day it open a new case of evolution rather than using the open one is this a bug or design feature?
[15:23] <seb128> design
[15:23] <seb128> there is some bugs about that already
[15:23] <davmor2> seb128: Thanks
[15:23] <pitti> seb128: shall I work on bug 335888 now?
[15:24] <seb128> pitti: please do, I still have a backlog around 10 updates and 100 bugs for today
[15:24] <pitti> seb128: right, just making sure we don't collide
[15:24] <seb128> thanks
[15:25] <seb128> pitti: there is a new version available if you want to do the update too ;-)
[15:25] <hyperair> is notify-osd supposed to concat messages for pidgin-libnotify yet?
[15:25] <pitti> seb128: absolutely, while I'm at it anyway
[15:25] <seb128> pitti: http://download.gnome.org/sources/gnome-themes/2.25/gnome-themes-2.25.92.tar.gz
[15:25] <davmor2> seb128: Out of curiosity is there any plan to make evolution minimise into the new comms notification applet like pidgin can?  It would save on screen real estate I just have no idea if it is possible or not
[15:25] <pitti> seb128: consider it done
[15:25] <seb128> pitti: it's only translations updated so it should be trivial
[15:26] <seb128> davmor2: not that I know but I'm not in the dxteam, maybe they have plan for it, ask to davidbarth
[15:26] <davmor2> seb128: thanks again
[15:27] <davidbarth> davmor2: no plan for that now, but that's an interesting idea
[15:27] <davidbarth> davmor2: is there a bug/enhancement request in the evolution tracker or LP? you can subscribe me to the bug
[15:28] <davmor2> davidbarth: no but I can write one :)
[15:30] <Riddell> rickspencer3: meeting in an hour?
[15:31] <seb128> I don't think sending random applications to the notification area is a good thing
[15:31] <rickspencer3> yup
[15:31] <seb128> or message indicator
[15:31] <seb128> rickspencer3: you didn't send a reminder email apparently ;-)
[15:31] <rickspencer3> seb128: really? I thought I did, but I am using Kubuntu
[15:31]  * rickspencer3 ducks
[15:32] <seb128> lol
[15:32] <seb128> so less work for us thanks to kubuntu? ;-)
[15:33] <rickspencer3> aparantly
[15:33] <rickspencer3> it looks like only the first two people ended up in the mailing list that I made in Kontact
[15:33] <rickspencer3> :(
[15:33] <rickspencer3> actually, only Arne got it, it appears!
[15:40] <davmor2> davidbarth: bug 337274
[16:00] <Ampelbein> seb128: got any updates for me to do?
[16:01] <seb128> Ampelbein: http://download.gnome.org/sources/totem-pl-parser/2.25/totem-pl-parser-2.25.92.tar.gz http://download.gnome.org/sources/totem/2.25/totem-2.25.92.tar.gz
[16:01] <seb128> they are in bzr, did you use bzr before for updates?
[16:01] <Ampelbein> unfortunately not, no.
[16:02] <seb128> you are interested to use it?
[16:03] <Ampelbein> yes, just opened wiki.ubuntu.com/Bzr
[16:03] <seb128> Ampelbein: https://wiki.ubuntu.com/DesktopTeam/Bzr
[16:04] <seb128> read the updating a package there
[16:05] <Ampelbein> currently on it. will have to experiment a bit with it. but does not sound too complicated.
[16:06] <seb128> no it's not, good opportunity to give it a try ;-)
[16:06] <Ampelbein> ok, will start and check back here if i have questions.
[16:06] <Ampelbein> thanks for helping me.
[16:07] <seb128> mpt: would you have suggestion for the evolution-alarm-notify strings? bug #331825 is about translating those but I think we should fix the string before doing it
[16:07] <seb128> Ampelbein: you're welcome, don't hesitate to ask on the channel if you have any question, didrocks wrote this page and is open suggestions on how to make it better too ;-)
[16:08] <seb128> mpt: basically evolution-alarm-notify is the service which reminds you about your meetings, etc
[16:08] <kenvandine_wk> seb128: gnome-user-share is  a good example, had to change configure args, deps, etc
[16:08] <seb128> mpt: "Evolution Alarm Notifier" is used right now as name and description
[16:09] <seb128> kenvandine_wk: excellent ;-)
[16:09] <kenvandine_wk> still got build failures... but good example
[16:09] <seb128> upstream issue?
[16:10] <pitti> seb128: grabbing bug 337066, ok?
[16:10] <seb128> pitti: sure, thank you
[16:15] <pitti> seb128: taking bug 336947, too
[16:15] <mpt> seb128, so something like "Ensures that alarms set in Evolution go off at the appropriate time."?
[16:16] <seb128> pitti: thanks
[16:16] <seb128> mpt: is that for Name= or Description= (those are listed in gnome-session-properties)
[16:17] <mpt> seb128, Name=Evolution Alarm Notifier, presumably :-)
[16:17] <seb128> mpt: ok thanks!
[16:24] <didrocks> Ampelbein: I will just change this page a little tomorrow and the workflow will differ a little bit
[16:24] <rickspencer3> desktop team meeting in 6 miuntes
[16:26] <pitti> seb128: taking bug 337054 too
[16:26] <seb128> pitti: you rock!
[16:26]  * calc arghs at gvfs-fuse
[16:26] <pitti> seb128: ah, just don't want to start something new before the meeting :)
[16:26] <pitti> seb128: and in those rush times I guess even a couple of sponsors help
[16:27] <calc> it looks like a real filesystem but can't operate like one :(
[16:27] <seb128> pitti: yeah
[16:28] <ArneGoetje> mvo: 2 UI changes in my l-s branch
[16:28] <asac> hi all
[16:28] <asac> bb in 2 minutes
[16:29] <rickspencer3> https://wiki.ubuntu.com/DesktopTeam/Meeting/2009-03-03
[16:30] <rickspencer3> ready to start the desktop team meeting?
[16:30] <mvo> ArneGoetje: thanks, looks good, could you please write a debian/changelog entry, then I will sponsor the upload
[16:30] <rickspencer3> asac: ArneGoetje: bryce calc kenvandine_wk pitti seb128 Riddell
[16:30] <seb128> rickspencer3:
[16:30] <pitti> o/
[16:30] <asac> o
[16:31] <calc> hi
[16:31] <asac> \/
[16:31] <rickspencer3> sorry that you didn't get the reminder mail. I'm using Kubuntu this week, and apparently I'm not smart enough to set up a list in Kontact.
[16:31] <rickspencer3> :)
[16:31] <rickspencer3> I see that my Jaunty change mail box is on fire, so I'm going to strive to make this a short and sweet meeting so that everyone can get back to shipping.
[16:31] <asac> rickspencer3++
[16:31] <ArneGoetje> mvo: will do.
[16:31] <kenvandine_wk> here
[16:31] <pitti> asac: feel better now?
[16:31] <asac> yeah
[16:32] <asac> much ;)
[16:32] <pitti> great *hug*
[16:32] <rickspencer3> Mostly, we should quickly review a few of the action items from last week.
[16:32] <rickspencer3> ACTION: kenvandine to work with Dx team to identify changes for UIF, and also changes that might require a UIFE.
[16:32] <rickspencer3> kenvandine_wk: you did this, right?
[16:32] <kenvandine_wk> yes
[16:32] <rickspencer3> I seem to recall an email discussion
[16:32] <pitti> those are tagged now?
[16:32] <kenvandine_wk> pitti: yes
[16:33] <pitti> how bad is it?
[16:33] <rickspencer3> when you get a moment, could you post a link?
[16:33] <kenvandine_wk> not terrible
[16:33] <bryce> heya
[16:33] <rickspencer3> kenvandine_wk: ^^^^
[16:33] <rickspencer3> while we're waiting
[16:33] <rickspencer3> reminder: ACTION: Desktop team to review current goals and update as needed. Feel free to update outside the normal web site if it's easier to do so.
[16:33] <pitti> oh, ugh
[16:34] <kenvandine_wk> https://bugs.launchpad.net/ubuntu/+bugs?field.tag=jaunty-uif
[16:34] <seb128> ditto
[16:34] <rickspencer3> no problems
[16:34] <pitti> I don't actually think that I want to change them, though
[16:34] <calc> updated mine
[16:34] <pitti> rather try to fulfill them :)
[16:34] <calc> or rather wrote them i somehow forgot to write them before
[16:34] <rickspencer3> there is no deadline ... I just don't want it to be a hideous crush right when we are trying to organize UDS Karmic
[16:34] <kenvandine_wk> rickspencer3: that list is down from like 28 on thursday
[16:35] <asac> the firefox UI thing will - as expected - be a last minute thing - if at all
[16:35] <rickspencer3> ACTION: rickspencer3 to start a wiki page for brainstorming features for marketing
[16:35] <rickspencer3> I didn't do this, we shoud just use the marketing page, and I'll just put our stuff from last week there, so consider this done
[16:36] <rickspencer3> I also didn't get to talking about sponsoring
[16:36] <rickspencer3> so that's all from last week's actions that aren't marked as done on the wiki
[16:36] <pitti> kenvandine_wk: still quite a big list for two days
[16:36] <pitti> rickspencer3: sponsoring queue looks quite good actually
[16:36] <pitti> we were hammering like mad
[16:36] <rickspencer3> pitti: ack
[16:36] <rickspencer3> you guys rock
[16:37] <pitti> i. e. the old and crufty things are still there, and the brand new items
[16:37] <rickspencer3> next: Release Bugs/Release Status
[16:37] <rickspencer3> Please look at the section on work items in the team meeting wiki. I'd like to quickly get a handle on the work items that will and will not happen this week, but will do that one on one in email, unless there are any questions, we can move on.
[16:37] <rickspencer3> I've listed our release targeted bugs in the meeting wiki. Please be aware of your release targeted bugs.
[16:37] <rickspencer3> pitti: anything to report on the release front? I see two FFE exceptions for us.
[16:38] <ArneGoetje> mvo: pushed
[16:38] <pitti> I'm still a bit concerned about the long-standing bugs on https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:38] <pitti> the X.org driver problems seem to be a pain in the butt
[16:39] <asac> (as usual ;))
[16:40] <pitti> I don't have much to report, rather to ask around whether anyone has anything on their mind which is release critical
[16:40] <pitti> rickspencer3: FFE for -ati and the search page in ffox?
[16:40] <rickspencer3> those are the two I am aware of
[16:40] <asac> my resume works again ... but my X seems to crash (i end up 7/10 times at gdm login)
[16:40] <didrocks> seb128: I had a lot of work, but between two meetings, I did that: bugs #337298
[16:41] <calc> asac: me too
[16:41] <didrocks> (oupss sorry, your meeting)
[16:41] <asac> bryce: what info do you need ;) ^^
[16:41] <calc> there seems to be a Xorg crash on suspend/resume issue on intel (or has in the past)
[16:41] <seb128> didrocks: thanks
[16:41] <calc> the last few times my system has resumed ok though
[16:41] <rickspencer3> bryce: it looks like you have some of the more complex RC issues
[16:41] <pitti> mine freezes after 5 minutes up to two hours after resume
[16:41] <pitti> ssh still works
[16:41] <asac> i can also make X go back to gdm by trying to switch to console (as i found out 30 minutes ago)
[16:41] <pitti> gdb useless, strace inconclusive
[16:42] <asac> bryce: ^^ ;)
[16:42] <pitti> anyway, this should be fodder for LP bug
[16:42] <pedro_> rickspencer3: btw the release target was added to the http://qa.ubuntu.com/reports/team-assigned/canonical-desktop-team-assigned-bug-tasks.html
[16:42] <pitti> it seems there are several unrelated issues here
[16:42] <pedro_> rickspencer3: should be better to look at those reports now ;-)
[16:42] <asac> pitti: we also have this focus-stealing deadlock ... does your mouse pointer change to a "text select" state
[16:42] <asac> ?
[16:42] <pitti> asac: never had that
[16:42] <kenvandine_wk> asac: i had that once
[16:43] <bryce> sorry, someone pinged me about another bug
[16:43] <asac> strange ... most X lockups that still allow ssh feel like its that
[16:43] <rickspencer3> pedro_: yes
[16:43] <rickspencer3> thank you for that
[16:43] <pitti> kenvandine_wk: do you have an overview about the jaunty-uif bugs? i. e. how many are on track, how many need someone to work on, how many are blocked?
[16:43] <asac> e.g. the mouse pointer changes to something else, but you cannot do anything anymore (neither keyboard nor mous)
[16:43] <kenvandine_wk> there are 3  that we will need exceptions for
[16:43] <pitti> asac: ok, that sounds similar to my problem
[16:43] <bryce> asac: for crashes, backtraces are necessary - http://wiki.ubuntu.com/X/Backtracing
[16:44] <pitti> bryce: it doesn't crash, it just stops updating the screen
[16:44] <kenvandine_wk> gossip, gaijim, amsn
[16:44] <pitti> bryce: apps continue to work
[16:44] <asac> pitti: yeah. we have a gnome bug for that with a testcase
[16:44] <pitti> bryce: gdb is totally useless (??), even with -dbg
[16:44] <asac> gnome bug 571423
[16:44]  * pitti will file a bug and then we'll compare
[16:44] <seb128> asac: never had this one either and it's there since dapper or something no?
[16:44]  * kenvandine_wk re-phrases, at least 3... those 3 depend on python bindings to libindicate, which won't be ready
[16:45] <asac> seb128: well. actually i think its a different issue, but related. the one we have a bug for is there since dapper. the new one has the same symptoms, but i get it out of nowhere
[16:45] <asac> and also since the grab menu thing was claimed to be fixed by NM it might be that its all the new issue now
[16:45] <seb128> asac: for what is worth I've read no bug about that out of the nm case
[16:45]  * calc will try to get a backtrace for the intel crash on suspend/resume if it happens again
[16:45] <rickspencer3> kenvandine_wk: for bug #335654
[16:46] <asac> seb128: right. it feels like a X lockup ;)
[16:46] <kenvandine_wk> rickspencer3: davidbarth said he would work on that one  today
[16:46] <rickspencer3> pitti: are you aware of 335654 ?
[16:46] <asac> seb128: but if you saw the menu bug once, then you see that at lesat the mouse pointer is in "grab" mode
[16:46] <pitti> bug 335653
[16:46] <pitti> bug 335654
[16:46] <pitti> sorry
[16:46] <asac> seb128: i will try to kill around apps next time i see the randoe lockup
[16:46] <bryce> pitti: right, freezes != crash.  asac mentioned a crash; what you describe sounds more like an x freeze.
[16:46]  * kenvandine_wk doesn't thing tomcat on ppc will block uif :)
[16:47] <asac> bryce: i dont know if its a crash. i end up at gdm login
[16:47] <bryce> pitti: freezes are harder to debug but if you file a lp bug I can look into it
[16:47] <pitti> bryce: okay
[16:47] <asac> bryce: but i dont get a crash file
[16:47] <pitti> rickspencer3: aware in the sense that I've seen it before
[16:47] <kenvandine_wk> asac: i ssh'd in and killed all the apps that was visible, and nothing fixed it
[16:47] <bryce> asac: yes that's a crash.  Often there'll be some error messages in your /var/log/gdm/* files
[16:47] <asac> bryce: ways to reproduce: a) resume, b) switch to console
[16:47] <asac> bryce: i will look there next time
[16:47] <kenvandine_wk> pitti: there will be patches coming for s-c-p :)
[16:48]  * kenvandine_wk hopes
[16:48] <bryce> asac, should be easy to get a backtrace  then at least...
[16:48] <pitti> kenvandine_wk: great
[16:48] <asac> bryce: i hope
[16:48] <bryce> pitti: are you on -intel or -ati?
[16:48] <pitti> as always, I act as a sponsoring machine these days
[16:48] <kenvandine_wk> bryce: happened on my -intel, 965
[16:48] <pitti> please subscribe ubuntu-main-sponsors, turnaround time should be very fast these days
[16:48] <pitti> bryce: intel gma945
[16:50] <rickspencer3> looks like X is shaping up to be a hot spot for Jaunty
[16:50] <bryce> right, I believe there are a lot of different crash and freeze bugs on -intel right now (even upstream has mentioned they have some qa problems)
[16:50] <asac> bryce: X: ../../src/i830_batchbuffer.h:78: intel_batch_emit_dword: Assertion `pI830->batch_ptr != ((void *)0)' failed.
[16:51] <asac> thats the only thing that looks like it could be the crash
[16:51] <pitti> can we please take that to bugs?
[16:51] <bryce> asac: aha, yes that sounds like it.  null pointer dereference
[16:51] <bryce> pitti: huh?
[16:52] <pitti> to the bug tracker, I mean
[16:52] <asac> heh
[16:52] <rickspencer3> agreed
[16:52] <rickspencer3> :)
[16:52] <asac> obviously yes.
[16:52] <pitti> it looks like meaningful information, and it's not meeting topic
[16:52] <asac> was just a quick up-front check
[16:52] <pitti> sure :)
[16:52] <asac> topic was "Release critical things" ;)
[16:52] <bryce> sure
[16:52] <asac> ok i am done then for that
[16:53] <pitti> right, and it was good to confirm that it's an RC issue, since several people have it
[16:53] <asac> ok lets move
[16:53] <rickspencer3> randa asked me to tell you all that she will be scheduling 9.10 meetings in the next cuople of days, some of you will be invited to one or two of those
[16:53] <rickspencer3> any other business?
[16:53] <pitti> is there anything we need to discuss about the jaunty-uif bugs?
[16:53] <rickspencer3> I only see 12 of them
[16:53] <pitti> bug 283095
[16:53] <asac> pitti: do we have a deadline for those?
[16:53] <pitti> asac: thursday
[16:54] <kenvandine_wk> pitti: just keep an eye out for bugs you get subscribed to
[16:54] <pitti> wasn't that a topic that Ted proposed?
[16:54] <rickspencer3> system-config-printer is the only one that I am worried about
[16:54] <asac> pitti: ah. thought those were candidates for an exception. sorry
[16:54] <rickspencer3> oh, right
[16:54] <kenvandine_wk> make sure if they have that tag, they move along quickly
[16:54] <pitti> asac: well, they will after Thursday :)
[16:54] <pitti> kenvandine_wk: I'll be responsible for fast sponsoring, yes
[16:54] <asac> so what is our deadline for things that need exceptions? i just want to prevent that stuff lands too close to or even after beta
[16:54] <rickspencer3> the dx team plans to land a lot of the changes tomorrow
[16:54] <kenvandine_wk> they are working on the logout confirmation now too
[16:55] <tedg> asac: I'm working on it.  Fighting GTK ATM.
[16:55] <pitti> asac: before beta, I'd say
[16:55] <rickspencer3> may I suggest that we postpone discussion of session/logout management to next week?
[16:55] <tedg> pitti: I think it died when I realized that we're just as good at saving sessions as GNOME session.  Sadly.
[16:55] <rickspencer3> tedg: ^^^ is that okay?
[16:55] <tedg> rickspencer3: Sure, I think the topic is closed in my opinion.
[16:55] <pitti> rickspencer3: right; I personally think it's not a biggie, since gnome-session session shutdown is terminally broken anyway
[16:55] <rickspencer3> okay
[16:56] <pitti> tedg: you mean "as nonexistant" :)
[16:56] <rickspencer3> any other business?
[16:56] <pitti> tedg: well, session saving is one thing, but it doesn't even cleanly shut down the session
[16:56] <pitti> and Firefox gets eternally confused by that, as well as unsaved documents..
[16:56] <asac> yes, please give ffox some time
[16:57] <pitti> asac: it's not a firefox issue, it's gnome-session doing basically a killall -9
[16:57] <asac> please dont do that ;)
[16:57] <seb128> that is fixed in svn and will be fixed in jaunty today
[16:57] <asac> at least killall ... wait ... then killall -9
[16:57] <pitti> which is a major regression in intrepid/jaunty, compared to hardy or so
[16:57] <rickspencer3> is there anything that we should be doing to address this in Jaunty?
[16:57] <pitti> seb128: \o/
[16:57] <seb128> pitti: hugs for vuntz
[16:57]  * asac hugs seb128 for being a messenger of good news
[16:57] <seb128> ;-)
[16:57]  * pitti hugs vuntz
[16:58] <pitti> seb128: that relieves me a lot
[16:58]  * seb128 hugs vuntz
[16:58] <kenvandine_wk> is there a bug for the logout "close apps" dialog not having a gtk theme?
[16:58] <pitti> rickspencer3: seems that hugging suffices :)
[16:58] <seb128> kenvandine_wk: yes, fixed in svn too
[16:58] <rickspencer3> :)
[16:58] <kenvandine_wk> vuntz appreciates hugs, i am sure
[16:58] <kenvandine_wk> :)
[16:58] <seb128> so going to be fixed in jaunty today too
[16:58] <pitti> kenvandine_wk: bug 277309
[16:58] <seb128> pitti: no, that's the old icon one
[16:59] <pitti> http://bugzilla.gnome.org/show_bug.cgi?id=567958 then?
[16:59] <seb128> bug #320921
[16:59] <seb128> that's the jaunty issue, fixed in svn as said
[17:00] <kenvandine_wk> ok
[17:01] <rickspencer3> meeting adjourned?
[17:01] <pitti> ack
[17:01] <pitti> thanks everyone
[17:01] <seb128> thanks
[17:01] <ArneGoetje> thanks
[17:01] <calc> thanks
[17:01] <rickspencer3> thanks all
[17:01] <bryce> thanks
[17:01] <asac> thanks
[17:02] <pitti> seb128: taking bug 336981
[17:02] <seb128> pitti: rock on
[17:03] <LaserJock> I've got a question for the Gnome desktop people. Sabayon has been in pretty terrible shape since Intrepid and I'm wondering if anybody would be willing to help get it back into shape
[17:03] <seb128> pitti: so gdm-new config migration issue should be fixed now, they do have code for it but hardcoded a different .conf name than the one we used, I updated to the ubuntu-desktop ppa
[17:03] <seb128> LaserJock: I don't, upstream code wise or packaging wise?
[17:03] <LaserJock> seb128: well, bit of both
[17:04] <seb128> what is the packaging issue?
[17:04] <pitti> seb128: nice, they did that upstream?
[17:04] <pitti> seb128: please update the spec status (rock!)
[17:04] <Ampelbein> seb128: i've done totem now and push it to my launchpad-codepage (https://code.edge.launchpad.net/~andreas-moog/totem/totem-22592) can you look over this if i have made this right?
[17:04] <LaserJock> seb128: it's not packaging specifically, it's Ubuntu-specific though
[17:04] <seb128> pitti: yes, they still use the gdm.conf in fact and have a schemas mapping then, I will update the blueprint once I tested to make sure that works
[17:04] <LaserJock> seb128: since sabayon is mostly a Red Hat project it makes some assumptions about the underlying Gnome
[17:04] <seb128> LaserJock: ie?
[17:05] <LaserJock> so changes we might make to Gnome mess it up
[17:05] <LaserJock> so Sabayon works in Fedora, but is unusable in Ubuntu
[17:06] <LaserJock> the first crasher I narrowed down to differences in how we do panels
[17:06] <seb128> ok, I'm too busy to work on it though but I can sponsor changes
[17:06] <LaserJock> well, so can I :-)
[17:06] <LaserJock> I just wondered if there were desktop-team people who'd be interested in that sort of thing
[17:06] <seb128> ok, not me, I will let other people raise their hand if they want
[17:06] <LaserJock> I didn't expect you to do it with all you've got on your plate
[17:06] <seb128> maybe send an email on the list?
[17:06] <seb128> you have better chance to get a reply there
[17:07] <LaserJock> right, yeah
[17:07] <seb128> Ampelbein: looks good to me, bug linked to the bzr etc, good work ;-)
[17:08] <Ampelbein> thanks to didrocks for the informative wiki-page.
[17:08] <Ampelbein> seb128: do you take the changes now from my codepage or do i need to push somewhere else?
[17:09] <seb128> Ampelbein: not "now" but I will when I sponsor the upload
[17:09] <seb128> no need to change anything
[17:09] <Ampelbein> that's what i meant. ok. will do totem-pl-parser now
[17:19] <seb128> cool
[17:23] <calc> rickspencer3: i'm pretty sure i know why OOo fails to write to gvfs-fuse shares now, but not sure if it is fixable in jaunty timeframe :-\
[17:23] <calc> rickspencer3: i'm working on it and may end up trying to patch gvfs-fuse myself if i can figure it out
[17:24] <Ampelbein> seb128: totem-pl-parser done, https://code.edge.launchpad.net/~andreas-moog/totem-pl-parser/totem-pl-parser
[17:24] <seb128> thanks
[17:24] <seb128> brb
[17:26] <rickspencer3> calc: sounds good
[17:29] <calc> it looks like they don't implement truncate support at all currently and special case truncation to 0
[17:41] <seb128> pitti: I'm sponsoring gnome-games if you didn't do it yet
[17:43] <LaserJock> seb128: do you happen to know if pessulus is still being "actively" maintained in Gnome?
[17:44] <seb128> LaserJock: I don't think it is, there has been no recent tarballs
[17:46] <ember> same for svn
[17:46] <pitti> seb128: nope, got stalled (phone call)
[17:48] <tedg> seb128: pitti: I actually have to run to lunch (sorry) but I'm not sure what to do with this bug 336609
[17:49] <tedg> Is there something I should do to get them in rosetta?
[17:49] <pitti> tedg: I'll comment
[17:49] <tedg> pitti: Cool, thank you.
[17:49] <seb128> tedg: do a new upload
[17:49] <seb128> binaries have probably be moved from universe right now?
[17:49] <pitti> presumably, yes
[17:50] <tedg> seb128: Okay, I'm testing a new version of the patch (that does IRC) and I'll post that.  Then that'll be an upload.
[17:50] <seb128> right
[17:53] <asac> is there an intro how to use gi18n.h ?
[17:53] <asac> especially how to setup a project for that? ... something like a simple blueprint
[17:54] <pitti> seb128: I'll just finish the yelp sponsoring, then I have to leave anyway
[17:55] <didrocks> Ampelbein: you're welcome
[17:55] <seb128> pitti: ok, thanks for the help on the sponsoring queue!
[17:55]  * didrocks hugs pitti for his sponsoring :)
[17:56] <didrocks> seb128: do you have some updates on the fire?
[17:56] <seb128> didrocks: no
[17:57] <seb128> didrocks: you can try helping huat to get anjuta updates if he need extra hands
[17:58] <didrocks> huats: ? can I help you ? :)
[17:59]  * didrocks makes big signs to huats ;)
[18:05] <ember> LaserJock do you have a bug for sabayon?
[18:06] <LaserJock> ember: sure, bug #150068
[18:17] <huats> seb128: I am around
[18:17] <huats> I will put the anjuta update tonigh
[18:17] <huats> so no need for didrocks help I think, but thanks anyway
[18:18] <didrocks> huats: you are snobbing me??? :p
[18:19] <huats> didrocks: not at all
[18:20] <didrocks> huats: :)
[18:24] <seb128> didrocks: http://download.gnome.org/sources/pessulus/2.25/pessulus-2.25.92.tar.gz
[18:24] <seb128> chrisccoulson: hi, want to do the gnome-session update?
[18:24]  * didrocks jumps on it :)
[18:25] <didrocks> seb128: ok, I will jump just after having my dinner :)
[18:26] <seb128> didrocks: enjoy, I will have dinner soon too
[18:26] <seb128> huats: ok
[18:26] <seb128> huats: don't do too much if you are busy or still feel you need some rest there is no hurry
[18:26] <didrocks> seb128: thanks, enjoy too :)
[18:26] <huats> seb128: I have put gcalctool on bzr
[18:27] <huats> (the old version... but I would use it to update it)
[18:27] <seb128> huats: ok good
[18:27] <seb128> thanks to mvo and didrocks we will have bzr for everything soon ;-)
[18:27] <huats> so if you want to merge it...
[18:27] <didrocks> seb128: \o/
[18:27] <seb128> huats: you did the update or not? it's no clear now
[18:28] <huats> I haven't... I thought I need to have it in the ubuntu-desktop branch first
[18:29] <huats> ok, so I will do the update in my branch
[18:29] <seb128> no you don't
[18:29] <huats> and then ask you for the merge again...
[18:29] <huats> :)
[18:29] <huats> so you can have your dinner :)
[18:33] <rickspencer3> UIF
[18:33] <seb128> rickspencer3: yes?
[18:33] <rickspencer3> Quassel has the find box right next to the text input box
[18:33] <rickspencer3> more evidence that I am not smart enough to use KDE :)
[18:34] <seb128> lol
[18:46] <pochu> LaserJock: seems vuntz heard you, he just uploaded a new pessulus ;)
[18:46] <LaserJock> heh
[18:46] <pochu>        Module: pessulus
[18:46] <pochu>       Version: 2.25.92
[18:46] <pochu>   Uploaded by: Vincent Untz
[18:46] <pochu> LaserJock: http://download.gnome.org/sources/pessulus/2.25/pessulus-2.25.92.tar.gz in case you're interested
[18:48] <pochu> LaserJock: Debian bug #514809, fwiw
[18:48] <pochu> I investigated it for the Lenny but didn't get too deep unfortunately
[18:50] <LaserJock> right
[18:51] <LaserJock> for Intrepid and Jaunty we can't even get a session open yet so we haven't gotten that far :-)
[18:53] <pochu> oh
[18:53] <pochu> that sucks
[18:53] <pochu> but it's very crashy in lenny
[18:53] <pochu> so it's not much better ;)
[18:53] <LaserJock> yeah, we've been looking at it
[18:54] <LaserJock> it seems to be making certain assumptions about Gnome that sometimes only seem true in Fedora/non-Debian-based systems
[18:55] <LaserJock> the first crasher we found was where it assumes all gnome panels have panel IDs, which seems to not be the case for us
[18:58] <LaserJock> fixing that got me to at least a loaded gnome-session
[18:58] <LaserJock> but then it started crashing quite a bit after that
[19:06] <calc> it appears getting truncate to work with gvfs may take a bit more work than i thought, but at least i am talking to the right people now :)
[19:17] <vuntz> LaserJock: err
[19:17] <vuntz> LaserJock: a panel with no id?
[19:17] <vuntz> LaserJock: that sounds... not possible
[19:18] <LaserJock> vuntz: one would have guessed, but that's what happens
[19:18] <LaserJock> so a simple workaround is to test for the panel id first, before using it in a function call
[19:18] <vuntz> LaserJock: sure, but I can tell you for sure that it should never happen
[19:18] <LaserJock> right
[19:19] <LaserJock> that's why I'm interested in getting Desktop Team input
[19:19] <vuntz> LaserJock: I'd be interested in seeing such a case
[19:19] <LaserJock> the problem seems to be the way Sabayon interacts with Gnome
[19:19] <LaserJock> vuntz: what do you need?
[19:20] <vuntz> gconftool-2 --dump /apps/panel
[19:20] <vuntz> LaserJock: and a screenshot of the desktop to see the panels, I guess
[19:20] <LaserJock> it's not a visable panel
[19:20] <LaserJock> or at least I can't see it
[19:20] <LaserJock> well, let me say this, I'm not necessarily convinced it's actually a panel
[19:21] <LaserJock> as Sabayon says there's 3 and I'd have thought that there were only 2
[19:21] <LaserJock> so it could be something in the way Sabayon detects panels
[19:22] <LaserJock> vuntz: and it's sort of hard to get a screenshot of the desktop as it just crashes
[19:23] <vuntz> hrm, okay
[19:23] <LaserJock> what I first did is in Sabayon's iteration through panels I had it simply print out the panel ID
[19:23] <LaserJock> and *it* says there are 3 panels, 2 with IDs and one without
[19:24] <vuntz> LaserJock: well, that'd be a sabayon bug
[19:25] <LaserJock> right, that's my guess as well, but I don't know why it'd pick up a 3rd panel
[19:26] <vuntz> LaserJock: the maintainer would know how to debug this
[19:26] <vuntz> LaserJock: just file a bug :-)
[19:26] <LaserJock> uhhh
[19:27] <LaserJock> vuntz: the gnome "maintainers" know about the issue but are essentially inactive at this point
[19:27] <vuntz> LaserJock: pointer?
[19:27] <LaserJock> a couple guys are trying to revive some things but it's fairly slow going presently
[19:28] <vuntz> (just to see how far they went in the analysis)
[19:29] <LaserJock> vuntz: nobody upstream has picked it up, that's my point
[19:30] <LaserJock> fedrico knows about it, I idle in #sabayon, it's just that generally at least Fedora doesn't have these issues
[19:31] <vuntz> LaserJock: my point is that if you don't file a bug to track this, there won't be any progress
[19:31] <LaserJock> vuntz: my point is that nobody is there to track
[19:32] <LaserJock> I'm pretty sure it's on bugzilla, but I can't find the specific one offhand
[19:32] <LaserJock> we have had it in Launchpad for quite some time
[19:32] <vuntz> seriously. If it's not on bugzilla, it will not help
[19:32] <vuntz> even if there's no active development right now
[19:32] <vuntz> the day someone starts again, the bug will be useful
[19:32] <LaserJock> sure
[19:33] <LaserJock> I think it's http://bugzilla.gnome.org/show_bug.cgi?id=572306
[19:33] <LaserJock> not sure though
[19:33] <LaserJock> most people just give the errorlog
[19:34] <LaserJock> the bug I'm talking about is in paneldelegate.py though
[19:34] <LaserJock> might also be http://bugzilla.gnome.org/show_bug.cgi?id=566775
[19:38] <LaserJock> also http://bugzilla.gnome.org/show_bug.cgi?id=565533
[19:39] <LaserJock> and a couple others, but I think you've got the idea
[19:39] <vuntz> good
[19:40] <vuntz> so for the panel issue, we just need to find out what event caused the error
[19:41] <LaserJock> vuntz: right, so paneldelegate just uses the panel id so it chokes when it get's passed a panel with no idea
[19:41] <LaserJock> s/idea/id/
[19:41] <LaserJock> but I'm not sure yet where it gets the list of panels in the first place
[19:43] <vuntz> LaserJock: well, you have the full stack trace with python
[19:43] <mvo> anyone here fancy testing a compiz update? with some speedup improvments?
[19:43] <LaserJock> vuntz: right, but that ends at paneldelegate
[19:43] <vuntz> LaserJock: what matters is where it starts, not where it ends
[19:43] <mvo> LaserJock: do you have news from the freeze exception yet?
[19:43] <LaserJock> mvo: nope :( should I poke slangasek?
[19:44] <mvo> LaserJock: its probably ok to wait a little bit more, but within the next few days I would say :)
[19:44] <LaserJock> vuntz: it stats in sabayon-session I believe
[19:50] <asac> does ubuntu-desktop have a ppa?
[19:52] <didrocks> asac: I think there is none, because we don't (unlike KDE team) have pre-release version. We just land version one after the other when released (2.25.3, 2.25.90, 2.25.91…) directly in the official archives
[19:52]  * mvo likes that explaination
[19:53] <didrocks> mvo: I didn't used a very good English? :)
[19:53] <mvo> didrocks: I haven't actually paied attention to that :) I just like the fact that we just upload the snapshots, so much more like a real unstable distro branch :)
[19:54] <didrocks> mvo: seems logic as it is an unstable distro branch :)
[19:54] <didrocks> mvo: or people have to consider like this ^^
[19:55] <LaserJock> I don't think that's particularly the difference
[19:55] <LaserJock> Kubuntu uses PPAs for pre-release staging
[19:56] <LaserJock> not that they don't give out alphas or betas
[19:56] <didrocks> LaserJock: yes, because, (AFAIK) you have access to new pre-release before it is offical
[19:56] <didrocks> I didn't meant anything else ^^
[19:56] <didrocks> mean*
[19:57] <LaserJock> right, so it's just a staging issue
[19:57] <didrocks> or haven't meant (that's more correct) :)
[19:57] <LaserJock> Kubuntu could do it just the same as Gnome
[19:57] <LaserJock> but since the tarballs are available they use the "embargo" time to get things staged
[19:58] <didrocks> yes, indeed it just depends on upstream workflow
[19:59] <didrocks> LaserJock: I think that without a ppa or central "hidden" repository, you can't work this way, right?
[20:00] <LaserJock> didrocks: right, they just use a private PPA
[20:03] <LaserJock> that way the whole KDE stack is built and ready to release on release day, rather than rushing it
[20:04] <chrisccoulson> hi seb128 - just done the gnome-session update
[20:04] <seb128> chrisccoulson: excellent, thanks
[20:04]  * seb128 just finished dinner and will do sponsoring now
[20:05] <chrisccoulson> i'm struggling a bit here because i've lost my internet connection, so everything i do has to go over my cell phones 3g connection, which is slow :(
[20:05] <seb128> urg
[20:05] <seb128> you don't have to pay expensive rate for download at least?
[20:06] <chrisccoulson> i get 1gb/month free;)
[20:06] <chrisccoulson> but ive nearly used that
[20:06] <seb128> ok, so enough updates for you today ;-)
[20:06] <kenvandine_wk> seb128: got some more you can toss my way?
[20:06] <chrisccoulson> i shall probably use the rest of it later when i update my jaunty machine. not done that since friday when my connection went down
[20:07] <chrisccoulson> got 190MB of updates waiting. nice!
[20:07] <seb128> kenvandine_wk: http://download.gnome.org/sources/seahorse-plugins/2.25/seahorse-plugins-2.25.92.tar.gz
[20:07] <kenvandine_wk> ok
[20:09] <asac> didrocks: yes, but if we want to do some experiental stuff and my ppa is already used for something else ... i ams stuck ;)
[20:10] <asac> but well. i guess just throw it in ;)
[20:10] <asac> and get some up-front testing
[20:12] <didrocks> asac: I guess, you can use it, so. seb use it this way for gdm-new :)
[20:12] <didrocks> asac: https://edge.launchpad.net/~ubuntu-desktop/+archive/ppa
[20:13] <huats> seb128: I am doing the gdl update right now... we were in sync with debian, but so far we cannot build the new on debian (related to a libgnomeui-dev issue which will be solved soon I think). Do you have any problem that I break the sync ?
[20:13] <huats> (I am doing the gdl one to work after on the anjuta update)
[20:14] <seb128> huats: no
[20:14] <huats> ok
[20:15] <huats> so I will put the new gdl on ubuntu, and once it is fixed on debian I will push it there too to get the sync soon...
[20:18] <didrocks> seb128: I can't push pessulus to lp in ~whatever/pessulus/ubuntu as it is not a registered LP project
[20:19] <seb128> jcastro: hello
[20:19] <didrocks> jcastro: some work for you, apparently (pessulus product creation on LP) :)
[20:19] <seb128> jcastro: ^ can you fix that for us please, launchpad doesn't know about pessulus yet
[20:20] <didrocks> seb128: I can push the branch to ~didrocks/+junk/pessulus if you want to review it
[20:20] <seb128> didrocks: doing gnome-games and gnome-session first but I will look to it next
[20:20] <didrocks> seb128: also, FYI, I changed the worflow regarding last pitti discussion, cf https://wiki.ubuntu.com/DesktopTeam/Bzr
[20:21] <didrocks> mvo, huats & Ampelbein: I think you want to have a look at this page again: https://wiki.ubuntu.com/DesktopTeam/Bzr
[20:21] <seb128> didrocks: what did he suggest?
[20:22] <didrocks> seb128: one commit = one change
[20:22] <seb128> let me look at the page rather than making you repeat ;-)
[20:22] <didrocks> and a final commit for the changelog :)
[20:22] <didrocks> seb128: my last bzr uploads respect that :)
[20:23] <didrocks> (with UNRELEASED pocket)
[20:23] <didrocks> seb128: I am used to repeat, you know, with huats :p
[20:24] <LaserJock> is pessulus or sabayon likely to end up in the Desktop Team bzr?
[20:24] <huats> what I have done again ?
[20:24] <seb128> LaserJock: yes but we can move it somewhere else if required
[20:24] <didrocks> LaserJock: I put the Vcs-Bzr tag to it (=pessulus), yes, why?
[20:24] <didrocks> huats: it was just a free bashing :)
[20:25] <mvo> didrocks: it looks pretty good now the page, I will probably forget half the time to do debcommit ; dch; debcommit -r though :/
[20:25] <seb128> didrocks: I see, not sure if that's better to have one commit by change, I usually do batch changes and commit and then fix things if required
[20:25] <didrocks> mvo: I am getting used to it. It's pretty simple :)
[20:25] <mvo> you overestimate me here ;)
[20:25] <jcastro> seb128: on it (pessulus)
[20:25] <didrocks> seb128: I think it's just a "best practice"
[20:26] <didrocks> seb128: you can discuss it with pitti when he will be around, I guess :)
[20:26] <didrocks> mvo: really ? ;)
[20:26] <seb128> jcastro: you rock!
[20:26] <didrocks> jcastro: thanks!
[20:26] <LaserJock> didrocks: well, specifically that would me right now I couldn't commit to it
[20:26] <LaserJock> *mean
[20:27] <LaserJock> I could join ~ubuntu-desktop if needed, I just wondered
[20:27] <didrocks> seb128: I think you had some discussion about it to let core-dev commit to this repository, no?
[20:27] <seb128> right, I guess that would make sense
[20:28] <jcastro> didrocks: https://edge.launchpad.net/pessulus
[20:28] <seb128> we use ubuntu-desktop to include extra people not to limit people who have upload rights
[20:28] <didrocks> jcastro: thanks a lot, can bzr push now :)
[20:28] <LaserJock> I was thinking of doing some branches in ~edubuntu-dev
[20:28] <seb128> brb trying gnome-session
[20:28] <jcastro> didrocks: holler at me if you need anything, also, in the future feel free to ping me directly
[20:28] <didrocks> jcastro: for sure, I will, thanks ;)
[20:28] <LaserJock> but obviously we don't want 3 different teams (~ubuntu-core-dev, ~edubuntu-dev, ~desktop-team) having branches
[20:29] <LaserJock> well, "canonical" branches anyway
[20:29] <didrocks> LaserJock: hum, mirror the branch in two ways?
[20:29] <didrocks> it would be great
[20:30] <Ampelbein> didrocks: nice work on the page, now everything is even clearer to me.
[20:31] <didrocks> Ampelbein: great :)
[20:33] <Ampelbein> although i did the totem and totem-pl-parser update not obeying the "one change-one commit" suggestion.
[20:33] <Ampelbein> (it was not in there by the time)
[20:33] <Ampelbein> should i redo the updates?
[20:34] <didrocks> Ampelbein: I don't think it's a mandatory. Some of my update didn't follow that. It's very new (from yesterday :))
[20:35] <LaserJock> didrocks: you want pessulus 2.25.92 in Intrepid? ;-)
[20:36] <didrocks> LaserJock: oupssss
[20:36] <didrocks> it's late :)
[20:36] <tedg> If someone (core-dev) would be so kind, I'd love to get this sponsored: bug 337407  Hopefully it'll get more Ubuntu-devs testing notifications as I'm sure they all use IRC :)
[20:36] <LaserJock> tedg: the question is if they use *pidgin* for IRC
[20:36] <didrocks> LaserJock: I would deny I wrote that. What? "Activity log" ? ;)
[20:37] <LaserJock> didrocks: hehe
[20:37] <LaserJock> didrocks: LP doesn't lie ... oh wait
[20:37] <tedg> LaserJock: heh, yeah.  The notifications are so cool I'm sure we'll switch them all from the terminal clients ;)
[20:37] <tedg> At last UDS I even saw some folks using Compiz to tile their terminals on their screen.
[20:38] <didrocks> LaserJock: unfortunately, I don't have some magical sql commands to change the past :)
[20:38] <seb128> re
[20:38] <seb128> vuntz: still there?
[20:40] <LaserJock> tedg: yeah, I've been wanting to do something like that. I'd like to keep Ubuntu defaults as much as possible while still "getting things done"
[20:42] <chrisccoulson> seb128 - i put gnome-session in to bzr now, if you would like to merge it in to ubuntu-desktop
[20:42] <tedg> It was actually an interesting bug to fix, as lots of Pidgin is based on the concept of buddies, and buddy lists, but IRC doesn't work like that.  Turns into lots of checking for (null) buddies.
[20:42] <LaserJock> tedg: sounds ... fun
[20:42] <seb128> chrisccoulson: url?
[20:42] <chrisccoulson> that would help ;)
[20:42] <chrisccoulson> https://code.edge.launchpad.net/~chrisccoulson/gnome-session/ubuntu
[20:43] <LaserJock> tedg: got a sponsor yet? I could do it
[20:43] <tedg> LaserJock: No one has come forward.  Thank you.
[20:44] <mpt> vuntz, what do you think of <http://live.gnome.org/LowDiskSpaceWarning>? Does it look practical?
[20:47] <tedg> mpt: Should we have a little more information on there?  For instance if your home partition is full, bad things can start happening.
[20:47] <tedg> mpt: Same with /tmp, though we work around that in Ubuntu.
[20:47] <mpt> tedg, it's already at the two-sentence limit. :-) What did you have in mind specifically?
[20:48] <tedg> mpt: "This is the partition that your home directory is on.  If you don't fix the problem you might not be able to log in again."  That's probably a little bit scary, but it's kinda the reality.
[20:48] <tedg> mpt: Usually you can login, but things break.
[20:48] <seb128> chrisccoulson: uploaded and pushed to the ubuntu-desktop bzr now
[20:48] <chrisccoulson> thanks
[20:49] <tedg> mpt: I'm just concerned that a user won't know why they're choosing the various options.
[20:49] <mpt> ah, I didn't know that it could prevent login
[20:50] <tedg> mpt: I guess prevent is too strong a word, but "Next time you login there will be lots of error dialogs and things will look wrong" would probably be correct :)
[20:52] <tedg> Heh, reading the gksu code I realized you can't gksu without being able to create a lock file in your home directory.  Kinda funny really.
[20:53] <asac> ArneGoetje: so seems we will get "automatic" ;)
[20:53] <tedg> We should probably have a better solution than laughing about how FU-BAR it is on IRC. :)
[20:53] <chrisccoulson> tedg - are you doing any work on the FUSA at the moment? there is a mistake in one of my last patches which mean that shutdown/restart options are still hidden when g-p-m is not running. i was going to provide a patch to fix that unless you are already doing some work on it
[20:53] <asac> ArneGoetje: backend is already there: 332172
[20:53] <tedg> chrisccoulson: I am, but if you just grab the bazaar branch it should be easy to merge.
[20:54] <chrisccoulson> no problem - i'll do that
[20:54] <mpt> tedg, first step is reporting the bug
[20:55]  * tedg checks what mpt's karma score is...
[20:55] <mpt> 14
[20:56] <mpt> ... er, not that I keep track of it, or anything
[20:56] <didrocks> mpt: you can commit "foo" or "bar" in bzr and push to lp :)
[20:56]  * didrocks is sure that some people do that :)
[20:57] <mpt> tedg, you know much more of what you're talking about for that issue, and Bugzilla descriptions aren't editable, so if I reported it I'd almost certainly permanently mess it up
[20:57] <mpt> didrocks, oh, I was referring to my bugzilla.gnome.org karma
[20:57] <mpt> I have no idea what my LP karma is
[20:57] <didrocks> mpt: oh, ok, sorry, I just come in the conversation and didn't backlog :)
[20:58] <pidgin-tester> tedg: when should I get notifications?
[20:58] <tedg> pidgin-tester: When someone talks to you but you don't have the conversation in focus.
[20:58] <tedg> Bitch to test isn't it :)
[20:58] <seb128> didrocks: he knows what lp karma is don't worry ;-)
[20:58] <pidgin-tester> tedg: well, that worked pretty well
[20:58] <pidgin-tester> tedg: try one more
[20:59] <tedg> pidgin-tester: Here is a test.
[20:59] <pidgin-tester> tedg: awesome
[20:59] <tedg> What's nice is if you miss the notification, you should also get an indicator for the IRC stuff.
[20:59] <seb128> tedg: you know you can /j #ted-chan rather than abuse a public one? ;-)
[20:59] <tedg> Saved me more than once.
[20:59] <didrocks> seb128: I didn't explain what lp karma is but how people may raise them in fooling it :)
[20:59] <tedg> seb128: Yes, I've been using "#talktome"
[21:00] <seb128> tedg: will you log IM messages in the indicator?
[21:00] <tedg> seb128: The logs from that channel are between me an my therapist ;)
[21:00] <tedg> seb128: Yes.  Pidgin currently.
[21:00] <tedg> seb128: Well, not as much log.  As show you the ones you haven't seen.
[21:00] <seb128> tedg: is that supposed to work in current intrepid?
[21:00] <seb128> intrepid -> jaunty
[21:00] <LaserJock> sorry, just wanted to test real quick before uploading
[21:01] <tedg> seb128: Not until LaserJock uploads the package :)
[21:01] <seb128> ok
[21:01] <seb128> because I still didn't get the indicator interest
[21:01] <seb128> it's that useless icon which never change and always list evolution or pidgin when started there
[21:02] <LaserJock> tedg: done
[21:02] <tedg> seb128: I think it's interesting, but no unbelievable.  But it solves the problem of responding when there are lots of people talking to you.  For this release I focused more on getting a good architecture.  I'm hoping to do more with it in the future.
[21:02] <tedg> LaserJock: cool, thanks!
[21:03] <LaserJock> tedg: np, glad to see more info in the notifier
[21:03] <seb128> tedg: I'm not convinced but let's see
[21:04] <seb128> tedg: usually I read my emails in the morning then switch to IRC
[21:05] <seb128> and I don't need to get those 15 highlights to be listed in the applet, I just go to IRC and read everything pending there
[21:05] <chrisccoulson> i'm confused about the indicator-applet actually. it doesn't do anything here, other than show an icon that lists evolution and pidgin. is it meant to be doing something else, or is it broken on my setup?
[21:05] <tedg> seb128: Yes, and that works if you're focusing on IRC.  But if you're trying to avoid people, and you come back, that's a different case.
[21:06] <chrisccoulson> i'm never told when i have unread messages at all
[21:06] <tedg> seb128: Like when I walk away from my computer, so that I notice someone pinged me on IRC.
[21:06] <seb128> chrisccoulson: cf what ted just said, after next upload it will
[21:06] <chrisccoulson> fantastic (H)
[21:06] <seb128> tedg: it does the glowing effect in the taskbar so I know a message is waiting
[21:07] <chrisccoulson> the colour of the applet doesn't seem to match the panel colour either
[21:09] <seb128> tedg: I mean I read everything pending when looking at IRC
[21:09] <seb128> tedg: so if I have to click 15 times in the applet menu after that to clear the queue that's going to annoy me I think
[21:10] <tedg> seb128: No, when you use pidgin it matches the pidgin state.  So if you view them, it clears automatically.
[21:10] <tedg> Basically, if the tab is blue in pidgin, it's in the indicator.  If it's not, it's not.
[21:10] <seb128> how does it know what channels you read?
[21:10] <seb128> ok
[21:10] <tedg> seb128: If I tell you there'll be no mystery ;)
[21:11] <seb128> I'm using xchat-gnome for IRC though so let's way on this one to be updated ;-)
[21:11] <tedg> It watches for when the widgets get focus.
[21:13] <seb128> tseliot: still there?
[21:13] <tseliot> seb128: yep
[21:14] <tseliot> not for long though
[21:14] <seb128> tseliot: you didn't manage to update the g-c-c patch today I guess?
[21:15] <tseliot> seb128: no, sorry, I was busy with some bugs I'm working on for my team
[21:15] <seb128> do you think you will be able to do that tomorrow?
[21:15] <tseliot> is it just g-c-c that doesn't build?
[21:15] <seb128> that's block GNOME updates
[21:15] <seb128> "just" yes
[21:15] <tseliot> or also gnome-desktop
[21:16] <seb128> g-c-c
[21:16] <seb128> gnome-desktop has been uploaded
[21:16] <tseliot> hehe, I know, "just" is not really just
[21:16] <tseliot> ok, I think I can have a look at it tomorrow
[21:16] <tseliot> it shouldn't take long
[21:16] <tseliot> as usually gnome-desktop is the worst part
[21:17] <tseliot> to fix
[21:17] <seb128> thanks
[21:19] <seb128> chrisccoulson: want other updates?
[21:19] <seb128> ups
[21:19] <seb128> didrocks: want other updates?
[21:19] <seb128> chrisccoulson: sorry was for didrocks, you have downloaded enough ;-)
[21:19] <chrisccoulson> i can do. will have to be rather limited though with my bandwidth restriction;_
[21:19] <chrisccoulson> lol
[21:20] <chrisccoulson> i've still got all the jaunty updates from friday to do
[21:20] <chrisccoulson> ;)
[21:25] <seb128> chrisccoulson: how much can you download if you still want to do an update? ;-)
[21:25] <chrisccoulson> if it's an update that pulls in similar dependencies to gnome-session, then it should be no problem. my pbuilder is up to date and the packages are cached
[21:26] <seb128> chrisccoulson: not easy to see if build-depends are similar, gnome-media?
[21:27] <chrisccoulson> that should probably be ok
[21:27] <seb128> chrisccoulson: http://download.gnome.org/sources/gnome-media/2.25/gnome-media-2.25.92.tar.gz
[21:27] <didrocks> seb128: yes and thanks for sponsoring :)
[21:27] <seb128> let me know if that's an issue or too much to download
[21:27] <seb128> didrocks:
[21:27] <seb128> http://download.gnome.org/sources/glibmm/2.19/glibmm-2.19.8.tar.gz http://download.gnome.org/sources/gtkmm/2.15/gtkmm-2.15.5.tar.gz
[21:27] <seb128> if you want to do those today or tomorrow
[21:28] <didrocks> seb128: no problem, tomorrow probably :)
[21:28] <chrisccoulson> that should be ok, i'll work on that now
[21:28] <seb128> didrocks: yes sure
[21:28] <seb128> chrisccoulson: thanks
[21:28] <seb128> brb trying updates
[21:35] <mpt> Oh, Rhythmbox, you are so silly
[21:36] <seb128> mpt: what did it do now?
[21:36] <mpt> "An application is preventing the volume 'iPod' from being unmounted." ... Yes, that's YOU, RHYTHMBOX, who's preventing it
[21:37] <mpt> Which I think means that the Eject menu item in Rhythmbox never works.
[21:37] <didrocks> seb128: thx for pessulus too. Going to bed to have some time to watch TV :) Have a good day/night everyone!
[21:37] <seb128> right, there is a bug open about that
[21:37] <mpt> oh good :-)
[21:37] <seb128> didrocks: 'night, anything interest on TV right now?
[21:38]  * mpt -> home
[21:38] <didrocks> seb128: hum, let's see a little bit of "C dans l'air", talking about japan economic situation :)
[21:38] <seb128> didrocks: ok, enjoy!
[21:39] <didrocks> seb128: thanks, have a longer night than yesterday ;)
[21:41] <seb128> I will!
[21:48] <kenvandine_wk> bryce: i have no decent errors to give... but X just crashed, sort of
[21:48] <kenvandine_wk> dmesg reported some gem i915 stuff
[21:49] <bryce> kenvandine_wk: checked both /var/log/gdm/* nor /var/log/Xorg.0.log[.old]?
[21:49] <kenvandine_wk> looking
[21:49] <bryce> fwiw, tjaalton suggested these crashes may be due to some of the vblank stuff left in the kernel
[21:49] <kenvandine_wk> i got something in messages
[21:49] <bryce> he disabled vblank for us in X due to various problems, but the kernel patches are not yet reverted, and could still be causing issues.  working theory so far anyway
[21:50] <kenvandine_wk> http://pastebin.com/m503ac2a8
[21:50] <bryce> mm, yep, gem stuff in the kernel
[21:50] <kenvandine_wk> bryce: it was weird... every window hung and grayed out
[21:50] <kenvandine_wk> except one terminal :)
[21:50] <kenvandine_wk> which i could type in... but not get any tabs
[21:51] <kenvandine_wk> ok
[21:51] <kenvandine_wk> so you think that is already reported somewhere?
[21:51] <bryce> heh, never seen that before
[21:51] <bryce> kenvandine_wk: even if it is, it's worth re-reporting
[21:51] <kenvandine_wk> ok
[21:51] <bryce> it can always be duped pretty easily
[21:51]  * kenvandine_wk hates to create noise if we are confident it is  the same
[21:52] <bryce> actually I've come to the opinion that the "noise" from dupe bug reports is not nearly such a big deal
[21:52] <kenvandine_wk> ok
[21:52] <bryce> the worse noise is people adding confirms to existing bug reports, since sometimes they don't actually have the same problem, and it detracts from the original issue
[21:52] <kenvandine_wk> what should i report it against?
[21:53] <bryce> 'linux'
[21:53] <dobey> mpt: i think that's hal being stupid. i also can't eject from right clicking on my ipod in nautilus. i have to 'Unmount'
[21:53] <kenvandine_wk> hehe
[21:53] <bryce> since it's a kernel backtrace
[21:53] <kenvandine_wk> ok
[21:53] <dobey> mpt: and i have both Unmount and Eject options, which also seems wrong
[21:53] <bryce> kenvandine_wk: can you also subscribe me to that bug?
[21:53] <kenvandine_wk> sure
[21:53] <bryce> kenvandine_wk: then I can help with shepherding it towards a solution
[21:54] <bryce> kenvandine_wk: please attach your Xorg.0.log and lspci -vvnn to it as well, since it touches on X stuff.
[21:54] <kenvandine_wk> ok
[21:54] <bryce> kenvandine_wk: use 'ubuntu-bug -p linux' to report it, which I think may pull in necessary kernel files
[21:55] <bryce> or if you've already reported it, use the apport-collect command to add the files
[22:01] <kenvandine_wk> bryce: done
[22:01] <bryce> cool, bug id?
[22:04] <kenvandine_wk> bug 337451
[22:06] <bryce> kenvandine_wk: thanks
[22:06] <asac> back ... anyone with a more or less recent install, can you please paste ls /etc/fonts/conf.d?
[22:06] <bryce> oops, btw I'm 'bryceharrington' in launchpad.  'bryce' is some other guy
[22:06] <kenvandine_wk> bryce: damn...
[22:07] <kenvandine_wk> of course i can't unsubscribe him :)
[22:08] <bryce> he's not active in launchpad anyway
[22:08] <bryce> wish there was a way to take over usernames when the owner is inactive
[22:10] <bryce> kenvandine_wk: I wonder if lp: #336888 relates to your bug
[22:14] <Ng> seb128: the gnome-keyring-daemon didn't really change anythin :/
[22:14] <seb128> Ng: lack a word?
[22:15] <Ng> +update
[22:15] <seb128> Ng: update? did you restart your session? is it still crashing? can you get a stracktrace?
[22:15] <Ng> I think I can get a trace now
[22:15] <Ng> I have a bunch of debsyms installed :)
[22:16] <bryce> kenvandine_wk: interesting; I searched launchpad for "drm_gem_object_free" and yours was the only bug that turned up
[22:16] <Ng> and I can reproduce the crash easily enough. ssh in a for loop, it runs for a bit, then wedges. kill the loop, try one more ssh, the daemon segfaults
[22:16] <bryce> so either no one else has seen this bug, or no one else's report included the stack trace
[22:31] <Ampelbein> seb128: sry about the totem issue, i accidently built the 2.25.91 version with pbuilder thus not seeing the build-failure
[22:31] <seb128> that's ok
[22:31] <Ampelbein> will do again with autoreconf.
[22:31] <kenvandine_wk> bryce: ok... so glad i filed it :)
[22:32] <seb128> thanks
[22:32] <bryce> kenvandine_wk: yep.  Fwiw, I think the vblank bug (the one I mentioned above) is a separate issue.
[22:32] <calc> is there any way with gdb and ddebs to get the source file and line in a backtrace?
[22:33] <bryce> calc: you mean without installing -dbgsym's ?
[22:33] <calc> iirc there are ways to do this with gdb but it doesn't seem to do it at least automatically with just adding ddebs
[22:33] <calc> bryce: with installing dbgsym's
[22:33] <calc> bryce: once i installed those i got the function names but not the line numbers, etc
[22:33] <bryce> if you install those, then it should give the line numbers and such automatically (at least, it does for me with X)
[22:34] <calc> oh hmm, i wonder if it is some breakage with OOo
[22:34] <calc> i just get things like:
[22:34] <calc> #9  0x00007fcc6ae061f0 in SfxObjectShell::SaveTo_Impl () from /usr/lib/openoffice/program/../basis-link/program/libsfxlx.so
[22:34] <bryce> actually I should say for X we have -dbg packages which are slightly different than -dbgsym, but I believe both work analogously and give line numbers
[22:35] <bryce> calc, hmm
[22:36] <bryce> is libsfxlx.so in java or C++?
[22:36] <calc> c++ i believe
[22:36] <calc> i don't get line numbers anywhere in the backtrace afaict
[22:36] <bryce> calc: try running 'backtrace full' ?
[22:36] <calc> bryce: iirc i did that and it just claimed no locals for anything
[22:37] <calc> but i can try it again in a bit
[22:37] <bryce> yeah the no locals thing is annoying, but at least it should give line num's
[22:37] <seb128> your debug version is not a debug one
[22:37] <calc> seb128: ah not debug, just not stripped?
[22:37] <seb128> it seems
[22:37] <calc> ah ok
[22:37] <seb128> well dunno how it built
[22:38] <seb128> but you should get line numbers
[22:38] <calc> seb128: i don't know how dbgsym packages are created, i suppose i need to enable full debug in my build and just have it be stripped out during regular build?
[22:38] <seb128> the dbgsym are just built using dh_strip too
[22:38]  * calc looks in his rules file
[22:38] <seb128> equivalent to standard dbg build
[22:38] <seb128> they just don't clean the binaries
[22:39] <seb128> so they don't get stripped twice when normal dh_strip runs
[22:39] <seb128> do you build using -g?
[22:40] <calc> we do something different apparently, i see comment in the rules file that -g causes the deb to be 400MB
[22:41] <bryce> calc, what we do for X packages is set up a separate binary package that holds the debug symbols (see xserver-xorg-video-ati as a reasonably concise example)
[22:41] <calc> i may take a look at it closer though since ubuntu builds things a bit differently than debian in general
[22:41] <seb128> well -g add debug symbols
[22:42] <seb128> then dh_strip is run usually which clean those
[22:42] <bryce>         dh_strip -pxserver-xorg-video-ati --dbg-package=xserver-xorg-video-ati-dbg
[22:42] <calc> it's possible this part of the rules file is old and rotten
[22:42] <calc> rules for OOo is over 3000 lines so completely possible
[22:43] <bryce> yikes
[22:46] <Ampelbein> seb128: i'm encountering an error running autoreconf (no matter if i use autoreconf or autoreconf2.50), see http://paste.ubuntu.com/126043/
[22:49] <seb128> Ampelbein: use "autoreconf" which is 2.63 and works?
[22:49] <seb128> let me try
[22:50] <seb128> autoreconf works on my jaunty
[22:52] <Ampelbein> does not work here, giving the same error.
[22:53] <Ampelbein> autoconf: Installed: 2.63-2ubuntu1
[22:53] <seb128> same version
[22:54] <Ampelbein> which automake-version have you installed?
[22:54] <seb128> automake --version?
[22:55] <seb128> 1.10
[22:55] <seb128> ii  automake             1:1.10.2-0ubuntu1    A tool for generating GNU Standards-compliant Makefiles
[22:55] <Ampelbein> same.
[22:56] <seb128> do you get any error if you run automake?
[22:57] <Ampelbein> same as in http://paste.ubuntu.com/126043/ starting from line 7
[22:58] <seb128> hum, I don't see an error in this log
[22:58] <seb128> I mean any error message before the exit 1 error
[22:59] <seb128> automake --verbose?
[23:00] <chrisccoulson> you tried "autoreconf -f"?
[23:00] <Ampelbein> hmm, in a virtual machine it works flawlessly. i guess i messed up my system.
[23:01] <chrisccoulson> seb128 - i did the gnome-media update, and imported it in to bzr too
[23:01] <seb128> chrisccoulson: thanks!
[23:01] <chrisccoulson> you're welcome
[23:02] <Ampelbein> will reinstall later, now i use the vm to do the update.
[23:05] <chrisccoulson> Ampelbein - when doing the autotools update with totem, remember that a new Makefile.in gets created due to the BBC plugin patch. You'll need to remember to add this extra file to the patch. I forgot last time and then it failed to build
[23:06] <seb128> quilt should be forbidden to use
[23:06] <chrisccoulson> i quite like it, but when extra files are silently created, it's a real pain
[23:07] <chrisccoulson> you need to "quilt add" the files before they're created don't you (unless there's another way to do it?)
[23:07] <chrisccoulson> i forgot to do that last time, which missed the extra Makefile.in out of the patch
[23:08] <seb128> I don't like it
[23:08] <seb128> it's lot of extra command for no win usually
[23:08] <seb128> export QUILT_PATCHES=..*
[23:08] <seb128> quilt push
[23:08] <seb128> quilt add
[23:08] <seb128> edit
[23:08] <seb128> quilt refresh
[23:08] <seb128> ups, forgot quilt new
[23:09] <seb128> quilt pop
[23:09] <seb128> etc
[23:09] <seb128> where cdbs-edit-patch is one command
[23:09] <chrisccoulson> it can be a pain. i often forget to do the refresh before the pop, and then it messes up
[23:11] <seb128> I often forget the add and get files in the diff.gz
[23:11] <seb128> and lintian complain
[23:11] <seb128> and then fixing that is no fun, need to clean the source and restart
[23:12] <dobey> ugh
[23:12] <dobey> libcurl update broke apt-transport-https :(
[23:12] <chrisccoulson> i've done that countless times with the gnome-session updates actually, perhaps i should migrate it to cdbs at the next update?
[23:13] <seb128> chrisccoulson: we usually don't bother to not diverge from debian but for packages were we have ubuntu changes anyway why not
[23:13] <seb128> in fact we should rather get cdbs-edit-patch work with quilt packages
[23:14] <chrisccoulson> that would be good as well
[23:16] <seb128> re
[23:16] <seb128> awalton__: there?
[23:18] <seb128> awalton__: I commented on the bug rather
[23:25] <Nafallo> hohum
[23:25] <Nafallo> my 8.10 notifications doesn't show about the panel :-P
[23:25] <Nafallo> quite... interesting ;-)
[23:26] <seb128> Nafallo: what?
[23:26] <Nafallo> s/about/above/
[23:26] <seb128> intrepid notifications?
[23:27] <Nafallo> ya
[23:27] <Nafallo> the yellow stuff that's clickable :-P
[23:27] <seb128> you should be using jaunty ;-)
[23:27] <seb128> those are neither yellow nor clickable
[23:27]  * Nafallo larts seb128
[23:28] <seb128> heh!
[23:28] <Nafallo> seb128: do on my eeepc hon' ;-)
[23:28] <Nafallo> ehrm
[23:28] <Nafallo> yea. need new disk for the main laptop before I walk that ext4 path :-P
[23:32]  * calc is staying away from ext4 until at least 2.6.30
[23:33]  * xhaker is using ext4
[23:33] <calc> xhaker: good luck with that :)
[23:33] <calc> they are still finding lots of bugs in it at this point
[23:33] <Nafallo> well. the 200GB extra is part of my motivation as well :-)
[23:33] <xhaker> calc: thank you, i might need it
[23:33] <calc> Nafallo: i got a 500gb drive for my laptop, nice and fast :)
[23:34] <Nafallo> or 380GB extra. haven't decided yet :-)
[23:34] <Nafallo> calc: WD Blue? :-)
[23:34] <calc> Nafallo: seagate momentus 7200.4
[23:35] <calc> iirc its ~ 100MB/s in hdparm
[23:35] <Nafallo> hmm. oki.
[23:46] <x86> i've got a new Dell Latitude E4300 laptop with a built-in bluetooth miniPCI card
[23:46] <x86> ubuntu sees the miniPCI card just fine, and even paired to my bluetooth keyboard without any interaction on my part (i'm typing on it now)
[23:46] <x86> but I can't get the bluetooth manager thing to pair my bluetooth mouse...
[23:47] <x86> on the screen where it asks what device to pair, nothing shows up in the list at all
[23:47] <chrisccoulson> hi x86, you should visit #ubuntu for support
[23:47] <x86> it's impossible with ~2000 people in there, it scrolls so fast no one even sees what I type
[23:47] <x86> so i was hoping to get help here in a smaller channel
[23:51] <maxb> I have to agree, #ubuntu's kind of a victim of its own popularity
[23:52] <calc> xhaker: another good option is to ask in your loco channel
[23:52]  * calc has bluetooth in his laptop but doesn't have any bluetooth devices
[23:52] <chrisccoulson> i was just about to suggest what calc just suggested
[23:52] <chrisccoulson> i find my loco team to be quite helpful
[23:54] <x86> loco?
[23:57] <calc> x86: local community team, eg #ubuntu-(country)
[23:57] <x86> i'm sure #ubuntu-us is just as busy as #ubuntu ;)
[23:58] <calc> x86: for us there are state level channels that are smaller :)
[23:58] <Nafallo> s/ry/rycode/
[23:58] <x86> i've got someone helping with it though, so thanks for your help anyways guys
[23:58] <Nafallo> ;-)
[23:58] <x86> have a gooduntu evening :)
[23:58] <calc> x86: ubuntu-us only has 49 people
[23:58] <x86> hmm ok
[23:58] <x86> i'll check it out next time
[23:58] <x86> thanks again guys