https://bugs.kde.org/show_bug.cgi?id=400367
Wolfgang Bauer <wba...@tmo.at> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wayland
Resolution|WORKSFORME |---
Ever confirmed|0 |1
Status|RESOLVED |REOPENED
See Also|https://bugs.kde.org/show_b |
|ug.cgi?id=400368 |
--- Comment #7 from Wolfgang Bauer <wba...@tmo.at> ---
(In reply to Patrick Silva from comment #6)
> yes, the problem with kget only occurs under Wayland.
> I can't reproduce with kmail anymore, it launches as expected under X11 and
> Wayland.
Ok, I just noticed that the Exec line in kget's desktop file still has the %i
parameter. IIRC that may cause problems on Wayland as Qt doesn't support the
--icon option there.
Can you try to remove the %i?
Either in the menu editor or by editing the .desktop file (likely
/usr/share/applications/org.kde.kget.desktop) with a text editor. (you might
have to run kbuilsycoca5 afterwards in the latter case)
A bit strange that it works here, but that may be due to some openSUSE patch
(making it being run via XWayland).
It should be removed anyway though, according to
https://community.kde.org/Guidelines_and_HOWTOs/Wayland_Porting_Notes:
> Exec key of .desktop files
>
> The Exec key of your .desktop file should not contain the %i "field code".
> Your application won't start on Wayland otherwise, because the specification
> expands that code in the --icon argument, which is accepted by
> QGuiApplication
> only on XCB platforms. This code review contains a discussion about the
> upstream decision. You can use the -qwindowicon argument as replacement. It
> still won't work on Wayland (it will on most other platforms) but now your
> app will start everywhere.
>
> // Don't
> Exec=someapp %i %U
> // Do
> Exec=someapp -qwindowicon someicon %U
--
You are receiving this mail because:
You are watching all bug changes.
