Bug 358353 - kscreen ignores primary screen
Summary: kscreen ignores primary screen
Status: RESOLVED DUPLICATE of bug 356727
Alias: None
Product: KScreen
Classification: Plasma
Component: common (show other bugs)
Version: 5.5.3
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Daniel Vrátil
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-22 08:29 UTC by Martin van Es
Modified: 2016-04-18 04:50 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin van Es 2016-01-22 08:29:39 UTC
Since upgrade to plasma 5.5.3 kscreen allways places my panel on external monitor, even though I configure it to be above laptop panel and make laptop panel primary. After disconnecting external monitor, panel does not return to laptop leaving me with a broken system which can only be reparied by "find .config '*plasma*' -delete"

Reproducible: Always

Steps to Reproduce:
1. Connect external monitor
2. Open Display Configuration and place monitor above laptop screen and mark (or keep) laptop primary
3. Watch panel go to external monitor
4. Disconnect monitor
5. Panel disappears

Actual Results:  
Panel is lost

Expected Results:  
Panel stays on Laptop screen, and stays there after external monitor disconnect

The same happens if I configure external screen using xrandr, so I suspect it not to be the config tools fault. It seems plasma doesn't respect "primary" anymore.
Comment 1 Martin van Es 2016-01-22 08:44:45 UTC
Some more testing reveals kscreen DOES think HDMI1 is primary after connection and setting eDP1 primary using xrandr makes the panel go down again, but I do have to restart plasmashell for that to happen. Unitl the restart, the laptop panel is black.
Comment 2 Martin van Es 2016-01-25 07:49:04 UTC
I seems I can reliably work-around the  problem by restarting plasmashell after connecting the external monitor.
Comment 3 Adrian Piotrowicz 2016-02-04 07:54:20 UTC
I am also affected by this bug.
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


And after manually setting up correct configuration I need to restart plasmashell to get app launcher show up on correct screen - it often shows on left screen not center when panel is.

Removing laptop from dock, assuming that kscreen detects that action, messes up all configuration - plasmashell needs to be restarted again.
Placing laptop back again on dock - messed up configuration - it's easier to reboot and setup everything again from scratch.

Same happens with single monitor attached directly to laptop via HDMI.
Expected setup is:
left: laptop (primary)
right: external monitor
I don't have problems with primary output then because I want it to be laptop - so no work for kscreen/kde here and nothing to mess up. However kscreen does not detect disconnecting external monitor.

OS: Chakra
kscreen/libkscreen version: 5.5.4
plasma-framework: 5.18.0
Comment 4 Herb Miller 2016-02-22 04:42:40 UTC
I've been having this problem as well (for about three months now). I have a DVI display at 1920,0 set to primary and an HDMI display at 0,0 not set to primary (so secondary display left of primary), yet when I enable the HDMI display my panel jumps to the HDMI screen. When I disable it, instead of moving back to my DVI display it just disappears, leaving me stranded.

Sometimes I can right click and create a new panel. Sometimes I can't. Right now my Logout screen is stuck on my HDMI monitor even though I most definitely have DVI set as primary.

It's all very random and undefined.

OS: Gentoo
libkscreen version: 5.5.4
Comment 5 markuss 2016-02-29 20:48:34 UTC

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