thread '<unnamed>' panicked at src/lib.rs:997:52

[Fd929c2CE5fA]

04.04.26: - Make Wayland default disable with PIXELFLUX_WAYLAND=false.

But since Wayland is now used by default, I seem to be running into another issue.

Originally posted by @Fd929c2CE5fA in #4

Now I can't run without PIXELFLUX_WAYLAND=false, is this expected?

[migrations] started
[migrations] no migrations found
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    1000
User GID:    1000
───────────────────────────────────────
Linuxserver.io version: 6.8.2-ls44
Build-date: 2026-05-31T12:09:48+00:00
───────────────────────────────────────
    
[ls.io-init] Generating labwc rc.xml from template
which: no nvidia-smi in (/command:/lsiopy/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin)
[custom-init] No custom files found, skipping...
[svc-de] Wayland mode: Waiting for socket at /config/.XDG/wayland-1...
2026/06/06 21:19:51 [warn] 244#244: could not build optimal types_hash, you should increase either types_hash_max_size: 1024 or types_hash_bucket_size: 64; ignoring types_hash_bucket_size
[ls.io-init] done.
19
20
INFO:selkies.__main__:Starting mode 'websockets'...
INFO:selkies.__main__:Starting Selkies in 'websockets' mode.
INFO:data_websocket:pcmflux library found. Audio capture is available.
INFO:data_websocket:pixelflux library found. Striped encoding modes available.
[Wayland] DRINODE unset. Initializing Software Renderer (Pixman).

thread '<unnamed>' panicked at src/lib.rs:997:52:
called `Result::unwrap()` on an `Err` value: Io(Os { code: 95, kind: Unsupported, message: "Operation not supported" })
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
INFO:selkies.__main__:Starting mode 'websockets'...
INFO:selkies.__main__:Starting Selkies in 'websockets' mode.
INFO:data_websocket:pcmflux library found. Audio capture is available.
INFO:data_websocket:pixelflux library found. Striped encoding modes available.
[Wayland] DRINODE unset. Initializing Software Renderer (Pixman).

thread '<unnamed>' panicked at src/lib.rs:997:52:
called `Result::unwrap()` on an `Err` value: Io(Os { code: 95, kind: Unsupported, message: "Operation not supported" })
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
INFO:selkies.__main__:Starting mode 'websockets'...
INFO:selkies.__main__:Starting Selkies in 'websockets' mode.
INFO:data_websocket:pcmflux library found. Audio capture is available.
INFO:data_websocket:pixelflux library found. Striped encoding modes available.
[Wayland] DRINODE unset. Initializing Software Renderer (Pixman).

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[thelamer]

I cannot replicate this, start with a simple test and move up from there.

docker run --rm -it -p 3001:3001 --shm-size=1gb -e PIXELFLUX_WAYLAND=false linuxserver/telegram bash

[Fd929c2CE5fA]

I cannot replicate this, start with a simple test and move up from there.

docker run --rm -it -p 3001:3001 --shm-size=1gb -e PIXELFLUX_WAYLAND=false linuxserver/telegram bash

I already said it works when PIXELFLUX_WAYLAND=false was included, If I didn't make it clear.

[thelamer]

It just seems like it does not work on your system, and you did not post anything about your system.
https://ci-tests.linuxserver.io/linuxserver/telegram/latest/index.html

[Fd929c2CE5fA]

In fact, I'm guessing it might be due to some pollution of the config directory.

When I deleted the directory, the issue disappeared.

The problem is that I have never manually made any modifications to the config directory content, but I was running the x11 default environment before, and when the new version defaulted to Wayland, the problem arose.

I think this default setting change may be backwards incompatible.

Obviously your CI tests don't cover this situation.