Bug 1286771 - Primary display setting being ignored
Summary: Primary display setting being ignored
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kwin
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Daniel Vrátil
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-30 16:58 UTC by Dan Mossor [danofsatx]
Modified: 2016-12-20 16:26 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-20 16:26:17 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Requested log from from enable display (14.66 KB, text/plain)
2015-12-03 18:34 UTC, Dan Mossor [danofsatx]
no flags Details
Requested log from disable display (15.17 KB, text/plain)
2015-12-03 18:35 UTC, Dan Mossor [danofsatx]
no flags Details

Description Dan Mossor [danofsatx] 2015-11-30 16:58:48 UTC
When connecting an external display to a laptop equipped with nvidia GTX660M GPU, the "Primary Display" setting within the Display Configuration is being ignored. 

I move my laptop between home and office, where I have a different external display at each location, but the system is not always connected to the external displays. I leave the displays disabled in System Settings when I disconnect them to avoid the associated crash in plasmashell.

I have the "Primary Display" set to the Laptop Display in all cases, but when an external display is attached and then enabled, all open windows move to the external display. If I take the time to move the windows back to the laptop where I want them, they are then moved off-screen when the external display is disabled or removed, apparently moved as an offset of the total screen area.

When I connect the external display with the laptop display designated as the primary, absolutely nothing should happen other than the placement of the panel and the wallpaper - no windows should move. When an external display is removed or disabled, the only windows that should move are the ones that were on the now non-existent external display, no windows on the primary laptop display should move.

kscreen-5.4.3-1.fc23.x86_64
plasma-workspace-5.4.3-3.fc23.x86_64
xorg-x11-drv-nouveau-1.0.12-0.3.fc23.x86_64

Comment 1 Daniel Vrátil 2015-12-02 23:16:29 UTC
Window placement is managed by KWin, not by KScreen. I would assume that KWin remembers where the windows were originally opened and tends to move then back to the original screen once it's available. In any case, I'd recommend bringing this issue up with kwin upstream.

Windows however should never been moved off-screen. Could you please reproduce this (i.e. disconnecting the external display), running 

QT_LOGGING_RULES="* = true" kscreen-console bug

and attaching the output here? If the display is not correctly turned off, then it's a KScreen bug, otherwise it's an issue in KWin again.

I would also recommend trying with 5.4.90 or .95 (beta for upcoming 5.5 release, available in @kdesig/plasma-5-unstable Copr), there were plethoras of bugfixes in kwin in 5.5, maybe your issue was fixed as well.

Comment 2 Dan Mossor [danofsatx] 2015-12-03 18:34:19 UTC
Created attachment 1101895 [details]
Requested log from from enable display

This log is from a konsole session where plasmashell had been started manually. This is the snippet from the time I entered the QT_LOGGING_RULES to when the external display was active and all the windows moved to it.

Comment 3 Dan Mossor [danofsatx] 2015-12-03 18:35:42 UTC
Created attachment 1101896 [details]
Requested log from disable display

This log is from a konsole session where plasmashell had been started manually and contains the plasmashell stdout. This is the portion of the output from when I disabled the external display and all the windows moved back to the laptop.

Comment 4 Dan Mossor [danofsatx] 2015-12-08 15:46:29 UTC
An interesting development cropped up today. This only happens when the displays are positioned vertically - not horizontally. In other words, when the Laptop display is centered under the external display, all of the windows move to the external display. When I position them side by side, it works as intended.

Comment 5 Fedora End Of Life 2016-11-24 13:50:48 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2016-12-20 16:26:17 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.