Some entries that seem to fail (using precise i386 + nvidia 295)
# ls -l /usr/lib32
libOpenCL.so -> /etc/alternatives/i386-linux-gnu_libOpenCL.so_lib32
libvdpau_nvidia.so.dpkg-tmp ->
/etc/alternatives/i386-linux-gnu_libvdpau_nvidia.so_lib32
# ls -l /etc/alternatives/i386-linux-gnu_libO*
/etc/alternatives/i386-linux-gnu_libOpenCL.so ->
/usr/lib/nvidia-current-updates/libOpenCL.so
/etc/alternatives/i386-linux-gnu_libOpenCL.so_lib32 ->
/usr/lib32/nvidia-current-updates/libOpenCL.so
The second is broken (recursive).
Same here with both lib32-links being recursive:
# ls -l /etc/alternatives/i386-linux-gnu_libvdpau_nvidia*
/etc/alternatives/i386-linux-gnu_libvdpau_nvidia.so ->
/usr/lib/nvidia-current-updates/vdpau/libvdpau_nvidia.so
/etc/alternatives/i386-linux-gnu_libvdpau_nvidia.so.1 ->
/usr/lib/nvidia-current-updates/vdpau/libvdpau_nvidia.so.1
/etc/alternatives/i386-linux-gnu_libvdpau_nvidia.so.1_lib32 ->
/usr/lib32/nvidia-current-updates/vdpau/libvdpau_nvidia.so.1
/etc/alternatives/i386-linux-gnu_libvdpau_nvidia.so_lib32.dpkg-tmp ->
/usr/lib32/nvidia-current-updates/vdpau/libvdpau_nvidia.so
Might there be an issue with update alternatives or symlinks?
Maybe something with the setup that confuses /usr/lib with /usr/lib32 causing
the invalid links (and those "missing associated file messages").
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/826860
Title:
jockey installs nvidia-current-updates & then reports failure to
install
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/826860/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
