Bug 354284 - KScreen doesn't restore the original primary display after unplug
Summary: KScreen doesn't restore the original primary display after unplug
Status: RESOLVED WORKSFORME
Alias: None
Product: KScreen
Classification: Plasma
Component: common (other bugs)
Version First Reported In: 5.4.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Daniel Vrátil
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-23 22:40 UTC by Viorel-Cătălin Răpițeanu
Modified: 2022-11-08 21:56 UTC (History)
2 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 Viorel-Cătălin Răpițeanu 2015-10-23 22:40:18 UTC
Connect a monitor to your laptop. Extend your laptop and make your monitor your primary display (this will move all your panels from the laptop screen to your monitor). Poweroff your machine, disconnect your monitor and start the laptop. After the login, the panels of your secondary screen are shown instead of the primary one, even if the isn't any other display connected! Also, when trying to add new widgets, the indicator also increment those from the now invisible first monitor.

Reproducible: Always

Steps to Reproduce:
1. Connect a monitor to your laptop.
2. Extend your laptop and make your monitor your primary display (this will move all your panels from the laptop screen to your monitor).
3. Poweroff your machine
4. Disconnect your monitor.
5. Power on your machine.
6. Login

Actual Results:  
After the login, the panels of your secondary screen are shown instead of the primary one, even if the isn't any other display connected!

Expected Results:  
Since there is only one display connected, your laptop should become your primary screen.
Also, it should be a settings available for this type of behavior.

To fix this you need to reconect your monitor, extend your laptop, make your laptop your primary display again and then disconnect the monitor.
Comment 1 Justin Zobel 2021-03-10 00:32:30 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.
Comment 2 Nate Graham 2022-11-08 21:56:29 UTC
No response, closing.