An application not running "natively" in wayland isn't a bug and definitely shouldn't merit negative karma. There are other environments within Fedora than GNOME, specifically KDE Plasma which while has some support for wayland, still has many people using the X environment. The proper place to address this is bugzilla, and I created an issue: https://bugzilla.redhat.com/show_bug.cgi?id=1752665
Sorry, but I disagree. This is definitely a regression. I used to be able to just click on the Picard icon in Gnome and it would launch, now it fails silently, unless you manually set an env variable.
Unskilled users will just think that the update broke their program, and wouldn't be very far from truth.
I would like to know what is the rationale behind ignoring XDG_SESSION_TYPE=wayland on Gnome.
This update has been submitted for testing by gbcox.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'ignored'.
This update has been pushed to testing.
Picard won't run natively on Gnome on Wayland, which is Fedora's default environment:
[r1348@localhost ~]$ picard Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
QT_QPA_PLATFORM=wayland picard works fine.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
An application not running "natively" in wayland isn't a bug and definitely shouldn't merit negative karma. There are other environments within Fedora than GNOME, specifically KDE Plasma which while has some support for wayland, still has many people using the X environment. The proper place to address this is bugzilla, and I created an issue: https://bugzilla.redhat.com/show_bug.cgi?id=1752665
Sorry, but I disagree. This is definitely a regression. I used to be able to just click on the Picard icon in Gnome and it would launch, now it fails silently, unless you manually set an env variable. Unskilled users will just think that the update broke their program, and wouldn't be very far from truth. I would like to know what is the rationale behind ignoring XDG_SESSION_TYPE=wayland on Gnome.
If you want to disagree, do it somewhere where it will be helpful... like the bug I created.
This update has been obsoleted by picard-2.2.1-1.fc30.