[00:27] <gicmo> anybody here?
[03:31] <jgamio> hi
[05:31] <nxvl> is there any way to tell a .desktop file to use gkdu or kdesu depending on if it is KDE or GNOME?
[05:31] <nxvl> or do i just need to install 2 .desktop files?
[05:49] <dholbach> good morning
[05:51] <nxvl> dholbach: guten nacht!
[05:52] <dholbach> hi nxvl - hehe :)
[07:16] <lool> nxvl: su-to-rootN
[07:16] <lool> s/N/?
[08:30] <slomo_> seb128: the youtube plugin works fine here for me... do you get the same failure?
[08:31] <seb128> slomo_: did you try on hardy or debian?
[08:31] <seb128> slomo_: searching for videos work correctly, ie ubuntu lists lot of those
[08:31] <seb128> but playing doesn't work
[08:32] <seb128> trying to play "Ubuntu @ the Library" for example
[08:33] <seb128> "0:00:28.448213545 11128 0x80a2490 ERROR                totem /build/buildd/totem-2.22.0/src/backend/bacon-video-widget-gst-0.10.c:330:bvw_error_msg: uri     = http://www.youtube.com/get_video?video_id=nWIrxuF5NSo&t=OEgsToPDskJBHaSvPvJkOqOMX83tFaJT
[08:33] <seb128> ** Message: Error: Could not open resource for reading.
[08:33] <seb128> gstgnomevfssrc.c(841): gst_gnome_vfs_src_start (): /play/source:
[08:33] <seb128> Could not open vfs file "http://www.youtube.com/get_video?video_id=nWIrxuF5NSo&t=OEgsToPDskJBHaSvPvJkOqOMX83tFaJT" for reading: Generic error (2)
[08:33] <slomo_> seb128: that was on debian, i don't think there's any important difference with the used packages... hm, let me try that one :)
[08:33] <seb128> "
[08:33] <slomo_> yes, that one fails for me too
[08:33] <seb128> I've been trying a lot of different one in the ubuntu query and most don't play due to similar errors
[08:34] <slomo_> seb128: search for "badger", the first result plays for me
[08:35] <seb128> slomo_: is that the eeePC gutsy one?
[08:35] <seb128> same error, that seems to be random
[08:36] <seb128> I get some videos to play sometime
[08:36] <slomo_> no, the badger song :) www.badgerbadgerbadger.com
[08:36] <seb128> trying to play the badger song one
[08:36] <seb128> "** Message: Error: Element doesn't implement handling of this stream. Please file a bug.
[08:36] <seb128> gstffmpegdemux.c(1372): gst_ffmpegdemux_sink_activate_push (): /play/decodebin13/ffdemux_flv1:
[08:36] <seb128> failed to activate sinkpad in pull mode, push mode not implemented yet"
[08:36] <slomo_> hm
[08:36] <seb128> but I might not have gstreamer-plugins-bad installed
[08:36] <seb128> let me check
[08:36] <slomo_> yes, that's missing definitely
[08:37] <slomo_> you need the flv demuxer from -bad
[08:37] <seb128> shouldn't the easy codec thing be triggered?
[08:38] <slomo_> no, gst-ffmpeg can demux flv too... just not in push mode (i.e. http)
[08:38] <seb128> ok, it works now
[08:38] <seb128> slomo_: alright, so the thing just doesn't like the ubuntu videos for some reason
[08:40] <seb128> doesn't like the one from a debian query neither
[08:40] <slomo_> yay, i'm playing ubuntu @ the library now
[08:41] <slomo_> seems to be something broken in gnomevfs, with soup it works
[08:41] <seb128> what did you change?
[08:41] <seb128> ah
[08:41] <slomo_> we should talk with gicmo ;)
[08:42] <seb128> I doubt he's still interested in gnomevfs ;-)
[08:42] <slomo_> last time i had a similar bug he listened to me... and now we can seek over http without bigger problems
[08:42] <slomo_> btw, for some reason when using gnomevfs one gets a "forbidden" when trying to download the video itself, all redirects before work fine
[08:44] <lool> slomo_: Missing referrer?  cookie?
[08:44] <slomo_> then soup would miss it too... well, let's ask wireshark :)
[08:47] <slomo_> seb128: do you keep track of http://live.gnome.org/GioPort and get patches for gio ports in ubuntu?
[08:48] <seb128> slomo_: no
[08:48] <seb128> slomo_: we stick to what GNOME do, they usually get things to svn
[08:49] <slomo_> hm, maybe found the bug...
[08:52] <slomo_> most notable difference between soup and gnomevfs is, that gnomevfs sends keepalive http requests and includes "Range: 0-" in the header... apart from that they do the same. so i guess the range makes youtube unhappy and it should work fine with gnomevfs 2.21.90 or something
[08:52] <slomo_> seb128: if you still have that version around (without the http seeking patch) could you test? :)
[08:54] <seb128> slomo_: ok, trying
[09:01] <lool> slomo_: Not sure, but I would guess the particular range "Range: 0-" can be ommitted, no?
[09:01] <seb128> slomo_: that makes it work correctly
[09:01] <slomo_> seb128: thanks, would you mind filing a bug upstream? i've to leave now for an hour or something... i could do it afterwards though
[09:01] <slomo_> lool: iirc gnomevfs uses this to determine if it can seek later or not
[09:02] <seb128> slomo_: I'll let you do it, there is no hurry and you know what to write there ;-)
[09:02] <lool> slomo_: Aha
[09:02] <slomo_> lool: but then... if that Range stuff failed it should fallback to a request without Range... maybe the "forbidden" confuses it here
[09:02] <slomo_> lool: or that all redirects before happily accepted the range
[09:03] <slomo_> whatever, bbl :)
[09:04] <lool> slomo_: Right
[09:33] <DktrKranz> Has someone familiar with mono seen something similar to debian 470328 ?
[09:33] <ubotu> Debian bug 470328 in beagle "beagle: FTBFS: GConfThreadHelper.cs(30,7): error CS0246: The type or namespace name `GLib' could not be found. Are you missing a using directive or an assembly reference?" [Serious,Open] http://bugs.debian.org/470328
[09:33] <slomo_> DktrKranz: nope
[09:35] <DktrKranz> slomo_, there's a fix in gnome 514252 but it seems incomplete.
[09:35] <ubotu> Gnome bug 514252 in General "beagle evolution backend doesn't build" [Trivial,Resolved: fixed] http://bugzilla.gnome.org/show_bug.cgi?id=514252
[09:37] <slomo_> DktrKranz: why incomplete?
[09:37] <DktrKranz> it keeps FTBFS
[09:37] <slomo_> did you regenerate or patch configure too (not only configure.in)?
[09:37] <DktrKranz> well, probably it's because of my very poor mono knowledge
[09:38] <DktrKranz> both
[09:38] <slomo_> and when getting a svn checkout it fails too?
[09:38] <DktrKranz> didn't tried, let's see
[09:40] <DktrKranz> oh, wait a sec...
[09:40] <DktrKranz> http://svn.gnome.org/viewvc/beagle/trunk/beagle/configure.in?r1=4470&r2=4469&pathrev=4470
[09:40] <DktrKranz> is backslash required?
[09:40] <DktrKranz> glib-sharp-2.0 >= $GTK_SHARP_REQUIRED      \
[09:43] <slomo_> yes
[09:44] <DktrKranz> so, I missed it
[09:45] <slomo_> :)
[09:45] <slomo_> seb128: btw, don't sync glib 2.16.1-2 from debian :) it breaks network-manager in a way that doesn't make much sense
[09:46] <seb128> slomo_: ok, thanks, I was no planned to do soon due to freeze but good to know ;-)
[09:48] <huats> moring everyone
[09:50] <seb128> hey huats
[09:51] <huats> hello seb128
[09:51] <huats> how are you ?
[09:52] <seb128> good, thanks
[09:52] <seb128> how are you?
[09:52] <huats> good too
[09:52] <huats> :)
[09:53] <huats> not very available to work on desktop stuff for a few days since I am quite working on the new ubuntu-fr website
[09:53] <huats> but I try to find some little time :)
[09:55] <seb128> cool
[09:59] <huats> seb128: you might be able to tell me : do you have any idea why gnome-commander has been sync for powerpc and not for i386 ?
[09:59] <huats> or amd64 ?
[09:59] <huats> where can I find such information ?
[09:59] <seb128> huats: we sync sources, not binaries
[10:00] <seb128> so your question is why it didn't build on those
[10:00] <huats> yeah that was my question ...
[10:00] <seb128> huats: https://launchpad.net/ubuntu/+source/gnome-commander/ has informations
[10:00] <seb128> hardy i386   Failed to build
[10:00] <huats> I guess there is a FTBFS somewherre :)
[10:00] <seb128> installability issue
[10:00] <seb128> ask some buildd admin to give it a retry
[10:01] <huats> ok
[10:02] <DktrKranz> slomo_, backslash was the key :)
[10:25] <huats> seb128: you were right, the rebuild of the sources fixes the pb...
[10:25] <huats> :)
[10:25] <huats> thanks
[10:25] <seb128> huats: you are welcome
=== Hobbsee is now known as Spiky
=== Spiky is now known as Hobbsee
=== dholbach_ is now known as dholbach
[17:02] <_MMA_> Can we turn off "Show Weather/Temp" in Hardys Clock prefs? Because a location is not set by default, it adds a large amount of space on the left of the applet in the panel.
[17:03] <_MMA_> Turn off by default that is.
[17:09] <seb128> _MMA_: no
[17:09] <seb128> _MMA_: that is a bug and it should be fixed rather
[17:09] <seb128> _MMA_: vuntz knows about the issue
[17:10] <_MMA_> It being on by default or no location set?
[17:10] <seb128> adding space when no location is configured
[17:10] <_MMA_> I see. Will it make Hardy?
[17:10] <_MMA_> The fix?
[17:10] <Amaranth> crap now i can't get rid of it
[17:11] <Amaranth> i added my own location and it added the temp but it doesn't do the forecast so it's no use to me
[17:11] <Amaranth> and now it won't go away :P
[17:11] <seb128> _MMA_: depends on whether if somebody work on a patch for the issue
[17:11] <Amaranth> ah, unchecked the boxes
[17:12] <_MMA_> seb128: If the "fix" won't make Hardy, and it can be set in gconf (unchecking the options) I would think that would be a fine solution for now.
[17:14] <seb128> _MMA_: we have space on this panel, I don't think it's that an important issue
[17:15] <seb128> I would prefer having the feature working out of the box when adding a location
[17:15] <seb128> and we go no complain so far
[17:16] <_MMA_> Sure. I'll just turn it off for Ubuntu Studio till there's a proper patch.
[17:19] <_MMA_> seb128: And nobody is gonna complain 'till it's released. Classic situation. And if you won't listen to people like me, we'll continue to put out  product with quirks like this.
[17:22] <seb128> _MMA_: oh, that's not true, subscribe one week to the desktop bugs if you want to see if nobody complains about issues ;-)
[17:24] <_MMA_> seb128: Pales in comparison to after a release. And sure, "nobody" should have been "most people".
[17:25] <seb128> _MMA_: still don't agree with you, but let's not discuss on that
[17:25] <_MMA_> seb128: But this will quickly go into how we work and what I feel the shortcomings of our system are. Not really something to get into here.
[17:25] <seb128> _MMA_: "how we work" being?
[17:25] <_MMA_> seb128: In Prague. :)
[17:25] <seb128> _MMA_: you don't like having somebody in charge of packages and controlling changes we apply or not?
[17:26] <_MMA_> Some things are better in person.
[17:26] <_MMA_> I'll just leave it at that for now. :) We _really_ don't wanna get into it here. :)
[17:27] <seb128> well, I'm not sure if I should take it as a personnal criticism, but as you want
[17:27] <seb128> there is no perfect answer to most changes
[17:27] <_MMA_> seb128: Sure, but others might and text just isn't best for some chats.
[17:27] <seb128> that's like having tracker enabled or not, or deskbar installed
[17:27] <seb128> you can't make everybody happy and you need to decide on something
[17:33] <lmanul> seb128: ping?
[17:34] <seb128> lmanul: hi
[17:34] <lmanul> seb128: Hi !
[17:34] <lmanul> Any news for mentors? Should I subscribe to something if I want to help out?
[17:35] <seb128> no idea
[17:35] <lmanul> seb128: Okay, I saw the list of organizations was out, but I guess if you don't know it mustn't be time yet :)
[17:35] <lmanul> seb128: Thanks anyway
[17:35] <seb128> I've been busy updating GNOME to 2.22 etc and didn't read those discussions
[17:35] <seb128> you are welcome
[17:36] <seb128> try asking dholbach tomorrow
[17:36] <seb128> he might know better
[18:52] <mvo> no seb128?
[19:03] <mvo> does anyone here particullarly cares about evo-data-server?
[19:05] <Keybuk> in what kind of sense?
[19:10] <mvo> fixing a file overwrite problem, but I'm happy to do it, I had hoped that seb128 would be around
[19:11] <Keybuk> it's a bit late ;)
[19:11] <mvo> yeah, good point :)
=== asac_ is now known as asac
[19:27] <Keybuk> vuntz: why is it that sometimes, when I click the Window Selector applet, it gives me the applications from all of my viewports
[19:27] <Keybuk> but then sometimes it only gives me from my current viewport
[23:50] <vuntz> Keybuk: the window selector always lists all windows
[23:50] <vuntz> if it doesn't, then, there's a bug
[23:50] <vuntz> maybe it happens when all your apps are in the current workspace?
[23:51] <vuntz> could also be some viewport weirdness