Sunshine fails to start in Archlinux, icu has updated to 76 but it's linking to 75

[knyipab]

Describe the Bug

sunshine: error while loading shared libraries: libicuuc.so.75: cannot open shared object file: No such file or directory

Likely becuz arch is providing /usr/lib/libicuuc.so.76. Ever consider to link to /usr/lib/libicuuc.so instead?

Also, it's not the latest version (v2025.122.141614 is the latest). Ever consider to make a Github action to automate this? Thanks.

Expected Behavior

No response

Additional Context

No response

[ReenigneArcher]

Also, it's not the latest version. Ever consider to make a Github action to automate this? Thanks.

What do you mean by this? What isn't the latest version? This runs automatically in a GitHub workflow everyday to rebuild things.

[knyipab]

Sorry, I think I mistaken the release shown in LizardByte/pacman-repo-builder to be the latest of pacman repo. And perhaps that's not true and please ignore if that's the case and focus on the ICU issue. Thank you~

[samvv]

I'm running Arch, configured an Arch VM with Sunshine yesterday and am not seeing this issue.

[murkl]

Strange, I also get the error on startup under Arch Linux: sunshine: error while loading shared libraries: libicuuc.so.75: cannot open shared object file: No such file or directory

Workaround: I have installed icu75 from the AUR.

[ZenMaxe]

This issue is caused by a partial update. If you primarily use the AUR, your yay/paru might not have detected the compatibility issue and updated icu separately.

To fix this, you need a full system update:

sudo pacman -Syu

This should resolve the issue.

[knyipab]

@ZenMaxe

Fyip, I do not use AUR or yay at all. And I always upgrade my system using sudo pacman -Syu.

Fyi, my computer has
sunshine v2025.122.141614-1
icu 76.1-1

[murkl]

This issue is caused by a partial update. If you primarily use the AUR, your yay/paru might not have detected the compatibility issue and updated icu separately.

To fix this, you need a full system update:

sudo pacman -Syu

This should resolve the issue.

That is certainly not the problem! The icu package was updated on 2025-02-20 and I think since then it doesn't work anymore, because sunshine needs version 75 and this is now 76.

[ReenigneArcher]

The icu package was updated on 2025-02-20

Sunshine is rebuilt every single day, so you need to update/re-install it whenever you do a pacman update.

[knyipab]

I see and should be workarounded by sudo pacman -S sunshine.

So this sunshine package and pacman repo do not work like the usual archlinux packages which increment pkgrel in every rebuild. Since pkgrel is not incremented, users will not receive a newer build by running the usual sudo pacman -Syu. Instead, users would have to re-install the package specifically and manually by sudo pacman -S sunshine whenever they observe incompatibility.

This appears to be not intuitive. Does it sound better to increment pkgrel whenever any of its dependencies gets upgraded (deps pkgver+pkgrel)? Perhaps some build system could have relevant automation but I am not sure where we can find.

Edit: Another idea: if nothing in deps has changed, does rebuild gives the file of same checksum? If so, can we increment pkgrel by detecting a change in checksum?

[ReenigneArcher]

@knyipab I agree it's not intuitive. The easiest thing is probably to compare the checksums and bump the pkgrel accordingly. I guess something would need to be added to https://github.com/LizardByte/pacman-repo-builder ... I'll accept a PR but for now I don't plan on doing this myself.

It might be easier to just static link dependencies in Sunshine and then this issue wouldn't even pop up.

[murkl]

I see and should be workarounded by sudo pacman -S sunshine.

So this sunshine package and pacman repo do not work like the usual archlinux packages which increment pkgrel in every rebuild. Since pkgrel is not incremented, users will not receive a newer build by running the usual sudo pacman -Syu. Instead, users would have to re-install the package specifically and manually by sudo pacman -S sunshine whenever they observe incompatibility.

This appears to be not intuitive. Does it sound better to increment pkgrel whenever any of its dependencies gets upgraded (deps pkgver+pkgrel)? Perhaps some build system could have relevant automation but I am not sure where we can find.

Edit: Another idea: if nothing in deps has changed, does rebuild gives the file of same checksum? If so, can we increment pkgrel by detecting a change in checksum?

Great, sudo pacman -S sunshine solves the problem!