XRandR cannot set "scaling mode"

Bug #1173492 reported by Cecil Pierce
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
x11-xserver-utils (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

X11-xserver-utils 7.6+3 Precise

When entered from a terminal the command
 >xrandr --output DFP2 --set "scaling mode" "Full aspect"

Gives the following error:

X Error of failed request: BadName (named color or font does not exist)
  Major opcode of failed request: 157 (RANDR)
  Minor opcode of failed request: 11 (RRQueryOutputProperty)
  Serial number of failed request: 35
  Current serial number in output stream: 35

I use the ATI Proprietary FGLRX driver, does XRandR not use "scaling mode" with this driver?

I am attempting to change the behaviour of the display when I attempt to change screen resolutions in KDE, my monitor (Acer H233H) appears 'stuck' in 1920x1080. When I attempt to switch to a lower resolution, ie, 1280x720 (which is listed as a valid mode), the monitor does not actually change mode, the displayed screen shrinks, with large black bars on all 4 sides. the displayed part of the screen is 1280x720, but, I expected the screen to fill the monitor, not a section of it.

Thank you!

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in x11-xserver-utils (Ubuntu):
status: New → Confirmed
Revision history for this message
Dave Long (dystrust) wrote :

Seeing identical behavior running Xubuntu 12.10 & 13.04 on an IBM Thinkpad T60. Scaling mode quit working when updating to kernel 3.5.0-27 on 12.10 and continues to not work on 13.04. Default resolution for this panel is 1024x768; switching to either 800x600 or 640x480 results in a window of that size at the top-left of the screen with black borders below and to the right. Confirmed that booting with the 3.5.0-26 kernel in 12.10 resolved the issue and scaling resumed working.

Revision history for this message
Dave Long (dystrust) wrote :

Commands & results:
$ xrandr --output LVDS1 --set "scaling mode" "Full aspect"
Appears to have no affect.

$ xrandr --output LVDS1 --set PANEL_FITTING full_aspect
X Error of failed request: BadName (named color or font does not exist)
  Major opcode of failed request: 140 (RANDR)
  Minor opcode of failed request: 11 (RRQueryOutputProperty)
  Serial number of failed request: 31
  Current serial number in output stream: 31

Revision history for this message
Cecil Pierce (silverwolf) wrote :

Hmm... I just checked my kernel version, I am running 3.2.0-38-Generic (from package linux-image-3.2.0-38-generic_3.2.0-38.61_amd64.deb).

Dave, what was the last kernel you used where it worked properly?

Also, your behaviour is slightly different from mine, your screen is top-left, but mine is centered both left-right and up-down.

Revision history for this message
Cecil Pierce (silverwolf) wrote :

Oops, sorry I missed that you have it working correctly with 3.5.0-26. But that is still newer than my running kernel...

Will install 3.5.0-26 and see if that helps...

Revision history for this message
Dave Long (dystrust) wrote :

I'm using Intel integrated graphics instead of ATI/AMD, and I'm also on a 32-bit kernel instead of AMD64. I'm not sure if this points to separate driver issues, or an issue with X. I've also noticed that the issue seems to affect only the Thinkpad LCD (LVDS1), a monitor connected to VGA1 scales properly.

Revision history for this message
Cecil Pierce (silverwolf) wrote :

Still have the problem with the 3.5.0-26 Generic kernel (x64)...

I haven't tried changing the connection type yet, I normally use DVI, but my monitor can also use VGA, will try later and will post in a day or 2.

Revision history for this message
Dave Long (dystrust) wrote :

In my case the root cause of this issue was corrupted firmware rather than problems with XRandR (X11-xserver-utils). The machine in question had been running lm sensors 3.3.2 which was discovered to potentially cause firmware corruption in Sept 2013.

The issue was immediately resolved following a re-flash of the BIOS on the T60 in question.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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