https://bugs.kde.org/show_bug.cgi?id=524392
TraceyC <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WAITINGFORINFO Keywords| |qt-crash Summary|Crash loop with |Crash loop in |baloo_file_extractor |QGuiApplicationPrivate::cre | |ateEventDispatcher with | |baloo_file_extractor CC| |[email protected] Platform|Other |EndeavourOS Status|REPORTED |NEEDSINFO --- Comment #1 from TraceyC <[email protected]> --- The crash looks to be in Qt In bug 520166, which has a similar backtrace, it was explained that this indicates it's aborting (not crashing) because it can't find a display. It probably just outlived the session after a logout and restarted. #7 0x00007f081729771d in QMessageLogger::fatal (this=this@entry=0x7ffe61b702a0, msg=msg@entry=0x7f081820de9f "%s") at /usr/src/debug/qt6-base/qtbase/src/corelib/global/qlogging.cpp:902 Your journal logs confirm that it can't connect to the display > Aug 15 14:44:13 laughingman baloo_file_extractor[38127]: could not connect to > display :0 Does this recurring abort happen if you reboot and log directly into the kwin_wayland session? -- You are receiving this mail because: You are watching all bug changes.
