When opening the app starter and searching certain terms, plasmashell crashes for me this seems to be due to a bug in the battery indicator, that triggers a bug in Qt (which should probably also be investigated) Log: plasmashell[2790]: file:///usr/share/plasma/plasmoids/org.kde.plasma.battery/contents/ui/CompactRepresentation.qml:53:39: Unable to assign [undefined] to int plasmashell[2790]: trying to show an empty dialog kernel: GlobalQueue[13][2837]: segfault at 7eff7ba2e3a0 ip 00007f02e5476a60 sp 00007f01af7fd7f8 error 4 in libQt5Core.so.5.10.1[7f02e5194000+4f7000] systemd[1]: Started Process Core Dump (PID 2841/UID 0). DLXA systemd-coredump[2842]: Core file was truncated to 2147483648 bytes. DLXA systemd-coredump[2842]: Process 2790 (plasmashell) of user 1002 dumped core. Note that this is on a wall plugged machine, where the indicator should not be shown with default settings Workaround: Disable the "Battery and Brightness" (translated from german) indicator
Can you get a backtrace? On console type gdb plasmashell then type r for run and make it crash, once that happens type thread apply all bt and paste the output of that here. Depending on your distro, you should also install debug symbols, e.g. packages named libqt5core-dbg and plasma-workspace-dbg and similar. > where the indicator should not be shown with default settings Is the indicator shown in the panel next to the clock (wrong) or hidden in the popup (correct)? The indicator is always loaded for e.g. if you have a mouse, an UPS, or to provide access to the "enable power management" checkbox
Yes, please give me a bit of time
I am really sorry, it seems to have been a glitch, the integer assign error does not seem to be related to the crash i observed. After a reboot the crash happened again, even with my "workaround" applied, but after update of a few KDE components in the arch repos it is resolved permanently now.