© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Thanks.
I've been debugging this further today. The problem seems to be originating from GDK's init_randr12() routine. It makes a XRRGetOutputInfo() against libXrandr and the xserver, and receives back a (output->crtc = 0) value that then leads into the problems mentioned above.
So, in other words, on the client side it's calling the server to retrieve output info, and it's getting a structure back that doesn't have a crtc attached to it. Odd.
Anyway, best guess is that it's a bug introduced either with -vesa 2.0.0 or xserver 1.5 (or perhaps both), possibly gdk deserves a bug too since it's not properly checking this failure condition. I've filed this upstream with debian.