Hi, I don't know wheather this is a driver, xserver or xrandr bug. System configuration is: xorg-server-1.3, xf86-video-ati-6.7.19{2,3,4,5,} and latest svn, xrandr 1.2.2 I've observed the following reproducable problem on my T41p: 1. enable VGA-0 or DVI-0 with 1280x1024 resolution and disable LVDS 2. start vmplayer with a linux client that has vmware tools installed 3. suspend linux client in vmplayer 4. disable VGA-0 or DVI-0 5. enable LVDS 6. start suspended linux client in vmware 7. xserver crashes with the following output. * Backtrace: * 0: /usr/bin/X(xf86SigHandler+0x84) [0x80d2f24] * 1: [0xb7fa4420] * 2: /usr/bin/X(VidModeGetNumOfModes+0x40) [0x80cdf90] * 3: /usr/lib/xorg/modules/extensions//libextmod.so [0xb7c6b4ba] * 4: /usr/bin/X [0x814b28e] * 5: /usr/bin/X(Dispatch+0x1ab) [0x80874eb] * 6: /usr/bin/X(main+0x488) [0x806f2b8] * 7: /lib/libc.so.6(__libc_start_main+0xd8) [0xb7d27838] * 8: /usr/bin/X(FontFileCompleteXLFD+0xa5) [0x806e5e1] * * Fatal server error: * Caught signal 11. Server aborting Accidentally I discovered that running xrandr without arguments after step 5 prevents the xserver from crashing. After adding some printf's I discovered that calling XRRGetScreenSizeRange() from libXrandr that is called in get_screen() does the job. The attached patch is a workaround for the specified problem. Regards, Ruben
Created attachment 12112 [details] [review] xrandr-1.2.2-update-screen-size.patch patch that forces xrandr to call XRRGetScreenSizeRange() from libXrandr after switching outputs.
The server is crashing, so it's a server bug. No client should cause the server to crash no matter how misbehaving it is. Does this still happen with recent servers/drivers? If so, can you please attach a recent backtrace.
Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please file a new report if you continue to experience issues with a current server.
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.