Bug 750760

Summary:	xserver console switching turns off the external display
Product:	Red Hat Enterprise Linux 7	Reporter:	Karel Srot <ksrot>
Component:	xorg-x11-server	Assignee:	Adam Jackson <ajax>
Status:	CLOSED WONTFIX	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	low	Docs Contact:
Priority:	low
Version:	7.0	CC:	jkoten, ksrot, ofourdan, ravi.prakash, tpelka
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-12-15 07:24:43 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	842499

Description Karel Srot 2011-11-02 10:24:03 UTC

Description of problem:

I am using external display attached to my notebook but the notebook lid is closed and display is configured for mirroring - therefore I am using my external display only.

When you
1. click on "username -> Switch user" in gnome panel
2. once login dialog appears press Ctrl+Alt+F1 to switch to primary console (there is a lockscreen dialog)
observe that the display turns off 

My colleague is using external display not mirrored and for him also the external display is turned off.

Version-Release number of selected component (if applicable):
xorg-x11-drv-intel-2.16.0-1.el6.x86_64
xorg-x11-server-common-1.10.4-4.el6.x86_64
xorg-x11-server-Xorg-1.10.4-4.el6.x86_64
xorg-x11-server-utils-7.5-5.2.el6.x86_64
I am running RHEL6.2 nightlies on my T500 ThinkPad

How reproducible:
always

Steps to Reproduce:
see above
  
Actual results:
display turns off

Comment 5 Jiri Koten 2012-04-12 17:26:24 UTC

Not fixed in xorg-x11-server-Xorg-1.10.6-1.el6.
External display turns off on VT switch. After I move mouse or type on keyboard, it turns on again.

Comment 25 RHEL Program Management 2020-12-15 07:24:43 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.