fman refuses to start on Wayland desktop
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 275
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Hey,
I noticed fman refuses to start on Sway / Arch Linux. Usually Qt applications run just fine so that seems kinda strange. I saw a similar problem was in the bug tracker 2017 so I followed your advice that you gave back then and ran /opt/fman/fman directly.
This application failed to start because it could not find or load the Qt platform plugin "wayland"
in "".
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
Reinstalling the application may fix this problem.
zsh: abort (core dumped) /opt/fman/fman
The problem would seem obvious from that message. Though I have qt-wayland and even xwayland installed.
pacman -Qe | grep wayland
egl-wayland 1.1.5-1
glew-wayland 2.2.0-1
glfw-wayland 3.3.2-1
qt5-wayland-git 5.15.0.efc94a48-1
wayland 1.18.0-2
xorg-server-xwayland 1.20.8-2
Is there a way to point fman to the Qt installation on my system? Or is wayland not supported?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running /opt/fman/fman on Sway/Arch Linux and review the reported Qt platform-plugin error and available plugins. Done means fman starts on the Wayland desktop, or the issue clearly establishes that Wayland is unsupported and explains the required Qt setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100