https://bugs.kde.org/show_bug.cgi?id=450050
--- Comment #3 from torokat...@gmail.com --- I think I'm a bit closer to a semi-reliable reproduction method. The problem is, it only works on my main system, the one affected by this issue - but not on my laptop, which is very similar software-wise. Anyway, the steps I devised for triggering the glitch: 1.: Open https://www.bennish.net/web-notifications.html in Firefox (on Wayland, which may or may not matter), and make sure the page is a completely fresh tab, by pressing Ctrl+F5 2.: Click the "Authorize" button, and grant notification permissions to the site 3.: Verify that the notifications work by pressing the "Show" button a few times, then wait for all notifications to disappear 4.: Open the Web Developer Console on the page, and enter this: `setInterval(notify.show, 1000)`. This might rely on the fact that the default timeout is a whole number of seconds, so there can be race conditions between queueing a new notification, and receiving callback about it being shown, and an older one closing. 5.: Don't hover over any of the notifications and don't close them, so this potential race condition is kept going 6.: Open LibreOffice Writer, and copy a few lines of text from the page in Firefox into a new document in Writer (yes, for some reason, this also seems to be needed) 7.: Wait for a few more notifications to come and go, and not much later, Firefox should lock up, maybe crash, and plasmashell is now in the mentioned degraded state. If Bustle is recording the Session Bus in the meantime, it errors out and stops recording (see attached screenshot). Then, if I start a new Bustle recording, I see some corrupted-looking messages going around on the Session bus (see another attached screenshot). Also, in this degraded state, if I enter `notify-send test` to a terminal, it does nothing, but doesn't return either - it's just blocked indefinitely. -- You are receiving this mail because: You are watching all bug changes.
