Bug 461932 - Volume control disabled when Pulse Audio is restarted
Summary: Volume control disabled when Pulse Audio is restarted
Status: RESOLVED FIXED
Alias: None
Product: plasma-pa
Classification: Unmaintained
Component: applet (other bugs)
Version First Reported In: 5.26.3
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-11-17 04:45 UTC by Aaron Williams
Modified: 2024-10-02 10:57 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Audio devices present (192.63 KB, image/png)
2022-11-17 04:45 UTC, Aaron Williams
Details
No devices shown (97.91 KB, image/png)
2022-11-17 04:46 UTC, Aaron Williams
Details
Disabled icon in desktop panel (1.18 KB, image/png)
2022-11-17 04:47 UTC, Aaron Williams
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Aaron Williams 2022-11-17 04:45:22 UTC
Created attachment 153815 [details]
Audio devices present

SUMMARY
For some unknown reason I often need to restart Pulse Audio in order for it to work. The problem is that after
restarting pulse audio with pulse-audio -k; pulse-audio --start the volume control applet shows a red line through it and is disabled. Clicking on it shows no devices or applications.

STEPS TO REPRODUCE
1.  Restart pulse audio with pulse-audio -k; pulse-audio --start

OBSERVED RESULT
No audio devices or applications are shown

EXPECTED RESULT
I expect all of the applications and devices to be shown after restarting Pulse audio

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma:  OpenSUSE 15.4, Plasma 5.26.3
(available in About System)
KDE Plasma Version: 5.26.3
KDE Frameworks Version: 5.99.0
Qt Version:  5.15.7

ADDITIONAL INFORMATION
Comment 1 Aaron Williams 2022-11-17 04:46:17 UTC
Created attachment 153816 [details]
No devices shown
Comment 2 Aaron Williams 2022-11-17 04:47:06 UTC
Created attachment 153817 [details]
Disabled icon in desktop panel
Comment 3 ratijas 2022-11-18 22:56:14 UTC
I have run into this once or twice, but with PipeWire. Not sure if that counts for confirmation. Also, I don't have a reliable way to reproduce my case: if I run `systemctl --user restart pipewire.service`, devices and outputs briefly disappear, but all come back after few seconds.
Comment 4 Harald Sitter 2024-10-02 10:57:37 UTC
6.2 will have improved context reconnect UX.