Bug 441977 - After cloning, kscreen does not return to original resolution when using "Switch to laptop screen"
Summary: After cloning, kscreen does not return to original resolution when using "Swi...
Status: RESOLVED WORKSFORME
Alias: None
Product: KScreen
Classification: Plasma
Component: common (show other bugs)
Version: 5.22.4
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kscreen-bugs-null@kde.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-09-04 07:11 UTC by Horst Schirmeier
Modified: 2022-12-08 05:15 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Horst Schirmeier 2021-09-04 07:11:00 UTC
SUMMARY
When I clone my laptop screen (2560x1440) to an HDMI-connected TV (FHD), both displays go to FHD.  When disabling clone mode by using kscreen's "Switch to laptop screen", the external display is disabled as expected, but the laptop display stays at FHD instead of going back to 2560x1440.

This is a regression.

STEPS TO REPRODUCE
- attach external Full-HD monitor (e.g. via HDMI)
- use kscreen to "Unify outputs" (Fn+F7 on my Lenovo T460p, or using the "Display Configuration" tray applet)
- internal monitor is now down to 1920x1080, showing the same content as the external one
- use kscreen to "Switch to laptop screen"

OBSERVED RESULT (since Ubuntu 21.10, i.e. the kscreen 5.21.4 -> 5.22.4 transition):
- external monitor goes black
- internal monitor stays at 1920x1080

EXPECTED RESULT (seen up to and including Ubuntu 21.04, i.e. kscreen 5.21.4):
- external monitor goes black
- internal monitor returns to native resolution (2560x1440 in my case)

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Ubuntu 21.10
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Ubuntu bug report: https://bugs.launchpad.net/ubuntu/+source/kscreen/+bug/1939377
Comment 1 Nate Graham 2021-09-08 21:40:27 UTC
Does it work properly in the Plasma Wayland session? Can you check?
Comment 2 Horst Schirmeier 2021-09-09 15:14:56 UTC
Plasma Wayland exhibits a differently unexpected behavior: With "Unify outputs", both displays stay at their original (native) resolution.  The laptop screen is still at 2560x1440, the external FHD monitor at 1920x1080 and mirroring a cutout of the laptop screen.

When using "Switch to laptop screen" then, the internal screen stays at its native resolution; so in a way, the state afterwards is better with Wayland, but "Unify outputs" doesn't do what I expect.  Guess that's a different bug.
Comment 3 Horst Schirmeier 2021-09-09 15:50:53 UTC
Disregard that.  My KDE/Plasma setup seems to be broken since Ubuntu's 5.22.4->5.22.5 recent update.  I'll report on Wayland again when this is smoothed out.
Comment 4 Horst Schirmeier 2021-09-23 17:22:27 UTC
(In reply to Horst Schirmeier from comment #2)
> Plasma Wayland exhibits a differently unexpected behavior: With "Unify
> outputs", both displays stay at their original (native) resolution.  The
> laptop screen is still at 2560x1440, the external FHD monitor at 1920x1080
> and mirroring a cutout of the laptop screen.
> 
> When using "Switch to laptop screen" then, the internal screen stays at its
> native resolution; so in a way, the state afterwards is better with Wayland,
> but "Unify outputs" doesn't do what I expect.  Guess that's a different bug.

This differently broken behavior on Xwayland persists.
Comment 5 Horst Schirmeier 2021-09-24 05:55:35 UTC
Also happens from a "clean" user account.
Comment 6 Horst Schirmeier 2021-09-24 19:24:49 UTC
(In reply to Horst Schirmeier from comment #2)
> When using "Switch to laptop screen" then, the internal screen stays at its
> native resolution; so in a way, the state afterwards is better with Wayland,
> but "Unify outputs" doesn't do what I expect.  Guess that's a different bug.
Reported as bug #442874.
Comment 7 Bug Janitor Service 2021-10-09 04:35: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 8 Nate Graham 2022-11-08 22:34:07 UTC
Thank you for the bug report. Unfortunately we were not able to get to it yet. Can we ask you to please check if this is still an issue with Plasma 5.25 or 5.26?

If it is, please add a comment with the output of `kscreen-doctor -o` and change the status to CONFIRMED. If not, or if you can't because you no longer use this setup, you can change the status to RESOLVED WORKSFORME. Thanks a lot!
Comment 9 Bug Janitor Service 2022-11-23 05:16:03 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 10 Bug Janitor Service 2022-12-08 05:15:33 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!