Bug#427406: No more mouse/keyboard-input possible after closing crashed application

2007-09-12 Thread Sven Arvidsson
forwarded 427406 http://bugzilla.gnome.org/show_bug.cgi?id=476279 severity important thanks On Mon, 2007-09-03 at 19:36 -0300, Ivan Baldo wrote: > I suggest two things: >1 - forwarding the bug upstream: because maybe they want to look > into this to make the application or library more ro

Processed (with 1 errors): Re: Bug#427406: No more mouse/keyboard-input possible after closing crashed application

2007-09-12 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > forwarded 427406 http://bugzilla.gnome.org/show_bug.cgi?id=476279 Bug#427406: metacity: No more mouse/keyboard-input possible after closing crashed application Noted your statement that Bug has been forwarded to http://bugzilla.gnome.org/show_bug.cgi?

Bug#427406: No more mouse/keyboard-input possible after closing crashed application

2007-09-03 Thread Ivan Baldo
I suggest two things: 1 - forwarding the bug upstream: because maybe they want to look into this to make the application or library more robust. 2 - see what makes GTK+ 2.11 refuse to create the icon cache and backport it to GTK+ 2.10, then close this bug: so Metacity transitions

Bug#427406: No more mouse/keyboard-input possible after closing crashed application

2007-09-01 Thread Sven Arvidsson
Original bug report: > whenever a crashed application is closed by hitting the "x" button in the > titlebar, > Metacity used to showing a window "The application doesn't answer [Close] > [Wait]" or > something like this. Now, it causes the system to become unusable by grabbing > every > keyboard