Resapplet fails to switch between MergedFB "dualhead" and "clone" modes

Resapllet shows incorrect refresh rates and crashes when trying to switch mode - xrandr tool works fine.

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

xorg set-up using MergedFB with two available modes: 2680x1050 for "dualhead" and 1400x1050 for "clone/no external LCD" mode:

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

the following commands work as expected:
sarim:~$ xrandr -s 1400x1050 (even move the windows from external LCD back to internal one - coool ;-)
sarim:~$ xrandr -s 2680x1050 (the gnome-panel is shown only on the internal LCD and the screen on external LCD doesn't scroll up/down at all - coool ;-)

when using resapllet I get two available modes in menu:
2680x1050@6895Hz
1400x1050@-19554Hz

strange, the same values are in System/Preferences/Screen Resolution - the bug is related to this tool too...?

and switching the mode causes resapllet to crash:

sarim:~$ resapplet
The program 'resapplet' 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 1691 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:~$ resapplet --sync
The program 'resapplet' 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 3890 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.)

and when I use the Screen Resolution tool from System menu it allows me to apply the change but nothing happens - if I run it manually it crashes in similar way:

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.)

I'll attach the xor.conf in a separate post below...