Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 599028 - x11-misc/sddm-0.14.0 expects EDID to be perfect for proper function
Summary: x11-misc/sddm-0.14.0 expects EDID to be perfect for proper function
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: LxQt maintainers
URL: https://github.com/sddm/sddm/issues/692
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-06 00:58 UTC by Andreas Steinmetz
Modified: 2017-10-21 20:05 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Steinmetz 2016-11-06 00:58:09 UTC
Situation in short:

White screen instead of expected greeter (screen color depends on selected theme, white for elarun), no errors in any logs, sddm and greeter running. One can actually login by typing blindly and KDE then appears as expected.

Actual problem:

Turns out the EDID data for the physical screen dimension shown with "xrandr -q" is wrong, e.g. 4mm x 3mm in my case and the sddm greeter takes this value to calculate its view, resulting in a 15x9 pixel view instead of the proper screen resolution.

Workaround:

One has to create an EDID file and load it into the kernel, overriding the display EDID data, to convince the sddm greeter to create a proper view as there is no other way (radeon) to override the physical display dimension used by the greeter. Setting the "DisplaySize" option for the "Monitor" section of xorg.conf doesn't help.

Required solution:

sddm should not rely on EDID physical display dimensions to be valid and calculate the view size based EDID dimensions or, alternately, needs some kind of override in sddm.conf.

Notes:

The physical dimensions got probably messed up by an "ADDERlink iPEPS" in my case. This device is OTOH essential for remote management and thus must stay in the hardware path of the affected system.

Creating an EDID file is not exactly trivial and thus no workaround for the majority of users.
Comment 1 Manuel Rüger gentoo-dev 2016-11-19 17:22:32 UTC
This sounds like something you should request upstream https://github.com/sddm/sddm Thanks!