Le sam. 20 août 2022 à 15:13, sagitter <sagit...@rpmfusion.org> a écrit : > > commit ecb20ec407a7f64d003319d92cb922fe8a863183 > Author: Antonio Trande <sagit...@fedoraproject.org> > Date: Sat Aug 20 15:13:13 2022 +0200 > > Fix QT_QPA_PLATFORM env variables > > ppsspp-qt-wayland.desktop | 2 +- > ppsspp-qt.desktop | 2 +- > ppsspp.spec | 5 ++++- > 3 files changed, 6 insertions(+), 3 deletions(-)
Hello Antonio, Why do you need to hardcode the QT_QPA_PLATFORM at all ? Is there an upstream bug with this patch ? > --- a/ppsspp-qt-wayland.desktop > +++ b/ppsspp-qt-wayland.desktop > @@ -3,7 +3,7 @@ Version=1.0 > Type=Application > Terminal=false > Name=PPSSPP Qt for Wayland > -Exec=env QT_QPA_PLATFORM=xcb /usr/bin/PPSSPPQt > +Exec=env QT_QPA_PLATFORM=wayland /usr/bin/PPSSPPQt If PPSSPPQt doesn't work well with wayland, I guess one way to workaround it is to force the xcb platform to rely on the Xwayland But I don't see the point to force the wayland plateform under wayland (unless qt is that broken). > diff --git a/ppsspp-qt.desktop b/ppsspp-qt.desktop > index be7cf91..6b69a53 100644 > --- a/ppsspp-qt.desktop > +++ b/ppsspp-qt.desktop > @@ -3,7 +3,7 @@ Version=1.0 > Type=Application > Terminal=false > Name=PPSSPP Qt > -Exec=/usr/bin/PPSSPPQt > +Exec=env QT_QPA_PLATFORM=xcb /usr/bin/PPSSPPQt Same, is this fixing a real issue ? As I understand, the variable can sometimes takes a vnc platform, so it will be sub-optimal (still a corner case). Hope that it helps. _______________________________________________ rpmfusion-developers mailing list -- rpmfusion-developers@lists.rpmfusion.org To unsubscribe send an email to rpmfusion-developers-le...@lists.rpmfusion.org
