Created attachment 107207 [details] Backtrace of one such crash Krunner sometimes crashes on me while I'm typing in something. I haven't been able to find any patterns in what triggers the crash. I have attached a backtrace.
Created attachment 107208 [details] Backtrace of one such crash I seem to have accidentally truncated some of the lines from the previous backtrace.
Unfortunately without debug symbols for glibc, the kf5-i18n framework and libsqlite, it is impossible to tell where it crashes. If you found a way to install those, please add an updated backtrace. If disabling the bookmarks runner helps to avoid the crash, it is likely in libsqlite. Relevant part from comment #1: Stack trace of thread 2094: #0 0x00007ff2da8588c0 raise (libc.so.6) #1 0x00007ff2debd5625 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5) #2 0x00007ff2da858940 __restore_rt (libc.so.6) #3 0x00007ff2da85229c transcmp (libc.so.6) #4 0x00007ff2da90f7ab __tfind (libc.so.6) #5 0x00007ff2da85319a __dcigettext (libc.so.6) #6 0x00007ff2dd00b835 n/a (libKF5I18n.so.5) #7 0x00007ff2dd006c4b n/a (libKF5I18n.so.5) #8 0x00007ff2dd00799c n/a (libKF5I18n.so.5) #9 0x00007ff2dd00898e _ZNK16KLocalizedString8toStringEv (libKF5I18n.so.5) #10 0x00007ff2b0733078 n/a (krunner_services.so) #11 0x00007ff2b072f622 n/a (krunner_services.so) #12 0x00007ff2b88e3970 _ZN6Plasma14AbstractRunner12performMatchERNS_13RunnerContextE (libKF5Runner.so.5) Stack trace of thread 2096: #0 0x00007ff2da904bad __read (libc.so.6) #1 0x00007ff2debd46ad n/a (libKF5Crash.so.5) #2 0x00007ff2debd4eba n/a (libKF5Crash.so.5) #3 0x00007ff2debd55a3 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5) #4 0x00007ff2da858940 __restore_rt (libc.so.6) #5 0x00007ff2b0e02160 sqlite3StrICmp (libsqlite3.so.0) #6 0x00007ff2b0dec75e n/a (libsqlite3.so.0) #7 0x00007ff2b0e194cd n/a (libsqlite3.so.0) #8 0x00007ff2b0ded62c sqlite3ResolveExprNames (libsqlite3.so.0) #9 0x00007ff2b0ded880 sqlite3ResolveExprListNames (libsqlite3.so.0) #10 0x00007ff2b0dedb5f n/a (libsqlite3.so.0) #11 0x00007ff2b0e19486 sqlite3WalkSelect (libsqlite3.so.0) #12 0x00007ff2b0ded8f7 sqlite3ResolveSelectNames (libsqlite3.so.0) #13 0x00007ff2b0df8785 sqlite3SelectPrep (libsqlite3.so.0) #14 0x00007ff2b0df89a5 sqlite3Select (libsqlite3.so.0) #15 0x00007ff2b0de330e sqlite3Parser (libsqlite3.so.0) #16 0x00007ff2b0dfe30f sqlite3RunParser (libsqlite3.so.0) #17 0x00007ff2b0de8cc6 n/a (libsqlite3.so.0) #18 0x00007ff2b0de907d n/a (libsqlite3.so.0) #19 0x00007ff2b0de91d5 n/a (libsqlite3.so.0) #20 0x00007ff2b106676c n/a (libqsqlite.so) #21 0x00007ff2d60cfb8a _ZN10QSqlResult11savePrepareERK7QString (libQt5Sql.so.5) #22 0x00007ff2d60c0739 _ZN9QSqlQuery7prepareERK7QString (libQt5Sql.so.5) #23 0x00007ff2b127d94a n/a (krunner_bookmarksrunner.so) #24 0x00007ff2b12858da n/a (krunner_bookmarksrunner.so) #25 0x00007ff2b1282fa6 n/a (krunner_bookmarksrunner.so) #26 0x00007ff2b88e3970 _ZN6Plasma14AbstractRunner12performMatchERNS_13RunnerContextE (libKF5Runner.so.5)
Created attachment 108010 [details] Backtrace with additional debug symbols I have finally been able to catch another crash. This one is with debug symbols for glibc, k1i8n, and sqlite installed.
Backtrace from comment #3 is bug 378493, but unfortunately unrelated to the backtrace from comment #1.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
I haven't been able to reproduce this, at least for the last few months. I think that whatever it was has been fixed.
Great! Thanks for the update!