okay basically, there was a bug in alarm-clock that caused the entire desktop to freeze. the reason this bug is filed separately is because the bug in alarm-clock was fixed, but python should not be able to freeze the entire desktop like that. Here are the details i linked to and how to reproduce. I'm also uploading the test case
"Here's how I think you can reproduce the problem. Just write a program (C or Python, doesn't matter) that: 1. Creates a toplevel window (make it a fullscreen window for increased effect) 2. calls gdk_pointer_grab on that window 3. never calls gdk_pointer_ungrab >From that moment on, the program captures the pointer (and as side effect also the keyboard). Consequently, the clueless user thinks that "X is frozen", when in actual fact is just "poorly written app grabs the pointer and never ungrabs it". This is *NOT* a PyGTK bug. This is *NOT* a Gtk+ bug. This is *NOT* a Xorg bug. Every programmer that ever needed to write code to grab the mouse pointer will occasionally temporarily write code that grabs the pointer but forgets to ungrab it. I have been there myself. But the X session is not completely frozen. You can recover by pressing <Ctrl><Alt>F1, login in a linux console, and manually kill the offending program. Then you can go back to the X11 console (normally <Alt>F7), and everything is back to normal." ** Attachment added: "crash.py" http://launchpadlibrarian.net/33008881/crash.py -- Programs can freeze the desktop https://bugs.launchpad.net/bugs/397472 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
