You are not logged in.
Pages: 1
System: Arch64 /w multlib enabled running kernel 3.0.7-1 with the Nvidia proprietary blob
After switching from the official Nvidia blob to Nouveau and back, I have found that Clementine (music player) does not function correctly. Upon entering the program in a terminal window, the application fails to launch with this message:
clementine: error while loading shared libraries: libGLU.so.1: cannot open shared object file: No such file or directory
Only the multilib equivalent /usr/lib32/libGLU.so.1 is found on the filesystem.
Believing this error to be caused by the mesa package itself, I took the liberty of checking the package, only to find this mysterious result:
$ pacman -Ql mesa
$
The package mesa does not appear to install any files. Reinstallation of the package does not have effect on the results. I am not sure if this is a product of my own negligence, but I do not recall deviating from the installation instructions for both Nouveau and the official Nvidia blobs.
Any advice would be much appreciated.
Last edited by jengajam3 (2011-10-22 04:25:23)
Offline
On my machine
$ pacman -Ql mesa
mesa /usr/
mesa /usr/include/
mesa /usr/include/GL/
mesa /usr/include/GL/GLwDrawA.h
mesa /usr/include/GL/GLwDrawAP.h
mesa /usr/include/GL/GLwMDrawA.h
mesa /usr/include/GL/GLwMDrawAP.h
mesa /usr/include/GL/gl.h
mesa /usr/include/GL/gl_mangle.h
mesa /usr/include/GL/glext.h
mesa /usr/include/GL/glfbdev.h
mesa /usr/include/GL/glu.h
mesa /usr/include/GL/glu_mangle.h
mesa /usr/include/GL/glx.h
mesa /usr/include/GL/glx_mangle.h
mesa /usr/include/GL/glxext.h
mesa /usr/include/GL/internal/
mesa /usr/include/GL/internal/dri_interface.h
mesa /usr/include/GL/mesa_wgl.h
mesa /usr/include/GL/osmesa.h
mesa /usr/include/GL/vms_x_fix.h
mesa /usr/include/GL/wglext.h
mesa /usr/include/GL/wmesa.h
mesa /usr/lib/
mesa /usr/lib/libGLU.so
mesa /usr/lib/libGLU.so.1
mesa /usr/lib/libGLU.so.1.3.071100
mesa /usr/lib/libGLw.so
mesa /usr/lib/libGLw.so.1
mesa /usr/lib/libGLw.so.1.0.0
mesa /usr/lib/pkgconfig/
mesa /usr/lib/pkgconfig/dri.pc
mesa /usr/lib/pkgconfig/gl.pc
mesa /usr/lib/pkgconfig/glu.pc
mesa /usr/lib/pkgconfig/glw.pc
mesa /usr/share/
mesa /usr/share/licenses/
mesa /usr/share/licenses/mesa/
mesa /usr/share/licenses/mesa/LICENSE
Last edited by skunktrader (2011-10-22 03:30:38)
Offline
Maybe posting the output of these two will shine some light:
grep -B 1 Include /etc/pacman.conf
grep -v "#" /etc/pacman.d/mirrorlist
--EDIT--
After re-reading and seeing that I misread your post, my suggestion probably won't help. I would check to see if you have any 'zero-byte' mesa files in your cache:
ls -al /var/cache/pacman/pkg/ | grep mesa
Last edited by skottish (2011-10-22 04:14:14)
Offline
Maybe posting the output of these two will shine some light:
grep -B 1 Include /etc/pacman.conf
grep -v "#" /etc/pacman.d/mirrorlist
--EDIT--
After re-reading and seeing that I misread your post, my suggestion probably won't help. I would check to see if you have any 'zero-byte' mesa files in your cache:
ls -al /var/cache/pacman/pkg/ | grep mesa
ls -al /var/cache/pacman/pkg/ | grep mesa
-rw-r--r-- 1 root root 161420 Aug 3 05:17 lib32-mesa-7.11-2-x86_64.pkg.tar.xz
-rw-r--r-- 1 root root 280220 Aug 31 02:44 mesa-7.11-2-x86_64.pkg.tar.xz
-rw-r--r-- 1 root root 75768 Oct 9 2010 mesa-demos-8.0.1-1-x86_64.pkg.tar.xz
Everything seems to be in order
I have resolved the problem by removing mesa and then forcing an upgrade by running
pacman -S --force mesa
To all future readers: this command is potentially harmful, as this installation ignores all conflict checks and overwrites conflicting files.
Last edited by jengajam3 (2011-10-22 04:37:16)
Offline
I have resolved the problem by removing mesa and then forcing an upgrade by running
pacman -Sf mesa
To all future readers: this is potentially harmful, as the installation ignores all conflict checks and overwrites conflicting files.
A bit OT: copy-pasting that line may not work due to http://mailman.archlinux.org/pipermail/ … 14589.html (I think it's for pacman 4.1)
Offline
A bit OT: copy-pasting that line may not work due to http://mailman.archlinux.org/pipermail/ … 14589.html (I think it's for pacman 4.1)
Fixed
Seems like a good idea IMHO
Last edited by jengajam3 (2011-10-22 04:40:18)
Offline
Pages: 1