| negafon |
03-31-2013 03:14 PM |
gnome-shell won't start after software upgrade
After doing an upgrade today with apt, gnome-shell won't start. The login manager comes up, asks for my username and password, I enter it and I get nothing but my desktop background. I was able to log in via the terminal and selecting 'Gnome-Classic' on the login manager will also allow me to log in. I noticed an upgrade to gnome-settings-daemon in the apt log. I also noticed that I am unable to open the 'System Settings' dialog; it crashes after a few seconds of trying to start. Here is the relevant info in .xsession-errors:
Quote:
/etc/gdm3/Xsession: Beginning session setup...
localuser:[user] being added to access control list
openConnection: connect: No such file or directory
cannot connect to brltty at :0
GNOME_KEYRING_CONTROL=/home/[user]/.cache/keyring-staj8v
SSH_AUTH_SOCK=/home/[user]/.cache/keyring-staj8v/ssh
GNOME_KEYRING_CONTROL=/home/[user]/.cache/keyring-staj8v
SSH_AUTH_SOCK=/home/[user]/.cache/keyring-staj8v/ssh
GNOME_KEYRING_CONTROL=/home/[user]/.cache/keyring-staj8v
SSH_AUTH_SOCK=/home/[user]/.cache/keyring-staj8v/ssh
GPG_AGENT_INFO=/home/[user]/.cache/keyring-staj8v/gpg:0:1
GNOME_KEYRING_CONTROL=/home/[user]/.cache/keyring-staj8v
SSH_AUTH_SOCK=/home/[user]/.cache/keyring-staj8v/ssh
GPG_AGENT_INFO=/home/[user]/.cache/keyring-staj8v/gpg:0:1
(gnome-settings-daemon:4275): color-plugin-WARNING **: failed to get edid: unable to get EDID for output
(gnome-settings-daemon:4275): color-plugin-WARNING **: unable to get EDID for xrandr-LVDS: unable to get EDID for output
(gnome-shell:4312): Gdk-WARNING **: The program 'gnome-shell' received an X Window System error.
This probably reflects a bug in the program.
The error was 'GLXBadRenderRequest'.
(Details: serial 170 error_code 153 request_code 137 minor_code 1)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
|
Does anyone know what I should do from here? Is it a GNOME keyring issue? Do I try to rollback the gnome-settings-daemon update? Thanks. |
