[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Gnome shell won't open.



I am getting errors and gnome shell won't open. I'm not sure why, my system installed the latest security updates today is the only system change I can think of.

I get the following output from gnome-session...

GNOME_KEYRING_CONTROL=/home/john/.cache/keyring-5FLzEO
GPG_AGENT_INFO=/home/john/.cache/keyring-5FLzEO/gpg:0:1
GNOME_KEYRING_PID=12219
GNOME_KEYRING_CONTROL=/home/john/.cache/keyring-5FLzEO
GPG_AGENT_INFO=/home/john/.cache/keyring-5FLzEO/gpg:0:1
GNOME_KEYRING_CONTROL=/home/john/.cache/keyring-5FLzEO
GPG_AGENT_INFO=/home/john/.cache/keyring-5FLzEO/gpg:0:1
GNOME_KEYRING_CONTROL=/home/john/.cache/keyring-5FLzEO
GPG_AGENT_INFO=/home/john/.cache/keyring-5FLzEO/gpg:0:1
SSH_AUTH_SOCK=/home/john/.cache/keyring-5FLzEO/ssh
Initializing tracker-store...
Initializing tracker-miner-fs...
Starting log:
  File:'/home/john/.local/share/tracker/tracker-store.log'
Starting log:
  File:'/home/john/.local/share/tracker/tracker-miner-fs.log'
Initializing nautilus-gdu extension
Initializing nautilus-dropbox 1.6.0
Starting Dropbox...Created new window in existing browser session.
[INFO 15:36:22.111] Initializing Mono.Addins
Dropbox isn't running!
Done!
[ERROR 15:36:22.970] Unparsable last-sync-date element in /home/john/.config/tomboy/manifest.xml

Received signal:1->'Hangup'

Received signal:1->'Hangup'g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.

Received signal:15->'Terminated'
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.

Received signal:15->'Terminated'
OK


OK

---EOF---

X does not exit abruptly, I get no warnings, just the applications in my session load but I never get a shell. I assume gnome-shell is the window manager these days. I noticed tomboy compaining about an error so I moved ~/.config/tomboy to ~/oldtomboy and tried again but the error still appears in the log.

I really don't know why this would happen, perhaps some kind of disk corruption. I killed gdm3 to upgrade my nvidia driver just before it happened without logging out but I had closed most applications. Help would be greatly appreciated.

--
www.johntate.org

Reply to: