I am not able to start the "Window Manager" settings dialog within the settings manager. After clicking on the icon nothing happens. Someone posted a similar problem concerning the 'Iconbox" settings on the xfce forum. Before I had the problem with the icons don't showing up (see bug 366) I had no problems starting the 'W Manager" config dialog.
What happens when you run 'xfce-setting-show xfwm4' from a terminal? If that does nothing, you could try to run the settings manager from a terminal and check for warnings when you try to open the dialog: $ killall xfce-mcs-manager $ xfce-mcs-manager --no-daemon-debug
Using Debian Kernel 2.6.8-1-k7 XFCE 4.2BETA1 Got trough Apt-Get After running configuration wizard only had 1152 * 864 pixel res. After editing correct hor. vert. sync rate of my monitor, had correct res (1280 * 1024) but settings dialog won't show anymore ___________________________________________________________________________ The program 'xfce-mcs-manager' 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 128 error_code 2 request_code 155 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.)
(In reply to comment #2) > Using Debian Kernel 2.6.8-1-k7 > XFCE 4.2BETA1 > Got trough Apt-Get > After running configuration wizard only had 1152 * 864 pixel res. > After editing correct hor. vert. sync rate of my monitor, had correct res (1280 > * 1024) but settings dialog won't show anymore > > ___________________________________________________________________________ > > The program 'xfce-mcs-manager' 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 128 error_code 2 request_code 155 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.) > This is a different bug. Could you open a new report for it please?
Alexander, could you please try what I said in comment #1? Without any additional information, I will have to close this bug as WORKSFORME.
This looks like an installation error to me. Please reopen if you have additional information.