Bug 491399 - Plasma panel disappears after unlocking screen
Summary: Plasma panel disappears after unlocking screen
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Panel (show other bugs)
Version: 6.0.5
Platform: Other Linux
: NOR grave
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: multiscreen
Depends on:
Blocks:
 
Reported: 2024-08-07 15:56 UTC by Waqar Ahmed
Modified: 2024-09-17 19:37 UTC (History)
8 users (show)

See Also:
Latest Commit:
Version Fixed In: 6.2.0
Sentry Crash Report:


Attachments
panel (285.91 KB, image/png)
2024-08-08 07:08 UTC, Waqar Ahmed
Details
Logs since unlocking screen (151.04 KB, text/plain)
2024-08-14 14:51 UTC, Waqar Ahmed
Details
new logs (74.74 KB, text/plain)
2024-09-09 15:16 UTC, Waqar Ahmed
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Waqar Ahmed 2024-08-07 15:56:41 UTC
SUMMARY

Plasma panel disappears after unlocking screen. I have an external display connected to my laptop, and use the external display as the only display i.e., my laptop screen is off.

Replugging the external display brings back the panel

STEPS TO REPRODUCE

Happens randomly. No idea how to reproduce


SOFTWARE/OS VERSIONS
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.4
Qt Version: 6.7.1
Comment 1 fanzhuyifan 2024-08-07 17:43:07 UTC
What kind of panel is it? (Always visible/ dodge windows/autohide)
Where is the panel positioned?
Is this on wayland or x11?
Comment 2 Waqar Ahmed 2024-08-08 07:08:22 UTC
Created attachment 172390 [details]
panel

Adding a screenshot for the first two questions.

