Re: Gnome desktop settings borked on testing after reboot
On Thu, 2011-06-09 at 18:38 +0100, AG wrote:
> Hi all
>
> Having just rebooted after an uptime of 7 days, I have logged into my
> Gnome DE to find that all of my settings for the desktop have been
> borked and the desktop is close to unfunctional.
>
> These are some of the issues:
> 1. Windows manager is "unknown" and no configuration tool is registered
> 2. windows are launched at the top of the screen & I cannot drag these
> elsewhere
> 3. clicking a mouse on a window does not bring it to the fore
> 4. there are no longer multiple workspaces
> 5. windows do not have the 'x' in the corner to close, nor any option to
> minimise/ enlarge
> 6. a screensaver launches after ~30 seconds of inactivity (I don't use a
> screensaver)
> 7. no key mapping exists
>
> Both metacity and nautilus are the most current versions. No other
> user-based changes made to configuration except for whatever gets
> configured in safe updates using update-manager.
>
> Can anyone please help - I really do need a usable desktop environment
> to work in.
>
> Thanks.
>
> AG
PS, not an issue, but it might has to do with those issues:
spinymouse@debian:~$ gedit
spinymouse@debian:~$ su
Password:
root@debian:/home/spinymouse# gedit
(gedit:7637): EggSMClient-WARNING **: Failed to connect to the session
manager: None of the authentication protocols specified are supported
GConf Error: Failed to contact configuration server; the most common
cause is a missing or misconfigured D-Bus session bus daemon. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
GConf Error: Failed to contact configuration server; the most common
cause is a missing or misconfigured D-Bus session bus daemon. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
GConf Error: Failed to contact configuration server; the most common
cause is a missing or misconfigured D-Bus session bus daemon. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
GConf Error: Failed to contact configuration server; the most common
cause is a missing or misconfigured D-Bus session bus daemon. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
GConf Error: Failed to contact configuration server; the most common
cause is a missing or misconfigured D-Bus session bus daemon. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
GConf Error: Failed to contact configuration server; the most common
cause is a missing or misconfigured D-Bus session bus daemon. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
GConf Error: Failed to contact configuration server; the most common
cause is a missing or misconfigured D-Bus session bus daemon. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
(gedit:7637): Gtk-WARNING **: Unable to rename
'/root/.recently-used.xbel': No such file or directory
GConf Error: Failed to contact configuration server; the most common
cause is a missing or misconfigured D-Bus session bus daemon. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)
GConf Error: Failed to contac [snip]
Reply to: