@[email protected] to [email protected] • 1 year agoIssue with audio on pop!_OSyorunoken.s-ul.eumessage-square8fedilinkarrow-up119arrow-down11file-text
arrow-up118arrow-down1external-linkIssue with audio on pop!_OSyorunoken.s-ul.eu@[email protected] to [email protected] • 1 year agomessage-square8fedilinkfile-text
minus-square@[email protected]OPlinkfedilink1•1 year agoyes, but when I go to start the service this is what it outputs: Failed to start pipewire.service: Unit pipewire.service not found.
minus-squareMichael Murphy (S76)linkEnglish2•edit-21 year agoAre you using sudo? The pipewire/pipewire-pulse/wireplumber services only exist for users. systemctl --user enable --now pipewire pipewire-pulse wireplumber Make sure that the services are not masked, and use apt reinstall pipewire if necessary.
minus-square@[email protected]OPlinkfedilink1•1 year agomy electricity got cut off for like 10 hours and after it came back, it fixed itself. It still does it after every restart so I run systemctl --user restart pipewire.service and it fixes itself
minus-squareMichael Murphy (S76)linkEnglish1•1 year agoAre there any logs from startup indicating a potential issue here? You can see all warnings and errors since boot with journalctl -p 4 -xb.
minus-square@[email protected]OPlinkfedilink1•1 year agocouldn’t find anything in particular, there are just pages and pages of logs. My only solution is to restart the audio services everytime I boot in.
yes, but when I go to start the service this is what it outputs:
Failed to start pipewire.service: Unit pipewire.service not found.Are you using
sudo? The pipewire/pipewire-pulse/wireplumber services only exist for users.systemctl --user enable --now pipewire pipewire-pulse wireplumberMake sure that the services are not masked, and use
apt reinstall pipewireif necessary.my electricity got cut off for like 10 hours and after it came back, it fixed itself. It still does it after every restart so I run
systemctl --user restart pipewire.serviceand it fixes itselfAre there any logs from startup indicating a potential issue here? You can see all warnings and errors since boot with
journalctl -p 4 -xb.couldn’t find anything in particular, there are just pages and pages of logs. My only solution is to restart the audio services everytime I boot in.