Bug 679624 - When connecting one additional monitor, two new monitors appear in the configuration tool
Summary: When connecting one additional monitor, two new monitors appear in the config...
Alias: None
Product: Fedora
Classification: Fedora
Component: control-center
Version: 20
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Control Center Maintainer
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2011-02-23 02:12 UTC by Remco
Modified: 2015-06-29 11:35 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-06-29 11:35:58 UTC
Type: ---

Attachments (Terms of Use)
Screenshot of display properties (73.60 KB, image/png)
2014-06-23 16:04 UTC, Remco
no flags Details
Xrandr output (1.85 KB, text/plain)
2014-06-23 16:06 UTC, Remco
no flags Details

Description Remco 2011-02-23 02:12:58 UTC
Description of problem:
When connecting one additional monitor, two new monitors appear in the configuration tool. One of them can be activated, the other not.

Version-Release number of selected component (if applicable):
Fedora 15 Nouveau Test Day image livecd

How reproducible:

Steps to Reproduce:
1. Start the Fedora 15 Nouveau Test Day livecd
2. Connect additional monitor
3. Start gnome-control-center display
Actual results:
Two new monitors appear

Expected results:
One new monitor appears

Additional info:
My hardware: http://www.smolts.org/client/show/pub_77e0b572-4581-4e99-913b-4ffd7337eaf9

Comment 1 Bastien Nocera 2011-02-23 17:20:09 UTC
What's the output of "xrandr -q" before and after plugging in the monitor?

Could you show a screenshot of the problem? Is the monitor that was already plugged in duplicated, or is a completely different one?

Comment 2 Fedora End Of Life 2013-04-03 14:13:32 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:

Comment 3 Remco 2014-06-23 16:04:18 UTC
Created attachment 911513 [details]
Screenshot of display properties

Comment 4 Remco 2014-06-23 16:06:02 UTC
Created attachment 911514 [details]
Xrandr output

First time: external monitor disconnected
Second time: external monitor connected and activated

Comment 5 Fedora End Of Life 2015-05-29 08:38:37 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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 2015-06-29 11:35:58 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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

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.