https://bugs.kde.org/show_bug.cgi?id=430111
--- Comment #11 from Mathew Robinson ---
Based on the line "#3 QMessageLogger::fatal(char const*, ...) const
(this=this@entry=0x7ffefef4eb40, msg=msg@entry=0x7fe8b70350b8 "The Wayland
connection broke. Did the Wayland compositor die?&q
https://bugs.kde.org/show_bug.cgi?id=430111
--- Comment #10 from Mathew Robinson ---
Managed to get a backtrace with GDB where I have most of the debug info for the
components involved. I'm attempting to track the bug down and fix it, but it's
my first foray into the KDE code base. F
https://bugs.kde.org/show_bug.cgi?id=430111
--- Comment #9 from Mathew Robinson ---
I've done some more testing on this. It appears if I unpin the "default" pins
then pin some new applications the issue goes away.
I've tried repinning the old default pins to see if the issue
https://bugs.kde.org/show_bug.cgi?id=430111
Mathew Robinson changed:
What|Removed |Added
CC||mat...@chasinglogic.io
--- Comment #8 from
