My Gnome environment has a security issue affecting many other apps. The root of the problem is with the dbus => gnome-keyring interaction. Messages are: From Dmesg: Code:polkitd(authority=local): Registered Authentication Agent for unix-session: /org/ freedesktop/ConsoleKit/Session1 (system bus name :1.15 [/usr/local/libexec/polkit-gnome- authentication-agent-1], object path /org/gnome/PolicyKit1/AuthenticationAgent, locale ) gnome-keyring-daemon: couldn't allocate secure memory to keep passwords and or keys from being written to the disk dbus-daemon: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.39" (uid=xxx pid=1710 comm="nautilus ") interface="org.freedesktop.DBus. Properties" member="GetAll" error name="(unset)" requested_reply=0 destination=":1.2" (uid=0 pid=1710 comm="/usr/local/sbin/console-kit-daemon --no-daemon ")) seahorse-daemon: init gpgme version 1.3.0 and in other places: Code:(polkit-gnome-authentication-agent-1:1722): polkit-gnome-1-WARNING **: Error enumerating temporary authorizations: GDBus.Error:org.freedesktop.PolicyKit1. Error.Failed: Cannot determine session the caller is in Code:atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup. (gnome-settings-daemon:1710): atk-bridge-WARNING **: IOR not set. Supporting Evidence: Other apps complain in various ways when they are launched as root from terminal emulator: Code:a. Failed to connect to the session manager: None of the authentication protocols specified are supported. GLib-GIO:ERROR:gdbusconnection.c:2270: initable_init: assertion failed: (connection->initialization_error == NULL) b. cannot connect to the session bus: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, etc. c. GDM pitches in with its 2 (or 50) cents: Code:Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. CurrentTime used to choose focus window; focus window may not be correct. Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen! Unfortunately, my google search did not turn up with much relevant answers on the topic. Thanks in advance.