I'm sorry, I agree with Emmanuel: I can't understand the closing of this bug.
Is this bug resolved? If so, why opening the new #195051 bug? Beside that, what about applying the patch for Gutsy too (maybe would be useful to anyone who can't swith to the Hardy beta or try Hardy as soon as it's released)? If this bug isn't resolved, why closing? Where can we follow the resolution of the problem? If there's a more specific bug, why not marking this as a duplicate? The bug is related to ATI open source driver? Let's open a new one with "X freezes when compiz is enabled on ATI open source driver" and mark all related bugs as duplicates! The #195051 is "X freezes in drmCommandWrite() when Compiz is enabled on ATI Radeon Mobility 9600", I say: it should be marked as a duplicate. @Bryce, You said you were "sort of able to reproduce a lockup on an ATI R350 9800 using firefox 3, without Compiz enabled...", you kill firefox3 by switching to a vt and everything comes back... I think this is not a reproduction of this bug: the system freezes with a clean install of Gutsy (and Feisty with compiz) - all of them without Firefox 3 - and it's impossible to switch to a vt... Besides that, I don't think it's a "client application" related bug: I tried to send "a SIGKILL to all my processes (using Alt-SysRq-i)" and X remained freezed. -- X freezes when compiz is enabled on ATI X300 https://bugs.launchpad.net/bugs/108527 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
