search

LukeSmithxyz / voidrice

My dotfiles (deployed by LARBS)
GNU General Public License v3.0
4.26k stars 1.22k forks source link

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

Open BEST8OY opened 7 months ago

BEST8OY commented 7 months ago

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 commented 7 months ago

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

BEST8OY commented 7 months ago

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 commented 7 months ago

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! https://github.com/LukeSmithxyz/voidrice/issues/1287

appeasementPolitik commented 4 months ago

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 commented 3 months ago

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!