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

2007-07-28 Thread Claudius Hubig
Morning, "Robert Freund" <[EMAIL PROTECTED]> wrote: >Claudius 'x2017' Hubig wrote: >> it happens regulary and reproducible while my system >> passes 18h memtest86+-testing > >How exactly is the 18h memory test related to this? How can you run >metacity while running memtest86+? Memtest86+ is some

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

2007-07-28 Thread Robert Freund
Hi, Claudius 'x2017' Hubig wrote: > it happens regulary and reproducible while my system > passes 18h memtest86+-testing How exactly is the 18h memory test related to this? How can you run metacity while running memtest86+? Memtest86+ is some kind of boot image which has to be run at boot time, i

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

2007-07-23 Thread manphiz
>I somehow resist the possibility of making my system unstable again, >since everything else works fine with Testing and upgrading to 2.18.3 >didn't help. Additionally, I noticed no hint showing that this >problem was solved with never versions. Some search work at http://bugzilla.gnome.org shows

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

2007-07-22 Thread Claudius Hubig
Hi, manphiz <[EMAIL PROTECTED]> wrote: >Thanks to curiosity, I updated my metacity from 1:2.14.5-4(testing) >to current unstable 1:2.18.5-1, and when encountering "Force Quit" >situation, everything works fine at my place: no lockup, no >non-responding, everything is fine. Well, this bug doesn'

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

2007-07-22 Thread manphiz
Thanks to curiosity, I updated my metacity from 1:2.14.5-4(testing) to current unstable 1:2.18.5-1, and when encountering "Force Quit" situation, everything works fine at my place: no lockup, no non-responding, everything is fine. Maybe you were still staying at 2.18.3? Try the newer version.

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

2007-07-19 Thread manphiz
According to the partial backtrace provided by Claudius Hubig, in which the backtrace got lost when encountered libc6-i686 stuff, I've got a Deja Vu with a recent bug reported toward aptitude(#431054) reporting keyboard handling lost when lib6-i686 was installed under kernel 2.6.18, and the sym

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

2007-06-04 Thread Claudius Hubig
Josselin Mouette <[EMAIL PROTECTED]> wrote: >Le dimanche 03 juin 2007 à 20:24 +0200, Claudius 'x2017' Hubig a écrit : >> To reproduce it, do the following: >> * Crash an application to make it not answering; I use claws-mail and remove >> the >>network-connection while it is fetching mails,

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

2007-06-03 Thread Josselin Mouette
Le dimanche 03 juin 2007 à 20:24 +0200, Claudius 'x2017' Hubig a écrit : > To reproduce it, do the following: > * Crash an application to make it not answering; I use claws-mail and remove > the >network-connection while it is fetching mails, but it's the same with > other apps. > * Click the

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

2007-06-03 Thread Claudius 'x2017' Hubig
Package: metacity Version: 1:2.18.3-1 Severity: grave Justification: renders package unusable Hi, 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