qt packages (e.g. pcmanfm-qt) missing wayland qt module

  • Done
  • quality assurance status badge
Details
5 participants
  • bdju
  • Josselin Poiret
  • Efraim Flashner
  • Genevieve
  • Maxim Cournoyer
Owner
unassigned
Submitted by
bdju
Severity
normal
B
B
bdju wrote on 14 Nov 2021 04:59
(address . bug-guix@gnu.org)
CFP7A6U72RXO.0FJMS2EFI1US@masaki
I am running Guix System with Sway
guix (GNU Guix) 33a80e111096b05af3d60576dfcb2d67099dc60e

Running `QT_QPA_PLATFORM=wayland pcmanfm-qt` results in failure to
launch and the following errors:

```
21:50:38.413|qt.qpa.plugin|W|Could not find the Qt platform plugin "wayland" in ""
21:50:38.413|default|F|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, vnc, xcb.

zsh: abort QT_QPA_PLATFORM=wayland pcmanfm-qt
```

Due to this problem, I cannot set this env var for my whole profile or
many programs will break. This means they run with xwayland instead of
native wayland. I have run some of these same programs on another
distro (postmarketOS on a Pinebook Pro) and found they run in Sway.

I believe this is likely a packaging issue with qt stuff.
J
J
Josselin Poiret wrote on 14 Nov 2021 14:44
(address . dev@jpoiret.xyz)
87czn2am32.fsf@jpoiret.xyz
Hello,

This plugin is packaged as a part of qtwayland, and `guix shell --pure
--preserve="^(XDG_|WAYLAND_DISPLAY)" bash pcmanfm-qt qtwayland -- bash
-c "QT_QPA_PLATFORM=wayland pcmanfm-qt"` does work as expected (whereas
it does not if I leave out qtwayland). You might want to install
qtwayland in your profile for it to work.

Best,
Josselin Poiret
B
B
bdju wrote on 15 Nov 2021 01:13
CFPX3V5HX0YF.YHPKBJLUPBUA@masaki
On Sun Nov 14, 2021 at 7:44 AM CST, Josselin Poiret wrote:
Toggle quote (10 lines)
> Hello,
>
> This plugin is packaged as a part of qtwayland, and `guix shell --pure
> --preserve="^(XDG_|WAYLAND_DISPLAY)" bash pcmanfm-qt qtwayland -- bash
> -c "QT_QPA_PLATFORM=wayland pcmanfm-qt"` does work as expected (whereas
> it does not if I leave out qtwayland). You might want to install
> qtwayland in your profile for it to work.
>
> Best,
> Josselin Poiret
Thanks, installing that does indeed get pcmanfm-qt to launch, although
the right click menu and file menus seem to be invisible! I had to open
up a pcmanfm-qt without this env var to see how to get to preferences
blindly. (alt-e alt-e will open edit then preferences). The missing
right click menu is even worse since what's under the menu can vary,
especially the "open with" menu.

Also, should this have been a dependency of something? I definitely
didn't install it manually on postmarketOS (alpine-based).
E
E
Efraim Flashner wrote on 16 Nov 2021 20:12
(name . bdju)(address . bdju@tilde.team)
YZQCrqVZ7vf1qjgH@3900XT
On Sun, Nov 14, 2021 at 06:13:41PM -0600, bdju via Bug reports for GNU Guix wrote:
Toggle quote (21 lines)
> On Sun Nov 14, 2021 at 7:44 AM CST, Josselin Poiret wrote:
> > Hello,
> >
> > This plugin is packaged as a part of qtwayland, and `guix shell --pure
> > --preserve="^(XDG_|WAYLAND_DISPLAY)" bash pcmanfm-qt qtwayland -- bash
> > -c "QT_QPA_PLATFORM=wayland pcmanfm-qt"` does work as expected (whereas
> > it does not if I leave out qtwayland). You might want to install
> > qtwayland in your profile for it to work.
> >
> > Best,
> > Josselin Poiret
> Thanks, installing that does indeed get pcmanfm-qt to launch, although
> the right click menu and file menus seem to be invisible! I had to open
> up a pcmanfm-qt without this env var to see how to get to preferences
> blindly. (alt-e alt-e will open edit then preferences). The missing
> right click menu is even worse since what's under the menu can vary,
> especially the "open with" menu.
>
> Also, should this have been a dependency of something? I definitely
> didn't install it manually on postmarketOS (alpine-based).

I have qtwayland installed in my profile too. I have a couple of qt
programs which need it installed to use. It is better than before, where
each package had to be modified to support displaying on wayland, but
I'm not sure where we would inject qtwayland in the qt/kde build stack
to make sure everything builds against it.

