Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#74633 - featherpad fails to start

Attached to Project: Community Packages
Opened by Mangoduck (Mangoduck) - Tuesday, 03 May 2022, 19:32 GMT
Last edited by Antonio Rojas (arojas) - Wednesday, 04 May 2022, 07:13 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Attempting to open featherpad results in error stating that "no Qt platform plugin could be initialized." The entire stderr output is below.

I don't know anything about Qt, but I'm guessing maybe a dependency isn't installed? If so, then I imagine that including the dependency in the package would fix the issue. If not, then I'll open an issue on github.

Additional info:
FeatherPad 1.2.0
stderr output:
```
qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in ""
qt.qpa.xcb: could not connect to display
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

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

Steps to reproduce:
install the featherpad package with pacman
try to run featherpad
This task depends upon

Closed by  Antonio Rojas (arojas)
Wednesday, 04 May 2022, 07:13 GMT
Reason for closing:  Not a bug
Comment by Doug Newgard (Scimmia) - Tuesday, 03 May 2022, 19:46 GMT
Using Wayland? Pacman told you that you would need qt5-wayland in that case when you installed qt5-base.
Comment by Doug Newgard (Scimmia) - Tuesday, 03 May 2022, 19:47 GMT
My apologies, those would be qt6 packages, not qt5.
Comment by Mangoduck (Mangoduck) - Tuesday, 03 May 2022, 23:07 GMT
You are correct. Installing qt6-wayland fixed the issue. Should I make a new bug for the qt6-base package, or is there a way to notify the maintainer about this one I've already made?
Comment by Doug Newgard (Scimmia) - Tuesday, 03 May 2022, 23:14 GMT
As I said, it's already listed, there's nothing to do.
Comment by Mangoduck (Mangoduck) - Tuesday, 03 May 2022, 23:17 GMT
It's listed as optional, but it's not. It doesn't function without that package installed. It seems to me that one either needs X or qt6-wayland installed. It should make sure that at least one of those is installed, yeah?
Comment by Doug Newgard (Scimmia) - Tuesday, 03 May 2022, 23:17 GMT
No, you should read what pacman tells you and make your own decision.
Comment by Mangoduck (Mangoduck) - Tuesday, 03 May 2022, 23:19 GMT
You could make that argument for every dependency for every package. The point of a package manager is to make sure you have necessary dependencies installed, not to just tell you about the packages you could install and let you decide for yourself if they're necessary.
Comment by Mangoduck (Mangoduck) - Tuesday, 03 May 2022, 23:53 GMT
I would like to clarify that I understand this isn't a high priority and that maintainers' time and efforts are finite resources. However, I maintain that it is a problem that should be addressed at some point.

Loading...