OK, I'm totally sure it's a freeze.
Moreover, gnome-shell stack trace looks normal, event loop runs just fine.
I can generate and provide core file if needed.
What I managed to debug so far, is that in case of multiple /dev/dri/cardX
being created
frame_cb in meta-stage-x11.c:296 is not called w
Alright. Please first ensure you have followed all the steps in comment
#3. Then if there's still no evidence of a crash we can assume it's a
freeze. The next thing to try then is to force it to dump core during
the freeze (from an ssh login) by sending some signal to the process
like:
kill -USR
Point is, there is no crash file. Graphical environment is not responsive, but
nothing seems to have crashed.
If there's a stacktrace or core file needed, no problem, I can rebuild in debug
mode, attach debugger and gather those.
--
You received this bug notification because you are a member of
If the HW cursor still moves then it's not Xorg that's
locked/frozen/crashed, it is gnome-shell (via the mutter project).
** Package changed: xorg-server (Ubuntu) => mutter (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
