thread 'main' panicked at 'Failed to initialize any backend! Wayland status: NoCompositorListening X11 status:

[mb0x88]

Describe the bug
Opening sniffnet I get an error

thread 'main' panicked at 'Failed to initialize any backend! Wayland status: NoCompositorListening X11 status: LibraryOpenError(OpenError { kind: Library, detail: "opening library failed (libX11.so.6: cannot open shared object file: No such file or directory); opening library failed (libX11.so: cannot open shared object file: No such file or directory)" })', /github/home/.cache/Homebrew/cargo_cache/registry/src/gitlite.zycloud.tk-1ecc6299db9ec823/winit-0.27.5/src/platform_impl/linux/mod.rs:719:9 note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

To Reproduce
Describe steps to reproduce the bug, e.g.:

1. Open terminal and type sniffnet

Expected behavior
I expected sniffnet to start running

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS:ParrotOS 6.0.0-12parrot1-amd64
• Browser N/A

Additional context
I installed with brew and installed all dependencies

[GyulyVGC]

Try installing libx11-xcb-dev and let me know if you solve the problem

[mb0x88]

no i get the same error after installing it

[3asyAiden]

I'm facing the same issue, and the same after installing libx11-xcb-dev.

[GyulyVGC]

I'm facing the same issue, and the same after installing libx11-xcb-dev.

On which OS? @NULLAiden

[GyulyVGC]

As last resort, I can suggest you try to install libx11-xcb1.
Please let me know if the problem persists.

[Albonycal]

I am facing the same issue.
OS: Archlinux
Using hyprland twm (Wayland)

[GyulyVGC]

I am facing the same issue.
OS: Archlinux
Using hyprland twm (Wayland)

Did you install the app via pacman?

[Albonycal]

Yeah from the arch repos

[yermulnik]

Should I file standalone ticket for the alike error?

thread 'main' panicked at 'Failed to initialize any backend! Wayland status: NoCompositorListening X11 status: LibraryOpenError(OpenError { kind: Library, detail: "opening library failed (libXcursor.so.1: cannot open shared object file: No such file or directory); opening library failed (libXcursor.so: cannot open shared object file: No such file or directory)" })', /github/home/.cache/Homebrew/cargo_cache/registry/src/gitlite.zycloud.tk-1ecc6299db9ec823/winit-0.27.5/src/platform_impl/linux/mod.rs:719:9

(affected both of mine Ubuntu Bionic and Ubuntu Jammy)

UPD: on both systems

> dpkg -L libxcursor1
/.
/usr
/usr/lib
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libXcursor.so.1.0.2
/usr/share
/usr/share/doc
/usr/share/doc/libxcursor1
/usr/share/doc/libxcursor1/changelog.Debian.gz
/usr/share/doc/libxcursor1/copyright
/usr/lib/x86_64-linux-gnu/libXcursor.so.1

UPD2: on both installed via Homebrew

[GyulyVGC]

After Googling for some possible solution, I've found out that it could be related to the GUI.
Before asking you to install other dependencies, can you guys try if this version of sniffnet solves the issue?

sniffnet_1.2.0_amd64.deb.zip

It's built using an alternative graphical renderer (glow instead of wgpu).

[yermulnik]

@GyulyVGC
On my local Ubuntu Bionic:

> /usr/bin/sniffnet
/usr/bin/sniffnet: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory

On remote Ubuntu Jammy via SSH works fine.

Which version of OpenSSL does libssl.so.3 belong in? Bionic looks to have 1.1.1.

[GyulyVGC]

@yermulnik I'm happy it now works on your Ubuntu Jammy at least.

Have a look at #199 where earlier we discussed about a problem which could be related to yours.
We hope to solve it with the next release.

[yermulnik]

@GyulyVGC Despite packaging complexity for Linux distros because there are some in the wild, it shouldn't be a big deal to package binaries for most of the LTSes of common platforms — there are quite a few of them actually — though (to continue about "despite..." that I started with) I do have Homebrew installed along with openssl@3 and respectively with libssl.so.3, hence, probably, packaging the updated binary for Homebrew would fix the issue for me on Bionic as well 👍🏻 Works for me... though having packages for package managers of most common Linux distros (inc LTS) may give this project a pretty good kick to broader popularity 🤞🏻