Hi, I will repeat myself even here. > I am developing a Qt app in Fedora 31 using the default GNOME wayland session and I am > very sorry to see the state of Qt in this configuration. > > 1) qt creator crashes often (https://bugzilla.redhat.com/show_bug.cgi?id=1773356) the > crash report tool does not seem to help I cannot reproduce the crash and you didn't even provide any backtrace or a prove that this is Wayland related. > 2) drag & drop does not work in Qt creator (and in no other Qt app) > (https://bugzilla.redhat.com/show_bug.cgi?id=1774762 and > https://bugreports.qt.io/browse/QTBUG-80303) This is an issue. I already spoke with the QtWayland developer and he unfortunately doesn't have time right now to look into this. I will try to look into this myself tomorrow. > 3) main window geometry cannot be restored when the application restarts > (https://bugreports.qt.io/browse/QTBUG-80612) As I told you in the bug above, I believe this a Wayland limitation. > I think GNOME / Wayland / Qt it is just not ready and should not be offered as the default > desktop session for Fedora. > > If I force Qt to use X11 emulations, things are much better. > > Probably Qt is responsible (but in the bug reports someone says that KDE / Wayland works > well), and GNOME is not Qt, but there are so many Qt apps, that sending new users to a non > working environment re-enforces the fact that "just works" is not true in > Linux. > We are trying hard to make all the issues you have fixed, but nothing can be done immediately and requires some time. It helps that you report all the issues you have, but please be little more patient. Thank you. Regards, Jan _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
