Bug 413329

Summary:	dual monitor configuration break secondary extended monitor
Product:	[Plasma] KScreen	Reporter:	lesto <lestofante88>
Component:	common	Assignee:	kscreen-bugs-null <kscreen-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	nate
Priority:	NOR
Version First Reported In:	5.17.1
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description lesto 2019-10-22 18:51:51 UTC

SUMMARY
since update to 5.17.0 my dual monitor setup reset. Normally it look like -| (main monitor horizontal on the left, secondary vertical on the right, The horizontal is in the middle of the vertical.)

It reset to a configuration with the monitor in a _| configuration. if I try to slide the scondary monitor down, as original, and apply the conf, the secondary monitor goes black (maouse pointer is still visible), and the screen configuration windows goes in that screen (i can still drag it back by right click on the Task Manager and selecting "move"), and also the conf displayed goes back to _|.

As workaround i found it works if i leave some space between the two monitor instead of letting them snap together.

Comment 1 lesto 2019-10-22 18:52:24 UTC

part of 3 bug report: 413326 413328 413329

Comment 2 lesto 2019-10-24 17:53:37 UTC

fixed by deleting the kscreen folder under ~/.local/share; looks like even if I enable/disable the monitors and change the conf, something broken get carried over.

I think proper fix should be to find the problematic configuration and get rid of it at load time

Comment 3 lesto 2019-11-03 21:45:35 UTC

Not really fixed; looks like sometimes (every reboot? every minor update?) it breaks again.

Comment 4 Justin Zobel 2022-09-27 08:23:49 UTC

Thank you for reporting this crash 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 crash with a recent software version?

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

Comment 5 Bug Janitor Service 2022-10-12 04:55:15 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 6 Bug Janitor Service 2022-10-27 05:05: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!