Comment 19 for bug 463915

Revision history for this message
SwaJime (john-swajime) wrote :

WG,

I don't know why my installation went so horribly wrong ... :-(

I followed your suggestion, and I don't see any difference. I'll try the "new defaults" for a while to see if that fixed any of the other myriad of problems that came up.

To get any desktop at all, I had to use
    gconftool-2 --type bool --set /apps/nautilus/preferences/show_desktop true
* and also *
with gconf, go to /apps/nautilus/desktop and enable all of the "-visible" settings.

I also had to rebuild the gnome-panel. It turned out that there were invisible applets taking up the whole panel, so that the portion of the panel you normally right-click on to add applets was inaccessible. The fix for that was to unlock and then move the broken and invisible "go-home" applet, so that an empty spot on the panel could be accessed.

Now I'm trying to figure out why gnome-screensaver is not running ... and I'm having other annoying errors, like:

   $ gnome-screensaver
   (gnome-screensaver:3246): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.
   (gnome-screensaver:3246): atk-bridge-WARNING **: IOR not set.
   (gnome-screensaver:3246): atk-bridge-WARNING **: Could not locate registry
   $ gedit error.odd
   (gedit:3248): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.
   (gedit:3248): atk-bridge-WARNING **: IOR not set.
   (gedit:3248): atk-bridge-WARNING **: Could not locate registry