I'm using arch linux and plasma 5.3.2. The problem is, even on clear installation plasmashell keeps crashing frequently. I'm still able to do my things, as the shell automatically restarts. I had same problem on clean installation of kubuntu 15. The crash occurs mostly on browsing menu or adjusting widgets and interface layout. My specs are: pentium 2020m, nvidia gt 740m, 4 gb ram. Also, crash occurs almost always when shutting down or logging off. I'm also interested if this process creates a dump or a log file (or any other garbage after crash), and, if it does, where.

Can you look in your logs (journalctl)? I also see a crash in kactivitymanagerd on logout (which does not happen when I run

Code: Select all

kactivitymanagerd stop

before logout)., but you claim that plasmashell is crashing. In your logs, look for "segfault" and (stacktrace) messages from drkonqi.

Have you enabled testing or other non-default repos?

I dont have testing enabled, the only non-default repo I have is multilib one, though I enabled it after crashes started to occur. There are logs from the second the crash happened, no segfault messages though:
Jul 27 02:46:38 tricopc kdeinit5[492]: Service "org.kde.StatusNotifierHost-585" unregistered
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: Requested backend: ""
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: Lookup paths: ("/usr/lib/qt/plugins", "/usr/lib/kf5")
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: Trying "/usr/lib/qt/plugins/kf5/kscreen/KSC_XRandR11.so"
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.xrandr11: This backend is only for XRandR 1.1, your version is: 1 . 4
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: Skipping "XRandR 1.1" backend
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: Unloading "/usr/lib/qt/plugins/kf5/kscreen/KSC_XRandR11.so"
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: Trying "/usr/lib/qt/plugins/kf5/kscreen/KSC_XRandR.so"
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.xrandr: Connected output 67 to CRTC 63
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.xcb.helper: Detected XRandR 1.4
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.xcb.helper: Event Base: 89
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.xcb.helper: Event Error: 147
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: Loading "XRandR" backend
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: Failed to register as DBus service: another launcher already running?
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: ""
Jul 27 02:46:38 tricopc kscreen_backend_launcher[566]: kscreen: Primary output changed from KScreen::Output(Id: 67 , Name: "LVDS1" ) ( "LVDS1" ) to KScreen::Output(Id: 67 , Name: "LVDS1" ) ( "LVDS1" )
Jul 27 02:46:38 tricopc kscreen_backend_launcher[566]: kscreen: Primary output changed from KScreen::Output(Id: 67 , Name: "LVDS1" ) ( "LVDS1" ) to KScreen::Output(Id: 67 , Name: "LVDS1" ) ( "LVDS1" )
Jul 27 02:46:38 tricopc kwin_x11[568]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 43503, resource id: 54525958, major code: 18 (ChangeProperty), minor code: 0
Jul 27 02:46:38 tricopc kscreen_backend_launcher[566]: kscreen: Primary output changed from KScreen::Output(Id: 67 , Name: "LVDS1" ) ( "LVDS1" ) to KScreen::Output(Id: 67 , Name: "LVDS1" ) ( "LVDS1" )
Jul 27 02:46:38 tricopc kscreen_backend_launcher[566]: kscreen: Primary output changed from KScreen::Output(Id: 67 , Name: "LVDS1" ) ( "LVDS1" ) to KScreen::Output(Id: 67 , Name: "LVDS1" ) ( "LVDS1" )
Jul 27 02:46:38 tricopc kglobalaccel5[512]: kglobalaccel-runtime: Unregistering key "Alt+F1" for "plasmashell" : "activate widget 2"
Jul 27 02:46:38 tricopc kglobalaccel5[512]: kglobalaccel-runtime: Registering key "Alt+F1" for "plasmashell" : "activate widget 2"
Jul 27 02:46:38 tricopc drkonqi[847]: Using /proc to determine executable path
Jul 27 02:46:38 tricopc drkonqi[847]: Executable is: "/usr/bin/plasmashell"
Jul 27 02:46:38 tricopc drkonqi[847]: Executable exists: true
Jul 27 02:46:38 tricopc drkonqi[847]: Unable to find an internal debugger that can work with the KCrash backend
Jul 27 02:46:38 tricopc drkonqi[847]: Enabling drkonqi crash catching
Jul 27 02:46:38 tricopc drkonqi[847]: Invalid pixmap specified.
Jul 27 02:46:38 tricopc drkonqi[847]: No frame loaded
Jul 27 02:46:38 tricopc drkonqi[847]: No frame loaded
-- Logs begin at Sat 2015-07-25 23:08:47 MSK, end at Mon 2015-07-27 03:14:48 MSK. --
Jul 27 02:46:38 tricopc kdeinit5[492]: Service "org.kde.StatusNotifierHost-585" unregistered
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: Requested backend: ""
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: Lookup paths: ("/usr/lib/qt/plugins", "/usr/lib/kf5")
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: Trying "/usr/lib/qt/plugins/kf5/kscreen/KSC_XRandR11.so"
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.xrandr11: This backend is only for XRandR 1.1, your version is: 1 . 4
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: Skipping "XRandR 1.1" backend
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: Unloading "/usr/lib/qt/plugins/kf5/kscreen/KSC_XRandR11.so"
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: Trying "/usr/lib/qt/plugins/kf5/kscreen/KSC_XRandR.so"
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.xrandr: Connected output 67 to CRTC 63
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.xcb.helper: Detected XRandR 1.4
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.xcb.helper: Event Base: 89
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.xcb.helper: Event Error: 147
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: Loading "XRandR" backend
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: Failed to register as DBus service: another launcher already running?
Jul 27 02:46:38 tricopc kscreen_backend_launcher[851]: kscreen.backendLauncher: ""
Jul 27 02:46:38 tricopc kscreen_backend_launcher[566]: kscreen: Primary output changed from KScreen::Output(Id: 67 , Name: "LVDS1" ) ( "LVDS1" ) to KScreen::Output(Id: 67 , Name: "LVDS1" ) ( "LVDS1" )
Jul 27 02:46:38 tricopc kscreen_backend_launcher[566]: kscreen: Primary output changed from KScreen::Output(Id: 67 , Name: "LVDS1" ) ( "LVDS1" ) to KScreen::Output(Id: 67 , Name: "LVDS1" ) ( "LVDS1" )
Jul 27 02:46:38 tricopc kwin_x11[568]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 43503, resource id: 54525958, major code: 18 (ChangeProperty), minor code: 0
Jul 27 02:46:38 tricopc kscreen_backend_launcher[566]: kscreen: Primary output changed from KScreen::Output(Id: 67 , Name: "LVDS1" ) ( "LVDS1" ) to KScreen::Output(Id: 67 , Name: "LVDS1" ) ( "LVDS1" )
Jul 27 02:46:38 tricopc kscreen_backend_launcher[566]: kscreen: Primary output changed from KScreen::Output(Id: 67 , Name: "LVDS1" ) ( "LVDS1" ) to KScreen::Output(Id: 67 , Name: "LVDS1" ) ( "LVDS1" )
Jul 27 02:46:38 tricopc kglobalaccel5[512]: kglobalaccel-runtime: Unregistering key "Alt+F1" for "plasmashell" : "activate widget 2"
Jul 27 02:46:38 tricopc kglobalaccel5[512]: kglobalaccel-runtime: Registering key "Alt+F1" for "plasmashell" : "activate widget 2"
Jul 27 02:46:38 tricopc drkonqi[847]: Using /proc to determine executable path
Jul 27 02:46:38 tricopc drkonqi[847]: Executable is: "/usr/bin/plasmashell"
Jul 27 02:46:38 tricopc drkonqi[847]: Executable exists: true
Jul 27 02:46:38 tricopc drkonqi[847]: Unable to find an internal debugger that can work with the KCrash backend
Jul 27 02:46:38 tricopc drkonqi[847]: Enabling drkonqi crash catching
Jul 27 02:46:38 tricopc drkonqi[847]: Invalid pixmap specified.
Jul 27 02:46:38 tricopc drkonqi[847]: No frame loaded
Jul 27 02:46:38 tricopc drkonqi[847]: No frame loaded

