=== bluesmoke is now known as Amaranth
[10:09] <mib_guqaued9> hi all
[10:09] <mib_guqaued9> can i get some help ?
[15:10] <asac> any way i can tell totem to use alsa again (if i switch the gstreamer-properties to alsa, totem greys out the volumen control)
[15:11] <tyche> Only way I've found to work was to disable PulseAudio, and force the whole thing back to Alsa
[15:12] <Amaranth> Why would you do that?
[15:13] <tseliot> killing pulse helps but it's not a long-term solution
[15:13] <asac> i killed pulseaudio
[15:13] <asac> mplayer can then use alsa again
[15:13] <tyche> Because PulseAudio just doesn't work.  I hit too many bugs, too many things (like midi) that it just wouldn't support
[15:13] <asac> gstreamer-properties can play test sound
[15:13] <asac> but totem seems to have forgotten everything ;)
[15:13] <asac> for me pulse just makes sound not work in jaunty now
[15:14] <asac> e.g. play video -> no sound (or well, really really silent)
[15:14] <asac> what was the benefit of using pulse again?
[15:14] <asac> ;)
[15:14] <tyche> tseliot: I agree.  It's not a long term solution.  The long term solution is for Ubuntu to use something that WORKS.  Period.  Not mess around with experimental stuff.  Wait until something is PROVEN THEN add it in.
[15:17] <asac> well, i could certainly live without midi for a while ;) ... but when it kills sound completely its rather an annoying thing
[15:18] <asac> tyche: i think upstream thinks that pulse is not really experimental ;)
[15:18] <tseliot> it just makes sound choppy here ;)
[15:18] <tyche> asac: I think upstream needs to listen to bug reports.  They didn't even respond to the one I entered.
[15:20] <asac> hmm we are still on 9.13 ... upstream has released 0.14 a few days ago ;OI
[15:20] <asac> 9.14
[15:20] <tyche> tseliot: Try listening to "Le Sacre du Prentemps" when it's choppy.  Especially if you have the piece very nearly memorized.  You'll see why I have as little hair as I do.
[15:20] <asac> http://pulseaudio.org/milestone/0.9.14
[15:22] <tyche> Oh, BTW, I'm https://launchpad.net/~tyche.  Or, for a better picture, see:  http://www.flickr.com/photos/22090195@N03/3103654354/
[15:24] <asac> heh
[15:25] <tyche> Another version of the second picture is titled "Complaint Department"
[15:31] <tyche> tseliot: BTW, thank you for your work on the NVidia driver, and Envy.  You've helped me a great deal over the past couple of years.
[15:32] <tseliot> I'm glad to know that it was of help
[15:33] <tyche> It was.  A previous NVidia card used to cause me the fits trying to get it to work.  you came out with Envy, and made it simple.  The card in this machine is newer, and easier, but it still helped.
[15:35] <tseliot> :-)
[17:12] <crusader1> Hi all,
[17:12] <crusader1> I'm not sure that this is the right channel, but maybe someone can help me.
[17:12] <crusader1> At least someone can tell me were to post this:
[17:13] <crusader1> I was searching for a way to set same option globally on this installtion.Especially for one to look the screen when the screensaver starts, which also should be enabled globally.
[17:13] <crusader1> I've found the gconf-editor and the mandatory options. For same options (eg. idle_activation_enabled, idle_delay or mode) this was the perfect way. but one does not work:
[17:13] <crusader1> /apps/gnome-screensaver/lock_enabled
[17:13] <crusader1> can some check if I'm doing something wrong or maybe I've found a bug.
[17:13] <crusader1> I've testes this on diffent boxes, all the same (8.04 i386, 8.10 i386. 8.10 amd64).
[17:16] <pochu> crusader1: I think you want to set it in /usr/share/gconf/defaults/ so that it works system-wide
[17:17] <pochu> you could put "/apps/gnome-screensaver/lock_enabled true" in a file called /usr/share/gconf/defaults/50_my_gnome_screensaver
[17:19] <crusader1> ok i can try this, but why have a tool like the gconf-editor (which works perfect with other options) when I have to go other way?
[17:20] <pochu> gconf-editor is per-user AFAIK
[17:20] <pochu> not system-wide
[17:21] <pochu> by the way, people will still be able to disable it
[17:22] <crusader1> in the gconf-editor you can set every option "mandatory" (only as admin/root) then this option is set fix to every user
[17:23] <crusader1> AFAIK
[17:26] <pochu> ah, I see. I didn't know that feature existed
[17:27] <pochu> and that doesn't work for that option?
[17:27] <crusader1> so for some thing I've need this feature is perfect... but it seems not working fine for /apps/gnome-screensaver/lock_enabled
[17:29] <crusader1> after tested in different boxes, i'm looking for others to check whether I'm doing something wrong or i've found a bug
[17:30] <pochu> Have you checked if it was added to some file in /etc/gconf/2/ ?
[17:30] <pochu> (I think that's where it should be added)
[17:32] <crusader1> it is added to /etc/gconf/gconf.xml.mandatory/%gconf-tree.xml
[17:32] <pochu> as the others?
[17:32] <crusader1> as the others!
[17:36] <pochu> crusader1: so, no idea then. May be a bug as you thought :)
[17:38] <crusader1> so were to report it? I'm new to the ubuntu-community and I'm not sure what to do now?
[17:39] <crusader1> I'm looking for an easy way to do this...
[17:40] <pochu> I'd say here: https://launchpad.net/ubuntu/+source/gconf2/+bugs
[17:43] <crusader1> ok, then I've to create a new account for launchpad? is this the offical site for reporting bugs? (no .buntu in name?)
[17:44] <pochu> yes, it's the official one for Ubuntu
[17:45] <pochu> you could also report it upstream at bugzilla.gnome.org, but if you don't have an account there, you will have to create one too ;)
[17:46] <crusader1> don't have one there either. thanks a lot. i will try to get help there
[17:47] <crusader1> bye
=== onestone__ is now known as onestone
[21:30]  * Nafallo wonders why we have a user administration tool where we can't disable users...
=== bluesmoke_ is now known as Amaranth