Bug 409286 - Crash when switching to one display + not switching to the right display
Summary: Crash when switching to one display + not switching to the right display
Status: RESOLVED DUPLICATE of bug 408768
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-multiscreen (show other bugs)
Version: 5.16.2
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Aleix Pol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-28 18:29 UTC by techxgames
Modified: 2019-07-16 12:34 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
kcrash log after switching dislay (34.79 KB, text/plain)
2019-06-28 18:29 UTC, techxgames 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description techxgames 2019-06-28 18:29:41 UTC 
Created attachment 121209 [details]
kcrash log after switching dislay

SUMMARY
I was in multi-monitor setup, but when I had to switch to single display, it switched to my secondary monitor (DVI) instead of my primary monitor (DisplayPort) when I selected "Switch to laptop screen".  I also got a notification that Plasma crash, which probably happened when I immediately switched to my main monitor by selecting "switch to external monitor".

STEPS TO REPRODUCE
1. Open the display switcher (Meta+P)
2. Select "Switch to laptop screen"

OBSERVED RESULT
Display switches to the secondary monitor connected to DVI instead of primary connected via DisplayPort.

EXPECTED RESULT
Switch to the primary monitor connected via DisplayPort

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 19.04
KDE Plasma Version: 5.16.2
KDE Frameworks Version: 5.59.0
Qt Version: 5.12.2
Kernel Version: 5.0.0-19-generic
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz
Memory: 15.6 GiB of RAM
GPU: ZOTAC GeForce GTX 1060 6GB

ADDITIONAL INFORMATION
Comment 1 techxgames 2019-06-28 20:29:12 UTC 
After switching back to multi-monitor mode, the configuration of the second monitor is gone.
Comment 2 Christoph Feck 2019-07-16 12:34:30 UTC 

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