Bug 351442 - Primary output not persistent
Summary: Primary output not persistent
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-multiscreen (other bugs)
Version First Reported In: 5.3.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Aleix Pol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-18 13:29 UTC by naraesk
Modified: 2016-08-08 11:29 UTC (History)
4 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description naraesk 2015-08-18 13:29:46 UTC
Seems to happen only when an external monitor is connected.

Reproducible: Always

Steps to Reproduce:
1. Connect an external monitor to the notebook
2. close notebook
3. open notebook

Actual Results:  
The wallpaper and plasma widgets from the external monitor have switched. The widgets that were displayed on the external monitor are now shown on the laptop etc.
Comment 1 Adrian Piotrowicz 2016-02-04 07:28:29 UTC
Also there is a problem restoring primary output after plasma start. 
I have many different scenarios besides the expected one.
Using 3 monitors (1 laptop, 2 connected to docking station), expected setup is:
left: laptop
center: external monitor 1 (primary output)
right: external monitor 2
Scenario 1: I have all outputs placed over each other
Scenario 2: Outputs are placed correctly, primary output is laptop
Scenario 3: Outputs are placed correctly, primary output is ext1, widgets are on ext1, however panel after some dancing between laptop and ext1 ends up on laptop screen
OS : Chakra
kscreen/libkscreen version: 5.5.4
Comment 2 Sebastian Kügler 2016-08-08 11:29:12 UTC
Could you test this against git master (either via Neon dev/unstable or openSUSE tumbleweed with latest git master builds)?

We've fixed an issue that could lead to this behavior last week.

If the problem persists, please clean out ~/.local/share/kscreen/kscreen.log, reproduce this issue, and attach the log to this bugreport.

Thanks for your help sorting this out!