Bug 680785 - switching primary display doesn't persist on Gnome 3
Summary: switching primary display doesn't persist on Gnome 3
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11
Version: 15
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-27 18:46 UTC by patrick korsnick
Modified: 2018-04-11 19:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-21 05:27:01 UTC
Type: ---


Attachments (Terms of Use)

Description patrick korsnick 2011-02-27 18:46:08 UTC
Description of problem:

Using xrandr to switch the primary display from the laptop's panel to an external monitor moves the Gnome panel to the other monitor for a while, but then switches back all by itself some minutes later.  This behavior worked fine on f14.

here is the script i run to make the change:

#!/bin/bash

xrandr --output LVDS1 --off;
xrandr --output DVI1 --off;
xrandr --output DVI1 --auto --primary;
xrandr --output LVDS1 --auto --left-of DVI1;


Version-Release number of selected component (if applicable):

fedora 15 rc1

How reproducible:

every time

Steps to Reproduce:
1. log in
2. run above script
3. wait
  
Actual results:

primary display reverts back to the laptop panel

Expected results:

primary display should remain on the external monitor until changed

Additional info:

Comment 1 Matěj Cepl 2011-03-01 11:50:04 UTC
We will certainly need to know more about what's going on in your system.

Please add drm.debug=0x04 to the kernel command line, restart computer, reproduce the problem, and attach

* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log)
* output of the dmesg command (after the issue happens and before reboot), and
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 2 patrick korsnick 2011-06-21 05:27:01 UTC
have been running the released version of F15 for some time now and have yet to come across this bug. assuming it was fixed since RC1. closing.


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