Bug 372511

Summary:	While using triple monitors, display settings lost on reboot.
Product:	[Plasma] KScreen	Reporter:	Matthew Schumacher <schu>
Component:	common	Assignee:	Sebastian Kügler <sebas>
Status:	RESOLVED WORKSFORME
Severity:	normal
Priority:	NOR
Version First Reported In:	5.8.3
Target Milestone:	---
Platform:	Slackware
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Current settings After logging out to console and startx again...

Description Matthew Schumacher 2016-11-15 18:07:23 UTC

I will try to be very verbose as this issue has persisted ever since I upgraded to KDE 5.

ISSUE:  When I login the monitor resolution is incorrect (I run a slightly lower res on my large monitor), and the order of the monitors is wrong.  I fix it, then on the next reboot everything is reset again, so every time I restart X windows I need to completely reconfigure my display settings.

Also, since the display settings are reset the task manager gets confused.  I normally only show tasks on the monitor that task appears on, using "show only tasks from current screen", but the task manager will show tasks on other screens unless I remove the task manager widget from the settings bar and add a new one.

OS: Slackware 14.2 with packages below.  This also happened on slackware 14.1 as well as earlier versions of kde 5.

PACKAGES:
I'm using these kde packages: http://alien.slackbook.org/ktown/ so you can see exactly how they are compiled here: http://alien.slackbook.org/ktown/source/5/kde/

HARDWARE CONFIG:
I have three monitors plugged into an AMD Radeon HD 7850, one on display port and two on DVI. 

TESTING:
I'm going to remove the display port monitor and do some testing with dual head and post back.  As I recall, that worked correctly.

Comment 1 Matthew Schumacher 2016-11-15 18:23:38 UTC

Okay, doesn't seem to matter, two or three monitors, every time I login my settings are lost.  Attached are screenshots of after setting things up and the next login.

Comment 2 Matthew Schumacher 2016-11-15 18:24:22 UTC

Created attachment 102248 [details]
Current settings

Comment 3 Matthew Schumacher 2016-11-15 18:24:49 UTC

Created attachment 102249 [details]
After logging out to console and startx again...

Comment 4 Matthew Schumacher 2016-11-15 18:26:12 UTC

Anything else I can provide (log files I'm missing, or things I can run in debug modes) then please let me know, I'll be happy to provide anything needed to look at this.

Comment 5 Justin Zobel 2022-10-27 02:49:02 UTC

Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Comment 6 Bug Janitor Service 2022-11-11 05:18: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 7 Bug Janitor Service 2022-11-26 05:16:34 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!