Red Hat Bugzilla – Bug 1294300
Dual monitor setup fails for second device (DVI-I-2) , that worked with a nvidia driver before
Last modified: 2016-12-20 12:24:08 EST
Description of problem:
Enabling the second dvi attached monitor in
the KDE or Gnome config/setting tools (section
display and monitor) identifies correctly both
1) ASUS PB278 (DVI-I-1 works)
2) Goldstar Company Ltd 22EA63 (DVI-I-2 try to get it working)
Then, i arranged the new monitor and expect, that
something happens. Well the X11 session expands the
screen virtually, but the monitor device tells me,
that there is no DVI signal.
Both devices are connected via DVI and the graphic
06:00.0 VGA compatible controller : NVIDIA Corporation G96 [GeForce 9500 GT] [10de:0640] (rev a1) (prog-if 00 [VGA controller])
has 2 DVI ports. Using Fedora F21 and Nvidia driver loaded
via RPMFusion i did not have any problem using both monitors.
There was no change with my cable, so it should work.
I also tried to address the LG monitor using a
Acer Aspire V3-771 notebook connected by HDMI
(also using a fresh Fedora F23 installation and
.. it worked. So i believe, it is a nouveau
Version-Release number of selected component (if applicable):
Simply go to the systemconfiguration tool (regardless gnome or kde)
and try to enable the dvi-i-2 connected second monitor. It will
Steps to Reproduce:
1. call system-setting in KDE or gnome and configure your second monitor.
2. tell your monitor (mine is a LG) to search for DVI input and you get "no signal".
3. hope that nvidia will be released ;-)
second monitor is a dark matter ;-)
an expanded screen
contact me, so i can send you additional information
see also: https://bugzilla.redhat.com/show_bug.cgi?id=692035
Gnome/Wayland behaves the same way, it shows
both displays correctly, but the monitor says
Screen 0: minimum 320 x 200, current 4480 x 1440, maximum 8192 x 8192
XWAYLAND0 connected 2560x1440+0+0 600mm x 340mm
XWAYLAND1 connected 1920x1080+2560+360 480mm x 270mm
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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'
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 23 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.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.