Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to connect to pulseaudio when booting with headphone already connected #1393

Open
BEST8OY opened this issue Jan 16, 2024 · 5 comments

Comments

@BEST8OY
Copy link

BEST8OY commented Jan 16, 2024

Hello
So, the thing is when I boot into the system while the headphone is already connected to laptop Puslemixer doesn't work.
In this situation the headphone works but when I plug the headphone out the speakers don't work.

If I boot into the system without connected headphone, Pulsemixer, speakers and headphone all work fine!

What should I to avoid this problem??

@BEST8OY BEST8OY changed the title Failed to connect to pulseaudio when logging in with headphone already connected Failed to connect to pulseaudio when booting with headphone already connected Jan 16, 2024
@BEST8OY
Copy link
Author

BEST8OY commented Jan 17, 2024

Not sure what happened!
For now it's okay.
If it happened again I'll reopen the issue!

@BEST8OY BEST8OY closed this as completed Jan 17, 2024
@BEST8OY
Copy link
Author

BEST8OY commented Jan 17, 2024

Okay.
The problem is with pipewire config file in /.config I removed that and now everything is good!
It sometimes causes the statusbar scripts to not load or sometimes when they load the pulsemixer only shows dummy audio.

@BEST8OY BEST8OY reopened this Jan 17, 2024
@BEST8OY
Copy link
Author

BEST8OY commented Jan 17, 2024

I also installed the two packages mentioned here and still there is some sort of conflict because of the config file which causes the issue!
#1287

@appeasementPolitik
Copy link
Contributor

Had the same issue. Boot with headphone connected and everything is fine, but boot without headphone or unplug and replug the headphone, and it doesn't work anymore.

Fixed it by removing ~/.config/pipewire/pipewire.conf, and replacing it with ~/.config/pipewire/pipewire.conf.d/user-session.conf with the following content:

context.exec = [
    { path = "/usr/bin/wireplumber" args = "" condition = [ { exec.session-manager = null } { exec.session-manager = true } ] }
    { path = "/usr/bin/pipewire" args = "-c pipewire-pulse.conf" condition = [ { exec.pipewire-pulse = null } { exec.pipewire-pulse = true } ] }
]

Also has the advantage of being more future-proof. I didn't need to install alsa-firmware or alsa-utils like in the linked issue. The second reason for the problem was that I had set the output to Analog Stereo Output. Setting it to Analog Stereo Duplex fixed it.

@bybv
Copy link

bybv commented Apr 30, 2024

Thank you so much for this. I will do a fresh install and see if this solves my issue. I had the same issue where Super+F4 pulled up a blank pulsemixer and couldn't figure out the pattern.

However I'm not following your note about the analog stereo output vs analog stereo duplex. Where were you making these selections?

Also has the advantage of being more future-proof. I didn't need to install alsa-firmware or alsa-utils like in the linked issue. The second reason for the problem was that I had set the output to Analog Stereo Output. Setting it to Analog Stereo Duplex fixed it.

Cheers!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants