libssl.so.1.1 not available on newer Debian releases

[DamianHurschler]

Seems like an awesome piece of software, thank you for sharing! Sadly I haven't been able to use it so far:

• I'm on Debian 14:
  cat /proc/version
Linux version 6.12.17-amd64 (debian-kernel@lists.debian.org) (x86_64-linux-gnu-gcc-14 (Debian 14.2.0-17) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44) #1 SMP PREEMPT_DYNAMIC Debian 6.12.17-1 (2025-03-01)
• I followed the install instructions in the readme (install the dependencies, then install serial-monitor-x86_64-unknown-linux-gnu.deb.zip [v0.3.5.1])
• When clicking the 'Serial Monitor' icon on Gnome simply nothing happens.
• When trying to start it from terminal, I get the following:
  serial-monitor-rust
serial-monitor-rust: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory

As far as I can tell, the root cause is that later Debian versions no longer come with libssl (1.1.1w-0+deb11u2) but only with much later versions like libssl3.so [openssl (3.4.1-1)].

Sadly I'm not able to provide a fix. What I tried:

• Create symlink inside of /usr/lib/x86_64-linux-gnu from libssl.so.1.1 to libssl3.so, which ended up failing this way:
  serial-monitor-rust: /lib/x86_64-linux-gnu/libssl.so.1.1: version OPENSSL_1_1_1' not found (required by serial-monitor-rust)`
• Downloaded libssl1.1-udeb_1.1.1w-0+deb11u2_amd64.udeb and openssl_1.1.1w-0+deb11u2_amd64.deb and tried installing manually. But of course this leads to loads of dependency problems and would downgrade openssl on my OS, which is also not a good thing.
• Also this did not help me: https://stackoverflow.com/questions/72133316/libssl-so-1-1-cannot-open-shared-object-file-no-such-file-or-directory/72633324#72633324

Maybe a future release could be made compatible with later versions of openssl/libssl?

[hacknus]

Thank you for raising this issue! You mentioned that you installed the dependencies:

sudo apt-get install libxcb-render0-dev libxcb-shape0-dev libxcb-xfixes0-dev libxkbcommon-dev libssl-dev

can you tell me which version of libssl-dev it installed?

Unfortunately, I currently do not have a linux machine to test on.

What you could always do is install rust and compile it from source.

[hacknus]

it could be that this is an issue with how I bundled the dependencies in Cargo.toml :

deb_depends = ["libclang-dev", "libgtk-3-dev", "libxcb-render0-dev", "libxcb-shape0-dev", "libxcb-xfixes0-dev", "libxkbcommon-dev", "libssl-dev"]

I though just putting the same dependencies should work.
The dependencies are required by egui: https://github.com/emilk/egui

[DamianHurschler]

Running this again:
sudo apt-get install libxcb-render0-dev libxcb-shape0-dev libxcb-xfixes0-dev libxkbcommon-dev libssl-dev
I get:
libxcb-render0-dev is already the newest version (1.17.0-2+b1).
libxcb-shape0-dev is already the newest version (1.17.0-2+b1).
libxcb-xfixes0-dev is already the newest version (1.17.0-2+b1).
libxkbcommon-dev is already the newest version (1.7.0-2).
libssl-dev is already the newest version (3.4.1-1).

[hacknus]

Thanks! Interesting, I think the issue is that the github runner that compiled your release used the old libssl version, it reported this:

libssl-dev is already the newest version (1.1.1f-1ubuntu2.24).

it is running ubuntu-20.04 and the command it uses is:

sudo apt-get update && sudo apt-get install -y libclang-dev libgtk-3-dev libxcb-render0-dev libxcb-shape0-dev libxcb-xfixes0-dev libxkbcommon-dev libssl-dev libudev-dev && cargo install cargo-bundle

so I don't know why it is unable to get a newer version of libssl but you are? Do you have an idea?

[hacknus]

Okay, so I did some researchg: Apparently, Ubuntu 20.04 only comes with libssl1.1.1, If I switch to ubuntu-22.04 it should fix this issue, so I will update the runners and the next release should be compatible with your libssl version.

[DamianHurschler]

Wow you're fast, thx!
I would guess that me running Debian testing/sid and having the related repositories active, has me getting fairly up-to-date versions of most things (and evidently the number of issues is similar to when I was running stable, just a different kind of issue ;-).