Bug 19340 - sddm + double screen + different resolutions = bad display
Summary: sddm + double screen + different resolutions = bad display
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-12 15:00 CEST by Samuel Verschelde
Modified: 2021-05-17 01:15 CEST (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Screenshot (315.99 KB, image/jpeg)
2016-09-12 15:01 CEST, Samuel Verschelde 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Samuel Verschelde 2016-09-12 15:00:47 CEST 
I have two screens, one with a high resolution and one with a low one.

sddm first draws its screen on the bigger screen, but then adjusts to the lower resolution one which gives mixed results on the bigger screen.

See attached screenshot to see what I mean.
Comment 1 Samuel Verschelde 2016-09-12 15:01:20 CEST 
Created attachment 8401 [details]
Screenshot
Comment 2 Nicolas Lécureuil 2016-09-13 10:14:42 CEST 
confirmed here, can you report upstream ? ( i tested with sddm default theme and i have the same issue ).

CC: (none) => mageia

Comment 3 Marja Van Waes 2017-03-27 12:25:13 CEST 
With both a 1600x900 and a 1920x1080 screen, there's no ugly mixed result here with sddm-0.14.0-13.mga6.

In one screen the SDDM login screen appears nicely centred, in the other it appears nicely, but off-center.. the latter is something different than the issue stormi had, and probably not fixable (and I don't care :-þ )

CC: (none) => marja11

Comment 4 Aurelien Oudelet 2021-05-17 01:15:12 CEST 
Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Status: NEW => RESOLVED
Resolution: (none) => OLD
Note You need to log in before you can comment on or make changes to this bug.