Bug 355484 - Using lock and unlocking right away prevents use of lock/logoff/shutdown etc. commands from menu
Summary: Using lock and unlocking right away prevents use of lock/logoff/shutdown etc....
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 5.4.3
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-17 10:47 UTC by nothanks3u
Modified: 2020-12-21 04:34 UTC (History)
4 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 nothanks3u 2015-11-17 10:47:52 UTC
Once KDE has loaded, if I use the main menu to lock the computer, then type my password to get back in, I can then go to the main menu and try to log off/lock screen/shutdown but nothing works, the menu closes but no action is taken - I need to manually switch to a virtual console and kill KDE.
If I then restart KDE right away without rebooting, it freezes on the loading bar at about 75%.

I'm not sure if this is a KDE issue or arch linux issue.

Reproducible: Always

Steps to Reproduce:
1. Login to KDE
2. Using main menu, lock the screen
3. Enter user password
4. Go to main menu and try to lock screen/logoff/other action

Actual Results:  
Menu closes, nothing happens

Expected Results:  
Action taken in step 4 should execute
Comment 1 Alexander Mentyu 2017-11-29 06:32:46 UTC
Can't confirm in:

Distribution: KDE neon Developer Edition - Stable Branches
Plasma: 5.11.3
Frameworks: 5.41.0
Qt: 5.9.2
Kernel 4.10.0-40-generic
Type: 64-bit
Comment 2 Justin Zobel 2020-11-21 10:11:33 UTC
I've just tested this on plasma 5.20.3 and I cannot reproduce this issue.

I locked and immediately unlocked the session and was then able to lock the screen from the launcher.

Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I've set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
Comment 3 Bug Janitor Service 2020-12-06 04:34:00 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 4 Bug Janitor Service 2020-12-21 04:34:47 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!