Hi, Today I saw 3rd case, so I guess the is real an issue on F31 .
1 - VirtualBox https://bugzilla.rpmfusion.org/show_bug.cgi?id=5383 filed a bug in fedora https://bugzilla.redhat.com/show_bug.cgi?id=1758724 The maintainer said that the reason for the crash is the hard coded dependencies on X11 API, without forcing the Qt's backend to be the one it depends on.
2 - smplayer https://bugzilla.rpmfusion.org/show_bug.cgi?id=5438
3 - Today mixxx commit https://pkgs.rpmfusion.org/cgit/free/mixxx.git/commit/?id=709069aaddacf11bf5... Use XCB instead of the default Qt Wayland platform adapter
https://bugs.launchpad.net/mixxx/+bug/1850729 https://fedoraproject.org/wiki/Changes/Qt_Wayland_By_Default_On_Gnome
On Sat, 2019-11-02 at 04:51 +0000, Sérgio Basto wrote:
Hi, Today I saw 3rd case, so I guess the is real an issue on F31 .
1 - VirtualBox https://bugzilla.rpmfusion.org/show_bug.cgi?id=5383 filed a bug in fedora https://bugzilla.redhat.com/show_bug.cgi?id=1758724 The maintainer said that the reason for the crash is the hard coded dependencies on X11 API, without forcing the Qt's backend to be the one it depends on.
2 - smplayer https://bugzilla.rpmfusion.org/show_bug.cgi?id=5438
3 - Today mixxx commit https://pkgs.rpmfusion.org/cgit/free/mixxx.git/commit/?id=709069aaddacf11bf5... Use XCB instead of the default Qt Wayland platform adapter
https://bugs.launchpad.net/mixxx/+bug/1850729 https://fedoraproject.org/wiki/Changes/Qt_Wayland_By_Default_On_Gnome
In the 3 cases QT_QPA_PLATFORM=xcb smplayer (or QT_QPA_PLATFORM=xcb other app ) works
-- Sérgio M. B. _______________________________________________ kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org 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/kde@lists.fedoraproject.org
Hi,
all the apps which do not work on Wayland should be forcing xcb plugin. I don't really think it's an issue on our side.
Regards, Jan
On sobota 2. listopadu 2019 5:51:28 CET Sérgio Basto wrote:
Hi, Today I saw 3rd case, so I guess the is real an issue on F31 .
1 - VirtualBox https://bugzilla.rpmfusion.org/show_bug.cgi?id=5383 filed a bug in fedora https://bugzilla.redhat.com/show_bug.cgi?id=1758724 The maintainer said that the reason for the crash is the hard coded dependencies on X11 API, without forcing the Qt's backend to be the one it depends on.
2 - smplayer https://bugzilla.rpmfusion.org/show_bug.cgi?id=5438
3 - Today mixxx commit https://pkgs.rpmfusion.org/cgit/free/mixxx.git/commit/?id=709069aaddacf11bf5 52ebdb364655eea166eddb Use XCB instead of the default Qt Wayland platform adapter
https://bugs.launchpad.net/mixxx/+bug/1850729 https://fedoraproject.org/wiki/Changes/Qt_Wayland_By_Default_On_Gnome
-- Sérgio M. B. _______________________________________________ kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org 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/kde@lists.fedoraproject.org
On Mon, 2019-11-04 at 07:41 +0100, Jan Grulich wrote:
Hi,
all the apps which do not work on Wayland should be forcing xcb plugin. I don't really think it's an issue on our side.
What side Kde or Gnome ? Until F30 all works in gnome without problem, seems "Qt_Wayland_By_Default_On_Gnome" break many apps , so also seems is not a Gnome issue .
Regards, Jan
On sobota 2. listopadu 2019 5:51:28 CET Sérgio Basto wrote:
Hi, Today I saw 3rd case, so I guess the is real an issue on F31 .
1 - VirtualBox https://bugzilla.rpmfusion.org/show_bug.cgi?id=5383 filed a bug in fedora https://bugzilla.redhat.com/show_bug.cgi?id=1758724 The maintainer said that the reason for the crash is the hard coded dependencies on X11 API, without forcing the Qt's backend to be the one it depends on.
2 - smplayer https://bugzilla.rpmfusion.org/show_bug.cgi?id=5438
3 - Today mixxx commit https://pkgs.rpmfusion.org/cgit/free/mixxx.git/commit/?id=709069aaddacf11bf5 52ebdb364655eea166eddb Use XCB instead of the default Qt Wayland platform adapter
https://bugs.launchpad.net/mixxx/+bug/1850729 https://fedoraproject.org/wiki/Changes/Qt_Wayland_By_Default_On_Gnome
-- Sérgio M. B. _______________________________________________ kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org 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/kde@lists.fedoraproject.org
Hi,
On úterý 5. listopadu 2019 2:43:26 CET Sérgio Basto wrote:
On Mon, 2019-11-04 at 07:41 +0100, Jan Grulich wrote:
Hi,
all the apps which do not work on Wayland should be forcing xcb plugin. I don't really think it's an issue on our side.
What side Kde or Gnome ? Until F30 all works in gnome without problem, seems "Qt_Wayland_By_Default_On_Gnome" break many apps , so also seems is not a Gnome issue .
With our side I mean Qt. And to be honest, how would you like to move towards Wayland if you keep waiting for apps which forces X11 and which do not work with anything else. Those apps should really be fixed to be able to work with Wayland instead.
On sobota 2. listopadu 2019 5:51:28 CET Sérgio Basto wrote:
Hi, Today I saw 3rd case, so I guess the is real an issue on F31 .
1 - VirtualBox https://bugzilla.rpmfusion.org/show_bug.cgi?id=5383 filed a bug in fedora https://bugzilla.redhat.com/show_bug.cgi?id=1758724 The maintainer said that the reason for the crash is the hard coded dependencies on X11 API, without forcing the Qt's backend to be the one it depends on.
2 - smplayer https://bugzilla.rpmfusion.org/show_bug.cgi?id=5438
3 - Today mixxx commit https://pkgs.rpmfusion.org/cgit/free/mixxx.git/commit/?id=709069aaddacf1 1bf5 52ebdb364655eea166eddb
Use XCB instead of the default Qt Wayland platform
adapter
https://bugs.launchpad.net/mixxx/+bug/1850729 https://fedoraproject.org/wiki/Changes/Qt_Wayland_By_Default_On_Gnome
Jan Grulich wrote:
Hi,
On úterý 5. listopadu 2019 2:43:26 CET Sérgio Basto wrote:
On Mon, 2019-11-04 at 07:41 +0100, Jan Grulich wrote:
Hi,
all the apps which do not work on Wayland should be forcing xcb plugin. I don't really think it's an issue on our side.
What side Kde or Gnome ? Until F30 all works in gnome without problem, seems "Qt_Wayland_By_Default_On_Gnome" break many apps , so also seems is not a Gnome issue .
With our side I mean Qt. And to be honest, how would you like to move towards Wayland if you keep waiting for apps which forces X11 and which do not work with anything else. Those apps should really be fixed to be able to work with Wayland instead.
So of the bugs being filed against qt5-qtwayland on the issue, we should be triaging those against the individual applications instead?
(I'm move forward doing that, unless someone hollers otherwise)
-- Rex
Rex Dieter wrote:
Jan Grulich wrote:
Hi,
On úterý 5. listopadu 2019 2:43:26 CET Sérgio Basto wrote:
On Mon, 2019-11-04 at 07:41 +0100, Jan Grulich wrote:
Hi,
all the apps which do not work on Wayland should be forcing xcb plugin. I don't really think it's an issue on our side.
What side Kde or Gnome ? Until F30 all works in gnome without problem, seems "Qt_Wayland_By_Default_On_Gnome" break many apps , so also seems is not a Gnome issue .
With our side I mean Qt. And to be honest, how would you like to move towards Wayland if you keep waiting for apps which forces X11 and which do not work with anything else. Those apps should really be fixed to be able to work with Wayland instead.
So of the bugs being filed against qt5-qtwayland on the issue, we should be triaging those against the individual applications instead?
(I'm move forward doing that, unless someone hollers otherwise)
FYI, triaged this one to mkvtoolnix, https://bugzilla.redhat.com/show_bug.cgi?id=1768244
-- Rex
Hi,
On úterý 5. listopadu 2019 2:43:26 CET Sérgio Basto wrote:
With our side I mean Qt. And to be honest, how would you like to move towards Wayland if you keep waiting for apps which forces X11 and which do not work with anything else. Those apps should really be fixed to be able to work with Wayland instead.
Qt should fallback to Xwayland for X11 apps. I wont be fixing any apps for this as the issue should be addressed in Qt.
Leigh Scott wrote:
Qt should fallback to Xwayland for X11 apps. I wont be fixing any apps for this as the issue should be addressed in Qt.
How is Qt supposed to know that it is an "X11 app"? The whole point of the Qt 5 platform abstraction system is that the backend can be selected at runtime. If the application supports only X11 (at least on *nix), then it has to tell Qt so at load time.
Kevin Kofler
On Sun, 2019-11-10 at 19:15 +0100, Kevin Kofler wrote:
Leigh Scott wrote:
Qt should fallback to Xwayland for X11 apps. I wont be fixing any apps for this as the issue should be addressed in Qt.
How is Qt supposed to know that it is an "X11 app"? The whole point of the Qt 5 platform abstraction system is that the backend can be selected at runtime. If the application supports only X11 (at least on *nix), then it has to tell Qt so at load time.
Hi, good fixed seems to be [1] but is a wayland problem ? or a kwayland ? Maybe the better is remove this default , or what is the problem with all these projects that use Qt ?
[1] dnf remove kf5-kwayland
Kevin Kofler
kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org 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/kde@lists.fedoraproject.org
Jan Grulich wrote:
With our side I mean Qt. And to be honest, how would you like to move towards Wayland if you keep waiting for apps which forces X11 and which do not work with anything else. Those apps should really be fixed to be able to work with Wayland instead.
Jan,
Can applications will known hard-coded dependencies on X11 force the use of xcb at runtime (without command-line switches or environment variables)?
-- Rex
Rex Dieter wrote:
Can applications will known hard-coded dependencies on X11 force the use of xcb at runtime (without command-line switches or environment variables)?
Change:
new QGuiApplication(argc, argv);
to something like:
int argcx = argc + 2; char **argvx = new char*[argcx]; std::memcpy(argvx, argv, argc * sizeof(char *)); argvx[argc] = const_cast<char *>("-platform"); argvx[argc + 1] = const_cast<char *>("xcb"); new QGuiApplication(argcx, argvx);
Kevin Kofler
Hi,
po 11. 11. 2019 v 17:47 odesílatel Rex Dieter rdieter@gmail.com napsal:
Jan Grulich wrote:
With our side I mean Qt. And to be honest, how would you like to move towards Wayland if you keep waiting for apps which forces X11 and which
do
not work with anything else. Those apps should really be fixed to be able to work with Wayland instead.
Jan,
Can applications will known hard-coded dependencies on X11 force the use of xcb at runtime (without command-line switches or environment variables)?
They can, either using something what Kevin posted or overriding QT_QPA_PLATFORM env variable.
Regards, Jan
Jan Grulich wrote:
Hi,
po 11. 11. 2019 v 17:47 odesílatel Rex Dieter rdieter@gmail.com napsal:
Jan Grulich wrote:
With our side I mean Qt. And to be honest, how would you like to move towards Wayland if you keep waiting for apps which forces X11 and which
do
not work with anything else. Those apps should really be fixed to be able to work with Wayland instead.
Jan,
Can applications will known hard-coded dependencies on X11 force the use of xcb at runtime (without command-line switches or environment variables)?
They can, either using something what Kevin posted or overriding QT_QPA_PLATFORM env variable.
That's pretty ugly, but ok.
I wonder how firefox handles it? (It apparently uses wayland by default on gnome-shell, but not everywhere else).
-- Rex
Removing qt5-wayland or adding an override to /etc/profile.d/ to make it system-wide is much easier. Apps using X11 should be respected so don't expect everyone else to adapt there apps for this qt5-wayland induced mess.
On Sun, 2019-11-24 at 09:04 +0000, Leigh Scott wrote:
Removing qt5-wayland or adding an override to /etc/profile.d/ to make it system-wide is much easier. Apps using X11 should be respected so don't expect everyone else to adapt there apps for this qt5-wayland induced mess.
Please quote context when replying via HyperKitty. It doesn't do so automatically and most people here don't use HK anyway.
poc
On Sun, 2019-11-24 at 10:56 +0000, Patrick O'Callaghan wrote:
On Sun, 2019-11-24 at 09:04 +0000, Leigh Scott wrote:
Removing qt5-wayland or adding an override to /etc/profile.d/ to make it system-wide is much easier. Apps using X11 should be respected so don't expect everyone else to adapt there apps for this qt5-wayland induced mess.
Please quote context when replying via HyperKitty. It doesn't do so automatically and most people here don't use HK anyway.
(In reply to Russell Odom from comment #9)
and running QT_QPA_PLATFORM=xcb mythfrontend ? fix it for you ?
Yes, that works (it also works under Xorg). Worth rolling out an
updated
mythfrontend with that in, until this is fixed properly upstream?
1 - VirtualBox https://bugzilla.rpmfusion.org/show_bug.cgi?id=5383 filed a bug in fedora https://bugzilla.redhat.com/show_bug.cgi?id=1758724 The maintainer said that the reason for the crash is the hard coded dependencies on X11 API, without forcing the Qt's backend to be the one it depends on.
2 - smplayer https://bugzilla.rpmfusion.org/show_bug.cgi?id=5438
3 - Today mixxx commit https://pkgs.rpmfusion.org/cgit/free/mixxx.git/commit/?id=709069aaddacf11bf5... Use XCB instead of the default Qt Wayland platform adapter https://bugs.launchpad.net/mixxx/+bug/1850729
4 - https://bugzilla.redhat.com/show_bug.cgi?id=1768244
and now 5 - mythtv https://bugzilla.rpmfusion.org/show_bug.cgi?id=5453,
It is Qt_Wayland [1] also remove qt-wayland fix the problem . But kde guy doesn't want assume the problem ...
[1] https://fedoraproject.org/wiki/Changes/Qt_Wayland_By_Default_On_Gnome