solution: So, gconf needed root privileges to install files in /etc. When I installed metacity to a fake directory, before actually installing it to the right place, I did it with user rights. So the install was not clean, and metacity could not start.
wrote by me: Hi all! I'd like to try out a compositing wm. I chose metacity. Maybe xfce's xfvm4 would have been a better choice, but maybe someone can help me. I get this, after startx: Window manager warning: "(null)" found in configuration database is not a valid value for mouse button modifier Window manager warning: Could not parse font description "(null)" from GConf key /apps/metacity/general/titlebar_font Window manager warning: 0 stored in GConf key /apps/metacity/general/num_workspaces is out of range 1 to 36 Window manager warning: 0 stored in GConf key /desktop/gnome/peripherals/mouse/cursor_size is out of range 1 to 128 ** metacity:ERROR:core/prefs.c:2482:meta_prefs_get_workspace_name: assertion failed: (workspace_names[i] != NULL) Maybe the error message is also related to gconf, just as the warning messages. I've found a bug report with this error message, but I've tried 3-4 versions of metacity, yet. I don't have gconf databases, as I guess I should. I got lots of warning messages when I did 'make install' to metacity: WARNING: failed to install schema `/schemas/apps/metacity/general/audible_bell', locale `te': Unable to stor e a value at key '/schemas/apps/metacity/general/audible_bell', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gnome/2.30.2/g conf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd proces ses 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dr opped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killi ng all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perh aps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its defaul t configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, che ck the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home direc tory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/. gconf regards, bendeguz -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
