https://bugs.kde.org/show_bug.cgi?id=458865
--- Comment #46 from Antonio Rojas <aro...@archlinux.org> --- (In reply to Adam Williamson from comment #45) > So we have folks running into this on Fedora: > https://bugzilla.redhat.com/show_bug.cgi?id=2133795 > > It looks like we don't have the change from this bug report yet. However, > Fedora users will generally be on Wayland, and the change from this bug > report is only to startplasma-x11.cpp. I notice that in > startplasma-wayland.cpp , `setupCursor` still happens very early - in fact > it's nearly the *first* thing that happens. Does it need to be delayed on > Wayland too? For the Wayland session, when setupCursor is called is irrelevant for this issue, because on Wayland setupCursor does not launch kapplymousetheme (or any other QApplication) [1], so it doesn't activate xdg-desktop-portal [1] https://invent.kde.org/plasma/plasma-workspace/-/blob/v5.26.0/startkde/startplasma.cpp#L208 Is anybody actually reporting wrong cursors on Wayland on Fedora? AFAICS the downstream bug report is about xdg-desktop-portal-kde crashes for the sddm user, which is also caused by the Qt change, but is unrelated to the wrong cursors issue. -- You are receiving this mail because: You are watching all bug changes.
