configuration: notebook HP compaq nc6000 (1400x1050) + external 19" LCD HP 1902 (1280x1024) ATI Technologies Inc RV350 [Mobility Radeon 9600 M10] Linux sarim 2.6.15-21-686 #1 SMP PREEMPT Fri Apr 21 16:57:03 UTC 2006 i686 GNU/Linux => up-to-date Dapper Drake preview
xserver-xorg 7.0.0-0ubuntu2 resapplet 0.0.7+cvs2005 xserver-xorg-driver-ati 6.5.7.3-0ubuntu5 xrandr 1.0.1-0ubuntu1 xorg set-up using MergedFB with two available modes: 2680x1050 for "dualhead" and 1400x1050 for "clone/no external LCD" mode. xrandr is able to switch between the modes but Screen resolution tool cannot and crashes instead. The same crash occurs when trying to do the same using resapplet from Universe. xrandr reports invalid refresh rates (see output below) and the graphical utilities cannot handle it properly even xrandr can. I'll also file a bug on xrandr package too and post its number here. Someone reported a bug in xrandr that could possibly have the same cause - see bug #33339... sarim:~$ xrandr SZ: Pixels Physical Refresh 0 2680 x 1050 ( 681mm x 267mm ) 6895 *1 1400 x 1050 ( 681mm x 267mm ) *-19554 Current rotation - normal Current reflection - none Rotations possible - normal Reflections possible - none If I run the Screen resolution tool from commandline and try to switch the modes it crashes and I get an error like this: sarim:~$ gnome-display-properties The program 'gnome-display-properties' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 13128 error_code 2 request_code 157 minor_code 2) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) sarim:~$ gnome-display-properties --sync The program 'gnome-display-properties' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 31625 error_code 2 request_code 157 minor_code 2) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) -- Screen Resolution tool fails to switch between MergedFB "dualhead" and "clone" modes https://launchpad.net/bugs/41610 -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
