Bug#927731: epiphany-browser/i386: private libdazzle not loaded

Simon McVittie smcv at debian.org
Mon Apr 22 10:22:22 BST 2019


Control: retitle -1 epiphany-browser/i386: private libdazzle not loaded

On Mon, 22 Apr 2019 at 10:29:15 +0800, 積丹尼 Dan Jacobson wrote:
> Users will get the message
> 
>     Error loading module
>     '/usr/lib/i386-linux-gnu/epiphany-browser/web-extensions/libephywebextension.so':
>     libdazzle-1.0.so.0: cannot open shared object file: No such file or
>     directory

It's meant to load a private copy from
/usr/lib/i386-linux-gnu/epiphany-browser (the version of libdazzle in
buster is too old for epiphany-browser).

I'm not sure why that isn't working for you: the amd64 version seems to
work without warnings. libephywebextension.so has:

Dynamic Section:
  NEEDED               libephymisc.so
  NEEDED               libgobject-2.0.so.0
  NEEDED               libglib-2.0.so.0
  NEEDED               libgio-2.0.so.0
  NEEDED               libsoup-2.4.so.1
  NEEDED               libwebkit2gtk-4.0.so.37
  NEEDED               libjavascriptcoregtk-4.0.so.18
  NEEDED               libc.so.6
  SONAME               libephywebextension.so
  RUNPATH              /usr/lib/i386-linux-gnu/epiphany-browser

so the runtime linker should automatically be loading all libraries it
depends on from its RUNPATH, /usr/lib/i386-linux-gnu/epiphany-browser.

Does this perhaps depend on settings or something? If you create a new
temporary user account, log in as the new user and run epiphany-browser,
do you get the same warnings?

    smcv



More information about the pkg-gnome-maintainers mailing list