Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Not selecting headphones output automatically when headphones are plugged in (which it used to do on my previous installation of Manjaro/Budgie).
- default setting: sound to spkrs works fine
- plug in headphones: no sound to spkrs or headphones
- manually change output to "headphones" in Settings>Sound or in pavucontrol
- sound now in headphones and cut off to spkrs
- unplug headphones: sound to spkrs resumes
- replug headphones: no sound to spkrs or headphones
Try udevadm in monitor mode to see if you get an event when connecting. It's not hard to add a udev rule that can run pavucontrol.
I have not used this previously - not familiar with it. Checking through arch-wiki it seems I will need to specify a device to be monitored, else I will get a printout of all udev kernel events, which could be voluminous.
Really? You are connecting and disconnecting devices that often that it would be voluminous?
Sorry, I ran an incorrect script. This is what is returned when I plug in the headphones - nothing.
Code:
[drew@drew-dell ~]$ udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
I tried on a CentOS system to see if I got any ACPI or udev events, and I don't get either. I think you are dependent on the polling in pulseaudio, and I don't know of a way to trigger a script on that.
I tried on a CentOS system to see if I got any ACPI or udev events, and I don't get either. I think you are dependent on the polling in pulseaudio, and I don't know of a way to trigger a script on that.
Thanks for looking into it. I'll try posting on the Manjaro forum; maybe someone there has a solution. If so, I'll report back here.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.