I had now similar problem; Computer did NOT hanged totally (keyboard was working), and after few minutes of trying alt-ctrl-F1 -F7 and various sys-rq I finally managed to go back to fully working X :0 (VT7)
It occured when 1. VT7 (:0) started new X session VT8 (:1) 2. I switched to VT1 3. back to VT8 4. afair back to VT1, or VT7 or something screen turned off then keyboard was responding Dmesg was flooded with sys-rq outputs, but kern.log contained: May 19 00:56:07 limcore kernel: [107016.084154] NVRM: Xid (0001:00): 6, PE007f May 19 00:56:07 limcore kernel: [107016.085900] NVRM: Xid (0001:00): 7, Ch 0000007f M 00001ffc D ffffffff intr ffffffff May 19 00:56:07 limcore kernel: [107016.087565] NVRM: Xid (0001:00): 26, Ch 0000007f M 00001ffc D ffffffff intr ffffffff May 19 00:57:38 limcore kernel: [107106.892054] SysRq : Keyboard mode set to system default May 19 00:57:41 limcore kernel: [107109.802749] SysRq : Emergency Sync Attaching other files that may be usefull ** Attachment added: "dmesg" http://launchpadlibrarian.net/14600718/dmesg -- restarting X (restarting kdm in example) and going back to VT then back to X causes X failure (nvidia, glx-new) https://bugs.launchpad.net/bugs/230203 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
