Bug 365346

Summary:	Screen configuration never restored on startup
Product:	[Plasma] plasmashell	Reporter:	Heiko Tietze <tietze.heiko>
Component:	generic-multiscreen	Assignee:	Aleix Pol <aleixpol>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	bugs.kde.org, kde, mgraesslin, plasma-bugs
Priority:	NOR
Version:	5.7.0
Target Milestone:	1.0
Platform:	Other
OS:	Other
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Heiko Tietze 2016-07-11 08:34:31 UTC

With the latest update to 5.7 I have to reconfigure my screens after every start. It's a laptop (MSI GE40 2OC) right of a full hd screen (ASUS VX238H) connected via HDMI. Both have panels on top and bottom. Before 5.7 I had issues when the lid is closed and the system was shutdown. Now it always happens that all panels are overlaid on the Full HD screen, which I set-up as primary. I have placed some widgets on the secondary screen and use different wallpapers. It's not easy to get back to this arrangement, switching primary/secondary on/off, closing the lid, and doing this back and forth ends up eventually in what I defined, but not always. There is no error message.
I tried to disable KScreen but with no success: same problems (didn't do much investigations though).

Reproducible: Always

Comment 1 Heiko Tietze 2016-07-17 09:27:33 UTC

Same issue when running LXQt
https://github.com/lxde/lxqt/issues/1096#issuecomment-233173103

Comment 2 Piotr Dobrogost 2016-07-17 13:12:43 UTC

Probably should be marked as duplicate of bug #356225

Comment 3 David Edmundson 2016-07-17 14:01:34 UTC


*** This bug has been marked as a duplicate of bug 356225 ***

Comment 4 Peter Mattern 2016-07-18 12:19:34 UTC

Cannot see how this should be a duplicate of bug 356225.
bug 356225 is about positioning of the panel, this one about restoring screen resolutions. bug 356225 got manifest in KDE 5.4, this one was introduced by KScreen 5.7.0. Our findings on LXQt suggest it's just the backend connecting to KScreen which needs to be adjusted to the library's new version.

Comment 5 Piotr Dobrogost 2016-07-18 21:03:32 UTC

(In reply to Peter Mattern from comment #4)
> Cannot see how this should be a duplicate of bug 356225.
> bug 356225 is about positioning of the panel, this one about restoring
> screen resolutions. 

Are you sure? OP here does not even mention any problems with resolution. However he complains on arrangement of _panels_ – "Now it always happens that all panels are overlaid on the Full HD screen, which I set-up as primary." In addition if you read comments on bug 356225 people complain on many different things not being restored, not only panels. That bug should really be renamed as it's not only about panels.

> bug 356225 got manifest in KDE 5.4, this one was introduced by KScreen 5.7.0.

OP writes "With the latest update to 5.7 I have to reconfigure my screens after every start." indeed but that's what many people (including me) had been doing for a long time now. I guess there must have been some other change in addition to update to Plasma 5.7 which triggered behavior described by OP but witnessed by many people much earlier.

Comment 6 Peter Mattern 2016-07-20 19:08:03 UTC

Could very well be you're right, yes.
Writing my previous comment I had looked at "Same issue when running LXQt" in comment 1 only and indeed that LXQt issue was affecting the resolution only (and could be fixed by adjusting the backend accessing KScreen). Also, looking at Plasma 5.7.2 on Arch Linux screen resolutions seem to get restored as expected on single and multi monitor systems while the panel is indeed pretty much misbehaving as depicted in bug 356225.
Maybe the OP will drop another note.

Comment 7 Heiko Tietze 2016-07-20 21:36:51 UTC

(In reply to Peter Mattern from comment #6)
> Maybe the OP will drop another note.

Neither arrangement nor resolution was restored well. Plasma adds the trouble with panels, while LXQt is even worse with background not fitting the original setup. Meanwhile I found a workaround, namely to configure the montor file in /etc/X11/xorg.onf/ properly. There are too many issues to track it down, IMHO. There are enough other bugs open.