| Stephen Gran on 7 Dec 2003 11:42:02 -0500 |
|
On Sat, Dec 06, 2003 at 05:15:08PM -0500, Michael Leone said: > On Fri, 2003-12-05 at 11:40, Stephen Gran wrote: > .xsession-errors: > > localhost being added to access control list > _IceTransmkdir: Owner of /tmp/.ICE-unix should be set to root > SESSION_MANAGER=local/latitude-cs:/tmp/.ICE-unix/2857 > Gnome-Message: gnome_execute_async_with_env_fds: returning -1 > Gnome-Message: gnome_execute_async_with_env_fds: returning -1 > X connection to :0.0 broken (explicit kill or server shutdown). > X connection to :0.0 broken (explicit kill or server shutdown). > gnome-smproxy: unable to open display :0.0 > sawfish: Can't open display: :0.0 > > Had to CTRL-ALT-BKSPACE to kill it. This is that library problem - liborbit or libbonobo, athough I can't find the threads about this now. It's a particular version problem, and only some versions of (whichever library it is) work with the gnome-session/nautilus setup. The others just refuse to connect to the X server for some reason. Try installing nautilus (as in the other email), and see how that goes. > > As others have said, GNOME has switched to a gconf-registry sysytem for > > handling details like what WM to use and so on, and they have decided > > that the default is going to be metacity, instead of allowing any > > compliant WM. *sigh* - starting to smack too much of Windows for my > > tastes, but that's what they want, I guess. If your old GNOME setup > > used a different WM, you may run into some problems. > > Wonder why mine says "sawfish", then? Gconf key. Use the gconf editor and change the key /desktop/gnome/applications/window_manager/current to /usr/bin/metacity - sawfish does still work, but the integration is not as good. Do not save your session afterwards - the running sawfish will make it write that back to that key. See how I think it's like Windows? :) > > If ~/.xsession-errors has nothing that looks fixable, and you're still > > getting problems, make sure you have metacity installed, mv your old > > setup out of the way (should be ~/.gnome ~/.gnome2 ~/.gnome-private > > ~/.gnome2-private) and try again - it may be some difficulty related to > > your particular setup. > > Deleted all those; no change. Really makes me wonder why it wants the > old sawfish, then. I have no gnome config files in my home directory. > (except for config files for some gnome programs, such as evolution, > which I am using to write this message, etc) I forgot to mention ~/.gconf and ~/.gconf2 - although deleting them has in the past not always gotten me the results I had hoped for - there are probably other places it keeps this stuff that I haven't yet found. XML registry keys. blech. Hopefully you're getting somewhere now. Write back if not. -- -------------------------------------------------------------------------- | Stephen Gran | One should always be in love. That is | | steve@lobefin.net | the reason one should never marry. -- | | http://www.lobefin.net/~steve | Oscar Wilde | -------------------------------------------------------------------------- Attachment:
pgpWNWE6GMKRI.pgp
|
|