servo: Nigthly won't start on some linux distros : fedora 24 / 23, debian testing

[ludo@Oulanl ~]$ cd servo/
[ludo@Oulanl servo]$ ./runservo.sh 
./servo: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory
[ludo@Oulanl servo]$ 

About this issue

  • Original URL
  • State: closed
  • Created 10 years ago
  • Reactions: 32
  • Comments: 79 (17 by maintainers)

Commits related to this issue

Most upvoted comments

This is still happening 😦

Yep, reproducible on Fedora-26 w/ all updates and latest servo nightly.

I’ve created a small Makefile to build a flatpak wrapping the servo nightlies, see

We could take it from here and use this (or alike) in the servo nightly build process, and push those builds to flathub (once it’s back online).

Fedora 25, today’s buid : Still

This is still reproducible on Fedora 27 (Beta) with the latest nightly

Can confirm that this issue remains on Fedora 25 on today’s build.

One of the ways to solve the soname problems once and for all would be to build flatpaks and distribute them instead: http://flatpak.org/developer.html http://flatpak.org/

openssl would I think be packaged via the runtime, so it could be updated without the intervention of servo.

The only requirement is that flatpak and the runtime are installed, but fedora already ships with flatpak, and debian based distros have a flatpak ppa.

To me this sounds like a build machine issue: For some reason, the machine doing the build uses a pretty old version of libssl, namely some variant of 1.0.0, and hence that’s what the binary links to. The OpenSSL website says

The 0.9.8, 1.0.0 and 1.0.1 versions are now out of support and should not be used.

So, probably what should happen is that the build machine gets updated to a non-legacy version of OpenSSL?

Just checked latest nightly on F27:

./servo: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory

Why not simply bundle libssl ? This is a nightly, and software you shouldn’t be running longer than a day without updating. Or am I missing something ?

same error fedora 29 - it’d be good to bundle that lib into the project

Nothing changed with F27 coming out of Beta.

This is a problem which has occurred due to the machine which creates the builds using outdated versions (from 2013) of the OpenSSL libraries (libssl and libcrypto on Fedora). There are currently only two solutions to this problem:

  1. Build Servo on the system you plan to use it on. This will link the new libraries to your own build of Servo automatically. This is currently the best method to run Servo on systems which do not hold copies of the OpenSSL 1.0.0 libraries.
  2. Downgrade your libraries NOT RECOMMENDED UNDER ANY CIRCUMSTANCE. This would be difficult to do on Fedora as the repositories do not hold the 1.0.0 packages for the OpenSSL libraries any more (they were available on Fedora 13). These would have to be compiled on your system independent of a package manager, as DNF will not allow you to do so.

Symbolic linking will not solve this issue it will simply cause the problem that @daboross was having, where the libraries used by the official nightly build of Servo still do not actually exist on your system.

I think the nightlies need to be built against a newer openssl to work smoothly on Fedora. Maybe another travis job can be added?

Servo compiles on my system against OpenSSL 1.1 just fine.

@StefanoD No, that’s the only logical solution, and it’s the one that takes the least amount of time on the part of us and the maintainers. (Apt install or dnf install, anyone?)

@axvr It won’t build on my machine, tried three times last night 😦

I am hijacking libraries from ubuntu debs as per a reddit thread, but Fedora 13? How do you maintain a build machine without updates for eons like that? So the build machine hasn’t been updated in 4 YEARS? That’s a long time, amigo.

By the way: You could do a snap package. It is stable (version 1.0+) and runs on Fedora as well.