Bug 784212

Summary:	Disadvantageous LoginScreen on DualMonitor
Product:	[Fedora] Fedora	Reporter:	Rolle <rolle.hoffmann>
Component:	gdm	Assignee:	Ray Strode [halfline] <rstrode>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16	CC:	jmorris, rstrode
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-13 22:00:27 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Rolle 2012-01-24 09:49:07 UTC

Description of problem:
I have 2 monitors. It is annoying when the login-dialog is only on 1 screen available. The login-dialog of gdm of gnome 2.32 had the ability to jump to that screen where the mouse is. This was a good feature, because the time to wakeup the monitor from sleepmode is on some monitors very long.
Also it is a very nice feature when I assemble new computers (I'm a computer engineer) and it is unclear, which monitor port is which signal (sometimes the monitor remains black because it is a displayport, hdmi or so on) and the login-dialog appears on a faulty port or faulty frequencies for the monitor or the monitor hasn't scanned the right input port.
So a it is a very annoying try and error to get a picture and the login-dialog.

Version-Release number of selected component (if applicable):
Fedora 16, GDM Gnome 3.2

How reproducible:
Every time

Steps to Reproduce:
1. connect 2 monitors
2. boot Fedora 16 with GDM of Gnome 3.2
3.
  
Actual results:
the login-dialog appear only on the "main" screen (whatever the mainscreen is?).

Expected results:
The login-dialog should appear an every active screen. For instance like in gnome 2.32 with jump to that screen, where the mousepointer is or a clone-mode for every screen.

Additional info:
This is not a bug. It's a design decision.

Comment 1 John Morris 2012-11-01 20:48:21 UTC

This is known to have worked in Fedora 16, doesn't work now in 17-current so it is a post Gnome 3 regression.  This one kills me on a laptop & dock scenario which is a lot more common than a problem with birthing & servicing computers where you don't know which port is which and/or which ports work.

Use case is a Thinkpad with a dock and an external display.  Boot or wake up on the dock with the lid closed, or even logout while docked and there isn't a login visible unless you open up the lid.

Comment 2 Fedora End Of Life 2013-01-16 17:23:48 UTC

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 WONTFIX if it remains open with a Fedora 
'version' of '16'.

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 prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Fedora End Of Life 2013-02-13 22:00:33 UTC

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.

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