I am running xorg.
Comment 3 Waqar Ahmed 2024-08-08 07:09:00 UTC
The panel is positioned at the bottom.
Comment 4 Nate Graham 2024-08-09 04:23:27 UTC
Any chance you could try with Plasma 6.1?
Comment 5 Dmitry Petrov 2024-08-12 14:58:12 UTC
(In reply to Nate Graham from comment #4)
> Any chance you could try with Plasma 6.1?

Yes, still happens on Plasma 6.1. Wayland session.
In my case, laptop is connected to TV. After blocking  screen goes off, then my TV turns off (because TV writes "no signal" message).
Also happens randomly, but usually the problem occurs, after long time with the laptop turned on.

To get the panel back, I press Alt+Enter, then open Settings and turn the laptop screen on and off.

Hardware
Laptop MSI GF63 Thin 11UC
Processor: Intel  i5-11400H
GPU: Intel UHD Graphics 730 + Nvidia RTX 3050
TV (2nd screen): Samsung T24H390SIX

Software:
Arch Linux. Linux kernel 6.10.3
KDE Plasma version: 6.1.3
KDE Frameworks Version: 6.4.0
Qt Version: 6.7.2
Wayland session
Comment 6 Waqar Ahmed 2024-08-12 17:58:15 UTC
I haven't found any concrete way to reproduce this so far
Comment 7 Niccolò Venerandi 2024-08-13 08:09:54 UTC
Could you send a screenshot of your "Edit mode > Panel and desktop management" window when the panel disappears?
Comment 8 Waqar Ahmed 2024-08-14 14:50:02 UTC
> Could you send a screenshot of your "Edit mode > Panel and desktop management" window when the panel disappears?

There is no panel to right click and get to Edit mode. Is there any other way?

Just triggered the bug again. Will attach logs
Comment 9 Waqar Ahmed 2024-08-14 14:51:41 UTC
Created attachment 172620 [details]
Logs since unlocking screen
Comment 10 Waqar Ahmed 2024-08-14 14:56:04 UTC
I tried to switch displays, but seems like the shortcuts for "Display Configuration" don't work for some reason :/
Comment 11 TraceyC 2024-08-19 16:54:54 UTC
*** Bug 485932 has been marked as a duplicate of this bug. ***
Comment 12 TraceyC 2024-08-19 17:02:18 UTC
(In reply to Waqar Ahmed from comment #8)
> > Could you send a screenshot of your "Edit mode > Panel and desktop management" window when the panel disappears?
> 
> There is no panel to right click and get to Edit mode. Is there any other
> way?

Right clicking on the desktop should have "Edit mode" in the menu.
Comment 13 Maxim Egorushkin 2024-08-21 17:03:13 UTC
I experience the same problem of the panel disappearing after the monitor goes off due to inactivity and then back on. I have one panel only, at the top. Some existing windows then resize to fill the gap at the top where the panel was. 

The desktop also seem to disappear - no icons, right click doesn't open a menu.

Keyboard shortcuts for KRunner, system settings, switching windows and desktops still work.

I have one DP monitor connected to the system.

Operating System: KDE neon 6.0
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Kernel Version: 6.8.0-40-lowlatency (64-bit)
Graphics Platform: Wayland
Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor
Memory: 125.7 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 4090/PCIe/SSE2
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: X570 AORUS MASTER
System Version: -CF
Comment 14 Maxim Egorushkin 2024-08-26 16:03:48 UTC
(In reply to Waqar Ahmed from comment #6)
> I haven't found any concrete way to reproduce this so far

Reproduction steps:

1. Enable notifications (turn off "do not disturb").
2. Connect Bluetooth headphones.
3. Lock the screen and wait till the monitor turns off.
4. Turn off the Bluetooth headphones.
5. Unlock the screen.
6. Observe that the panel is gone. Sometimes, there is a volume OSD stuck in a random place on the screen, cannot be removed.
Comment 15 Maxim Egorushkin 2024-08-26 23:33:19 UTC
(In reply to Maxim Egorushkin from comment #14)
> (In reply to Waqar Ahmed from comment #6)
> > I haven't found any concrete way to reproduce this so far
> 
> Reproduction steps:
> 
> 1. Enable notifications (turn off "do not disturb").
> 2. Connect Bluetooth headphones.
> 3. Lock the screen and wait till the monitor turns off.
> 4. Turn off the Bluetooth headphones.
> 5. Unlock the screen.
> 6. Observe that the panel is gone. Sometimes, there is a volume OSD stuck in
> a random place on the screen, cannot be removed.

Thinking more about the root cause of the issue, the audio device change OSD and volume OSD are displayed regardless of whether notifications are in "do not disturb" mode or not. There is no audio playing, and notification sounds are disabled in the "Colours & Theme -> System Sounds" on my system, when I turn the Bluetooth headphones off.

The problem seems to occur only when notifications are not in "do not disturb" mode. Which suggests that notification pop-ups could be crashing the panel when the only monitor turns off.
Comment 16 Nate Graham 2024-08-29 21:10:11 UTC
When this happens, is it just the panel that's gone? Or the wallpaper on that panel's screen, too?
Comment 17 Nate Graham 2024-08-29 21:12:18 UTC
I ask because if so, it sounds quite a bit like Bug 467074, which is X11 specific. So for any affected people, if you switch to Wayland, it'll probably stop happening. I hope, at least!
Comment 18 george fb 2024-08-29 21:20:25 UTC
In my case this happens when power saving kicks in and turns off the monitor.
The cause is a secondary monitor which is disabled in system settings.
If I enable the monitor or unplug it the issue stops.

(In reply to Nate Graham from comment #16)
> When this happens, is it just the panel that's gone? Or the wallpaper on
> that panel's screen, too?
Panel and wallpaper

(In reply to Nate Graham from comment #17)
> I ask because if so, it sounds quite a bit like Bug 467074, which is X11
> specific. So for any affected people, if you switch to Wayland, it'll
> probably stop happening. I hope, at least!
I'm using Wayland.

My bug report https://bugs.kde.org/show_bug.cgi?id=485932
Comment 19 Nate Graham 2024-08-30 15:53:41 UTC
Ok, thanks. Waqar, when this happens to you, does your wallpaper/desktop also disappear? Or is it just the panel?

I ask because the codepaths differ here, so there may be different bugs on X11 compared to Wayland.
Comment 20 Maxim Egorushkin 2024-08-30 22:38:17 UTC
(In reply to Nate Graham from comment #16)
> When this happens, is it just the panel that's gone? Or the wallpaper on
> that panel's screen, too?

For me, when that happens my desktop icons are gone, no desktop context menu. My black colour wallpaper might still be there, hard to tell. This happens in Wayland session, not X11.
Comment 21 Waqar Ahmed 2024-09-02 08:21:48 UTC
> Ok, thanks. Waqar, when this happens to you, does your wallpaper/desktop also disappear? Or is it just the panel?

Both the desktop and panel disappear and I get a black background instead of the wallpaper. I tried right clicking to enter edit mode but nothing happened.
Comment 22 Nate Graham 2024-09-03 20:18:00 UTC
Ok, thanks. Sounds like an issue we get a lot of reports about, usually on X11, never easily reproducible (Bug 487580, Bug 491868, Bug 490040). A few more questions for Waqar:
1. What's your GPU hardware?
2. Does it ever happen on login, or always after unlocking the screen?
3. After this happens, does it get fixed if you restart plasmashell with `systemctl restart --user plasma-plasmashell.service` (or `plasmashell --replace` if you're not using Plasma's systemd integration
Comment 23 Waqar Ahmed 2024-09-09 11:03:58 UTC
> 1. What's your GPU hardware?

I have an integerated gpu that comes with the amd 4700u cpu

> 2. Does it ever happen on login, or always after unlocking the screen?

So far it has only happened on unlocking.

Will answer the 3rd question once I am able to reproduce this bug again.
Comment 24 Waqar Ahmed 2024-09-09 15:15:39 UTC
> 3. After this happens, does it get fixed if you restart plasmashell with `systemctl restart --user plasma-plasmashell.service` (or `plasmashell --replace` if you're not using Plasma's systemd integration

Yes. I tried the `systemctl` variant.

Also, since it just happened I have noticed that it has nothing to do with locking screen. My 4 year old switched off the screen while I was working (pulled the plug), after turning it on again there was no plasmashell. There was no screen locking.
Comment 25 Waqar Ahmed 2024-09-09 15:16:08 UTC
Created attachment 173479 [details]
new logs

New logs
Comment 26 Nate Graham 2024-09-16 14:37:36 UTC
Thanks. This sounds quite a bit like Bug 467422, which was ultimately traced to a faulty HDMI cable. Any chance you could try using a different cable to rule that out?

If that doesn't fix the issue, it may still be one of these: Bug 469192, Bug 491868, Bug 490040.
Comment 27 Waqar Ahmed 2024-09-16 18:08:20 UTC
All those bugs look like duplicates of this one (or the other way around).

I don't think its a cable issue, otherwise plasmashell wouldn't restore itself on running `systemctl restart --user plasma-plasmashell.service`. The bug is quite hard to reproduce, I haven't seen it once since last week. My current hypothesis is that plasmashell is restored before the screen is actually ready to show content and gets stuck. This might actually be a bug somewhere lower in the stack.
Comment 28 Maxim Egorushkin 2024-09-16 23:06:28 UTC
(In reply to Nate Graham from comment #26)
> Thanks. This sounds quite a bit like Bug 467422, which was ultimately traced
> to a faulty HDMI cable. Any chance you could try using a different cable to
> rule that out?

The bug I experience is triggered by having desktop notifications on when the screen is locked, perfectly reproducible, as I documented above.

There is no evidence suggesting faulty hardware hypothesis.

Should I open a new bug report?
Comment 29 Waqar Ahmed 2024-09-17 17:27:11 UTC
I have tried to reproduce with a notification showing using

notify-send "summary" "some body text" -t 100000

but so far no luck. Can you try that?

Other than that, I am now running self built plasmashell but so far I haven't been able to hit the bug even after turning the monitor off and on dozens of times.
Comment 30 Nate Graham 2024-09-17 19:37:35 UTC
If you can't reproduce it with current git master, that's very encouraging. I'd say let's close this for now as fixed in Plasma 6.2, but with the option to re-open the Bugzilla ticker if it happens again, and then at that point we'll try some more debugging.

Everyone else experiencing an issue that looks similar or the same should open a new bug report for it. The challenge with this kind of issue is that it can be caused by many distinct causes, so we generally need a new bug report for each one, until we can determine that it's actually the same issue as another one.

Thanks folks!