Ah, okay sorry, this is the way you can get a backtrace for Unity without ssh etc:
- Use your Intel system
- Switch to VT1
- login
- export DISPLAY=:0
- export UBUNTU_MENUPROXY=libappmenu.so
- gdb --args mutter --replace --mutter-plugins=libunity-mutter
- At gdb prompt, type 'r' and then <enter>
- Switch to VT7
*** Cause the crash, system will stop responding but mouse will keep moving ***
- Switch back to VT1
- At the gdb prompt, type "bt" and <enter>
That should give you a full backtrace. Instead of copying it over, you can just take a picture of the trace with a camera and attach it to this bug, i just need to see the exact point of failure.
Ah, okay sorry, this is the way you can get a backtrace for Unity without ssh etc:
- Use your Intel system MENUPROXY= libappmenu. so plugins= libunity- mutter
- Switch to VT1
- login
- export DISPLAY=:0
- export UBUNTU_
- gdb --args mutter --replace --mutter-
- At gdb prompt, type 'r' and then <enter>
- Switch to VT7
*** Cause the crash, system will stop responding but mouse will keep moving ***
- Switch back to VT1
- At the gdb prompt, type "bt" and <enter>
That should give you a full backtrace. Instead of copying it over, you can just take a picture of the trace with a camera and attach it to this bug, i just need to see the exact point of failure.
I hope that helps!