https://bugs.kde.org/show_bug.cgi?id=498837
--- Comment #7 from Adam Williamson <ad...@happyassassin.net> --- Notes on the notification itself: even if it's true that XWayland exited abnormally, this seems like a very poor notification. What is a user supposed to *do* with this - and only this - information? Some users won't know what XWayland is. Even those who do may not know what it exiting abnormally means for them in practical terms. On my test system, when reproducing this issue and then checking running processes, there *is* a running XWayland process, which seems to imply that maybe it is automatically restarted and that restart works fine - but the notification doesn't convey that information. Think about, for instance, someone who's using Bazzite because they learned about it on Youtube, they go to desktop mode, they see this notification: that's not a great experience! If the notification: i) appeared after we'd given up restarting xwayland(? assuming that's what happens) ii) didn't lie and say it had crashed when it hadn't iii) told me, or linked to somewhere that told me, what xwayland not running means in practical terms and what I might be able to do about it ...then it'd be a lot more useful and a better experience. -- You are receiving this mail because: You are watching all bug changes.
