Bug 262153 - choose screen to show session unlock dialog because it defaults to external monitor which is a problem if it is no longer present
Summary: choose screen to show session unlock dialog because it defaults to external m...
Status: RESOLVED WORKSFORME
Alias: None
Product: krunner
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Debian unstable Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-05 05:16 UTC by Tim Richardson
Modified: 2021-01-01 04:39 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Richardson 2011-01-05 05:16:05 UTC
Version:           unspecified (using KDE 4.4.5) 
OS:                Linux

Problem:
1. Sessions locks (eg screensaver, or suspend/hibernate)
2. external monitor is disconnected or not present when machine resumes
3. The unlock dialog is not visible since it is displayed on the no longer present external monitor
requiring a clumsy solution (log into console and unlock the session from there).

A workaround would be to allow the user to control on which screen the unlock dialog appears. I would make sure it appears on the laptop's screen if I could.

I have intel graphics hardware; I wish that I could turn off the external screen when it is is disconnected. I have a script mapped to a keyboard shortcut, but it doesn't help when the screen is locked. 



Reproducible: Always

Steps to Reproduce:
see above.

Actual Results:  
see above.

Expected Results:  
see above.
Comment 1 Tim Richardson 2011-01-05 08:05:03 UTC
If I have an open krunner dialog (that is, from Alt-F2), the screen unlock dialog follows it. So if I leave an open krunner dialog on my laptop screen, I get the unlock dialog also on the laptop screen.
Comment 2 Andrew Crouthamel 2018-11-05 03:12:18 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-11-17 04:51:53 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Justin Zobel 2020-12-02 04:02:35 UTC
Thank you for the report, Tim.

As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved.

I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thank you.
Comment 5 Bug Janitor Service 2020-12-17 04:33:55 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 6 Bug Janitor Service 2021-01-01 04:39:18 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!