https://bugs.kde.org/show_bug.cgi?id=435190
--- Comment #4 from pyro4h...@gmail.com --- Glad I'm not alone, thanks Alex for confirming and providing a debug log. I have absolutely no idea if this is related, just looks to me like a double free. In Alex's log the IDs 199 and 250 are deleted twice just before the first "The Wayland connection broke" message [4107345.962] wl_display@1.delete_id(250) [4107358.380] wl_display@1.delete_id(199) [4107358.418] wl_callb...@199.done(13707024) [4107358.602] wl_callb...@250.done(8458) [4107359.103] wl_display@1.delete_id(250) [4107375.310] wl_display@1.delete_id(199) [4107375.361] wl_callb...@199.done(13707041) [4107831.124] wl_callb...@250.done(8458) [4107831.198] wl_buffer@201.release() [4107831.730] -> wl_surface@95.frame(new id wl_callback@199) [4107831.796] -> wl_surface@95.attach(wl_buffer@201, 0, 0) [4107831.870] -> wl_surface@95.damage(0, 0, 2147483647, 2147483647) [4107831.941] -> wl_surface@95.commit() [4107831.964] -> wl_disp...@1.sync(new id wl_callback@250) The Wayland connection broke. Did the Wayland compositor die? -- You are receiving this mail because: You are watching all bug changes.
