Pulseaudio module is failing on system startup
See original GitHub issueSo, after fixing #103 , I get “pacmd stat exited with status code 1”. This happens at boot and until I run an application that requires sound capabilities (e.g Spotify). Running pacmd stat
on the terminal returns (translated):
No PulseAudio daemon running or not running as session daemon
Not sure if it’s a fault on my end or if using pacmd stat
to fix #103 is not a good solution.
EDIT: Just to be clear, running spotify and then reloading i3 config solves the issue, but it’s suboptimal…
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:15 (11 by maintainers)
Top Results From Across the Web
Problem with pulseaudio at startup (it doesn't start) - Ask Ubuntu
I tried: pulseaudio -k , first and then: pulseaudio -D but, I just got the messages: Fail to stop the daemon because it...
Read more >PulseAudio/Troubleshooting - ArchWiki
Applications setting their volume on startup will therefore cause the system volume to "jump". Fix this by disabling flat volumes, as ...
Read more >Pulseaudio Daemon Startup Failed - Super User
Running pulseaudio -v. in a terminal (run pulseaudio -k first if it complains about already being started, but since you say it doesn't...
Read more >pulseaudio fails on startup when module-rtp-recv is enabled
in /etc/pulse/default.pa and everything works as expected if I run pulseaudio -D from a terminal after boot. ... Jul 15 23:15:54 raspberrypi pulseaudio[739]: ......
Read more >388971 – fluxbox fails to start pulseaudio at login
Description of problem: The pulseaudio daemon is started by gnome. For those of us not using gnome, several bugs prevent it from being...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Confirmed, same here after rebooting my system. Will investigate. Thanks for the bug report!
I didn’t experience the original issue but performed testing with the latest branch based on what I saw reflected in the comments and believe this to be fixed.