https://bugs.kde.org/show_bug.cgi?id=429211
--- Comment #28 from Wyatt Childers <dark...@nearce.com> --- (In reply to Prajna Sariputra from comment #27) > (In reply to Wyatt Childers from comment #24) > > This started happening for me, or at least something close to one of the > > duplicate bugs within the last week or so. Everything was fine, and now it's > > regularly breaking. Nothing fixes the problem other than restarting the > > session (i.e., user interaction with plasma is not sufficient to get the > > clock or notification area to start updating again). > > > > https://bugzilla.redhat.com/show_bug.cgi?id=2048151 > > Was there by any chance an update to qt5-qtwayland that you installed before > the issue occurred for you? That was what triggered the problem for me on > Arch, and downgrading that package fixed it in my case, so that might be > worth a try. For Arch the problematic package is `qt5-wayland > 5.15.2+kde+r44-1` and newer, looking through the sources the Fedora 35 > equivalent to that is `qt5-qtwayland 5.15.2-17.fc35`. On the 23rd (which roughly lines up): Upgrade qt5-qtwayland-5.15.2-17.fc35.x86_64 @updates Upgraded qt5-qtwayland-5.15.2-15.fc35.x86_64 @@System There isn't even a version bump there though, so that seems unlikely. I don't really have a way to rollback/downgrade (I'm not aware of any source for the old package). That said, it looks like they did "pull fixes" which maybe weren't fixes: https://src.fedoraproject.org/rpms/qt5-qtwayland/commits/f35 Namely: - Build 16 (https://src.fedoraproject.org/rpms/qt5-qtwayland/c/7500ad163e15e45219177b30dc1523aff14803eb?branch=f35) - Build 17 (https://src.fedoraproject.org/rpms/qt5-qtwayland/c/770c4ae5bb6d2bb7d2e4659d0fa1c822a005fe8e?branch=f35) It looks like there's a build 18 in the works to try to fix the issue (https://src.fedoraproject.org/rpms/qt5-qtwayland/c/d87aaf116e415d92178345ef5f84b2bc98e5ddd7?branch=f35). -- You are receiving this mail because: You are watching all bug changes.
