Bug 496923

Summary:	On X11 on resuming from suspend or hibernation, desktop is black/missing until plasmashell is restarted
Product:	[Plasma] plasmashell	Reporter:	Guido <guido.iodice>
Component:	Containment	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED DUPLICATE
Severity:	major	CC:	guido.iodice, kdedev, keplicz, nate, notmart
Priority:	NOR
Version First Reported In:	6.2.4
Target Milestone:	1.0
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Guido 2024-12-02 10:00:56 UTC

SUMMARY
Plasmashell seems to crash after suspend/resume

STEPS TO REPRODUCE
1. Wait for auto-suspend
2. Resume

OBSERVED RESULT
Plasmashell seems to crash: no panel, no backgroud, but nothing in log and the plasmashell process is in execution.
This does not happen 100% of the time, but very often.


EXPECTED RESULT
It should not crash.

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux rolling
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0
Kernel Version: 6.12.1-4-MANJARO (64-bit)
Graphics Platform: X11
Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® Iris® Xe Graphics
Manufacturer: Dell Inc.
Product Name: Inspiron 5502

Comment 1 TraceyC 2024-12-09 23:09:50 UTC

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!

Comment 2 Guido 2024-12-10 16:43:02 UTC

I tried it, but as I said, the process doesn't actually crash, but it feels like it does. The panel disappears, the background too. Now I notice, however, that the notifications are still displayed.

Comment 3 TraceyC 2024-12-10 17:05:01 UTC

Thanks for clarifying what's happening. Can you get a backtrace of what Plasma is doing when it's in this incomplete state?

Run this in a terminal window while it's in the bad state

     gdb attach -p $(pidof plasmashell) 

If it says "--Type  for more, q to quit, c to continue without paging--" at the bottom of the terminal window, press the "c" key.
When you see a prompt that says "(gdb)", type "bt" and press the enter key.
If it says "--Type  for more, q to quit, c to continue without paging--" at the bottom of the terminal window, press the "c" key.
Copy-and-paste the contents of the terminal window into a comment here.

Thanks!

Comment 4 Guido 2024-12-10 17:27:46 UTC

