When attempting to start triple-c on Linux distros with Wayland, we get the following error:
`❯ ./Triple-C_0.4.12_amd64.AppImage
[2026-08-27 07:44:01 INFO triple_c_lib::logging] Logging to /home/jknapp/.local/share/triple-c/logs/triple-c.log
Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...
[2026-08-27 07:44:02 INFO triple_c_lib::docker::container] Snapshot sweep (startup): 0 removed, 0.00 GB reclaimed, 0 still pinned by a container, 0 failed
Also links do not open on the host system when clicked or through the toast at the top of the screen.
I would like to also have an Arch/CachyOS native version as well.
When attempting to start triple-c on Linux distros with Wayland, we get the following error:
`❯ ./Triple-C_0.4.12_amd64.AppImage
[2026-08-27 07:44:01 INFO triple_c_lib::logging] Logging to /home/jknapp/.local/share/triple-c/logs/triple-c.log
Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...
[2026-08-27 07:44:02 INFO triple_c_lib::docker::container] Snapshot sweep (startup): 0 removed, 0.00 GB reclaimed, 0 still pinned by a container, 0 failed
** (triple-c:848557): WARNING **: 07:44:26.959: atk-bridge: get_device_events_reply: unknown signature`
Also links do not open on the host system when clicked or through the toast at the top of the screen.
I would like to also have an Arch/CachyOS native version as well.
The Wayland startup crash (Could not create default EGL display: EGL_BAD_PARAMETER. Aborting.) — fixed in #38: WebKitGTK's DMA-BUF renderer fails on some Mesa/driver/compositor combinations under Wayland, and WEBKIT_DISABLE_DMABUF_RENDERER=1 is now set unconditionally on Linux before the webview initializes.
Links not opening on the host — confirmed this isn't a Triple-C bug: xdg-open works correctly on your machine, so once the Wayland crash above stopped blocking startup entirely, this should resolve itself along with it. Let us know if it doesn't once you've tested a build with the crash fix.
A native Arch/CachyOS package — added in #39: triple-c-bin on the AUR, published via its own workflow (.gitea/workflows/publish-aur-package.yml). Note this needs a one-time manual AUR account setup (creating/claiming the triple-c-bin package and adding its SSH key as a repo secret) before the first real publish can go out — see packaging/arch/README.md for the details.
Both merged to main. Closing — please reopen if the Wayland fix doesn't actually clear the crash on your hardware once you've had a chance to test it.
All three things reported here are now resolved:
- **The Wayland startup crash** (`Could not create default EGL display: EGL_BAD_PARAMETER. Aborting.`) — fixed in #38: WebKitGTK's DMA-BUF renderer fails on some Mesa/driver/compositor combinations under Wayland, and `WEBKIT_DISABLE_DMABUF_RENDERER=1` is now set unconditionally on Linux before the webview initializes.
- **Links not opening on the host** — confirmed this isn't a Triple-C bug: `xdg-open` works correctly on your machine, so once the Wayland crash above stopped blocking startup entirely, this should resolve itself along with it. Let us know if it doesn't once you've tested a build with the crash fix.
- **A native Arch/CachyOS package** — added in #39: `triple-c-bin` on the AUR, published via its own workflow (`.gitea/workflows/publish-aur-package.yml`). Note this needs a one-time manual AUR account setup (creating/claiming the `triple-c-bin` package and adding its SSH key as a repo secret) before the first real publish can go out — see `packaging/arch/README.md` for the details.
Both merged to main. Closing — please reopen if the Wayland fix doesn't actually clear the crash on your hardware once you've had a chance to test it.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
When attempting to start triple-c on Linux distros with Wayland, we get the following error:
`❯ ./Triple-C_0.4.12_amd64.AppImage
[2026-08-27 07:44:01 INFO triple_c_lib::logging] Logging to /home/jknapp/.local/share/triple-c/logs/triple-c.log
Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...
[2026-08-27 07:44:02 INFO triple_c_lib::docker::container] Snapshot sweep (startup): 0 removed, 0.00 GB reclaimed, 0 still pinned by a container, 0 failed
** (triple-c:848557): WARNING **: 07:44:26.959: atk-bridge: get_device_events_reply: unknown signature`
Also links do not open on the host system when clicked or through the toast at the top of the screen.
I would like to also have an Arch/CachyOS native version as well.
All three things reported here are now resolved:
Could not create default EGL display: EGL_BAD_PARAMETER. Aborting.) — fixed in #38: WebKitGTK's DMA-BUF renderer fails on some Mesa/driver/compositor combinations under Wayland, andWEBKIT_DISABLE_DMABUF_RENDERER=1is now set unconditionally on Linux before the webview initializes.xdg-openworks correctly on your machine, so once the Wayland crash above stopped blocking startup entirely, this should resolve itself along with it. Let us know if it doesn't once you've tested a build with the crash fix.triple-c-binon the AUR, published via its own workflow (.gitea/workflows/publish-aur-package.yml). Note this needs a one-time manual AUR account setup (creating/claiming thetriple-c-binpackage and adding its SSH key as a repo secret) before the first real publish can go out — seepackaging/arch/README.mdfor the details.Both merged to main. Closing — please reopen if the Wayland fix doesn't actually clear the crash on your hardware once you've had a chance to test it.