Comment 10 for bug 146900

On 10/3/07, Tormod Volden <email address hidden> wrote:
> Try:
> dpkg -l '*fglrx*'

un xfree86-driver-fglrx
rc xorg-driver-fglrx 7.1.0-8.37.6+2.6.22.4-12.4 Video
driver for ATI graphics accelerators

> and
> locate fglrx
> to see if there is still some evil proprietary bits around.

Ah, we might be on to something here. Aside from archives, packages
and other out-of-the-way stuff, found these :

/etc/X11/Xsession.d/70fglrx_32bit_dri
/etc/X11/Xsession.d/70fglrx_32bit_dri/fglrx.xsession
/etc/X11/Xsession.d/10fglrx
/etc/X11/Xsession.d/10fglrx.dpkg-old
/etc/X11/fglrx.xsession
/etc/acpi/events/fglrx-lid-aticonfig
/etc/acpi/events/fglrx-ac-aticonfig
/etc/acpi/fglrx-powermode.sh
/etc/default/fglrx
/etc/ati/fglrxprofiles.csv
/etc/ati/fglrxrc
/lib/linux-restricted-modules/2.6.20-16-generic/fglrx
/lib/linux-restricted-modules/2.6.20-16-generic/fglrx/libfglrx_ip.a.GCC4
/lib/linux-restricted-modules/2.6.20-16-generic/fglrx/firegl_public.o
/lib/linux-restricted-modules/2.6.20-16-generic/fglrx/fglrx.mod.o

looks like something was *not* cleaned up correctly ; and considering
the kernel version above, this looks like the feisty fglrx wasn't
zapped when upgrading to gutsy. Still weird since nothing should be
calling them, but they're here.
(...)
Removing them manually didn't help. I'm still getting the same error in glxinfo.