Re-closing bug. Guys, the problem here is that the original bug report
was labeled with a generic title that described a symptom - "X freezes
with compiz" - that is common to many, many different bugs. A lot of
different kinds of coding errors in the -ati driver lead to X freezes
when using composited functionalities, often these are particular to a
given driver model, or to a specific user action or condition.
I talked about the compiz-related crashes with Alex Deucher at XDC2008
the other week, and he gave some additional detail. Long ago before ATI
released their documentation, developers simply had to make guesses
about what registers on different ATI cards mapped to functionality-
wise. By and large these guesses were wrong, with the result that the
driver is riddled with mis-mapped registers, which will result in a wide
range of different kinds of bugs on different cards. The good news is
that now that docs are available, these issues can be investigated one
by one and sorted out through reference to the documentation.
These different bugs can have seemingly the same result - a frozen or
crashed X. This particular bug report was titled in such a way that all
these bugs have gotten lumped together, even though they almost
certainly have nothing at all to do with one another. I've heard this
referred to as a "confirm storm" - so many people reporting they have
the "same" issue, that it actually becomes difficult to figure out what
the problems are. Also, many times commenters will believe they have
the problem (when they don't, and instead have a unique problem) and
unfortunately decide not to leave any details, believing that others
have already given enough info and that once the original bug is fixed,
their problem will go away too; yet without those details it's
impossible for anyone to determine if they had the original bug or
something unique, and makes it impossible to troubleshoot their issue -
thus their problem receives no attention and unfortunately remains
unfixed.
This is why we so strongly encourage each person to report their issue
separately. It aids in tracking, so even if you do have exactly the
same bug as person A, we can handle it by duping your bug report to
theirs; some times it turns out that it really is not a dupe, and this
lets us easily un-dupe the bug and treat it normally.
Furthermore, the way we can get these bugs fixed is through forwarding
them upstream. To get them closed most efficiently, the reports need to
be clear, complete, and specific. A bug report like this one (108527)
with a jumble of different reporters, incomplete information, and likely
a combination of different issues, would not be accepted by them.
So, in reality, having this bug open may actually *hinder* getting the
issues resolved, for all of the above reasons. Please do not reopen
this bug or add comments if you're having an X freeze - open a new bug.
If you've already opened a bug but it's not getting attention, please be
patient, we have a lot of bugs to go through but we do intend to get to
all of them. De-blacklisting ATI in compiz is a high priority for
Intrepid.
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Confirmed => Fix Released
--
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
