Launchpad has imported 7 comments from the remote bug at https://bugs.kde.org/show_bug.cgi?id=380411.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2017-06-01T00:42:51+00:00 Paul wrote: If pulseaudio becomes unresponsive or is in a bad state, plasmashell can hang, leaving the entire graphical system unresponsive unless you can kill and restart pulseaudio. This condition can occur when messing with jackd or if a device encounters an error or similar condition, of which if the user attempts to adjust the volume or trigger a plasma audio event, plasma will immediately hang indefinitely. Audio calls need to not be blocking, or should be handled in a sandboxed thread with a timeout, there is no guarantee that they will finish immediately or at all (hence why window's did away with push events). Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- desktop/+bug/1694863/comments/1 ------------------------------------------------------------------------ On 2017-06-01T08:04:39+00:00 U26 wrote: If it is hanging, can you get us a backtrace of it blocking please. Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- desktop/+bug/1694863/comments/2 ------------------------------------------------------------------------ On 2017-06-14T15:16:17+00:00 Cfeck wrote: If you can provide the information requested in comment #1, please add it. You can interrupt gdb while plasmashell hangs to get the backtrace. Without this information, we have to assume that it is some upstream component that blocks. Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- desktop/+bug/1694863/comments/3 ------------------------------------------------------------------------ On 2017-06-28T19:29:42+00:00 Cfeck wrote: To further investigate this issue, KDE developers need the information requested in comment #1. If you can provide it, or need help with finding that information, please add a comment. Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- desktop/+bug/1694863/comments/4 ------------------------------------------------------------------------ On 2017-06-28T22:16:33+00:00 Paul wrote: Created attachment 106365 stacktrace of plasmashell sorry, had been busy with other things to be bricking my system again... Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- desktop/+bug/1694863/comments/5 ------------------------------------------------------------------------ On 2017-07-17T16:15:22+00:00 Cfeck wrote: Thanks for the update; changing status. I cannot see a cause for a freeze in the trace, but maybe plasma-pa developers have an idea where Plasma does blocking calls to pulseaudio. Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- desktop/+bug/1694863/comments/6 ------------------------------------------------------------------------ On 2020-12-04T03:39:10+00:00 Justin Zobel wrote: Thank you for the report, Paul. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you. Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- desktop/+bug/1694863/comments/7 ** Changed in: plasmashell Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694863 Title: If pulseaudio is non-responsive, plasmashell hangs To manage notifications about this bug go to: https://bugs.launchpad.net/plasmashell/+bug/1694863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs