Bug 56339 - [sna ZaphodHeads] When unplugging displayport, windows on the second screen does not move to the first
Summary: [sna ZaphodHeads] When unplugging displayport, windows on the second screen d...
Status: RESOLVED NOTABUG
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: git
Hardware: Other All
: low normal
Assignee: Chris Wilson
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-24 00:02 UTC by Stephen Liang
Modified: 2013-07-15 08:10 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
xorg.conf (1.83 KB, text/plain)
2012-10-24 00:02 UTC, Stephen Liang 		no flags Details
View All

Description Stephen Liang 2012-10-24 00:02:19 UTC 
Created attachment 68978 [details]
xorg.conf

Situation (zaphodheads):

Full screen terminal on LVDS1
Full screen chromium browser on HDMI1

In regular randr mode (no xorg.conf), I can unplug the displayport adapter and chromium will shift from HDMI1 to LVDS1 and the workspace resolution shrinks. I plug in the displayport adapter again and the workspace expands and Chromium moves to HDMI1.

With xorg.conf and ZaphodHeads, I unplug the displayport adapter but Chromium remains on the HDMI1 area of the workspace and the workspace resolution does not shrink. Upon plugging the Displayport adapter back in, Chromium shows up in its usual spot on HDMI1.

This is using the latest git commit and applying the patch provided in Bug 55260 (attachment 68971 [details] [review]).

I feel like this is working as intended due to me not using RandR.
Comment 1 Chris Wilson 2012-10-24 08:03:24 UTC 
Right, since RandR is disabled with Xinerama, you have to manually reconfigure stuff (not even sure if that is technically possible). I think the request here is akin to https://bugs.freedesktop.org/show_bug.cgi?id=52438 which should give us the ability to reconstruct screens on the fly.
Comment 2 Chris Wilson 2013-07-15 08:10:42 UTC 
I've mulled this over for quite some time and have finally come to a conclusion: this is the responsibility of a window manager.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.