Bug: <EGL_BAD_PARAMETER>

[estem8]

---

Bug Description

Launching the AltSendme_0.2.4_amd64.AppImage on CachyOS (Wayland session) causes the application to terminate immediately with an EGL initialization error.
The UI never appears. The issue occurs 100% of the time.

Error displayed on every launch:

Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...

This affects the sender side (the application cannot start).

Steps to Reproduce

1. Download AltSendme_0.2.4_amd64.AppImage.
2. Mark it as executable:
   chmod +x AltSendme_0.2.4_amd64.AppImage
3. Launch it normally:
   ./AltSendme_0.2.4_amd64.AppImage
4. The application immediately exits with an EGL initialization error.

Additional attempts (same result):

• WINIT_UNIX_BACKEND=x11 ./AltSendme_0.2.4_amd64.AppImage
• WINIT_UNIX_BACKEND=wayland ./AltSendme_0.2.4_amd64.AppImage

Environment

• AltSendme version(s): 0.2.4 (AppImage)

• OS: CachyOS (Arch-based, rolling release)

• Session: Wayland

  • XDG_SESSION_TYPE=wayland
  • WAYLAND_DISPLAY=wayland-0
  • DISPLAY=:0

• GPU: AMD Radeon RX 9070 XT (radeonsi)
  Mesa version: 25.2.7-cachyos1.2

• Kernel: 6.17.8-2-cachyos

• Network: N/A (UI fails before any connection)

• Ticket / connection code: N/A

• Transfer type / size: N/A (application does not start)

Logs / Diagnostics

Main output:

2025-11-24T15:06:58.024739Z  INFO ThreadId(01) alt_sendme: 58: Starting Sendme Desktop application v0.2.4
Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...

Trying forced backends:

WINIT_UNIX_BACKEND=x11 ./AltSendme_0.2.4_amd64.AppImage
Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...

WINIT_UNIX_BACKEND=wayland ./AltSendme_0.2.4_amd64.AppImage
Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...

Environment output:

XDG_SESSION_TYPE=wayland
WAYLAND_DISPLAY=wayland-0
DISPLAY=:0

Partial RUST_LOG=trace output:

INFO alt_sendme: Starting Sendme Desktop application v0.2.4
TRACE os_info: Detected CachyOS rolling
DEBUG alt_sendme: File drop support enabled
Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...

** (alt-sendme): WARNING ** atk-bridge: get_device_events_reply: unknown signature

Additional Notes

• The error occurs on both Wayland and forced X11 backends, suggesting an EGL compatibility issue rather than a specific display backend.
• Mesa/OpenGL/OpenGL ES appear fully functional (glxinfo tested).
• Likely an incompatibility between the AppImage’s bundled EGL/wgpu/winit stack and the system’s Wayland/EGL environment on CachyOS.
• A full debug_log.txt generated via:
  RUST_LOG=trace ./AltSendme_0.2.4_amd64.AppImage | tee debug_log.txt

 RUST_LOG=trace ./AltSendme_0.2.4_amd64.AppImage 2>&1 | tee debug_log.txt
2025-11-24T15:11:42.000002Z  INFO ThreadId(01) alt_sendme: 58: Starting Sendme Desktop application v0.2.4
2025-11-24T15:11:42.000079Z TRACE ThreadId(01) os_info::imp: 9: linux::current_platform is called
2025-11-24T15:11:42.005315Z TRACE ThreadId(01) os_info::imp::lsb_release: 72: lsb_release command returned Output { status: ExitStatus(unix_wait_status(0)), stdout: "LSB Version:\tn/a\nDistributor ID:\tcachyos\nDescription:\tCachyOS\nRelease:\trolling\nCodename:\tn/a\n", stderr: "" }
2025-11-24T15:11:42.005328Z TRACE ThreadId(01) os_info::imp::lsb_release: 83: Trying to parse "LSB Version:\tn/a\nDistributor ID:\tcachyos\nDescription:\tCachyOS\nRelease:\trolling\nCodename:\tn/a\n"
2025-11-24T15:11:42.005334Z TRACE ThreadId(01) os_info::imp::lsb_release: 98: Parsed as 'Some("cachyos")' distribution and 'Some("rolling")' version
2025-11-24T15:11:42.005910Z TRACE ThreadId(01) os_info::imp: 17: Returning Info { os_type: CachyOS, version: Rolling(None), edition: None, codename: None, bitness: X64, architecture: Some("x86_64") }
2025-11-24T15:11:42.123367Z DEBUG ThreadId(01) alt_sendme: 84: File drop support enabled via dragDropEnabled config
Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...

** (alt-sendme:2479328): WARNING **: 18:12:07.124: atk-bridge: get_device_events_reply: unknown signature

---

[tonyantony300]

Hi @estem8 ,

Thank you for this detailed issue. Noted and will release fix.