Bug#490258: Failure in gdk when initializing randr12 with -vesa 2.0 driver
# not sure this is actually in rc2, but confirmed with rc5.
reassign 490258 xserver-xorg-core 2:1.4.99.902-1
kthxbye
On Thu, Jul 10, 2008 at 19:00:14 -0700, Bryce Harrington wrote:
> We're seeing this problem in Ubuntu after updating to -vesa 2.0.0 and
> xserver 1.4.99.905.
>
confirmed here with that combination (using the xrandr command-line
tool).
> Tracing back, the problem seems to be starting from inside
> XRRGetOutputInfo() when making the _XReply() call to the server. For
> whatever reason, the data structure it's getting back from the xserver
> is coming back without a crtc:
>
> _XReply (dpy, (xReply *) &rep, OutputInfoExtra >> 2, xFalse)
>
> rep.nCrtcs == 1
> rep.crtc == 0
>
> I'm not certain if 0 is a valid value for rep.crtc or not, but that
> seems to be what's causing the crashes. If it is a valid value, then
> gdk ought to be checking for it in init_randr12.
>
$ xrandr --verbose
Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
default connected (normal)
Identifier: 0x61
Timestamp: -1880288444
Subpixel: horizontal rgb
Clones:
CRTCs: 0
1024x768 (0x62) 0.0MHz
h: width 1024 start 0 end 0 total 1024 skew 0 clock 0.0KHz
v: height 768 start 0 end 0 total 768 clock 0.0Hz
$ xrandr --auto --verbose
crtc 0: 1024x768 0.0 +0+0 "default"
$ xrandr --verbose
Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
default connected 1024x768+0+0 (0x62) normal (normal) 0mm x 0mm
Identifier: 0x61
Timestamp: -1880288444
Subpixel: horizontal rgb
Clones:
CRTC: 0
CRTCs: 0
1024x768 (0x62) 0.0MHz *current
h: width 1024 start 0 end 0 total 1024 skew 0 clock 0.0KHz
v: height 768 start 0 end 0 total 768 clock 0.0Hz
It seems that things fix themselves after running xrandr --auto, for
some reason. Reassigning to the server, as that sounds like a bug in
the init code in hw/xfree86/modes/ (Xephyr works fine, and the vesa
driver doesn't know anything about randr).
Cheers,
Julien
Reply to: