Red Hat Bugzilla – Bug 861960
Disabling primary display when secondary is enabled blanks both of them
Last modified: 2014-09-14 20:03:51 EDT
Description of problem:
Disabling primary display when secondary is enabled blanks both of them.
Version-Release number of selected component (if applicable):
04:00.0 VGA compatible controller: NVIDIA Corporation G98 [Quadro NVS 450] (rev a1)
Steps to Reproduce:
1. Boot machine.
2. Connect secondary monitor.
3. Enable secondary monitor and expand workspace to it.
4. Disable primary monitor.
I don't see how this violates any of the F18 release criteria. If I'm misunderstanding something, please list the F18 release criterion (alpha, beta or final; links at the bottom of this comment) which this bug violates or at least a justification of why this bug should block the release of F18.
-1 blocker unless I'm misunderstanding something here
ditto tflink, -1.
-1 blocker, related to dual head setup and seems to be specific to user's HW.
I count -5 blocker votes here, moving to rejected
Michal, are you able to reproduce it on latest Fedora 18 or 19 using Quadro NVS 450?
I couldn't reproduce this issue. I booted up, connected a secondary monitor (at this point the desktop extended itself automatically), went to Settings->Displays, disabled the first monitor and ended up with only the secondary monitor powered on, as expected. So the bug is fixed (unless I did something in a different way).
Could you test this also in KDE?
Just tested in KDE with the latest packages:
And there was no such issue when following the steps in Description.
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.
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 18's end of life.
Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 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 to Fedora 18's end of life.
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.
Seems to be fixed in F19 according to comment #11.