Bug 29442 - xrandr does not ignore non-existent outputs
Summary: xrandr does not ignore non-existent outputs
Status: RESOLVED WORKSFORME
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: xf86-video-ati maintainers
QA Contact:
URL:
Whiteboard: 2011BRB_Reviewed
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-07 19:11 UTC by Peter D.
Modified: 2011-10-08 20:30 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Peter D. 2010-08-07 19:11:32 UTC
Using xrandr 1.3.2 and an X550 card.  (This might be an ati bug, rather that an xrandr bug.)  

My monitor is VGA-0.  DVI-0 is not connected.  

Cutting and pasting the example panning command from the xrandr man pages, should produce an error, and no change to the output, because it is directed to the non-existent output VGA (mine is VGA-0).  It actually produces an error, changes the screen (badly) and stops krandrtray from working.  

A second similar command to the real output of VGA-0 corrects the display, but that is when I noticed that krandrtray no longer changed modes.  

[root@test ~]# xrandr --fb 1600x768 --output VGA --mode 1024x768 --panning
1600x0
warning: output VGA not found; ignoring
xrandr: specified screen 1600x768 not large enough for output VGA-0
(1280x960+0+0)
[root@test ~]# xrandr --fb 1600x768 --output VGA-0 --mode 1024x768 --panning
1600x0
[root@test ~]#
Comment 1 Jeremy Huddleston Sequoia 2011-10-08 13:26:31 UTC
Is this still an issue?  Not sure why you're getting an 1600x0 mode, but sounds 
like a driver issue to me...
Comment 2 Peter D. 2011-10-08 17:31:57 UTC
I am not using that video card any more.  It would require considerable hardware shuffling to do so.  

I was just experimenting with the example commands given in "man xrandr" - and they did not work.  

(The 1600x0 was part of the example command given in the man pages.)
Comment 3 Jeremy Huddleston Sequoia 2011-10-08 18:07:38 UTC
Ok, well then we don't have much to go on to fix this.  Sorry for the slow response.
Comment 4 Peter D. 2011-10-08 20:30:27 UTC
All that I can recommend is finding a computer with an ATI card and typing the wrong output identifier.  i.e. VGA instead of VGA-0.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.