| Summary: | after login black screen in plasmashell 5.27.0. Deleted all plasmashell / kde .config folders. Black screen in bookworm sid 12 | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Ilias Tsolis <elias_0000_0000> |
| Component: | Startup process | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | grave | CC: | kde, nate |
| Priority: | NOR | ||
| Version First Reported In: | 5.27.0 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Ilias Tsolis
2023-03-08 20:23:14 UTC
`KCrash: Attempting to start /usr/bin/plasmashell KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = plasmashell path = /usr/bin pid = 57364 KCrash: Arguments: /usr/bin/plasmashell KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 12 and type 'Read', disabling... QSocketNotifier: Invalid socket 14 and type 'Read', disabling... Checking screens: available: (QScreen(0x563298b131a0, name="HDMI-1")) redundant: QHash() fake: QSet() all: (QScreen(0x563298b131a0, name="HDMI-1")) Invalid corona package metadata Containment graphic object not valid ` (gdb) run Starting program: /usr/bin/plasmashell [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7ffff05ff6c0 (LWP 58633)] [New Thread 0x7fffef3f66c0 (LWP 58634)] [New Thread 0x7fffeca386c0 (LWP 58637)] Thread 1 "plasmashell" received signal SIGSEGV, Segmentation fault. 0x00007ffff7cc9214 in Plasma::Containment::corona() const () from /usr/lib/x86_64-linux-gnu/libKF5Plasma.so.5 Can you paste the full backtrace? Tell me how to do full backtrace please... I am on bookworm (test version) I pasted whatever gdb printed. I cannot understand what other options to use in order to get more information from gdb on that. The GDB output from Comment 2 can't possibly be complete because in order to get that backtrace, you had to type `bt` at some point, which isn't in the text. I would recommend asking for help in a Debian forum. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |