Open leebaylis opened 3 years ago
However, neither package does anything to update LD_LIBRARY_PATH with the location of the library file, at
The libtls-padding0
package triggers the ldconfig trigger, so it's already updated. I also do not have this issue on my devices. The tls padding works as expected (I do not have an FP2 though).
I do not receive these messages when signing in to my FP2 via ssh. What is your current $LD_LIBRARY_PATH
in these shells? And, could you provide the output of ldconfig -p
?
https://gist.github.com/UniversalSuperBox/1cadf89dc2bc6442baa2fb1e1a32484a
Steps to reproduce
SSH into the phone and watch as the login scripts run.
Expected behavior
No error
Actual behavior
Multiple instances of this error: ERROR: ld.so: object 'libtls-padding.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
Logfiles and additional information
LD_PRELOAD on my system contains the entry
libtls_padding.so
this has been put there by the script
/etc/profile.d/ld_preload_tls_padding.sh
this script is installed by the package tls-padding, which also depends on libtls-padding0 which installs the library file itself.
However, neither package does anything to update LD_LIBRARY_PATH with the location of the library file, at
/usr/lib/arm-linux-gnueabihf/
and so any time LD_PRELOAD is called, these error messages are thrown.