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't happen on every system. As Joss already wrote, he hasn't got the problem, as I installed a fresh system in a virtual machine, it doesn't happen, too. >Maybe you were still staying at 2.18.3? [EMAIL PROTECTED]:~$ metacity --version metacity 2.14.5 >Try the newer version. 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. >Or maybe something else is culpable on your particular system? Probably, only question: what? Greetings, Claudius -- Mail: [EMAIL PROTECTED] ICQ: 224491597 ,= ,-_-. =. Jabber: [EMAIL PROTECTED] SIP: [EMAIL PROTECTED] ((_/)o o(\_)) MSN: [EMAIL PROTECTED] Nightfall.org:23 Claudius `-'(. .)`-' Yahoo: [EMAIL PROTECTED] Using: [Opera|Gaim|[EMAIL PROTECTED] \_/ GNU
signature.asc
Description: PGP signature
