← Back to team overview

ubuntu-x-swat team mailing list archive

[Bug 531000] [NEW] Setting mode with xrandr fails after changing panning region

 

Public bug reported:

Binary package hint: x11-xserver-utils

The problem was observed on both Karmic and Lucid (current as at March
2, 2010) using both the open-source radeon driver and the proprietary
fglrx driver on different ATI cards (at least RV730 and RV740).

Steps to reproduce (with a 1900x1200 DFP monitor using the fglrx driver, output names are different with radeon):
- xrandr --output DFP1 --mode 1440x900
- xrandr --output DFP1 --panning 1920x1200
- pan around
- xrandr --output DFP1 --panning 1440x900
- xrandr --output DFP1 --mode 1920x1200

Expected result:
- DFP1 should switch mode to 1920x1200, adjusting the desktop size as appropriate

Actual result:
- mode does not change from 1440x900
- the terminal shows the following message: "xrandr: Configure crtc0 invalid time"
- the system remains usable but the mode cannot be changed using xrandr on DFP1

After restarting the Xserver, modes can be changed again.

One of our engineers found a workaround in xrandr. It allows the mode to
be changed but there are still other error messages:

--- bak/x11-xserver-utils-7.4+2ubuntu3/xrandr/xrandr.c  2009-04-01 11:01:55.000000000 -0400
+++ x11-xserver-utils-7.4-panningchg/xrandr/xrandr.c    2010-03-01 18:54:30.000000000 -0500
@@ -1346,7 +1346,10 @@ crtc_apply (crtc_t *crtc)
                              rr_outputs, crtc->noutput);
        if (s == RRSetConfigSuccess && crtc->panning_info) {
            if (has_1_3)
+           {
+               crtc->panning_info->timestamp = CurrentTime;
                s = XRRSetPanning (dpy, res, crtc->crtc.xid, crtc->panning_info);
+           }
            else
                fatal ("panning needs RandR 1.3\n");
        }

** Affects: x11-xserver-utils (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Setting mode with xrandr fails after changing panning region
https://bugs.launchpad.net/bugs/531000
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to x11-xserver-utils in ubuntu.



Follow ups

References