| Summary: | ksmserver crashes when overriding audio device | ||
|---|---|---|---|
| Product: | [Unmaintained] ksmserver | Reporter: | kde |
| Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | 5.14.0 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
ksmserver backtrace
second backtrace (trying to play logout sound) third backtrace (again trying to play screen lock sound) |
||
|
Description
kde
2018-10-12 22:19:49 UTC
Created attachment 115608 [details]
ksmserver backtrace
I discovered that you have to "prime" your Plasma session to crash beforehand. If you override the default audio device with the volume applet, it will only apply to application audio streams and not to notification sounds like login/logout and screen lock. This also means that a new session and one that you modified while already running do not behave the same way as you'd expect. 1. set the onboard audio as standard in the system tray volume applet 2. log out 3. log in again, now the login sound will play over onboard audio and a message will appear informing you that the audio output was changed 4. press Ctrl-Alt-L, ksmserver will now crash as described above. When having an overridden audio device, ksmserver will also crash when trying to play the logout sound, basically all notification-type sounds are "dangerous" when starting a Plasma session in this state. I even had one case where the graphical session would just freeze, no crash dialog and not reacting to any user input anymore. Here are some additional backtraces, the file sizes are different so maybe they help as well. Created attachment 115609 [details]
second backtrace (trying to play logout sound)
Created attachment 115610 [details]
third backtrace (again trying to play screen lock sound)
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |