FS#39243 - [nvidia-304xx-utils] missing symlink for libEGL.so.1 after mesa ugrade to 10.1.0-2
Attached to Project:
Arch Linux
Opened by Peter Banks (pbanks) - Saturday, 08 March 2014, 21:35 GMT
Last edited by Laurent Carlier (lordheavy) - Sunday, 09 March 2014, 11:53 GMT
Opened by Peter Banks (pbanks) - Saturday, 08 March 2014, 21:35 GMT
Last edited by Laurent Carlier (lordheavy) - Sunday, 09 March 2014, 11:53 GMT
|
Details
After the upgrade to mesa 10.1.0-2 the file
/usr/lib/libEGL.so.1 was removed so as not to conflict with
blobs. This causes several applications (including evince
and awesome, the window manager) to cease to function
entirely, the exact error being "evince: error while loading
shared libraries: libEGL.so.1: cannot open shared object
file: No such file or directory". As I was using awesome as
my window manager, restarting X failed entirely, leaving me
with only ttys. This file is provided by mesa-libgl,
nvidia-libgl and nvidia-utils, which all provide libgl. As
nvidia-304xx-utils also provides libgl, trying to install
any of these packages results in an error. A possible fix to
this would be to create a symlink between
/usr/lib/libEGL.so.1 and /usr/lib/mesa-libEGL.so.1.0.0 (and
also for libEGL.so and libEGL.so.1.0.0). This file is
provided by mesa and is the one used before to provide
libEGL, so this should not introduce any new problems. This
is the solution I am currently using on my system, and seems
to work fine.
|
This task depends upon
Closed by Laurent Carlier (lordheavy)
Sunday, 09 March 2014, 11:53 GMT
Reason for closing: Fixed
Additional comments about closing: nvidia-304xx-utils 304.119-3
Sunday, 09 March 2014, 11:53 GMT
Reason for closing: Fixed
Additional comments about closing: nvidia-304xx-utils 304.119-3
See: https://bbs.archlinux.org/viewtopic.php?pid=1390131#p1390131
On my latop I just created the symlink as proposed as intermediate solution.
Please report to the maintainer of certain package in [unsupported]
Thanks, I'm sorry, but this happened after mesa upgrade and I thought it was a problem related to mesa package.