libertine complains about LD_PRELOAD libtls-padding.so

doniks

I notice that when I enter a libertine container with libertine-launch I get the following errors

phablet@deb:~$ libertine-launch -i xenial /bin/bash
ERROR: ld.so: object 'libtls-padding.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
: Xmir is not running on DISPLAY  !
ERROR: ld.so: object 'libtls-padding.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libtls-padding.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libtls-padding.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libtls-padding.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libtls-padding.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.

If I clear the variable I don't get the error

phablet@deb:~$ LD_PRELOAD= libertine-launch -i xenial /bin/bash
: Xmir is not running on DISPLAY  !

But, I'm unsure, should the variable be cleared? Or should this lib be available inside? I think this is somewhat new, I haven't seen this in the past.

dobey

This exists since OTA-16, as Qt 5.12 upgrade exposed some issues with TLS padding in bionic libc vs gnu libc, which we had to work around with an LD_PRELOAD lib. If you install the tls-padding package inside the container (ie, libertine-container-manager install-package -i xenial -p tls-padding), the ld.so messages should go away, I think.