(gdb) continue
Continuing.
[Thread 0x72da69ffb6c0 (LWP 47601) exited]
[Thread 0x72da83fff6c0 (LWP 47579) exited]
[Thread 0x72da75ffb6c0 (LWP 47578) exited]
[Thread 0x72da82ffd6c0 (LWP 47577) exited]
[Thread 0x72da757fa6c0 (LWP 47576) exited]
[Thread 0x72dab27586c0 (LWP 47461) exited]
[New Thread 0x72da757fa6c0 (LWP 47682)]
[New Thread 0x72da83fff6c0 (LWP 47683)]
[New Thread 0x72dab27586c0 (LWP 47684)]
[New Thread 0x72da82ffd6c0 (LWP 47685)]
[New Thread 0x72da837fe6c0 (LWP 47686)]
[New Thread 0x72da827fc6c0 (LWP 47687)]
[New Thread 0x72da81ffb6c0 (LWP 47688)]
[Thread 0x72da81ffb6c0 (LWP 47688) exited]
[Thread 0x72da827fc6c0 (LWP 47687) exited]
[Thread 0x72da837fe6c0 (LWP 47686) exited]
[New Thread 0x72da837fe6c0 (LWP 47689)]
[New Thread 0x72da827fc6c0 (LWP 47690)]
[New Thread 0x72da81ffb6c0 (LWP 47691)]
[New Thread 0x72da765fc6c0 (LWP 47692)]
[New Thread 0x72da6a7fc6c0 (LWP 47693)]
[New Thread 0x72da69ffb6c0 (LWP 47694)]
[New Thread 0x72da697fa6c0 (LWP 48187)]
[Thread 0x72da697fa6c0 (LWP 48187) exited]
[Thread 0x72da82ffd6c0 (LWP 47685) exited]
[Thread 0x72dab27586c0 (LWP 47684) exited]
[Thread 0x72da83fff6c0 (LWP 47683) exited]
[Thread 0x72da757fa6c0 (LWP 47682) exited]
[New Thread 0x72da757fa6c0 (LWP 48228)]
[New Thread 0x72da83fff6c0 (LWP 48229)]
[New Thread 0x72dab27586c0 (LWP 48230)]
[New Thread 0x72da82ffd6c0 (LWP 48231)]
[New Thread 0x72da697fa6c0 (LWP 48232)]
[New Thread 0x72da477fe6c0 (LWP 48233)]
[New Thread 0x72da46ffd6c0 (LWP 48234)]
[Thread 0x72da46ffd6c0 (LWP 48234) exited]
[Thread 0x72da477fe6c0 (LWP 48233) exited]
[Thread 0x72da697fa6c0 (LWP 48232) exited]
[New Thread 0x72da697fa6c0 (LWP 48235)]
[New Thread 0x72da477fe6c0 (LWP 48236)]
[New Thread 0x72da46ffd6c0 (LWP 48237)]
[New Thread 0x72da467fc6c0 (LWP 48238)]
[Thread 0x72da467fc6c0 (LWP 48238) exited]
[Thread 0x72da46ffd6c0 (LWP 48237) exited]
[Thread 0x72da477fe6c0 (LWP 48236) exited]
[Thread 0x72da697fa6c0 (LWP 48235) exited]
[Thread 0x72da82ffd6c0 (LWP 48231) exited]
[Thread 0x72dab27586c0 (LWP 48230) exited]
[Thread 0x72da83fff6c0 (LWP 48229) exited]
[Thread 0x72da757fa6c0 (LWP 48228) exited]
[New Thread 0x72da83fff6c0 (LWP 48251)]
[New Thread 0x72da757fa6c0 (LWP 48252)]
[Thread 0x72da83fff6c0 (LWP 48251) exited]
[Thread 0x72da757fa6c0 (LWP 48252) exited]
[New Thread 0x72da757fa6c0 (LWP 48271)]
[New Thread 0x72da83fff6c0 (LWP 48272)]
[New Thread 0x72da82ffd6c0 (LWP 48273)]
[Thread 0x72da82ffd6c0 (LWP 48273) exited]
[Thread 0x72da83fff6c0 (LWP 48272) exited]
[Thread 0x72da757fa6c0 (LWP 48271) exited]
[New Thread 0x72da757fa6c0 (LWP 48296)]
[New Thread 0x72da83fff6c0 (LWP 48301)]
[Thread 0x72da757fa6c0 (LWP 48296) exited]
[Thread 0x72da83fff6c0 (LWP 48301) exited]
[New Thread 0x72da83fff6c0 (LWP 48311)]
[New Thread 0x72da757fa6c0 (LWP 48312)]
[New Thread 0x72da82ffd6c0 (LWP 48313)]
[Thread 0x72da82ffd6c0 (LWP 48313) exited]
[Thread 0x72da757fa6c0 (LWP 48312) exited]
[Thread 0x72da83fff6c0 (LWP 48311) exited]
[New Thread 0x72da83fff6c0 (LWP 48314)]
[New Thread 0x72da757fa6c0 (LWP 48315)]
[New Thread 0x72da82ffd6c0 (LWP 48316)]
[New Thread 0x72dab27586c0 (LWP 48317)]
[New Thread 0x72da697fa6c0 (LWP 48318)]
[New Thread 0x72da46dd76c0 (LWP 48319)]
[Thread 0x72da46dd76c0 (LWP 48319) exited]
[Thread 0x72da82ffd6c0 (LWP 48316) exited]
[Thread 0x72da757fa6c0 (LWP 48315) exited]
[Thread 0x72da83fff6c0 (LWP 48314) exited]
[Thread 0x72da697fa6c0 (LWP 48318) exited]
[Thread 0x72dab27586c0 (LWP 48317) exited]
[New Thread 0x72da697fa6c0 (LWP 48341)]
[New Thread 0x72dab27586c0 (LWP 48346)]

