Re: [LyX/master] Fix #13305 - xcb is currently the only reasonable solution for Wayland
On Sun, 2026-05-17 at 22:02 +0200, Pavel Sanda wrote: > It turns out that the original issue is likely problem with drivers so I > reverted > this change. > > Pavel Thank you. :-) -- José Abílio -- lyx-devel mailing list [email protected] https://lists.lyx.org/mailman/listinfo/lyx-devel
Re: [LyX/master] Fix #13305 - xcb is currently the only reasonable solution for Wayland
On Tue, May 12, 2026 at 11:04:55AM +0200, Cor Blom wrote: > As maintainer of lyx on opensuse, forcing xwayland for lyx would not make me > happy. I would say some evidence is needed that this is a widespread issue > and that is indeed connected to wayland. It turns out that the original issue is likely problem with drivers so I reverted this change. Pavel -- lyx-devel mailing list [email protected] https://lists.lyx.org/mailman/listinfo/lyx-devel
Re: [LyX/master] Fix #13305 - xcb is currently the only reasonable solution for Wayland
On Tue, 2026-05-12 at 11:04 +0200, Cor Blom wrote: > Op 12-05-2026 om 10:45 schreef Pavel Sanda: > > Any other Waylanders around to report their experience on xcb vs non-xcb? > > I don't have any issues on opensuse tumbleweed, on kde plasma wayland > with Qt 6.11. Since a couple of Qt versions all wayland issues I had are > solved. The same for me. > System info: > > Versie 2.5.1 > (zondag 12 april 2026) > > Qt-versie (run-time): 6.11.0 op platform wayland > Qt-versie (compile-time): 6.11.0 > OS-versie (run-time): openSUSE Tumbleweed > Python gedetecteerd: 3.13.13 (/usr/bin/python3) > Teken-strategie: gedeeltelijk tekenen op de backing-store. > > As maintainer of lyx on opensuse, forcing xwayland for lyx would not > make me happy. I would say some evidence is needed that this is a > widespread issue and that is indeed connected to wayland. The same applies for me on Fedora. :-) > Cor -- José Abílio -- lyx-devel mailing list [email protected] https://lists.lyx.org/mailman/listinfo/lyx-devel
Re: [LyX/master] Fix #13305 - xcb is currently the only reasonable solution for Wayland
Le 12/05/2026 à 15:39, Cor Blom a écrit : It seems to me that this is not a lyx issue but one of Qt app integration in Gnome. Fedora seems to be doing (of did) something about this: https://github.com/FedoraQt/QAdwaitaDecorations Everything, including decorations, is fine in KDE and I don't think the distro matters here. Gnome people indeed have a very strict and annoying view on that. If I understand correctly, it is to avoid adding extra dependencies in the window manager. JMarc -- lyx-devel mailing list [email protected] https://lists.lyx.org/mailman/listinfo/lyx-devel
Re: [LyX/master] Fix #13305 - xcb is currently the only reasonable solution for Wayland
On Tue, May 12, 2026 at 03:39:05PM +0200, Cor Blom wrote: > It seems to me that this is not a lyx issue but one of Qt app integration in > Gnome. Fedora seems to be doing (of did) something about this: > > https://github.com/FedoraQt/QAdwaitaDecorations > > Everything, including decorations, is fine in KDE and I don't think the > distro matters here. Heh, right, now I rememeber reading some years back rant from KWin developer about Gnome or Mutter folks who basically pushed *each* app to deliver it's own handling of icons instead of doing it on their own. Apparently still there :) Pavel -- lyx-devel mailing list [email protected] https://lists.lyx.org/mailman/listinfo/lyx-devel
Re: [LyX/master] Fix #13305 - xcb is currently the only reasonable solution for Wayland
Op 12-05-2026 om 12:05 schreef Pavel Sanda: On Tue, May 12, 2026 at 11:39:09AM +0200, Jean-Marc Lasgouttes wrote: Wayland works for me too, except for the ugly windows decoration on Ubuntu. This is the only reason why I use xcb for all Qt apps. Is this decoration thing enough for us to claim xcb to be superior choice? Is the openSUSE experience different? It seems to me that this is not a lyx issue but one of Qt app integration in Gnome. Fedora seems to be doing (of did) something about this: https://github.com/FedoraQt/QAdwaitaDecorations Everything, including decorations, is fine in KDE and I don't think the distro matters here. Cor -- lyx-devel mailing list [email protected] https://lists.lyx.org/mailman/listinfo/lyx-devel
Re: [LyX/master] Fix #13305 - xcb is currently the only reasonable solution for Wayland
On Tue, May 12, 2026 at 11:39:09AM +0200, Jean-Marc Lasgouttes wrote: > Wayland works for me too, except for the ugly windows decoration on Ubuntu. > This is the only reason why I use xcb for all Qt apps. Is this decoration thing enough for us to claim xcb to be superior choice? Is the openSUSE experience different? Pavel -- lyx-devel mailing list [email protected] https://lists.lyx.org/mailman/listinfo/lyx-devel
Re: [LyX/master] Fix #13305 - xcb is currently the only reasonable solution for Wayland
Le 12/05/2026 à 10:32, José Matos a écrit : On Tue, 2026-05-12 at 09:31 +0200, Pavel Sanda wrote: Riki, ok to backport? P What is the culprit here? Version 2.5.1 (Sunday, 12 April 2026) Qt Version (run-time): 6.10.3 on platform wayland Qt Version (compile-time): 6.10.2 OS Version (run-time): Fedora Linux 44 (KDE Plasma Desktop Edition) Python detected: 3.14.4 (/usr/bin/python3) Draw strategy: partial draw on backing store I have never seen the issues reported and I have been using wayland for a long time. The only change from the original reporter is that I am using Qt 6.10. This is a work-around for a bug. To say that xcb is currently the only reasonable solution for Wayland is incorrect or at most incomplete. Wayland works for me too, except for the ugly windows decoration on Ubuntu. This is the only reason why I use xcb for all Qt apps. JMarc -- lyx-devel mailing list [email protected] https://lists.lyx.org/mailman/listinfo/lyx-devel
Re: [LyX/master] Fix #13305 - xcb is currently the only reasonable solution for Wayland
On Tue, May 12, 2026 at 11:04:55AM +0200, Cor Blom wrote: > Op 12-05-2026 om 10:45 schreef Pavel Sanda: > > Any other Waylanders around to report their experience on xcb vs non-xcb? > > I don't have any issues on opensuse tumbleweed, on kde plasma wayland with > Qt 6.11. Since a couple of Qt versions all wayland issues I had are solved. Ok, the reported is Qt 6.11 as well, so the Qt version is probably irrelevant. > As maintainer of lyx on opensuse, forcing xwayland for lyx would not make me > happy. I would say some evidence is needed that this is a widespread issue > and that is indeed connected to wayland. Noted. Let's wait what others might bring in. Pavel -- lyx-devel mailing list [email protected] https://lists.lyx.org/mailman/listinfo/lyx-devel
Re: [LyX/master] Fix #13305 - xcb is currently the only reasonable solution for Wayland
Op 12-05-2026 om 10:45 schreef Pavel Sanda: Any other Waylanders around to report their experience on xcb vs non-xcb? I don't have any issues on opensuse tumbleweed, on kde plasma wayland with Qt 6.11. Since a couple of Qt versions all wayland issues I had are solved. System info: Versie 2.5.1 (zondag 12 april 2026) Qt-versie (run-time): 6.11.0 op platform wayland Qt-versie (compile-time): 6.11.0 OS-versie (run-time): openSUSE Tumbleweed Python gedetecteerd: 3.13.13 (/usr/bin/python3) Teken-strategie: gedeeltelijk tekenen op de backing-store. As maintainer of lyx on opensuse, forcing xwayland for lyx would not make me happy. I would say some evidence is needed that this is a widespread issue and that is indeed connected to wayland. Cor -- lyx-devel mailing list [email protected] https://lists.lyx.org/mailman/listinfo/lyx-devel
Re: [LyX/master] Fix #13305 - xcb is currently the only reasonable solution for Wayland
On Tue, May 12, 2026 at 09:32:04AM +0100, José Matos wrote: > I have never seen the issues reported and I have been using wayland for a long > time. The only change from the original reporter is that I am using Qt 6.10. > > This is a work-around for a bug. To say that xcb is currently the only > reasonable solution for Wayland is incorrect or at most incomplete. I dont use Wayland at all, so just using information provided at #13305. If it was fixed by new Qt version, that would be great. But I see Radeon on the reporter's side and this smells like the real culprit - some drivers for gpu accelaration might break stuff... I do not have any opinion and can revert if you think the default on Wayland works fine. Any other Waylanders around to report their experience on xcb vs non-xcb? Pavel -- lyx-devel mailing list [email protected] https://lists.lyx.org/mailman/listinfo/lyx-devel
Re: [LyX/master] Fix #13305 - xcb is currently the only reasonable solution for Wayland
On Tue, 2026-05-12 at 09:31 +0200, Pavel Sanda wrote: > Riki, ok to backport? P What is the culprit here? Version 2.5.1 (Sunday, 12 April 2026) Qt Version (run-time): 6.10.3 on platform wayland Qt Version (compile-time): 6.10.2 OS Version (run-time): Fedora Linux 44 (KDE Plasma Desktop Edition) Python detected: 3.14.4 (/usr/bin/python3) Draw strategy: partial draw on backing store I have never seen the issues reported and I have been using wayland for a long time. The only change from the original reporter is that I am using Qt 6.10. This is a work-around for a bug. To say that xcb is currently the only reasonable solution for Wayland is incorrect or at most incomplete. -- José Abílio -- lyx-devel mailing list [email protected] https://lists.lyx.org/mailman/listinfo/lyx-devel
Re: [LyX/master] Fix #13305 - xcb is currently the only reasonable solution for Wayland
On Tue, May 12, 2026 at 05:44:42AM +, Pavel Sanda wrote: > commit aeaaef66b6374c43195411acda6b06be4e3b6811 > Author: Pavel Sanda > Date: Tue May 12 07:43:07 2026 +0200 > > Fix #13305 - xcb is currently the only reasonable solution for Wayland Riki, ok to backport? P -- lyx-devel mailing list [email protected] https://lists.lyx.org/mailman/listinfo/lyx-devel