--
Efraim Flashner <efraim@flashner.co.il> ????? ?????
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEoov0DD5VE3JmLRT3Qarn3Mo9g1EFAmGUAq0ACgkQQarn3Mo9
g1EsBw//WlITd0UCCZVQIfKV83jxA/Zh3xV9m5WuD3IFy63i74umkwzcZiqnwQKz
6GVglO8sqSQn/PlCQXKLBEIG4aTLP6T35Sn78LK9vn6uivDJoY8IeEc0fOl9CIpq
vaLUv+djPV0G9IrpmJFwl7w7oG5HxZrc1STLGHC8gpAIh0NpqG9cDzN9LWTYuxD/
Cx/GtNroo2LdDzRz2JkpGGqwMtVaa/aIywO+wlncHreQsderxaepBm3pK/xCK7Ox
0+0LJG5xvpxSj8bqmgKObocSi4rlWgLNHZCf6PrPPlTim4Bnh4EvaatCT2cDv/h3
Et0cmfJ0VI7879EBXPovBsmyTMt0sD1mrVCRWD0mxIBv9sU9b1i1McDagJkTMmKA
xxwct/vQP2rgidNVssuUFQYvqVmWP/1672J4d5ZwpuYPL0STC4ym8KMqfZT/2LOF
1zN9pYPVX6ClgwabstDmRUs1A68Ma6uMBEovwXpdjs5w8pPJS3NZqoZg7YpQpOFo
kmLNnsHM1bpoyTo5rqGt4bOKlw2TK+F5iktn+bfKgQQESbZ2JhQ+0TnkkM3wYW0A
qRmfum/0sO5wiy/dCFzOSe/iW6J/SadnQct0o18u14yux+f+upYqYFttbulCSGbJ
o5chltiZ9dTgQWsZQYWesw0wNRVBRWIShjablByurMs9o9nf2W4=
=33Uy
-----END PGP SIGNATURE-----


G
G
Genevieve wrote on 29 Jan 2023 22:24
qt packages (e.g. pcmanfm-qt) missing wayland qt module
(address . 51826@debbugs.gnu.org)
31BE4C2E-3FE9-497E-80CE-475B8DA75892@sunlashed.garden
Toggle quote (5 lines)
> `guix shell --pure --preserve="^(XDG_|WAYLAND_DISPLAY)"
> bash pcmanfm-qt qtwayland -- bash -c
> "QT_QPA_PLATFORM=wayland pcmanfm-qt"`
> does work as expected

Unfortunately I'm still experiencing this regression no matter
what I try, and the above command gives

qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in ""

Additionally, searching for qtwayland files in my guix profile only finds
license files in ~/.guix-profile/share/doc/qtwayland-6.3.1/...

So something is clearly not being installed, but I'm not sure where
to start with debugging this.
J
J
Josselin Poiret wrote on 2 Feb 2023 18:19
87r0v8vvbp.fsf@jpoiret.xyz
Hi Genevieve,

Genevieve via Bug reports for GNU Guix <bug-guix@gnu.org> writes:

Toggle quote (3 lines)
> Additionally, searching for qtwayland files in my guix profile only finds
> license files in ~/.guix-profile/share/doc/qtwayland-6.3.1/...

We now have qtwayland@6 as well, so by default guix will consider
qtwayland to be qtwayland@6. I'd say you need to put qtwayland@5 in the
above shell incantation. This is definitely something that we should fix
on core-updates, to have qtbase always include the corresponding
qtwayland.

Best,
--
Josselin Poiret
M
M
Maxim Cournoyer wrote on 29 Mar 2023 02:41
(name . bdju)(address . bdju@tilde.team)
874jq475j1.fsf@gmail.com
Hello,

"bdju" <bdju@tilde.team> writes:

Toggle quote (14 lines)
> I am running Guix System with Sway
> guix (GNU Guix) 33a80e111096b05af3d60576dfcb2d67099dc60e
>
> Running `QT_QPA_PLATFORM=wayland pcmanfm-qt` results in failure to
> launch and the following errors:
>
> ```
> 21:50:38.413|qt.qpa.plugin|W|Could not find the Qt platform plugin "wayland" in ""
> 21:50:38.413|default|F|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, vnc, xcb.
>
> zsh: abort QT_QPA_PLATFORM=wayland pcmanfm-qt

I believe the modern manifestation of this problem was #57742, now fixed
on the staging branch (see commit e4ef2db8fda85a469a6fc89bf3c46c9d7e8d44ea).

--
Thanks,
Maxim
Closed
?