[ENG-1286] Spacedrive fails to start after .deb install

[gedeondoescode]

Describe the bug

After installing the .deb package, the application fails to load. After running the application from the command line, it returns the following error:

spacedrive: error while loading shared libraries: libavutil.so.56: cannot open shared object file: No such file or directory

Reproduction

1. Install Spacedrive via deb package
2. Run for the first time
3. See nothing

Expected behavior

See the window open on the onboading page.

Platform and versions

OS: Ubuntu Budgie 23.04

Stack trace

No response

Additional context

No response

[julianbraha]

I have the same issue on Pop OS 22.04.

When I tried running spacedrive from the command line, I get this error: spacedrive: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory

Ubuntu 22.04 uses libssl3, and version 1.1 is deprecated. See: https://askubuntu.com/a/1412746

[HeavenVolkoff]

Thanks for reporting this issue. I'm centralizing all the problems related to the deb release here:

• Missing libssl.so.1.1 in the dependency list. [ENG-1325] Vendor openssl in tauri #1636
• Linking against libssl.so.1.1 not present in newer Debian/Ubuntu (and derivatives) versions. [ENG-1325] Vendor openssl in tauri #1636
• Linking against old FFmpeg versions not found in newer Debian/Ubuntu (and derivatives) versions. [ENG-1184, ENG-1286, ENG-1330] Rework native dependencies (+ deb fixes) #1685
• .desktop file has wrong permission [ENG-1184, ENG-1286, ENG-1330] Rework native dependencies (+ deb fixes) #1685
• Spacedrive binary does not have executable permission for some installs (reported on discord) [ENG-1184, ENG-1286, ENG-1330] Rework native dependencies (+ deb fixes) #1685
• GBM buffer / EGL images - Permission denied (app crash on startup) with nvidia proprietary drivers
  • Webkit issue, already fixed on Debian stable, should land on Ubuntu soon
  • Workaround: set this environment variable WEBKIT_DISABLE_DMABUF_RENDERER=1 before launching Spacedrive

The linking issues likely stem from distributing a single deb package, built on Ubuntu 20.04, for all platforms. I will work on addressing this by either vendoring some of these dependencies and/or releasing multiple deb packages targeting more recent versions of Debian/Ubuntu.

[loveyu]

in debian 12 kde:

• spacedrive: error while loading shared libraries: libavformat.so.58: cannot open shared object file: No such file or directory
• spacedrive: error while loading shared libraries: libavfilter.so.7: cannot open shared object file: No such file or directory

$ffmpeg -version

ffmpeg version 5.1.3-1 Copyright (c) 2000-2022 the FFmpeg developers
built with gcc 12 (Debian 12.2.0-14)
libavutil      57. 28.100 / 57. 28.100
libavcodec     59. 37.100 / 59. 37.100
libavformat    59. 27.100 / 59. 27.100
libavdevice    59.  7.100 / 59.  7.100
libavfilter     8. 44.100 /  8. 44.100
libswscale      6.  7.100 /  6.  7.100
libswresample   4.  7.100 /  4.  7.100
libpostproc    56.  6.100 / 56.  6.100

[TheGB0077]

As I understand OpenSSL is a Tauri dependency because it computes SHA256 hashes with it, so I suppose that there is no replacement for it.

So, perhaps the most straightforward way to fix this, would be to provide two .deb packages. One built on an Ubuntu 20 machine, for backwards compatibility sake, and the other with Ubuntu 22.

Otherwise embedding the missing libs directly could be the preferred choice.

[TheGB0077]

The .desktop file was copied without a read permission, thus the desktop entry cannot be accessed.

[TheGB0077]

Here's some additional linting:

[hobofan]

@TheGB0077

As I understand OpenSSL is a Tauri dependency because it computes SHA256 hashes with it, so I suppose that there is no replacement for it.

There is a replacement for it. OpenSSL is a dependency of native-tls, which apart from tauri is also pulled in by spacedrive via the reqwest and tokio-tls crates. There is usually an option for most crates that use native-tls to instead use rustls which will by default be statically linked into the final binary. That usually makes distribution easier, but as switch of dependencies also comes with some trade-offs, which I'm not sure the Spacedrive team would like to make.

[HeavenVolkoff]

I have finished addressing the issues with the deb release. A test version with the latest changes is available here for anyone who wants to try it out and check if it installs and runs correctly.

[gedeondoescode]

I’ll set up a VM and see if it works later today

[gedeondoescode]

@HeavenVolkoff Install went perfectly with my Ubuntu 23.10 VM. However, the window failed to fully load on my end. Will need someone else to confirm that this isn't a persistent issue.

[Upellift99]

It's working on my Ubuntu 22.04 LTS !

[HeavenVolkoff]

@HeavenVolkoff Install went perfectly with my Ubuntu 23.10 VM. However, the window failed to fully load on my end. Will need someone else to confirm that this isn't a persistent issue.

There is currently an issue with webkit2gtk and software rendering (such as llvmpipe, which is normally used in VMs) in which the web content fails to render or renders incorrectly. Can you check if you are using software rendering and if so could you try running Spacedrive with hardware rendering (such as virgl) or bare meal, just to make sure this issue is unrelated with the deb itself.

You can check what driver you are using for rendering with:
glxinfo | awk -F':' '$1 ~ /Device|OpenGL renderer/ {print $2}'
glxinfo is from the mesa-utils package

EDIT: Was looking more into this issue and there seems to be a work-around. Running with env WEBKIT_DISABLE_COMPOSITING_MODE=1 spacedrive fix the rendering errors in my test Ubuntu VM when using llvmpipe.

[gedeondoescode]

I'll see what I can do

[gedeondoescode]

Works after bare metal install of Ubuntu 23.10 @HeavenVolkoff

[HeavenVolkoff]

Thanks to everyone that contributed to this issue report and to @gedeondoescode and @Upellift99 for the post-fix tests. If anyone has any new problem with the deb release, please fell free to open a new issue