Sometime when I connect my headphones on my pc. They doesn't work and I can't understand. I have to turn off my pc two or three times to use it again. Someone have found a solution?
Dell xps 15 9550 ubuntu 16.04
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It only takes a minute to sign up.Sign up to join this community
Not a real fix, but a workaround.
Headphones should work now. Not pretty, but at least I can use headphones. I am able to unplug and plug the headphones in and it still works. But after a reboot, you have to do these steps again.
It's a known Bug (1575078) that seems to happen in Ubuntu 16.04 and Ubuntu 17.04 (depending on the Kernel version).
A bugfix seems to be available in Ubuntu 17.10.
All manual bugfixes seem to include the creation/editing of
/etc/modprobe.d/alsa.conf with different effects.
This configuration in
alsa.conf seems to be the best solution for all versions except Ubuntu 17.04:
options snd-hda-intel single_cmd=1 probe_mask=1 model=dell-headset-multi
or if you want avoid the dialogue asking which device you inserted into the headphone jack:
options snd-hda-intel single_cmd=1 probe_mask=1 model=headset-mic
Sorry, I can't add a comment (low karma), and actually, this is not a real answer.
Probably, the best thing you can do now: provide MORE information about system configuration, at least, related to sound subsystem.
Step one: check your headphones with the other device
Step two: check volume settings. For example, my PC turns sound off (or restore the previous volume level), when I plug anything to audio-out
Step three: connect your headphones and open Sound settings, try to run sound test. Run the same test without headphones, or with the other headphones.
If these actions will not help — make a screenshot of all tabs in Sound settings and attach them to your question.
But all this actions are not a real diagnostic, these are the necessary steps, you should do, before creating a question;) Probably, it is better to gather some information from system logs. But at first: eliminate obvious causes.
PS: 1-2-3-N reboots - it is not a diagnostic tool;)