hollywood
hollywood copied to clipboard
hollywood snap not working on Solus
Hey Dustin,
I've seen your talk about byobu and hollywood at UbuCon Europe in Paris last week and I've decided to try the snap :)
Unfortunately, I'm getting this when I try to start it:
marius@Lenovo-Carbon-X1-3rd ~ $ hollywood
/bin/bash: error while loading shared libraries: __vdso_time: invalid mode for dlopen(): Invalid argument
marius@Lenovo-Carbon-X1-3rd ~ $ snap --version
snap 2.27
snapd 2.27
series 16
solus 3
kernel 4.12.12-19.current
marius@Lenovo-Carbon-X1-3rd ~ $ lsb_release -a
LSB Version: 1.4
Distributor ID: Solus
Description: Solus
Release: 3
Codename: shannon
Hey Marius,
Hmm, I don't recognize that error...
I've copied Sergio and Alan, who might be able to help...
Sergio?
:-Dustin @dustinkirkland
On Wed, Sep 13, 2017 at 8:24 AM, Marius Quabeck [email protected] wrote:
Hey Dustin,
I've seen your talk about byobu and hollywood at UbuCon Europe in Paris last week and I've decided to try the snap :)
Unfortunately, I'm getting this when I try to start it:
marius@Lenovo-Carbon-X1-3rd ~ $ hollywood /bin/bash: error while loading shared libraries: __vdso_time: invalid mode for dlopen(): Invalid argument
marius@Lenovo-Carbon-X1-3rd ~ $ snap --version snap 2.27 snapd 2.27 series 16 solus 3 kernel 4.12.12-19.current
marius@Lenovo-Carbon-X1-3rd ~ $ lsb_release -a LSB Version: 1.4 Distributor ID: Solus Description: Solus Release: 3 Codename: shannon
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/dustinkirkland/hollywood/issues/19, or mute the thread https://github.com/notifications/unsubscribe-auth/AAzMhkByWHrO5QBpPUf-Tv0By50Ce5NRks5sh9dxgaJpZM4PWGpF .
Suspect glibc version or conflict - would suggest trying it on another machine, VM or container to rule out any glibc issues.
(Solus may be making slightly different changes to glibc versions/packages compared to Ubuntu/Debian/etc.)
Indeed, this is broken. I'm told by @sergiusens that he might have a fix for me in snapcraft/snapd?
solus or bust
It's likely because the snap is "classically" confined and is reliant on the OS's available libs. As the same libs aren't available in Solus (or other distros perhaps) including said libs in the snap build and then confining it (strict) would likely fix this.