Olivier, sorry for this, but I think there is still an issue with the xfwm4
defaults file. The defaults file in CVS does not contain an entry
'fullscreen_key'. When I run xfwm4 in gdb it complains about not finding this
entry (see below). I also browsed WebCVS to be sure, but maybe there is
something wrong with CVS atm?
missing value for option fullscreen_key
** (xfwm4:30971): WARNING **: xfwm4: Missing values in defaults file
** (xfwm4:30971): WARNING **: xfwm4: Missing data from default files
Program exited with code 01.
Yes, sorry, the message is misleading, the fullscreen_key is defined in the key
Can you make sure you don't have a copy of keythemerc in
this may sound silly, but why is a defaults file required at all? it's nice to
have as a template for users to modify, but IMHO xfwm4 should have the defaults
hardcoded in the binary to use in the case it can't find a theme file.
ok, the custom keythemerc file was the villain. But I guess it's not good that
a misconfigured user rc-file prevents xfwm4 from starting up at all? Shouldn't
it at least modify it silently or use, like kelnos said, some hardcoded value?
The user is not supposed to change the default values.
??? But what is a custom keythemerc good for, then? The user is not supposed to
change files that contain default values (like
A custom keytheme is perfectly okay, as long as it's not called "Default" ;)
This can be closed, right?
Dunno. If the custom theme was called "Default", then ok, it's not a bug,
but otherwise it might need some more investigations.
Ok, here is what I did:
1) create a theme in my home dir
2) Remove most of the mandatory entries
3) restart xfwm4
It doesn't complain, the default and customized key themes are merged nicely.
So I guess the custom theme was called "Default", that's not a good idea. No
bug here IMO.
Resolving. If you disagree, please let us hear your voice :)
appears to be no bug + no word from reporter in over a week = closed