You are not logged in.
Today I tried to start chromium, it will not start with the following error:
/usr/lib/chromium/chromium: error while loading shared libraries: libre2.so.0: cannot open shared object file: No such file or directory
I managed to solve the problem after downgrading the re2 package from:
re2-1:20200303-1-x86_64.pkg.tar.zst
to
re2-1:20200101-1-x86_64.pkg.tar.zst
I am using chromium-vaapi-bin and I am not 100% sure this problem will occur with the latest build (which I am waiting for a while to install hoping the binary package will appear in the aur without using deprecated repositories).
Offline
try:
sudo pacman -S re2
If you don't want chains on you hand and foot, your only escape is to switch to a free operating system
--richard stallman the great
Offline
Packages need rebuilt against new libs, that's totally normal. Anything outside the official repos isn't Arch's issue.
Offline
Mod note: Moving to AUR Issues.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
I had to do: sudo ln -s /usr/lib/libre2.so /usr/lib/libre2.so.0
This is probably not the ideal solution, though.
Offline
I had to do: sudo ln -s /usr/lib/libre2.so /usr/lib/libre2.so.0
This is probably not the ideal solution, though.
It's far more than "not ideal", it's completely idiotic. Do NOT post things like this that may make people think this is an actual solution.
Offline
Well, it got Chromium from "doesn't start at all" to "unstable but usable". If you have a proper fix, I'd love to hear it.
Offline
Well, it got Chromium from "doesn't start at all" to "unstable but usable". If you have a proper fix, I'd love to hear it.
Packages need rebuilt against new libs, that's totally normal. Anything outside the official repos isn't Arch's issue.
Library versions are changed to indicate the interface has changed in an incompatible way. Symlinking to the old version ignores that change resulting in undefined behavior.
https://github.com/google/re2/issues/243
Last edited by loqs (2020-03-21 00:57:14)
Offline
Right, and what do users need to do about that? That issue was closed 19 days ago but I don't see an update in pacman. Do I need to recompile something manually? Is there supposed to be an update and something's gone wrong on my end? Are we to just not use Chromium until the fix gets pushed?
To answer my own question without any name-calling, the package "ungoogled-chromium-bin" hasn't been updated, so I need to switch to "ungoogled-chromium" and spend 12 hours compiling it.
Offline
Update in pacman? You're not running Chromium from the Arch repos, it's YOUR responsibility.
Offline
so I need to switch to "ungoogled-chromium" and spend 12 hours compiling it.
I would not do that. Is there something ungoogled chromium does that one of these won't?
https://wiki.archlinux.org/index.php/Li … b_browsers
Or you could get a stand alone browser and use it until chromium is fixed.
https://linux.palemoon.org/
Offline
To answer my own question without any name-calling, the package "ungoogled-chromium-bin" hasn't been updated, so I need to switch to "ungoogled-chromium" and spend 12 hours compiling it.
The package was removed. https://lists.archlinux.org/pipermail/a … 36088.html
https://software.opensuse.org//download … d-chromium
Last edited by loqs (2020-03-22 17:48:54)
Offline