whats about vlc? Do the system still crash on new drivers when you want to play the movie?
The following is roughly what always pops up when the crash occurs.
The Clutter warning, followed by the two errors, also appear in the log without it being followed by a crash. So I expect that that isn't the cause.Code:Clutter-WARNING **: Unable to compile the GLSL shader: Fragment shader failed to compile with the following errors: ERROR: 1:1: error(#105) #version must occur before any other statement in the program ERROR: error(#273) 1 compilation errors. No code generated ** Message: applet now removed from the notification area gnome-shell-calendar-server: Got HUP on stdin - exiting gnome-session: WARNING: Application 'gnome-shell.desktop' killed by signal folks-DEBUG: individual-aggregator.vala:310: Setting primary store IDs to defaults. folks-DEBUG: individual-aggregator.vala:338: Primary store IDs are 'eds' and 'system'. JS ERROR: !!! WARNING: 'assignment to undeclared variable owner' JS ERROR: !!! WARNING: file '/home/forage/.local/share/gnome-shell/extensions/music-integration@brianrobles204/extension.js' line 1432 exception 0 number 156 JS LOG: GNOME Shell started at Sat Jan 28 2012 01:05:52 GMT+0100 (CET) ** Message: applet now embedded in the notification area
I can remove the music-integration extension, but as mentioned before, the issue also occurred before installing it and the warning does not show up until after the crash.
Is all of that what is spewed out immediately after the crash or simply all the output from the VT?
None of those errors look fatal to me. The GLSL error might cause problems if you hit that particular code path (did the crash happen to occur after you some interaction with the shell? like going to overview/looking at the calender/alt-tab/etc).
To get the errors in a more useful order we could try passing the "--sync" option to the gnome-shell command. If that doesn't help, have you tried installing the open drivers just as a check to see if something is wrong your installlation?
It was copied from ~/xsession-errors, because I did not manage to get a copy of the VT output. The content is the same nevertheless.
Using a VT to restart gnome-shell and continue to work normally is, however, a bit of a pain since other applications stop functioning properly if I do. E.g. Empathy can't login any more (telepathy errors) and Synaptic won't start, etc.
Just to be sure I could try the opensource drivers again for a day and see what happens. Seeing the "gnome-shell-calendar-server" in the log makes me question if it really can be related.
It is most likely not your error. AMD drivers have got those stupid defaults even on Win. The drivers are a mess there too, i wanted to use it on a Philips TV, could fix the overscan, but got bad colors after some time. I did not google to search for a possible workaround that day, it seems there should be a config option, but by default it is wrong. When you however use a nvidia card, then you dont need to do anything, it is just correct by default... AMD hardware is most likely not that bad, but drivers are complete crap. Even the defaults are more painful than helpful.
The driver is not part of the kernel, user space. This is why 64 of the installation image is a huge amount of more than 32 large.