https://bugs.kde.org/show_bug.cgi?id=458865
--- Comment #47 from Adam Williamson <ad...@happyassassin.net> --- (In reply to Antonio Rojas from comment #46) > (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. Well, I was following on from your comment 34, but now I see that yeah, it doesn't run `kapplymousetheme` on Wayland. Yes, the downstream report is just about the crash under SDDM. I got here via the Arch report, and both do seem to discuss that crash. Is there a different bug report for that? Do we know what's causing it / have a fix? I don't think we know yet if there are any practical consequences of it, it's more just that people are noticing the crash report. Thanks! -- You are receiving this mail because: You are watching all bug changes.
