Frédéric Bron wrote: >> If none of the crash handlers catch this (like abrt or drkonqi), you can >> try >> running plasmashell under gdb to get a backtrace. One way, use krunner >> (ALT-F2) to launch konsole, then run: >> >> gdb /usr/bin/plasmashell > > Good idea. The log is attached. > Can you see something? I think this thread, something to do with cups: Thread 1 (Thread 0x7fffe42fb040 (LWP 10727)): #0 0x00007fff28ce3d86 in JobModel::updateJob(int, KCupsJob const&) () at /lib64/libkcupslib.so #1 0x00007fff28ce6137 in JobModel::getJobFinished() () at /lib64/libkcupslib.so #2 0x00007fff28cec335 in JobModel::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) [clone .part.7] () at /lib64/libkcupslib.so #3 0x00007ffff1d727e9 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #4 0x00007ffff2616ecc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 ... will need more -debuginfo to know more, at least: dnf debuginfo-install kde-print-manager (and try generating a backtrace again) Now that we have a better idea what is crashing, one workaround to consider to get a working plasmashell... temporarily remove print applet support by doing: dnf remove kde-print-manager -- Rex _______________________________________________ kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kde-leave@xxxxxxxxxxxxxxxxxxxxxxx
