My prior backtrace attempt (2009-02-08) was over the network via ssh. I tried it again today, but this time I attached gdb to the polytopes process BEFORE polytopes locked up. However, the result was nearly identical to the log I uploaded on 2009-02-08. In short, once polytopes locked up, pressing ctrl-c in the gdb window caused gdb to silently abort. All I got was my bash prompt. Polytopes was still frozen on the other computer.
> Does this happen if you turn off locking (password checking) on the screensaver? I cannot test this until I figure out how to trigger the screensaver without waiting for the inactivity time out or locking the screen. My hunch is that the problem is somehow related to the signals when a key is pressed. When polytopes is running normally but gdb is attached, pressing a key on the polytopes computer causes gdb to print, "Program received signal SIGSTOP, Stopped (signal)." After pressing escape at the screensaver password prompt, gdb then prints, "Program received signal SIGTERM, Terminated." However, the polytopes pid does not change. I don't know if this is related, but after I did the above testing and had written most of these comments, I opened the screensaver preferences dialog (which displays a small preview of polytopes) and my laptop suddenly rebooted. It has never done this before and it seemed to happen exactly as the screensaver preferences dialog was opening. -- [intel] polytopes screensaver freezes, requiring hard reset https://bugs.launchpad.net/bugs/319097 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