here the system goes on autosuspend. 
I wait 30 seconds, then press a key. THis appears

[New Thread 0x72da83fff6c0 (LWP 48375)]
[New Thread 0x72da757fa6c0 (LWP 48376)]
[New Thread 0x72da82ffd6c0 (LWP 48377)]
[Thread 0x72da82ffd6c0 (LWP 48377) exited]
[Thread 0x72da757fa6c0 (LWP 48376) exited]
[Thread 0x72da83fff6c0 (LWP 48375) exited]
[New Thread 0x72da83fff6c0 (LWP 48378)]
[New Thread 0x72da757fa6c0 (LWP 48379)]
[New Thread 0x72da82ffd6c0 (LWP 48380)]
[New Thread 0x72da46dd76c0 (LWP 48381)]
[Thread 0x72da697fa6c0 (LWP 48341) exited]
[Thread 0x72dab27586c0 (LWP 48346) exited]
[Thread 0x72da76ffd6c0 (LWP 46137) exited]
[Thread 0x72da777fe6c0 (LWP 46136) exited]
[Thread 0x72da77fff6c0 (LWP 46135) exited]
[Thread 0x72da80ff96c0 (LWP 46134) exited]
[Thread 0x72dabdd646c0 (LWP 45830) exited]
[Thread 0x72dabe5a56c0 (LWP 45829) exited]
[Thread 0x72dad17436c0 (LWP 45828) exited]
[Thread 0x72dad1f446c0 (LWP 45827) exited]
[New Thread 0x72dad1f446c0 (LWP 48424)]
[New Thread 0x72dad17436c0 (LWP 48425)]
[Thread 0x72dad1f446c0 (LWP 48424) exited]
[Thread 0x72dad17436c0 (LWP 48425) exited]

then I have de gdb prompt, then I type "continue"

(gdb) continue
[New Thread 0x72dad17436c0 (LWP 48580)]
[New Thread 0x72dad1f446c0 (LWP 48581)]
[Thread 0x72dad17436c0 (LWP 48580) exited]

But plasmashell is still not appearing.

BUT

If I press Meta the menu appears!

Comment 5 Guido 2024-12-10 18:44:44 UTC

My suspicion now is that the problem is related to the screen configuration. 

I normally have the laptop connected to the external screen with the laptop's screen deactivated. 

If I activate the laptop's screen but leave the external screen as the main screen when I wake up, this happens: the main plasmashell panel appears on the laptop's screen, while the external screen remains black but active (I can put the mouse cursor there). 

Then if I restart plasmashell, the main panel reappears on the external screen and the secondary panel on the laptop's screen.

Comment 6 Guido 2024-12-10 18:56:09 UTC

(In reply to Guido from comment #5)
> My suspicion now is that the problem is related to the screen configuration. 
> 
> I normally have the laptop connected to the external screen with the
> laptop's screen deactivated. 
> 
> If I activate the laptop's screen but leave the external screen as the main
> screen when I wake up, this happens: the main plasmashell panel appears on
> the laptop's screen, while the external screen remains black but active (I
> can put the mouse cursor there). 
> 
> Then if I restart plasmashell, the main panel reappears on the external
> screen and the secondary panel on the laptop's screen.

I have tried resetting the screen configuration and redoing it the same way, but the problem recurs. Basically what happens is that in the screen configuration interface the two displays become overlapped. Maybe this is the cause of the problem? When waking up, maybe Plasmashell doesn't quite understand where to go?

Comment 7 Nate Graham 2024-12-11 21:11:40 UTC

Does it reproduce on Wayland, or is it X11-specific?

Comment 8 Guido 2024-12-12 11:07:42 UTC

