Why did you close bug 124714? https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=124714 Since when does one close a bug that crashes a system hard just because a poor work-around exists? 'vino' is a derivative of 'x0rfbserver' and suffers the same inherent inefficiencies. I'm seeing the same problem with 'vnc.so' and an ATI Radeon video card. Commenting out the "DRI" stanza does not fix it.
The bug was closed because information was requested: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=124714#c16 and nobody responded. The original reporter later indicated that it was no longer an issue for him. Fedora Core 2 is not going to get any further X updates except for security issues, so anyone experiencing crashes or other problems in FC2 is recommended to upgrade to FC3 and see if their issue is reproduceable still. Now that you've indicated you are experiencing this problem in FC3, it indicates the problem must still exist, which was not clear in the other bug report. If you switch to the "vesa" driver, is the problem still reproduceable?
Please see my comment in #124714.
Since this bugzilla report was filed, there have been several updates to xorg-x11, which may resolve this issue. Users who have experienced this problem are encouraged to upgrade to the latest Fedora Core updates. If this issue turns out to still be reproduceable in the latest updates also, please file a bug report in the X.Org bugzilla located at http://bugs.freedesktop.org in the "xorg" component. Once you've filed your bug report to X.Org, if you paste the new bug URL here, Red Hat will continue to track the issue in the centralized X.Org bug tracker, and will review any bug fixes that become available for consideration in future updates. Setting status to "ERRATA".