I also have this spam occupying majority of my log, what should I disable to stop these messages?
Jul 27 03:17:54 tricopc kscreen_backend_launcher[566]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored)
Jul 27 03:17:54 tricopc kscreen_backend_launcher[566]: kscreen.xcb.helper: Output: 67
Jul 27 03:17:54 tricopc kscreen_backend_launcher[566]: kscreen.xcb.helper: Property: Backlight
Jul 27 03:17:54 tricopc kscreen_backend_launcher[566]: kscreen.xcb.helper: State (newValue, Deleted): 0

Seems you've drkonqi installed, but it's not showing up??

Enable core dumps:
https://blogs.kde.org/2009/03/27/settin ... core-dumps

(if you generally know how anything about coredumps, "export KDE_DEBUG=1")

> what should I disable to stop these messages?

Have

Code: Select all

[Rules]
kscreen.xcb.helper=false


in ~/.config/QtProject/qtlogging.ini

Try installing gdb (drkonqi 5.3.2-2 added this required dependency) for sane traces. If coredumps are created, look at coredumpctl list.

luebking wrote:in ~/.config/QtProject/qtlogging.ini

qtlogging.ini doesn't exist there.
If I created that file and put kscreen.xcb.helper=false, that would not have any effect.
I have ~/.config/QtProject.conf. I've tried to put the settings in it, but no result as well.

