https://bugs.freedesktop.org/show_bug.cgi?id=41668
--- Comment #6 from dmotd inaudible@simplesuperlativ.es 2011-10-11 19:25:07 PDT --- (In reply to comment #4)
`DISPLAY=:0 openbox --replace` results in:
"Invalid MIT-MAGIC-COOKIE-1 keyOpenbox-Message: Failed to open the display from the DISPLAY environment variable."
This is because gdm3 uses a non-default X11 authentication cookie. I use something like
XAUTHORITY=/run/gdm3/$(sudo ls /run/gdm3|grep $(whoami))/database DISPLAY=:0 [...]
to work around it.
i've since ditched a graphical login, i've had better success reinitiating X with startx.. the last freeze i had i managed to initiate an openbox session (---replace) on top of the failed gnome-shell (which i killed, and switched 'fallback mode' from the cmdline). the result was many windows were inactive and frozen (ie. evolution, gnome-terminal, chromium), while a few others (gvim was one, and empathy was another) remained active and usable. i could however start new instances without issue.
running glxgears just shows an empty black box.. all other glx demos are the same empty boxes..
Do they work with the environment variable vblank_mode=0? If yes, does the number for radeon increase in /proc/interrupts once the problem occurs?
setting vblank_mode=0 works and displays an output.. but not much change in /proc/interrupts (irq 46 for radeon) i'll attach the output from after the freeze and one from a fresh happy boot..