Ubuntu
xserver-xorg-video-nv package

Second monitor not listed

Bug #472993 reported by Roger Browne on 2009-11-03

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	xserver-xorg-video-nv (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

I have just installed Ubuntu 9.10 on this computer. In the hardware testing process only one of the two monitors is listed. Both monitors are working but showing identical information. When I ran the OS from the live CD only one monitor worked. I will get the Nvidia drivers and I believe this should fix the problem.

ProblemType: Bug
Architecture: amd64
CheckboxCommand: xrandr
CheckboxDescription:
The following screens and video modes have been detected on your system:

$output

Is this correct?
CheckboxTest: xrandr_detect_modes
Date: Wed Nov 4 03:53:09 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
Package: x11-xserver-utils 7.4+2ubuntu3
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=b020264e-eb73-431c-82b1-1f24f40ddc5b ro quiet splash
ProcEnviron:
SHELL=/bin/bash
LANG=en_AU.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
xserver-xorg 1:7.4+3ubuntu7
libgl1-mesa-glx 7.6.0-1ubuntu4
libdrm2 2.4.14-1ubuntu1
xserver-xorg-video-intel 2:2.9.0-1ubuntu2
xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1
SourcePackage: x11-xserver-utils
Tags: checkbox-bug
Uname: Linux 2.6.31-14-generic x86_64
XorgLogOld: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log.old'
XsessionErrors:
(gnome-settings-daemon:1957): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
(gnome-settings-daemon:1957): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
(polkit-gnome-authentication-agent-1:2023): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
(nautilus:2021): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
dmi.bios.date: 09/02/2007
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BX97510J.86A.1487.2007.0902.1724
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: D975XBX
dmi.board.vendor: Intel Corporation
dmi.board.version: AAD27094-306
dmi.chassis.type: 2
dmi.modalias: dmi:bvnIntelCorp.:bvrBX97510J.86A.1487.2007.0902.1724:bd09/02/2007:svn:pn:pvr:rvnIntelCorporation:rnD975XBX:rvrAAD27094-306:cvn:ct2:cvr:
fglrx: Not loaded
system:
distro: Ubuntu
architecture: x86_64kernel: 2.6.31-14-generic

Tags:

Revision history for this message

Roger Browne (ozrog) wrote on 2009-11-03:

BootDmesg.txt Edit (45.8 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (1.1 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (13.0 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (521 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (772 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.5 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (134.3 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (249.0 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (268 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (46.1 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (1.1 KiB, text/plain; charset="utf-8")
glxinfo.txt Edit (18.3 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (233 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (17.2 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (44.0 KiB, text/plain; charset="utf-8")

Philip Muškovac (yofel) on 2009-11-03

affects:

ubuntu → xserver-xorg-video-nv (Ubuntu)

Revision history for this message

Bryce Harrington (bryce) wrote on 2009-11-04:

Thank you for seeking to improve Ubuntu. It seems you have filed a bug
against X using the new System Testing utility. Unfortunately, this tool
is filing bugs without collecting sufficient information to properly
diagnose the issues. I wish we could reply to every report to guide you
to gather the correct information, but it happens that so many people
are using this testing feature to file bug reports that we simply cannot
keep up with the influx. I'm replying in bulk so I can get everyone
pointed into a direction most likely to result in getting you a useful
workaround and us a complete bug report that can be solved.

Most of these problems describe issues that have documented
troubleshooting procedures, so perhaps the most helpful thing I can
do is point you to them:

http://wiki.ubuntu.com/X/Troubleshooting

These guides explain why things break the way they do, and in some cases
provide workarounds.

I would ask that you first go through the appropriate guide for your
problem, particularly if you are having problems with resolution,
crashes, fonts, or blank screen issues, and then file a bug report using
the following command:

ubuntu-bug xorg

This collects more detailed information than the System Testing tool
does. Please also write a detailed explanation, indicating when you
first discovered the problem, analysis steps you've done, workarounds
that work, and so on.

Or, if you suspect the problem has something to do with the way the test
script itself is working (such as if Ubuntu worked fine until you ran
the script), then file the bug against the test suite:

ubuntu-bug checkbox

Thanks again, and good luck!

Changed in xserver-xorg-video-nv (Ubuntu):
status:	New → Invalid

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntuxserver-xorg-video-nv package