| Summary: | Plasma widgets freeze after a while when unfocused or after getting a notification | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Akseli Lahtinen <akselmo> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | normal | CC: | kde, nate, niccolo.venerandi, patrick.auernig |
| Priority: | NOR | ||
| Version First Reported In: | 5.26.3 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| URL: | https://gitlab.freedesktop.org/mesa/mesa/-/issues/7624 | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Akseli Lahtinen
2022-11-24 21:03:18 UTC
Seems that just refreshing the web page on firefox also wakes up the widgets momentarily, but they pause again quickly. In my journalctl I see following around same time the pause happens: Nov 24 23:03:58 fedora kded5[1843]: org.kde.plasma.appmenu: Got an error Nov 24 23:03:58 fedora kded5[1843]: org.kde.plasma.appmenu: Got an error Even faster way to make this bug happen is using notify-send
Whenever I do notify-send, the notification pops up and the notification counter circle starts going down. However at certain point it just pauses, and this pauses all widgets etc.
This also appears during the bug:
Nov 24 23:06:57 fedora plasmashell[33591]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x56114051f740) QQmlContext(0x56113e372af0) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Nov 24 23:06:57 fedora plasmashell[33591]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x56114051f740) QQmlContext(0x56113e372af0) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
This bug is likely related to this: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7624 Fixed the issue for myself by going back to the regular mesa Fedora provides, instead of using mesa-git. That sounds like an issue on mesa's side, then? Yes, I forgot to close the issue :) *** Bug 463242 has been marked as a duplicate of this bug. *** |