[PR #553] [MERGED] Disable wayland support in the snap #1654

New issue

Closed

opened 2026-05-05 07:58:44 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

2026-05-05 07:58:44 -06:00

Owner

📋 Pull Request Information

Original PR: https://github.com/debauchee/barrier/pull/553
Author: @maxiberta
Created: 2/5/2020
Status: ✅ Merged
Merged: 2/13/2020
Merged by: @AdrianKoshka

Base: master ← Head: disable-wayland

📝 Commits (3)

d9745a7 Add build-essential to the snap's build deps.
f2f9f1e Explicitly disable wayland support in the snap.
65fb58e Add comment on snap env var

📊 Changes

1 file changed (+4 additions, -0 deletions)

View changed files

📝 snap/snapcraft.yaml (+4 -0)

📄 Description

Installed plasma-workspace-wayland, now the barrier snap crashes on start on X11 (!) with:

This application failed to start because it could not find or load the Qt platform plugin "wayland-egl"
in "".

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.

Reinstalling the application may fix this problem.

Reproduced on Ubuntu 18.04 and Ubuntu 20.04.

This just completely disables any native wayland support and allows the app to start on X11. Afaik, this is a known issue with snaps, and this is the "common" workaround.

I think enabling proper wayland support should start by adding qtwayland5 to stage-packages.

Additionally, make sure the minimum basic tools for building are installed (not an issue in Launchpad build farm, but helps on any desktop pc with no g++).

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/debauchee/barrier/pull/553 **Author:** [@maxiberta](https://github.com/maxiberta) **Created:** 2/5/2020 **Status:** ✅ Merged **Merged:** 2/13/2020 **Merged by:** [@AdrianKoshka](https://github.com/AdrianKoshka) **Base:** `master` ← **Head:** `disable-wayland` --- ### 📝 Commits (3) - [`d9745a7`](https://github.com/debauchee/barrier/commit/d9745a737ac46586ad2b72e5f3912991d23b1a0a) Add build-essential to the snap's build deps. - [`f2f9f1e`](https://github.com/debauchee/barrier/commit/f2f9f1ec643cc0de129c15f6a2816635813d71a6) Explicitly disable wayland support in the snap. - [`65fb58e`](https://github.com/debauchee/barrier/commit/65fb58ebe5e1f9fa5b9dbfcda394163b353fba8b) Add comment on snap env var ### 📊 Changes **1 file changed** (+4 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `snap/snapcraft.yaml` (+4 -0) </details> ### 📄 Description Installed `plasma-workspace-wayland`, now the `barrier` snap crashes on start on X11 (!) with: ``` This application failed to start because it could not find or load the Qt platform plugin "wayland-egl" in "". Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb. Reinstalling the application may fix this problem. ``` Reproduced on Ubuntu 18.04 and Ubuntu 20.04. This just completely disables any native wayland support and allows the app to start on X11. Afaik, [this is a known issue with snaps, and this is the "common" workaround](https://forum.snapcraft.io/t/problem-launching-qt-snaps-in-wayland/7055/2). I think enabling proper wayland support should start by adding `qtwayland5` to `stage-packages`. Additionally, make sure the minimum basic tools for building are installed (not an issue in Launchpad build farm, but helps on any desktop pc with no `g++`). --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>