Created attachment 410601 [details]
log from /var/log/gdm/
Description of problem:
After gnome-shell is started with export CLUTTER_VBLANK=none (it doesn't work without this env setting), there appears a gnome-shell desktop for the second and then the X crashes and returns to the gdm login screen. There is Xorg: radeon_texture.c:1023: radeon_get_tex_image: Assertion `image->base.Data' failed. error in log.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. export CLUTTER_VBLANK=none
2. gnome-shell --replace
short gnome-shell environment and crash
The fact that X crashed within a Mesa source file - radeon_texture.c - implies that you are running with "indirect rendering" - where the X server is doing the GL rendering instead of the client. The crash in Mutter you are seeing without CLUTTER_VBLANK=none (reported in 577512) also looks like indirect rendering - as far as I can decode it, it looks like gnome-shell was sending a detailed rendering stream over the GLX protocol.
This is unexpected... we supposedly should be using direct rendering almost always.
Can you describe in detail what steps you are taking to launch gnome-shell in the described experiments? (Alon the lines of "Log in to GNOME with the standard Metacity desktop. Open a terminal. Run 'CLUTTER_VBLANK=none ./gnome-shell'")
Can you attach, as attachments:
a) The output of 'glxinfo' (from the terminal you are using to start gnome-shell)
b) The output of 'env' (from the terminal you are using to start gnome-shell)
OK, I'm really just trying it opening terminal and running above mentioned commands. No special settings and it's run from standard metacity desktop.
Created attachment 410661 [details]
Created attachment 410662 [details]
Don't see anything interesting in the environment. From glxinfo:
direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)
Can you try setting LIBGL_DEBUG=verbose and see if you get useful additional information?
Errm. I checked GL libraries loaded by glxinfo and it seems nvidia proprietary driver libraries were messing with the system. I wiped them out and it seems to be OK. I'm sorry for the noise :-(.