Plasma crashes irreversibly when -enabling Holidays: Goto Digital Clock Settings->Calendar->check Holidays->Apply ->crash (see Video 2) -scroling in Holidays' list: Goto Digital Clock Settings->Holidays and scroll in the Holidays' list ->crash (see Video 1) Crash means: Taskbar and widgets and wallpaper and so on vanish. Irreversible means: Even after rebooting and entering my password on welcome screen, I will get a very long Splash Screen, which eventually turns into a black screen without taskbar/widgets/wallpapers. Nothing. How to restore a working system: rm ~/.config/plasma-org.kde.plasma.desktop-appletsrc or following line in this file: enabledCalendarPlugins=/usr/lib/qt/plugins/plasmacalendarplugins/holidaysevents.so I don't know if it is a KHolidays Bug or Plasma Bug or both. First of all, I will post it here (KHolidays), if there will be no feedback, I will post it also in Plasma. Reproducible: Always Expected Results: Enable Holidays and scroll in the list without permanent crash. kholidays 16.08.2-1 kde plasma 5.8.2 kde frameworks 5.27.0
Created attachment 101775 [details] Crash when scroling in holidays' list
Created attachment 101776 [details] Crash when enabling Holidays
Please add the backtrace for the crash. Only the backtrace reveals the information when component is responsible. For help with creating backtraces, please see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Mmh, sorry I haven't yet debugged with Arch, Arch currently doesn't offer debug packages with symbols? The KDE Crash Dialog does not show when plasmashell is killed by the bug. I tried to retrieve a backtrace with gdb, but mmh... sudo gdb --pid=808 #this is plasmashell --shut-up (gdb) set logging file trace.log (gdb) set logging on (gdb) thread apply all bt full See output 1 (perhaps not important). (gdb) continue See output 2 (note the comments I made).
Created attachment 101790 [details] Output 1
Created attachment 101791 [details] Output 2
The backtrace does not show a crash. You need to wait until it crashes before you use the 'bt' gdb command.
Thanks for your reply. You say "let it crash" afterwards do "(gdb) thread apply all bt full" ? The problem is the bug kills plasmashell, so issuing "(gdb) thread apply all bt full" after crash yields nothing "The program is not being run." Here's the gdb for /usr/bin/plasmashell, process 776 Continuing. [New Thread 0x7fcc51ed3700 (LWP 1837)] #this is ok (digital clock settings) [Thread 0x7fcd0ffff700 (LWP 865) exited] #all this should not happen [Thread 0x7fcc51ed3700 (LWP 1837) exited] [Thread 0x7fcc53ce5700 (LWP 1450) exited]#all this should not happen [Thread 0x7fcc74650700 (LWP 931) exited] #all this should not happen [Thread 0x7fccfeda2700 (LWP 930) exited] #all this should not happen [Thread 0x7fcd0ca44700 (LWP 929) exited] #all this should not happen [Thread 0x7fcd0e7c0700 (LWP 921) exited] #all this should not happen [Thread 0x7fcd15f3d700 (LWP 790) exited] #all this should not happen [Thread 0x7fcd2ca85800 (LWP 776) exited] #all this should not happen, this finally kills plasmashell [Inferior 1 (process 776) exited with code 02] Which other process should I examine? Which other commands might be helpful? Sorry I am not a newbee but for this problem apparantly too unexperienced.
It is possible that plasmashell does not really crash (SIGV etc.), but aborts because of a different condition. Could you add the Konsole output of plasmashell around the time of the crash?
Did you mean $ kstart5 plasmashell 2>&1 the moment plasmashell is killed, it just gives a "g". That's all. Or what command did you mean?
Try running plasmashell in Konsole without kstart. You might need to terminate the previous instances with "killall plasmashell".
# output of plasmashell (crashing while scroling in holidays' list): file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/configuration/AppletConfiguration.qml:301:21: QML StackView: Binding loop detected for property "height" g # output of journalctl: #plasmashell is process 1022 Okt 27 09:59:04 r101181 kwin_x11[1009]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 28826, resource id: 31457387, major code: 15 (QueryTree), minor code: 0 Okt 27 09:59:25 r101181 plasmashell[1022]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/configuration/AppletConfiguration.qml:301:21: QML StackView: Binding loop detected for property "height" Okt 27 09:59:26 r101181 plasmashell[1022]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/configuration/AppletConfiguration.qml:301:21: QML StackView: Binding loop detected for property "height" Okt 27 09:59:27 r101181 kdeinit5[977]: Service "org.kde.StatusNotifierHost-1022" unregistered Okt 27 09:59:27 r101181 ksmserver[999]: ksmserver: autostart service "plasmashell" finished with exit code 2 Okt 27 09:59:27 r101181 kwin_x11[1009]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 30257, resource id: 31457294, major code: 15 (QueryTree), minor code: 0 Okt 27 09:59:28 r101181 kwin_x11[1009]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 30303, resource id: 31457424, major code: 15 (QueryTree), minor code: 0 Okt 27 09:59:28 r101181 kwin_x11[1009]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 30328, resource id: 31457311, major code: 15 (QueryTree), minor code: 0 # output of plasmashell (crashing when enabling holidays and apply): g # output of journalctl: #plasmashell is process 805 Okt 27 10:13:43 r101181 kdeinit5[746]: Service "org.kde.StatusNotifierHost-805" unregistered Okt 27 10:13:43 r101181 ksmserver[769]: ksmserver: autostart service "plasmashell" finished with exit code 2 Okt 27 10:13:43 r101181 kwin_x11[789]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 12285, resource id: 35651598, major code: 15 (QueryTree), minor code: 0 Okt 27 10:13:43 r101181 kwin_x11[789]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 12331, resource id: 35651869, major code: 15 (QueryTree), minor code: 0 Okt 27 10:13:43 r101181 kwin_x11[789]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 12356, resource id: 35651615, major code: 15 (QueryTree), minor code: 0
I cannot extract any reason for a crash from the Konsole output either. Moving to Plasma developers for inspection.
I can _sometimes_ (not always) reproduce plasma 5.8.2 (in openSUSE 42.2 RC2) crash after enabling "Holidays" at "Available calendar plugins" or after selecting regions for holidays and pressing Applay. However KDE bug application waits for very long time and don't produce backtrace.
@opensuse.lietuviu.kalba@gmail.com: Yes, you are right it is only _sometimes_ (perhaps in one of two cases) when enabling Holidays. But it is always, when scroling in Holidays' list. Thanks for your confirmation.
But I can not reprode crash during scroll of regions in Plasma 5.8.2
Cannot reproduce this bug in: Distribution: KDE neon Developer Edition Unstable Branches KDE Plasma Version: 5.10.90 KDE Frameworks Version: 5.37.0 Qt Version: 5.9.1 Kernel Version: 4.10.0-32-generic
This bug has a duplicate: https://bugs.kde.org/show_bug.cgi?id=404594 It is still present in Operating System: Manjaro Linux KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.3 Kernel Version: 5.0.15-1-MANJARO OS Type: 64-bit
We cannot know if is a duplicate unless we have a backtrace.
No backtrace in five years. The code has changed substantially since then, so even if we get one, it's likely to have already been fixed. Please open a new backtrace if you get any new crashes in Plasma 5.22 or later.