Bug 354213 - Painful multi-monitors multi-resolutions configuration
Summary: Painful multi-monitors multi-resolutions configuration
Status: RESOLVED WORKSFORME
Alias: None
Product: KScreen
Classification: Plasma
Component: common (other bugs)
Version First Reported In: 5.4.2
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Daniel Vrátil
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-22 13:02 UTC by Arthur c
Modified: 2022-11-08 21:57 UTC (History)
1 user (show)

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


Attachments
buggy kscreen configuration (39.89 KB, image/jpeg)
2015-10-22 13:02 UTC, Arthur c
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Arthur c 2015-10-22 13:02:06 UTC
Hi,
I'm on Fedora 23/KDE 5.4.2 and I have issue with screen config since Fedora switched to wayland.

I have three screens (laptop + 2 extras). There is NO problem to configure them as a line in kscreen. There is troubles when I put one to the left and one to the top of laptop screen like this : https://i.imgur.com/8jYonDG.jpg

The trouble come from the vertical resolution size difference I think. Sometimes, the upper screen is only displaying a size part vertically equal to the vertical size part of the left screen on top of the laptop screen. If I put the two screens inline on the top of the laptop screen I don't have any problem. Am I understandable ? It seems to be only a vertical alignment problem.

To manage to get my screens to work as I want, I have to configure them inline, then retry and retry, and sometimes I get the right display but with a frozen plasma/kde desktop. Then I delog/relog and it's ok most of the time. It takes 5/10 minutes each time.


libkscreen-1.0.5-4.fc23.x86_64
libkscreen-qt5-5.4.2-1.fc23.x86_64
kscreen-5.4.2-1.fc23.x86_64


Reproducible: Always
Comment 1 Arthur c 2015-10-22 13:02:48 UTC
Created attachment 95082 [details]
buggy kscreen configuration
Comment 2 Justin Zobel 2021-03-10 00:32:39 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 3 Nate Graham 2022-11-08 21:57:01 UTC
No response, closing.