Application: plasmashell (5.19.5) Qt Version: 5.15.1 Frameworks Version: 5.75.0 Operating System: Linux 5.9.8-200.fc33.x86_64 x86_64 Windowing system: X11 Distribution: "Fedora release 33 (Thirty Three)" -- Information about the crash: - What I was doing when the application crashed: I clicked KDE menu -> on search box i wrote "nex" (because i would like run nextcloud). Then I see crash screen. System: New Fedora 33. On fedora 32 this function work's fine. The crash can be reproduced every time. -- Backtrace: Application: Plazma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x00007fec91b1edcc in __strchr_avx2 () at /lib64/libc.so.6 #5 0x00007fec93d438ee in KDisplayManager::KDisplayManager() () at /lib64/libkworkspace5.so.5 #6 0x00007fec4002bbe9 in QObject* KPluginFactory::createInstance<SessionRunner, QObject>(QWidget*, QObject*, QList<QVariant> const&) () at /usr/lib64/qt5/plugins/krunner_sessions.so #7 0x00007fec92f86092 in KPluginFactory::create(char const*, QWidget*, QObject*, QList<QVariant> const&, QString const&) () at /lib64/libKF5CoreAddons.so.5 #8 0x00007fec5885c67e in Plasma::RunnerManagerPrivate::loadInstalledRunner(KPluginMetaData const&) () at /lib64/libKF5Runner.so.5 #9 0x00007fec5885d95c in Plasma::RunnerManagerPrivate::loadRunners() () at /lib64/libKF5Runner.so.5 #10 0x00007fec5885fdb1 in Plasma::RunnerManager::launchQuery(QString const&, QString const&) () at /lib64/libKF5Runner.so.5 #11 0x00007fec588600d5 in Plasma::RunnerManager::launchQuery(QString const&) () at /lib64/libKF5Runner.so.5 #12 0x00007fec91ffa256 in void doActivate<false>(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #13 0x00007fec91ffde8a in QTimer::timeout(QTimer::QPrivateSignal) () at /lib64/libQt5Core.so.5 #14 0x00007fec91ff2d7f in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #15 0x00007fec92a1715f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #16 0x00007fec91fcbbe8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #17 0x00007fec92015dd3 in QTimerInfoList::activateTimers() () at /lib64/libQt5Core.so.5 #18 0x00007fec9201668c in idleTimerSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5 #19 0x00007fec90571fd7 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #20 0x00007fec905c2d88 in g_main_context_iterate.constprop () at /lib64/libglib-2.0.so.0 #21 0x00007fec9056f41f in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #22 0x00007fec92016a2f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5 #23 0x00007fec91fca64b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5 #24 0x00007fec91fd2010 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #25 0x000055abb8c4b195 in main () [Inferior 1 (process 1976) detached] Possible duplicates by query: bug 429026, bug 428986, bug 428977, bug 428949, bug 428751. Reported using DrKonqi
#4 0x00007fec91b1edcc in __strchr_avx2 () at /lib64/libc.so.6 #5 0x00007fec93d438ee in KDisplayManager::KDisplayManager() () at /lib64/libkworkspace5.so.5 #6 0x00007fec4002bbe9 in QObject* KPluginFactory::createInstance<SessionRunner, QObject>(QWidget*, QObject*, QList<QVariant> const&) () at /usr/lib64/qt5/plugins/krunner_sessions.so #7 0x00007fec92f86092 in KPluginFactory::create(char const*, QWidget*, QObject*, QList<QVariant> const&, QString const&) () at /lib64/libKF5CoreAddons.so.5 #8 0x00007fec5885c67e in Plasma::RunnerManagerPrivate::loadInstalledRunner(KPluginMetaData const&) () at /lib64/libKF5Runner.so.5 #9 0x00007fec5885d95c in Plasma::RunnerManagerPrivate::loadRunners() () at /lib64/libKF5Runner.so.5 #10 0x00007fec5885fdb1 in Plasma::RunnerManager::launchQuery(QString const&, QString const&) () at /lib64/libKF5Runner.so.5 #11 0x00007fec588600d5 in Plasma::RunnerManager::launchQuery(QString const&) () at /lib64/libKF5Runner.so.5
Would you be able to see if this reproduces in Plasma 5.20? KRunner got a lot of robustness fixes in that release, and 5.21 (upcoming) promises to be even better!
*** This bug has been marked as a duplicate of bug 428415 ***