Bug 467076 - after login black screen in plasmashell 5.27.0. Deleted all plasmashell / kde .config folders. Black screen in bookworm sid 12
Summary: after login black screen in plasmashell 5.27.0. Deleted all plasmashell / kde...
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: Startup process (other bugs)
Version First Reported In: 5.27.0
Platform: Ubuntu Linux
: NOR grave
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-03-08 20:23 UTC by Ilias Tsolis
Modified: 2023-04-13 03:45 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ilias Tsolis 2023-03-08 20:23:14 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

after login black screen in plasmashell 5.27.0. Deleted all plasmashell / kde .config folders. Black screen in bookworm sid 12


STEPS TO REPRODUCE
try to run plasmashell after sddm login screen. 
a black screen appears with mouse. I can move mouse, run terminal, apps eg. firefox, but no desktop, no menu bar nothing. 

OBSERVED RESULT
a black screen appears with mouse. I can move mouse, run terminal, apps eg. firefox, but no desktop, no menu bar nothing. 


EXPECTED RESULT
a desktop with menu taskbar panels etc. 

SOFTWARE/OS VERSIONS
dont know how to find them in terminal 

ADDITIONAL INFORMATION
all related config files of plasma shell kde deleted in .config folder.
Comment 1 Ilias Tsolis 2023-03-08 20:24:12 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
`
Comment 2 Ilias Tsolis 2023-03-08 20:36:28 UTC
(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
Comment 3 Nate Graham 2023-03-13 18:33:53 UTC
Can you paste the full backtrace?
Comment 4 Ilias Tsolis 2023-03-13 18:45:04 UTC
Tell me how to do full backtrace please...
Comment 5 Ilias Tsolis 2023-03-13 18:45:39 UTC
I am on bookworm (test version)
Comment 6 Nate Graham 2023-03-13 19:22:08 UTC
See https://wiki.debian.org/HowToGetABacktrace
Comment 7 Ilias Tsolis 2023-03-13 19:30:11 UTC
I pasted whatever gdb printed. I cannot understand what other options to use in order to get more information from gdb on that.
Comment 8 Nate Graham 2023-03-14 13:54:43 UTC
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.
Comment 9 Bug Janitor Service 2023-03-29 03:45:40 UTC
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!
Comment 10 Bug Janitor Service 2023-04-13 03:45:45 UTC
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!