Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror

Comment Re:are the debian support forums down? (Score 3, Informative) 286

Apologies if people think i shouldn't have posted this question to slashdot. I did a fair amount of googling to try to figure things out, to no avail. I didn't know whether my sound problems were caused by Debian or PulseAudio, so i figured Slashdot would cover both bases.

Aside from wanting to find a fix for my audio problems, i think the issue of Skype requiring a particular sound library is worthy of discussion on slashdot, as it the general UI issue of whether 'clever' behaviour should be easy to disable.

Oh, and i'm most definitely not a Microsoft troll, e.g. my day job involves working on some fairly hard-core linux debugging software.

Submission + - Stop PulseAudio from changing sound settings ? 3

cgdae writes: Does anyone know how to stop PulseAudio/Pavucontrol from changing sound settings whenever there is a hardware change such as headphones being plugged in/out or docking/undocking my laptop ?

I recently had to install PulseAudio on my Debian system because the Linux version of Skype started to require it. Ever since, whenever i dock/undock or use/stop using headphones, all sound disappears, and i have to go to Pavucontrol and make random changes to its 'Output Devices' or 'Speakers' or 'Headphones' tab, or mute/unmute things, or drag a volume slider which has inexplicably moved to nearly zero, until sound magically comes back again.

I've tried creating empty PulseAudio config files in my home directory, and/or disabling the loading of various PulseAudio modules in /etc/pulse/*.conf, but i cannot stop PulseAudio from messing things up whenever there's a hardware change.

It's really frustrating that something like PulseAudio doesn't have an easy-to-find way of preventing it from trying (and failing) to be clever.

[In case it's relevant, my system is a Lenovo X220 laptop, with Debian jessie, kernel 3.14-2-amd64. I run fvwm with an ancient config.]

Thanks for any suggestions,

- Julian

Comment OpenBSD's man page for systrace mentions this? (Score 5, Informative) 194

OpenBSD's systrace manpage appears to mention this problem in the BUGS section:

Applications that use clone()-like system calls to share the complete address space between processes may be able to replace system call arguments after they have been evaluated by systrace and escape policy enforcement.

Or see http://www.openbsd.org/cgi-bin/man.cgi?query=systr ace&apropos=0&sektion=0&manpath=OpenBSD+Current&ar ch=i386&format=html

Slashdot Top Deals

"If anything can go wrong, it will." -- Edsel Murphy

Working...