! Please note that this is a snapshot of our old Bugzilla server, which is read only since May 29, 2020. Please go to gitlab.xfce.org for our new server !
xfwm4 will not load, complaining about missing default values


Description Andrew Conkling 2004-09-21 17:37:54 CEST
I can't get xfwm4 to load today after rebuilding from CVS.  It complains with
the following: 
missing value for option up_workspace_key
missing value for option down_workspace_key
missing value for option left_workspace_key
missing value for option right_workspace_key
missing value for option move_window_up_workspace_key
missing value for option move_window_down_workspace_key
missing value for option move_window_left_workspace_key
missing value for option move_window_right_workspace_key

** (xfwm4:4871): WARNING **: xfwm4: Missing values in defaults file

** (xfwm4:4871): WARNING **: xfwm4: Missing data from default files
Comment 1 Olivier Fourdan editbugs 2004-09-21 17:43:09 CEST
Either your install is incomplete or you have a
$HOME/.themes/Default/xfwm4/keythemerc that should be removed.
Comment 2 Andrew Conkling 2004-09-21 18:21:32 CEST
Yes, that did it; sorry for polluting the bugs.
Comment 3 Olivier Fourdan editbugs 2004-09-21 19:07:12 CEST
You're not polluting the bugs, we have a major problem here and it has never
been addressed although I already reported it on the dev ML.

It is "illegal" to create a custom Default keythemerc because the defaults are
to be used when other data are missing. Problem is the keyboard shortcut editor
is creating that $HOME/.themes/Default/xfwm4/keythemerc causing the bug you saw.

I shall change xfwm4 so that it ignores that file (it's not the first time we
get sucha report, and I think that preventing the WM to start is a major
proble), but that means the the keyboard shortcut won't work anymore. So if that
issue is not addressed before the beta1 release, I shall remove the keyboard
shortcut editor all together.

Comment 4 Olivier Fourdan editbugs 2004-09-21 19:28:38 CEST
I took a more "pragmatic" approach. Custom defaults are now merged with system
defaults so I guess that fixes the issue all together in a smooth, simple way...
False alert!

Bug #323

Reported by:
Andrew Conkling
Reported on: 2004-09-21
Last modified on: 2009-07-14


Olivier Fourdan
CC List:
1 user



Additional information