| |||||||||||||
Tumbleweed backs off on systemd for nowTumbleweed backs off on systemd for nowPosted Sep 23, 2011 18:37 UTC (Fri) by jspaleta (subscriber, #50639)In reply to: Tumbleweed backs off on systemd for now by nevets Parent article: Tumbleweed backs off on systemd for now
To be clear, what is the expected default scenario on boot from your perspective?
With the usb headset plugged in you want the sound to be routed to both the speakers and the usb headset as the default configuration?
-jef
(Log in to post comments)
Tumbleweed backs off on systemd for now Posted Sep 23, 2011 21:58 UTC (Fri) by nevets (subscriber, #11875) [Link]
I want sound to default to my speakers. I have a single app (twinkle) that should go to the headset. Note, this headset has a mic and is for calling. Twinkle can select which source dependent from other sound apps. I have yet to figure out how to consistently make it default to the speakers.
pulseaudio digression [Tumbleweed backs off on systemd for now] Posted Sep 23, 2011 22:35 UTC (Fri) by sfeam (subscriber, #2841) [Link] I've had similar aggravations ever since pulseaudio appeared. In my case there is no bluetooth involved, but pa randomly loses devices and settings across suspend/resume, shutdown/reboot, and even at less well defined times. I have found no real solution, but for me it mostly worked to get an acceptable state in place and then do "chmod -R a-w ~/.pulse". That obviously has other drawbacks, but at least it stopped losing track of the devices altogether. And the instantaneous settings mostly got pinned as the default state.
|
|||||||||||||