https://bugs.kde.org/show_bug.cgi?id=366067
Sebastian Kügler <se...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |CONFIRMED
Keywords| |multiscreen
Ever confirmed|0 |1
--- Comment #5 from Sebastian Kügler <se...@kde.org> ---
Thanks for the bug report! I've had a look at the info you provided, here's my
analysis:
Facts:
- kscreen can write out a working configuration for your setup
- when logging in, kscreen fails to restore the working config
- a new configuration for your setup is written, your external screens are
disabled
- the modes aren't written because the displays are set to disabled
Fiction (my interpretation):
- when logging in, kscreen somehow fails to enable the two external displays
- it then writes out a new configuration with the two externals disabled,
overwriting the correct previous config file
- the correct config is now gone until you set the displays explicitly to
enabled again (crossing fingers that it works this time)
- everything is peachy, until it fails again...
A problem with debugging is is that we can't really see what's going on deep
down in xrandr. These calls are all made out of process, and it's quite hard to
get reliable information from it.
Questions:
- Could you try making the correct config file (in a working setup)
non-writable for your user, for example by chowning it (temporarily) to root?
In this case, do subsequent login attempts work?
- It would indeed be interesting to see if this is only a problem with your MST
setup, so if you could try displayport / hdmi as well, that would be useful
information.
--
You are receiving this mail because:
You are watching all bug changes.
