For a Qt5 application on a KDE Plasma Wayland session everything is fine, because there is a direct installation dependency
# rpm -q --whatrequires 'qt5-qtwayland(x86-64)' plasma-workspace-wayland-5.27.8-2.fc39.x86_64
But for a Qt6 application (wireshark, calibre (6.x on F39), qmasterpassword) you get a warning on the command line like
$ wireshark ** (wireshark:234933) 11:56:46.231227 [GUI WARNING] -- Could not find the Qt platform plugin "wayland" in ""
i.e. Qt6 applications are falling back to X11/XWayland.
Nothing depends on qt6-qtwayland and hence it is missing on a normal KDE Plasma installation.
qt6-qtwayland
Should plasma-workspace-wayland depend on qt6-qtwayland to fix this?
plasma-workspace-wayland
Metadata Update from @marcdeop: - Issue tagged with: meeting
I'm pretty sure the problem will appear in reverse for Qt5 applications on F40+ when we move to KDE Plasma 6.
I thought we already had implemented a conditional dependency for this...
@jgrulich Would it make sense to implement a conditional Requires on qtX-qtbase-gui packages?
qtX-qtbase-gui
For example, we could add the following to qt6-qtbase-gui:
qt6-qtbase-gui
# Ensure QtWayland is installed when libwayland-client is installed Requires: (qt6-qtwayland%{?_isa} if libwayland-client%{?_isa})
Metadata Update from @ngompa: - Issue assigned to jgrulich
Metadata Update from @ngompa: - Issue untagged with: meeting - Issue tagged with: easyfix, packaging
Any solution should not be tied to Plasma packages, the problem equally applies to running Qt apps on Gnome Wayland, Sway, etc
Metadata Update from @ngompa: - Issue assigned to ngompa (was: jgrulich)
I've taken care of this with a simple weak dependency (to avoid deploops when doing Qt upgrades):
These will be part of the next Qt updates.
Metadata Update from @ngompa: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Issue status updated to: Open (was: Closed)
Issue status updated to: Closed (was: Open) Issue close_status updated to: Fixed