Copilot app on Fedora fails to connect to Wayland

[ocrete]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Copilot CLI

Body

I've just tried the Copilot GUI app on Fedora 44, it seems to refuse to connect to my Wayland compositor, instead going through X11. The effect of that is that the text is incredibly small on my HiDPI screen making it useless.

It would be better if it was released also as a Flatpak as these seem to generally have a better integration than AppImage.

[ocrete]

• There is only an AppImage on the website
• This is GNOME, the default Desktop on Fedora Workstation 44

[ocrete]

I should mention that this is entirely a bad AppImage bundle. When extract the "github" binary, delete the rpath and just run it as-is, it works fine.

[SaulMoreno3]

The extracted-binary result is a very useful clue: if the app works after removing its RPATH, the main problem is likely the AppImage preferring bundled native libraries, rather than GNOME or Wayland itself.

Before patching the bundle, I would also test Electron's native Wayland path explicitly:

ELECTRON_OZONE_PLATFORM_HINT=wayland \
./github --ozone-platform=wayland \
  --enable-features=UseOzonePlatform,WaylandWindowDecorations

If that still falls back to XWayland, compare the executable before and after extraction with:

readelf -d ./github | grep -E 'RPATH|RUNPATH'

For a temporary workaround, keep the original AppImage untouched, extract a copy, and remove the RPATH only from the extracted github binary with patchelf --remove-rpath. Then launch that copy with the Wayland flags above. The permanent fix should be in the AppImage build: avoid shipping an incompatible GTK/Wayland library set or set the correct RPATH, and publish a Flatpak if broader desktop integration is desired.

It would be helpful to include the Copilot app version, Fedora version, compositor, and the readelf output in the report so the packaging regression can be reproduced.