Bug 500152

Summary: "Anwendungsstarter" - after wakeup from suspend-to-disk menu still shown
Product: [Plasma] plasmashell Reporter: crptdngl71
Component: Application Launcher (Kickoff) widgetAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: cwo.kde, kde, mikel5764, nate, noahadvs
Priority: NOR    
Version First Reported In: git-stable-Plasma/6.3   
Target Milestone: 1.0   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description crptdngl71 2025-02-15 22:39:14 UTC
SUMMARY
Application starter ("Anwendungsstarter" still shows menu after wakeup from suspend-to-disk

STEPS TO REPRODUCE
1.  Run a normal KDE session on a notebook connected to a DELL Tunderbolt docking station. German language set. Also set in system settings "Arbeitsflächen-Sitzung": "Sitzungswiederherstellung" -> "Bei letzer Abmeldung geöffnete"
2.  End session using "Anwendungsstarter" -> "Velassen" -> "Standby-Modus" to enter suspend-to-disk
3. Press button on docking station to wake up notebook from suspend-to-disk.

OBSERVED RESULT
3. KDE IDE is shown as intended, but it is still showing "Anwendungsstarter".

EXPECTED RESULT
3. KDE should restart without showing "Anwendungsstarter", as it is returning from suspend-to-disk and showing the "Verlassen" menu is no longer required as this step to go into status suspend-to-disk was completed. It is true that KDE is supposed to re-create last session after restart, but even so the "Verlassen" menu is not needed nor expected.

SOFTWARE/OS VERSIONS
Operating System: siduction 23.1
KDE Plasma Version: 6.3.0
KDE Frameworks Version: 6.10.0
Qt Version: 6.7.2
Kernel Version: 6.12.13-1-siduction-amd64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: Latitude 7490

ADDITIONAL INFORMATION
Comment 1 cwo 2025-02-16 23:45:28 UTC
Thank you for the bug report!

I can't reproduce this (I don't have a Thunderbolt docking station, but I don't think this should be relevant). 

We added code specifically to handle this for 6.2 (see https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/2543).

Did you have the Application Launcher pinned open (with the thumbtack icon in the top right)? That will prevent it from closing then, intentionally as the user signaled that they want to keep it open.

 Also, you say "Standby-Modus" and suspend-to-disk, but "Standby-Modus" is suspend-to-ram/sleep - suspend-to-disk/hibernate is called "Ruhezustand". Could you please confirm whether it is to-ram or to-disk (I don't think it should matter here).
Comment 2 crptdngl71 2025-02-17 16:29:23 UTC
(In reply to cwo from comment #1)
> Thank you for the bug report!
Thankyou for such a quick feedback!

> I can't reproduce this (I don't have a Thunderbolt docking station, but I
> don't think this should be relevant). 

The docking station has a hardware button to trigger on/off/wakeup etc. events. You could probably replicate this using a keyboard that has a power on/off button (or else if you can trigger power messages via your keyboard).

> We added code specifically to handle this for 6.2 (see
> https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/2543).
Hmm, not sure why this is not working then...

> Did you have the Application Launcher pinned open (with the thumbtack icon
> in the top right)? That will prevent it from closing then, intentionally as
> the user signaled that they want to keep it open.

No. App Launcher was not pinned open.

>  Also, you say "Standby-Modus" and suspend-to-disk, but "Standby-Modus" is
> suspend-to-ram/sleep - suspend-to-disk/hibernate is called "Ruhezustand".
> Could you please confirm whether it is to-ram or to-disk (I don't think it
> should matter here).

To be quite honest, I cannot even tell whether this is suspend-to-ram/sleep or suspend-to-disk/hibernate, as in German I do only have option "Standby-Modus" (little moon icon assigned to it), no other option deals with a standby/hibernate status. I can do these things (German):
Sperren (Lock screen)
Abmelden (Log out user)
Benutzer wechseln (Change user)
Stand-By (suspend-to-disk/ram?)
Neu starten (restart)
Herunterfahren (power off).
I have actually wondered where is option "hibernate" vs. "sleep".


lock screen, reboot computer, change user,
Comment 3 cwo 2025-02-17 16:47:13 UTC
(In reply to crptdngl71 from comment #2)
> The docking station has a hardware button to trigger on/off/wakeup etc.
> events. You could probably replicate this using a keyboard that has a power
> on/off button (or else if you can trigger power messages via your keyboard).

I do have a classic Thinkpad dock; I just tried it and pressing the on/off button there while it's sleeping will start the computer with the Application Launcher closed.

In fact, I can see it close just as the computer is going to sleep.  (On another computer I don't see that, yet the Application Launcher still closes, so don't take not seeing that as an indication it's not working)
 
> Hmm, not sure why this is not working then...

Neither am I. Very confusing. The only thing I can think of is that something in your hardware sends a Meta key press which causes it to open again. Possibly the power button? Does seem rather unlikely though.

You don't have the Application Launcher opening unexpectedly at other times, do you?

> To be quite honest, I cannot even tell whether this is suspend-to-ram/sleep
> or suspend-to-disk/hibernate, as in German I do only have option
> "Standby-Modus" (little moon icon assigned to it)

Little moon icon is sleep/suspend to RAM.  Hibernate/suspend-to-disk  has a snowflake.

> I have actually wondered where is option "hibernate" vs. "sleep".

It's only displayed if its actually available. You need on-disk swap with enough unused space for at least your ram (so it has a place to store your memory's content), and it can't be disabled for other reasons. Many distributions do not set this up correctly, as it often doesn't work all that well anyway, and failing can cause data loss.
Comment 4 Bug Janitor Service 2025-03-04 03:46:58 UTC
🐛🧹 ⚠️ 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!
Comment 5 Bug Janitor Service 2025-03-19 03:47:21 UTC
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.
Comment 6 crptdngl71 2025-03-19 17:16:39 UTC
(In reply to cwo from comment #3)
I still see this issue using:
Operating System: siduction 23.1
KDE Plasma Version: 6.3.2
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.7-1-siduction-amd64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: Latitude 7490

> You don't have the Application Launcher opening unexpectedly at other times,
> do you?

The Application Launcher does not open unexpectedly. It is working fine until I leave the session using sus-to-RAM.
 
> Little moon icon is sleep/suspend to RAM.  Hibernate/suspend-to-disk  has a
> snowflake.

OK then I can confirm it is sus-to-RAM. Hibernate/sus-to-disk is not seen here as I do not have a swap partition enabled.
Comment 7 cwo 2025-03-19 19:27:51 UTC
Well, then I'm out of ideas for now. Maybe someone else has an idea on what it could be.
Comment 8 Nate Graham 2025-03-19 22:02:45 UTC
To be clear, you're triggering suspend to RAM by clicking on the moon icon in Kickoff ("Anwendungsstarter"), right?
Comment 9 Bug Janitor Service 2025-04-03 03:46:44 UTC
🐛🧹 ⚠️ 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!
Comment 10 crptdngl71 2025-04-13 07:57:59 UTC
(In reply to Nate Graham from comment #8)
> To be clear, you're triggering suspend to RAM by clicking on the moon icon
> in Kickoff ("Anwendungsstarter"), right?

Yes, that is what I did.
Comment 11 Nate Graham 2025-04-14 20:21:35 UTC
Oh! I know what this is! It's Bug 500580, which is fixed in 6.4.0.

*** This bug has been marked as a duplicate of bug 500580 ***
Comment 12 cwo 2025-04-14 20:28:36 UTC
(In reply to Nate Graham from comment #11)
> Oh! I know what this is! It's Bug 500580, which is fixed in 6.4.0.

It's weird though, we explicitly set expanded to false when the user activates sleep, and don't rely on focus change detection.

It still might be the cause I guess; but please reopen the bug, crptdngl7, if it still happens in 6.4
Comment 13 Nate Graham 2025-04-14 20:31:00 UTC
It's because sleep was activated from the "Verlassen" menu, not by clicking on a button on the bottom bar. I missed that initially by not reading the German part closely enough.
Comment 14 cwo 2025-04-14 20:33:37 UTC
(In reply to Nate Graham from comment #13)
> It's because sleep was activated from the "Verlassen" menu, not by clicking
> on a button on the bottom bar. I missed that initially by not reading the
> German part closely enough.

Oooh good spot, I completely missed that as well.