For testing my hack to fix this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1395366 I renamed libepoxy.so.0.0.0 to libepoxy.so.0.0.0.orig and put my own hacked version of libepoxy.so.0.0.0 in the /lib64 directory in place of the orig. Things worked for a while, then started failing again, and now I notice that I have these symlinks: tomh> ls -l /lib64/libepoxy* lrwxrwxrwx 1 root root 17 Feb 4 2016 /lib64/libepoxy.so -> libepoxy.so.0.0.0* lrwxrwxrwx 1 root root 22 Nov 21 10:03 /lib64/libepoxy.so.0 -> libepoxy.so.0.0.0.orig* -rwxr-xr-x 1 root root 4588616 Nov 16 09:05 /lib64/libepoxy.so.0.0.0* -rwxr-xr-x. 1 root root 1031200 Feb 4 2016 /lib64/libepoxy.so.0.0.0.orig* So somehow the renamed file got linked back in to libepoxy.so.0. My current theory is that maybe updating something completely different ran ldconfig, and ldconfig rewrote the symlink. Does that sound believable? Maybe I need to move the orig file to some place other than the /lib64 directory... _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
