You are not logged in.
Hi, I am getting this error whenever I am trying to run megasync
error while loading shared libraries: libicuuc.so.74
.
I tried running
ldconfig -p | grep libicuuc
which gave me the following results
libicuuc.so.75 (libc6,x86-64) => /usr/lib/libicuuc.so.75
libicuuc.so (libc6,x86-64) => /usr/lib/libicuuc.so
So my libicuuc version is higher than the libcuuc version needed for megasync and since I don't think downgrading is a good idea, can I do anything else? I tried installing the app both from AUR and using Pacman to install the tar.gz package but I am getting same error on both.
Last edited by mr.monsterkoala (2024-06-15 15:30:13)
Offline
You will have to rebuild megasync against the new icu version.
Any other non-repo packages that depend on icu will also need rebuilding .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Thank you, by build do you mean NOT to install it using any AUR packages like yay and build it by downloading the github repo?
Offline
Thank you, by build do you mean NOT to install it using any AUR packages like yay and build it by downloading the github repo?
Please read the AUR wiki article again to understand what the AUR is and what it does. Rebuild means rebuilding it with makepkg, something yay will sometimes do and sometimes it won't. It's best to learn to do it the Arch way before you use tools like yay.
Offline
I build the package using makepkg and installed it using Pacman -U but I am still getting the same error whenever I am trying to run it.
Offline
If you ran just makepkg in the directory where it had been built previously, this is to be expected. You'd need to run `makepkg -f`.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Yeah, makepkg even tells you, that it didn't rebuild the package, because there still was one in the cache. Always read carefully and then "man makepkg".
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.
Online
What AUR package are you using, exactly?
Offline
If you ran just makepkg in the directory where it had been built previously, this is to be expected. You'd need to run `makepkg -f`.
Previously I was building through yay but I uninstalled the package and tried with makepkg -f however it's the same result.
Offline
What AUR package are you using, exactly?
Offline
Previously I was building through yay but I uninstalled the package and tried with makepkg -f however it's the same result.
I see, then you did most likely nothing wrong.
Scimmia wrote:What AUR package are you using, exactly?
The -bin suffix says, that the package has been pre-built and is only packaged and installed through the AUR. You should go to the AUR package page and read the comments there and if you have something new to add, write a comment yourself.
The maintainer of the package seems to be aware of the problem and upstream has to fix this. Since there is no source package we can build ourselves, upstream has to release an update first.
Offline
yes I saw the latest comments just now, seems like people are having similar issues, can only wait then.
Offline
yes I saw the latest comments just now, seems like people are having similar issues, can only wait then.
Or switch to the the none -bin package or use https://aur.archlinux.org/packages/icu74 then update the megasyc-bin package to depend upon it.
Last edited by loqs (2024-05-21 22:09:58)
Offline
Update on the issue, the upper stream package is still not fixed, however temporarily installing icu74 from AUR fixes the issue.
https://aur.archlinux.org/packages/icu74
Offline
Yea that one works!
Last edited by DeezUsers (2024-05-29 20:00:58)
Offline