Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

(Bug) Can't launch AppImage on CachyOS KDE Wayland

Open
  • Is something wrong?
#1,155 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
linux, rust
Domain
computer-graphics, desktop

Research direction

The panic is at opengl_cx.rs:88 in the Makepad platform crate, not in Robrix itself, and the log points to the Wayland backend selection at linux_wayland.rs:155. Start by reading how the EGL platform display is chosen on Wayland, and reproduce by launching on a Wayland session with the same GPU. Done means the app starts on Wayland with GPU rendering, or fails with a clear message instead of a panic.

Written by the indexing model from the issue text.

Description

The AppImage can't use the Mesa3D AMD Vulkan and OpenGL ES drivers, also don't fallback to Lavapipe or LLVMPipe.

Environment
  • OS: CachyOS
  • KDE Plasma version: 6.7
  • GPU: AMD
  • Vulkan version: 1.4.357
Log
❯ ./robrix-1.0.0-beta.3-x86_64.appimage
WAYLAND_DISPLAY: wayland-0
DISPLAY: :0
XDG_SESSION_TYPE: wayland
XDG_CURRENT_DESKTOP: KDE
Selected: Wayland backend
Reason: WAYLAND_DISPLAY environment variable is set
[I] /home/runner/.cargo/git/checkouts/makepad-69d78fae78fc8901/736c5ca/platform/src/os/linux/wayland/linux_wayland.rs:155:25 - Vulkan unavailable (Vulkan driver is missing VK_KHR_surface); rendering with OpenGL ES

thread 'main' (2701012) panicked at /home/runner/.cargo/git/checkouts/makepad-69d78fae78fc8901/736c5ca/platform/src/os/linux/opengl_cx.rs:88:9:
can't get EGL platform display
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Dominant language
Rust
Stars
489
Forks
71
Avg merge
1h 27m
Merged PRs (30d)
72

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from project-robius/robrix

All issues in project-robius/robrix

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.