Bug 425391 - Sometimes sound applet does not detect sound device after re-login on neon unstable
Summary: Sometimes sound applet does not detect sound device after re-login on neon un...
Status: RESOLVED FIXED
Alias: None
Product: plasma-pa
Classification: Plasma
Component: applet (show other bugs)
Version: 5.20.3
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: David Rosca
URL:
Keywords:
: 428979 (view as bug list)
Depends on:
Blocks:
 
Reported: 2020-08-15 16:22 UTC by Patrick Silva
Modified: 2023-11-17 00:34 UTC (History)
6 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Silva 2020-08-15 16:22:45 UTC
SUMMARY
Sometimes a diagonal red line overlaps the sound applet in systray
after I restart X11 or Wayland session on neon unstable.
When I click on sound applet, its popup opens and says that there is no sound device, but my speakers work as expected when I open an audio file.
Apparently it's a random problem and another re-login almost always solves it.

EXPECTED RESULT
sound applet should always detect sound devices

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.19.80
KDE Frameworks Version: 5.74.0
Qt Version: 5.14.2
Comment 1 Rainer Finke 2020-10-26 14:41:27 UTC
I do experience something similar on Plasma Wayland. After unlocking the screenlock, in many cases my sound output doesn't work anymore. My monitor is connected via display port. I need to go then to the sound settings, set the sound profile of my GPU to off, select again the digital stereo HDMI output and then I can play again sound. The audio controller of my mainboard is set to always off. 

I'm only experience this issue since Plasma 5.20.

Operating System: Arch Linux
KDE Plasma Version: 5.20.1
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.1
Kernel Version: 5.9.1-arch1-1
OS Type: 64-bit
Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor
Memory: 31.4 GiB of RAM
Graphics Processor: AMD Radeon VII
Comment 2 Rainer Finke 2020-11-05 19:18:34 UTC
To trigger the bug I think the external display needs to be turned off by the energy settings. Then after unlocking screenlock, audio is gone.

Operating System: Arch Linux
KDE Plasma Version: 5.20.2
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.1
Kernel Version: 5.9.3-arch1-1
OS Type: 64-bit
Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor
Memory: 31.4 GiB of RAM
Graphics Processor: AMD Radeon VII
Comment 3 Patrick Silva 2020-11-11 16:19:52 UTC
*** Bug 428979 has been marked as a duplicate of this bug. ***
Comment 4 Rainer Finke 2020-11-12 20:14:15 UTC
This bug is quite annoying. After every unlock of the screen I have to manually unset and set again my sound device to get the sound output working again. Could this please be marked as a regression? Plasma 5.19 didn't show this bug.

Operating System: Arch Linux
KDE Plasma Version: 5.20.3
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.1
Kernel Version: 5.9.6-arch1-1
OS Type: 64-bit
Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor
Memory: 31.4 GiB of RAM
Graphics Processor: AMD Radeon VII
Comment 5 Patrick Silva 2021-05-16 15:29:28 UTC
This problem has not occurred on my system for a long time.
Let's consider it fixed.

Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.22.80
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.2
Graphics Platform: Wayland
Comment 6 Patrick Silva 2021-05-17 11:21:23 UTC
It happened again on neon unstable. :(
This time I listened nothing when playing an audio file.

Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.22.80
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.2
Graphics Platform: Wayland
Comment 7 Kangarooo 2022-12-17 22:05:25 UTC
Does connecting monitors and then running this in terminal fixes?
xrandr -q
Comment 8 Niklāvs Koļesņikovs 2023-05-21 12:27:32 UTC
It's highly unlikely that this is plasma-pa or even a KDE bug. Instead this is most likely a driver level issue. For triaging I'd suggest doing `aplay -l` before and after suspend (once the issue has taken place) and see if ALSA reports the same devices. If yes, then maybe this should be reported to your distro or the audio daemon upstream that you're using (either PulseAudio or PipeWire). If the ALSA devices themselves disappear, then it's purely a kernel issue and it can only be fixed there.
Comment 9 Patrick Silva 2023-11-17 00:34:54 UTC
This problem has not occurred on my system since my previous comment.
Let's consider it fixed again.