| Summary: | Notifications provided by other software than Plasma - unclear how to revert | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | postix <postix> |
| Component: | Notifications | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | kde, nate |
| Priority: | NOR | ||
| Version First Reported In: | 6.1.4 | ||
| Target Milestone: | 1.0 | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Screenshot | ||
Test notification created with ``` notify-send -a "Thunderbird" -u normal "Header" "[Test] Body" -i "/usr/lib64/thunderbird/chrome/icons/default/default64.png" ``` That's a notification from Thunderbird, not Plasma. Apps will start sending their own custom notifications if they find that there's no notification server in Plasma running when they launch, or if it goes away while they're running. The former can happen if Plasma wasn't running by the time they launched, and the latter can happen if Plasma crashes and doesn't re-launch while the're were running. It seems your system is in an inconsistent state; a reboot ought to fix it. If you have Thunderbird set to auto-launch, and it launches before Plasmashell is finished loading, that would be the cause of the problem. Can you check on those? (In reply to Nate Graham from comment #2) > That's a notification from Thunderbird, not Plasma. You got misled by the Thunderbird icon, check Comment 2, this was a custom `notify-send` message to illustrate the issue. :) > It seems your system is in an inconsistent state; a reboot ought to fix it. I always use `zypper dup` and reboot. I wonder how it should went into an inconsistent state. Another dup and reboot hasn't helped unfortunately. Can you think of any reason where this style may come from? Also notifications now are displayed persistent until they are clicked and don't time out. Plasma is great, the Notifications KCM told me:
> Notifications are currently provided by 'emersion mako' instead of Plasma.
I have no idea, how that happened though! :D
However, it would be great to know to change this back to Plasma. Couldn't there be a setting for this? I've installed Sway additionally. Anyway, after `zypper remove mako && systemctl reboot` ...
> Notifications are currently provided by 'ErikReider SwayNotificationCenter' instead of Plasma.
Seems like I need to get rid of Sway completely unless there's some hidden setting somewhere?
Yep, that's another thing that can cause this. Because notifications are a standardized FreeDesktop spec, multiple pieces of software can register themselves to handle notifications. Plasma has one, but other software can do it too. Evidently Sway has one, and that's what's running. There is no way to choose which one does it; it's just a matter of which one launches first. I guess the Sway one is faster to launch. :) In this case it seems like we've unearthed a setup issue on your system: the Sway notification daemon is running when you're in Plasma. That's a bug; their notification system shouldn't be running while Plasma is running. This is either a bug in the software for not failing to terminate itself when Plasma is the active DE, or some kind of local configuration issue on your system. |
Created attachment 173130 [details] Screenshot SUMMARY Since a recent update, notifications have started to look wrong. Please see the screenshot. I use the Breeze theme. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240829 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.5-1-default (64-bit) Graphics Platform: Wayland