Bug 382374

Summary:	Second Screen Desktop config lost after turning off and on both DP-Displays
Product:	[Plasma] plasmashell	Reporter:	xtc <omedeto>
Component:	generic-multiscreen	Assignee:	Aleix Pol <aleixpol>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	aakandaurov, chgonzalezg, humufr, nate, nightelf7, omarelhajj97, plasma-bugs
Priority:	NOR
Version:	5.17.2
Target Milestone:	1.0
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description xtc 2017-07-15 10:25:55 UTC

Hi, 

when I turn off both of my display port screens. Now turning them back on (not at once), the 2nd screen is losing its desktop configuration and is going back to default.

After inspecting "config/plasma-org.kde.plasma.desktop-appletsrc"

I noticed that it was creating a new [Containment] ID and the "lastScreen" option changed.
After removing that [Containment] and using the new "lastScreen option" on the old [Containment] configuration the desktop could be restored with "kquitapp5 plasmashell && kstart plasmashell".

"lastScreen" is usually either 1 or 2. Main Screen stays 0. That means the system is detecting the 2nd screen sometimes as 1 and sometimes as 2.

I think Hardware detection of both screens is messed up and the IDs are changing 
depending on the "autodetect" situation.

After doing the manually restart of plasma shell the screen settings seem to change as well and I have to rearrange the monitor position or activating them again in the system settings when turning the monitors off and on again.

Using logout after applying the config fix doesn't lead to this monitor arrangement/settings loss in the system settings.

I am using the latest Mint 18.2 / Plasma 5.8.7 / Framework 5.36.0 / Qt 5.6.1
NVIDIA Drivers 381.22 / 1060 GPU / Kernel 4.10.0-26-generic.

Thx a lot.

Comment 1 Christian González 2018-04-12 12:14:06 UTC

Same here (now I'm in Kubuntu 18.04, Plasma 5.12.4, Frameworks 5.44.0, Qt 5.9.4, but I've seen this bug since at least Kubuntu 16.04). I often have to edit plasma-org.kde.plasma.desktop-appletsrc and change lastScreen=2 or lastScreen=3 to lastScreen=1.

A possible trigger for this bug is when I connect my laptop to an external projector and then come back to my LCD display.

Comment 2 humufr 2018-06-08 10:16:11 UTC

Multiple monitor is completely broken if we want to keep different configuration for desktop. 

It is extremely often that by changing the configuration of the desktop, having to separate screen or unified even on the same hardware, that the configuration is completely screwed:

- Principal display lost
- desktop layout back to default and not configurable anymore
- all plasmoid lost (extremely annoying if you have notes on it)

Only "solution" playing with the file: 

".config/plasma-org.kde.plasma.desktop-appletsrc"

which is clearly not a solution. 

Today I had an even funnier situation as usual: 

I used the Fn-F7 key on my laptop to modify the desktop configuration (I wanted to have a unified one for this morning) and that break every single activities even the one which were not started...

Comment 3 Christian González 2018-09-13 12:15:07 UTC

KDE Neon (based on Ubuntu 18.04) + Plasma 5.13.4 + Frameworks 5.50.0 + Qt 5.11.1. Intel Corporation HD Graphics 520. The problem is still present; only workaround is to mess with .config/plasma-org.kde.plasma.desktop-appletsrc.

Why is this bug still "unconfirmed"? What can we provide to you for aknowledge the problem? It's a very noticeable problem for all of us who use multiple displays.

Comment 4 omarelhajj97 2019-10-22 08:16:01 UTC

The bug is still present as of version 5.16.5, and it makes switching screen setups a nightmare. I hope that it will be looked at soon.

Comment 5 David 2019-11-08 07:43:57 UTC

The same happens with Kubuntu + backports and KDE 5.17.2.

Comment 6 Alexander Kandaurov 2020-05-21 13:24:10 UTC

When I disconnect both my monitors off and then reconnect them (first disconnect primary, then secondary, then reconnect in the same order), the ScreenConnectors section in my ~/.config/plasmashellrc file changes from this:

[ScreenConnectors]
0=HDMI-1
1=VGA-1

to this:

[ScreenConnectors]
0=HDMI-1
1=:0.0
2=VGA-1

So, basically what happens is that some generic screen with a name :0.0 appears and gets assigned an ID, then when the second monitor is reconnected back, its previous ID is already taken and thus becomes 2, and whatever desktop configuration that exists for screen 2 (none) is shown on it.

Comment 7 Nate Graham 2021-08-16 23:45:28 UTC


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

Comment 8 Nate Graham 2021-10-06 18:35:45 UTC


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

Comment 9 Nate Graham 2022-08-05 15:53:16 UTC


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