Created attachment 176146 [details] journalctl of plasmashellservice Hi, The report is in attachement ; config at the bottom. Action 1 : move dictionary widget from the widget selector to the destkop creates the black screen desktops Action 2 : restored desktop by deleting plasma-org.kde... in /.config Action 3: performed same action as action 1 with same result I could not reproduce with another widget than the dictionary. Operating System: Kubuntu 24.10 KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.6.2 Kernel Version: 6.11.0-8-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® N100 Memory: 15.4 Gio of RAM Graphics Processor: Mesa Intel® Graphics
If something crashed, we need a backtrace of it so we can figure out what's going on. Can you please attach a backtrace of the crash using the coredumpctl command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl? Thanks.
I thought journalctl logs would be enough and I won't reproduce the crash again to lose all my settings as I don't have the time for it.. We may close this one or if you just happen to have a test environement, do this drag and drop of the dictionary widget and see what happens Sorry but over the last few weeks as a regular user I'm just experiencing too many issues and cannot take time anymore for the moment : a few KDE bug reported + Thunderbird snap loading new mails inconstently(forced by the ubuntu update) I switched back to flat package which solve the issue, and yesterday, firefox 133 generating general CSS issues which you may see on forums.
If you can't supply a backtrace, then I'm afraid there's no way for us to debug the issue, sorry. Adding a Dictionary widget to my desktop doesn't crash Plasma on git master, so the best I can tell you is "it's probably fixed already". It sounds like you're having lots of general issues with the distro beyond just KDE software. I'd recommend getting in contact with the Kubuntu folks to see if they can help.
Hello, I just found this report via google after having this exact same issue. I am on Arch Linux. Crashed system badly it may have only started after clicking the widget. Had to boot into shell via ly and rm plasma-org.kde... in /.config.
(In reply to Jim from comment #4) > Hello, I just found this report via google after having this exact same > issue. > I am on Arch Linux. > Crashed system badly it may have only started after clicking the widget. > > Had to boot into shell via ly and rm plasma-org.kde... in /.config. Please let us know: KDE Plasma Version: KDE Frameworks Version: Qt Version: Kernel Version: Also, please provide a backtrace of the crash on your system. Thanks.
Sorry for not providing more elaborated logs but, I moved to Fedora after having too many bugs on Kubuntu, maybe Jim's logs will help us.
Plasma version 6.4.3 Framework version 6.16.0 QT version 6.9.1 Kernel 6.16-arch1-1 (64-bit) Grapics Platform Wayland 16GB RAM Intel 1165G7 cpu Here is my core dump for plasmashell. The issue only occured recently and I haven't used the system since so hopefully there is no need for me to create the issue again as it is a pain to deal with. CoreDump: https://pastebin.com/EsGfahjH Hope That helps.
Thanks for that backtrace. Unfortunately, it's incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong: #0 0x00007fac5d69bf0c n/a (libQt6WebEngineCore.so.6 + 0x4c9bf0c) #14 0x00007fac995d7ad7 n/a (libdictplugin.so + 0x10ad7) #27 0x00007facf2a54020 n/a (libPlasmaQuick.so.6 + 0x2b020) #29 0x00007facefdd37ef n/a (libQt6Core.so.6 + 0x1d37ef) #42 0x000055d106160592 n/a (/usr/bin/plasmashell + 0x28592) Could you please install debug symbols and attach a new symbolicated backtrace generated by using `coredumpctl gdb` in a terminal window? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl for details about how to do this. Thanks again!
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
Sorry for my late response, I have been away for a while. Here is the core dump I took around the time of the issue https://pastebin.com/NyEhLwuj I made sure the following env was set: DEBUGINFOD_URLS="https://debuginfod.archlinux.org" It was. It is worth noting I think I already had the symbols setup and installed as the package libelf sets it and is requried by mesa. The only thing I had missed was the gdb package not being installed. The core dump does appear to have a lot of extra information that I hope will be of use.
(In reply to Jim from comment #10) > Sorry for my late response, I have been away for a while. > > Here is the core dump I took around the time of the issue > https://pastebin.com/NyEhLwuj Thanks for the backtrace. Unfortunately the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong: #0 0x00007fac5d69bf0c n/a (libQt6WebEngineCore.so.6 + 0x4c9bf0c) #14 0x00007fac995d7ad7 n/a (libdictplugin.so + 0x10ad7) #23 0x00007facf1358688 n/a (libQt6Qml.so.6 + 0x358688) #27 0x00007facf2a54020 n/a (libPlasmaQuick.so.6 + 0x2b020) #29 0x00007facefdd37ef n/a (libQt6Core.so.6 + 0x1d37ef) #42 0x000055d106160592 n/a (/usr/bin/plasmashell + 0x28592) Could you please install debug symbols and attach a new symbolicated backtrace generated by using `coredumpctl gdb` in a terminal window? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl for details about how to do this. Please attach it as a text file directly to this report. Things on the Internet can disappear. Thanks again!
(In reply to TraceyC from comment #11) > (In reply to Jim from comment #10) > > Sorry for my late response, I have been away for a while. > > > > Here is the core dump I took around the time of the issue > > https://pastebin.com/NyEhLwuj > > Thanks for the backtrace. Unfortunately the backtrace is incomplete and > missing debug symbols for the following lines that we need to figure out > exactly what's going wrong: > > #0 0x00007fac5d69bf0c n/a (libQt6WebEngineCore.so.6 + 0x4c9bf0c) > #14 0x00007fac995d7ad7 n/a (libdictplugin.so + 0x10ad7) > #23 0x00007facf1358688 n/a (libQt6Qml.so.6 + 0x358688) > #27 0x00007facf2a54020 n/a (libPlasmaQuick.so.6 + 0x2b020) > #29 0x00007facefdd37ef n/a (libQt6Core.so.6 + 0x1d37ef) > #42 0x000055d106160592 n/a (/usr/bin/plasmashell + 0x28592) > > Could you please install debug symbols and attach a new symbolicated > backtrace generated by using `coredumpctl gdb` in a terminal window? See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl > for details about how to do this. > > Please attach it as a text file directly to this report. Things on the > Internet can disappear. Thanks again I have tried to get the debug symbols working but no luck. i have followed all the correct steps, with the DEBUGINFOD_URLS having the correct value too. All correct packages as well. In the dump i shared around line 468 I did noticed the following "Reading symbols from /usr/bin/plasmashell... (No debugging symbols found in /usr/bin/plasmashell)"
I found that this was supposed to have been fixed in 6.4.0, but you're seeing this in 6.4.3. I'm marking this as a regression. (In reply to Jim from comment #13) > I have tried to get the debug symbols working but no luck. > i have followed all the correct steps, with the DEBUGINFOD_URLS having the > correct value too. All correct packages as well. Without at least the symbols for libdictplugin, there isn't going to be anything the developers can do. We do need to get the symbols installed for this bug to be actionable. > In the dump i shared around line 468 I did noticed the following > "Reading symbols from /usr/bin/plasmashell... > (No debugging symbols found in /usr/bin/plasmashell)" That means that the system can't find debug symbols for plasmashell. I assume you had followed https://wiki.archlinux.org/title/Debuginfod. Did you set the DEBUGINFOD_URLS variable manually or via .urls files in /etc/debuginfod/ ? You might try adding https://debuginfod.elfutils.org/ that's mentioned there. You might try using debuginfod-find, but Arch should be set up to find debug symbols. You might also consider reaching out to the Arch community to get this working.
(In reply to TraceyC from comment #14) > I found that this was supposed to have been fixed in 6.4.0, but you're > seeing this in 6.4.3. I'm marking this as a regression. > > (In reply to Jim from comment #13) > > I have tried to get the debug symbols working but no luck. > > i have followed all the correct steps, with the DEBUGINFOD_URLS having the > > correct value too. All correct packages as well. > > Without at least the symbols for libdictplugin, there isn't going to be > anything the developers can do. We do need to get the symbols installed for > this bug to be actionable. > > > In the dump i shared around line 468 I did noticed the following > > "Reading symbols from /usr/bin/plasmashell... > > (No debugging symbols found in /usr/bin/plasmashell)" > > That means that the system can't find debug symbols for plasmashell. > > I assume you had followed https://wiki.archlinux.org/title/Debuginfod. Did > you set the DEBUGINFOD_URLS variable manually or via .urls files in > /etc/debuginfod/ ? You might try adding https://debuginfod.elfutils.org/ > that's mentioned there. > > You might try using debuginfod-find, but Arch should be set up to find debug > symbols. You might also consider reaching out to the Arch community to get > this working. I did not set the url manually. As per https://wiki.archlinux.org/title/Debuginfod The libelf package auto sets the debug url on arch, this is normally always installed as it is a core dependency. Also had gdb and drkonqi. I have verified said debug url was correctly set. I followed debug symbol setup as per the wiki as well as the kde community page you linked to earlier.
Thanks for clarifying how things were set up. At this point, your best bet is to reach out to the Arch community to help fill in the missing debug symbols in the backtrace.
Sorry for the forward-dupe, but we're already tracking this at high priority in Bug 509216.
*** This bug has been marked as a duplicate of bug 509216 ***
*** This bug has been marked as a duplicate of bug 502199 ***