gcarq / inox-patchset

Inox patchset tries to provide a minimal Chromium based browser with focus on privacy by disabling data transmission to Google.
BSD 2-Clause "Simplified" License
364 stars 26 forks source link

libicui18n.so.61 issue #159

Closed ghost closed 5 years ago

ghost commented 6 years ago

Error in Arch Linux after latest update on August 8th, 2018

/usr/lib/inox/inox: error while loading shared libraries: libicui18n.so.61: 
cannot open shared object file: No such file or directory
d-packs commented 6 years ago

This issue prevents inox from launching. Until there is an update, inox cannot be used on Arch. It seems this is the same error as #148 /usr/lib/inox/inox: error while loading shared libraries: libicui18n.so.61: cannot open shared object file: No such file or directory

Arch Linux packages state:

Inox Version: inox-bin 67.0.3396.87-1

ghost commented 6 years ago

@d-packs, Yes this is correct. "harfbuzz" and "icu" seems to break Inox anytime there is a new version. I can confirm that it doesn't work with "harfbuzz-icu 1.8.8-1" version too. And re-compiling Inox myself takes forever, hardware is just too old. So please fix this issue, by releasing new updated Inox version that works. Thank You!

ghost commented 6 years ago

It seems that you can manually copy those library files to make it work. Here is a temporary workaround.

This should do it. If it still doesn't work for you, run "inox" command in your terminal to see which other files you need to copy. This shouldn't affect any other software. So far so good, until we have proper inox-bin update ^_^ This works for any version of inox and icu, as far as my local tests go anyway...

Thrilleratplay commented 6 years ago

I switched from inox-bin to inox. It takes a while to compile but fixes the issue.

ghost commented 6 years ago

This above workaround is for existing installed inox. But if you want to use latest version of Chrome then recompiling is the way to go. But remember that the latest version of Chrome can have new features wich may prevent existing patches from working correctly.

keescpk commented 6 years ago

Have tried the workaround but it did not "work" for me , so based on the workaround, here is what i did. In the first two lines i replaced icu-62.1-1x86_64.pkg with icu-61.1-1-x86_64.pkg.tar.xz. Then i did the copy and install part of the workaround. Next i copied the files libicui18n.so61.1 from /usr/lib/backup to /usr/lib. And did the same with the files libicuuc.so.61.1 as well as libicudata.so61.1.

lightdot commented 5 years ago

The only proper way to fix this is to rebuild the inox (inox-bin) package.

In the mean time, this indeed works:

curl -Lo /tmp/icu-61.1-1-x86_64.pkg.tar.xz https://archive.archlinux.org/packages/i/icu/icu-61.1-1-x86_64.pkg.tar.xz
tar --wildcards --no-anchored --warning=none -xf /tmp/icu-61.1-1-x86_64.pkg.tar.xz *libicudata.so.61* *libicui18n.so.61* *libicuuc.so.61*
sudo mv /tmp/usr/lib/libicu*.so.61* /usr/lib
rm /tmp/icu-61.1-1-x86_64.pkg.tar.xz
rm -r /tmp/usr

Don't forget to remove /usr/lib/libicu.so.61 after inox has been rebuilt or updated:

sudo rm /usr/lib/libicu*.so.61*
ghost commented 5 years ago

Switching to "Ungoogled-Chromium" if anyone cares, as Inox no longer updated! You can find it here; https://github.com/Eloston/ungoogled-chromium