(In reply to Nate Graham from comment #7)
> Does it reproduce on Wayland, or is it X11-specific?

I did a few tests, it seems to be X11-specific.

Comment 9 Nate Graham 2024-12-12 16:29:08 UTC

Thanks. Do you have multiple screens?

Comment 10 Guido 2024-12-12 16:33:00 UTC

(In reply to Nate Graham from comment #9)
> Thanks. Do you have multiple screens?

Yes, I usually use my laptop connected to an external monitor, with the laptop screen deactivated. 

When I (rarely) use the laptop screen as secondary monitor, I have a second panel with only taskmanager on it.

Comment 11 Guido 2024-12-12 16:36:04 UTC

xrandr output:

Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
eDP-1 connected (normal left inverted right x axis y axis)
   1920x1080     59.98 +  47.98  
   1680x1050     59.98  
   1400x1050     59.98  
   1600x900      59.98  
   1280x1024     59.98  
   1400x900      59.98  
   1280x960      59.98  
   1440x810      59.98  
   1368x768      59.98  
   1280x800      59.98  
   1280x720      59.98  
   1024x768      59.98  
   960x720       59.98  
   928x696       59.98  
   896x672       59.98  
   1024x576      59.98  
   960x600       59.98  
   960x540       59.98  
   800x600       59.98  
   840x525       59.98  
   864x486       59.98  
   700x525       59.98  
   800x450       59.98  
   640x512       59.98  
   700x450       59.98  
   640x480       59.98  
   720x405       59.98  
   684x384       59.98  
   640x360       59.98  
   512x384       59.98  
   512x288       59.97  
   480x270       59.98  
   400x300       59.97  
   432x243       59.98  
   320x240       59.98  
   360x202       59.97  
   320x180       59.97  
HDMI-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 521mm x 293mm
   1920x1080     60.00*+  50.00    59.94    30.00    25.00    24.00    29.97    23.98  
   1680x1050     59.88  
   1280x1024     75.02    60.02  
   1280x720      60.00    50.00    59.94  
   1024x768      75.03    60.00  
   800x600       75.00    60.32    56.25  
   720x576       50.00  
   720x480       60.00    59.94  
   640x480       75.00    72.81    66.67    60.00    59.94  
   720x400       70.08  
DP-1 disconnected (normal left inverted right x axis y axis)

Comment 12 Nate Graham 2024-12-12 16:45:34 UTC

Thanks. Does the issue ever happen when you don't have any external screens connected?

Comment 13 Guido 2024-12-12 17:12:26 UTC

(In reply to Nate Graham from comment #12)
> Thanks. Does the issue ever happen when you don't have any external screens
> connected?

I did some tests and the problem did not occur with only the laptop monitor active.

Using the external monitor as secondary and the laptop monitor as primary, the problem occurs but still on the external monitor. Again, restarting plasmashell returns everything to normal.

Comment 14 Piotr Keplicz 2024-12-12 18:12:34 UTC

I have similar problems since Plasma 6.2.4 on KDE neon. It seems that it's sufficient for the external monitor to go to standby mode to cause such plasmashell behaviour. If you unlock the screen before standby everything works fine.

Comment 15 Nate Graham 2024-12-18 16:31:32 UTC

Guido and Piotr, does this ever happen on login as well? Or does it only ever happen after resume from suspend or unlock?

Comment 16 Nate Graham 2024-12-18 16:40:26 UTC

Actually never mind; I have all the info I need to say that this is the same issue as Bug 496926.

*** This bug has been marked as a duplicate of bug 496926 ***

Comment 17 Guido 2025-01-13 12:58:33 UTC

This does not seem to be the same as bug #496926 .

In fact, I have tried using other Plasma themes, but the problem still occurs, whereas for bug #496926, users report that by changing themes (even Breeze Light) the bug does not occur.

Comment 18 Guido 2025-01-13 13:03:54 UTC

Sorry, my fault, I got confused with another similar bug in which I am copying but it is not the same. So it is plausible that this is the same bug 496926

*** This bug has been marked as a duplicate of bug 496926 ***