xrandr (and displayconfig-gtk) deeply confused about analog monitor connected to dvi port via adapter

Bug #223284 reported by konny
4
Affects Status Importance Assigned to Milestone
displayconfig-gtk
Won't Fix
Undecided
Unassigned
libxrandr (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: libxrandr2

This bug likely concerns the xrandr extension as well as displayconfig-gtk.

I have an analog monitor connected over an adapter to the DVI port of my notebook. xrandr seems to be confused by this configuration.

Screen 0: minimum 320 x 200, current 2560 x 1024, maximum 2560 x 1024
VGA-0 connected (normal left inverted right x axis y axis)
   1280x800 59.8 60.0
   1280x768 60.0
   1024x768 60.0
   800x600 60.3
   640x480 59.9
LVDS connected 1280x800+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1280x800 60.2*+ 60.0
   1280x768 60.0
   1024x768 60.0
   800x600 60.3
   640x480 59.9
S-video disconnected (normal left inverted right x axis y axis)
DVI-0 connected 1280x1024+1280+0 (normal left inverted right x axis y axis) 359mm x 287mm
   1280x1024 60.0 + 74.9* 75.0 59.9
   1024x768 74.9 75.1 69.8 70.1 60.0 59.9
   832x624 74.6
   800x600 72.2 75.0 74.9 69.7 60.3 59.9 56.2
   640x480 75.0 72.8 66.7 60.0
   720x400 70.1

I have only one external port, but both VGA and DVI are connected according to xrandr. Actually it is the same physical port as it seems.
According to xrandr, DVI-0 output is active while the monitor itself stays in stand-by mode. VGA-0 (the actual correct output) is inactive, and furthermore the modes reported there are actually LVDS modes. None of them takes a CRTC, only LVDS uses CRTC 0.

I have failed to create a xorg.conf which reflects this configuration. bash commands bringing my second monitor to live are

#!/bin/bash
xrandr --output DVI-0 --off
xrandr --output VGA-0 --crtc 1 --mode 1280x1024_60.00 --right-of LVDS

Please note that I add the appriopriate modelines via xorg.conf.

I cannot turn off neither VGA-0 nor DVI-0 in xorg.conf without crashing the xserver (making it start in bulletproof mode). I have to enable both and I cannot put any of them on ignore, too. Basically X has to start up with both outputs enabled, directing output to dvi as it seems.

displayconfig-gtk seems to do the same. It reports the monitor being active while it is in stand-by. It does not allow for specifying vga or dvi output which would be really helpful in such a situation.

System: ATI Radeon Mobility X700 with radeon driver (xserver-xorg-video-ati 1:6.8.0-1)

Revision history for this message
Bryce Harrington (bryce) wrote :

We're no longer using displayconfig-gtk for monitor setup. Closing this bug task.

Changed in displayconfig-gtk:
status: New → Won't Fix
Revision history for this message
Bryce Harrington (bryce) wrote :

Please attach your /var/log/Xorg.0.log. The libxrandr task portion of this bug sounds interesting and should go upstream, but let's see the log first to see if it explains why it's doing this.

Changed in libxrandr:
status: New → Incomplete
Revision history for this message
konny (s-launchpad-gadzicki-de) wrote :

Here you are.

Revision history for this message
Duane Hinnen (duanedesign) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Bryce Harrington (bryce)
Changed in libxrandr (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Bryce Harrington (bryce) wrote :

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.

Changed in libxrandr (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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