P.S.
I also have the same issue with segmentation fault (11) and the journalctl output looks very similar to the logs above.

Code: Select all

$ kde-open -v
Qt: 4.8.7
KDE Development Platform: 4.14.10
KIO Client: 2.0

$ uname -r
4.1.3-1-ARCH


alexbel wrote:

luebking wrote:in ~/.config/QtProject/qtlogging.ini

qtlogging.ini doesn't exist there.
If I created that file and put kscreen.xcb.helper=false, that would not have any effect.
I have ~/.config/QtProject.conf. I've tried to put the settings in it, but no result as well.

That folder and file does not exist by default. To reduce log spam in journal, I put this in ~/.config/plasma-workspace/env/disable-kde-spam.sh

Code: Select all

# 2015-07-24 Attempt to force logging to ~/.xsession-errors
# https://stackoverflow.com/a/26325743
# http://lists.qt-project.org/pipermail/development/2014-July/017588.html
# http://www.kdab.com/wp-content/uploads/stories/slides/Day2/KaiKoehne_Qt%20Logging%20Framework%2016_9_0.pdf
# https://git.reviewboard.kde.org/r/121903/
# http://doc.qt.io/qt-5/qloggingcategory.html
export QT_LOGGING_TO_CONSOLE=1

alexbel wrote:P.S.
I also have the same issue with segmentation fault (11) and the journalctl output looks very similar to the logs above.

Code: Select all

$ kde-open -v
Qt: 4.8.7
KDE Development Platform: 4.14.10
KIO Client: 2.0

$ uname -r
4.1.3-1-ARCH


That is your library information for KDE 4.

BTW, I also have plasmashell crash issues on logout (tested with a new user account). Does it happen to you for events other than logging out (such as connecting an external monitor)?

Lekensteyn wrote:That is your library information for KDE 4.

oops.

Code: Select all

Qt: 5.5.0
KDE Frameworks: 5.12.0


Lekensteyn wrote:BTW, I also have plasmashell crash issues on logout (tested with a new user account). Does it happen to you for events other than logging out (such as connecting an external monitor)?

Yes it does. Usually it happens few times a day. I didn't notice any pattern for the events, except a crash on logout. It's the most frequent one.
Also, if plasmashell has crashed then the old process would be hanging in memory. At the end of the day I can see 4-6 copies (dead/abandoned?) of plasmashell.

Lekensteyn wrote:BTW, I also have plasmashell crash issues on logout (tested with a new user account). Does it happen to you for events other than logging out (such as connecting an external monitor)?

Yes it does. Usually it happens few times a day. I didn't notice any pattern for the events, except a crash on logout. It's the most frequent one.
Also, when plasmashell crashes the old process is still in memory. At the end of the day I can see 4-6 copies (dead/abandoned?) of plasmashell.[/quote]

Have you installed the gdb package? These processes are still in memory because drkonqi (crash reporter) tries to present you information about the crash (for debugging purposes). You can find those processes with ps uww -C drkonqi. To kill those plasmashell processes, try sending SIGTERM to drkonqi.

Lekensteyn wrote:Have you installed the gdb package? These processes are still in memory because drkonqi (crash reporter) tries to present you information about the crash (for debugging purposes). You can find those processes with ps uww -C drkonqi. To kill those plasmashell processes, try sending SIGTERM to drkonqi.

I did, but have no idea how to use it I'm a web developer. Anyway, I'm going to try to debug that.
Thanks for your help!!!

By installing gdb, drkonqi will be able to generate backtraces. You do not need to run it yourself.

I managed to capture the backtrace for a such a crash (could be different from yours though) and reported it at https://bugs.kde.org/show_bug.cgi?id=350866

Kde team says it's a bug in intel drivers:
https://mail.kde.org/pipermail/kde-dist ... 00088.html

There is also a problem relating to xproto which causes a segfauly in kactivitymanager. It will often show up as something like:

Code: Select all

kactivitymanage[720]: segfault at 7f2ac5430d10 ip 00007f2ac578b881 sp 00007fffb3881ce8 error 4 in libQt5Sql.so.5.5.0[7f2ac5735000+41000]


See https://bugs.freedesktop.org/show_bug.cgi?id=91316
https://bbs.archlinux.org/viewtopic.php?id=199812

For a long time this was crashing my desktop and taking me back to sddm 2 or 3 times a day until I downgraded Xproto to 7.0.27 on Gentoo. with other distros they probably put it all in their xorg-server package and might apply a special patch for it as they did in Arch Linux.