When using dual DVI-screens, both display adapters register as DVI1 as well as DVI0.

[Ghost]

Binary package hint: kdebase-workspace

Running a dual screen setup with an ATI card. This was fine until I upgraded the card. DVI1 and DVI0 are now seen on both adapters of my graphics card. Meaning that both screens insist that they're DVI1 and 0 at the same time - yet when I disable one a screen goes blank. Both adapters are also seen as connected even if I pull one out and restart the system that way. Am trying to run a dual-screen setup, but instead ending up with the same image duplicated across both monitors and the system telling me that I'm only running one physical monitor, but it's putting both (identical) displays on it. Most likely over the top of each other.

Further info: Recently upgraded my graphics card from an X1900XTX, to a 4850 (both ATI) - and now get told I have an *unknown display type* on starting Kubuntu. Suspect this is related to the problem, though simply loading the *default* allows the displays to run - but with the problem as stated.

Currently running Kubuntu 9.10, but problem has existed (for me) since 8.04.

ProblemType: Bug
Architecture: amd64
Date: Fri Jan 15 15:56:45 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/systemsettings
Package: systemsettings 4:4.3.2-0ubuntu7.1
ProcEnviron:
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
SourcePackage: kdebase-workspace
Uname: Linux 2.6.31-17-generic x86_64
XsessionErrors: (polkit-gnome-authentication-agent-1:3537): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

[Bryce Harrington (bryce)]

Hi wraith-994,

Thanks for including the attached files. Could you also include your /var/log/Xorg.0.log (or Xorg.0.log.old) from after reproducing the issue?

Please attach the output of `lspci -vvnn` too.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.