the bug disappeared with the update to fglrx 8.34.8
--
fglrx-driver behaves strange in 8.32.5, works fine in 8.28.8
https://launchpad.net/bugs/76383
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Closing.
** Changed in: linux-restricted-modules-2.6.20 (Ubuntu)
Status: Unconfirmed => Rejected
--
fglrx-driver behaves strange in 8.32.5, works fine in 8.28.8
https://launchpad.net/bugs/76383
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/lis
I found something funny :
when using the wxVTKRenderWindowIntreractor Class available at:
http://wxvtk.sourceforge.net/
the rendering is perfect. So the issue might come from VTK after all
(and most probably the vtkRenderWindowInteractor Class)
--
fglrx-driver behaves strange in 8.32.5, works
see the post http://ubuntuforums.org/showthread.php?t=323319 on
ubuntuforums.org for more details
--
fglrx-driver behaves strange in 8.32.5, works fine in 8.28.8
https://launchpad.net/bugs/76383
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/u
I can confirm this strange behavior. The programs given in the package
vtk-examples can reproduce this issue. (as an example,
/usr/share/vtk/Rendering/Python/rainbow.py)
The problem occurs on my laptop (radeon mobility 9600) and desktop (firegl
rv370)
This problem is not specific to Feisty, as th