Bug 417529

Summary: Notifications Plasmoid can't provide notifications because the notifications service is "currently provided by KDE Plasma"
Product: [Plasma] plasmashell Reporter: The Feren OS Dev <ferenosdev>
Component: NotificationsAssignee: Kai Uwe Broulik <kde>
Status: RESOLVED DOWNSTREAM    
Severity: normal CC: hipantcii, plasma-bugs-null
Priority: NOR    
Version First Reported In: 5.18.0   
Target Milestone: 1.0   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Latte Dock Notifications Plasmoid after the bug is triggered

Description The Feren OS Dev 2020-02-13 00:44:27 UTC
Created attachment 125920 [details]
Latte Dock Notifications Plasmoid after the bug is triggered

SUMMARY
Every now and then, in the past Latte Dock would stop displaying and collecting notifications despite working just fine earlier, leading to confusion in the past with what happened.
Then came Plasma 5.18. Since Plasma 5.18's Notifications Plasmoid now says what the current notification service is if the notifications plasmoid cannot collect notifications, I can now report this bug having an idea on what on earth is even going on.

Every now and then, Latte Dock's instance of Plasma 5.18's Notifications Plasmoid will suddenly say the notifications service is unavailable because "Notifications are currently provided by 'KDE Plasma'".

STEPS TO REPRODUCE
1. Add Notifications to a Latte Dock/Panel.
2. Remove it from any Plasma panels, Plasma desktops, System Tray Plasmoids, etc.
3. Wait and hopefully get lucky enough for this bug to randomly trigger on your session.

OBSERVED RESULT
(see the attached image)

EXPECTED RESULT
Notifications Plasmoid will keep working just fine at all times like it does when on a Plasma panel.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: KDE neon 5.18.0
(available in About System)
KDE Plasma Version: 5.18.0
KDE Frameworks Version: 5.67.0
Qt Version: 5.13.2

ADDITIONAL INFORMATION
Comment 1 The Feren OS Dev 2020-02-13 15:29:51 UTC
Update: It seems like it's happening immediately on login now.
Comment 2 Kai Uwe Broulik 2020-02-13 15:31:54 UTC
Do you have any particular plasmoids setup?
Can you set a breakpoint in NotificationManager::Server::init and see if there's a plasmoid or someone registering notifications?
Comment 3 The Feren OS Dev 2020-02-13 15:37:39 UTC
(In reply to Kai Uwe Broulik from comment #2)
> Do you have any particular plasmoids setup?
> Can you set a breakpoint in NotificationManager::Server::init and see if
> there's a plasmoid or someone registering notifications?

How would I go about setting a breakpoint?

As for my Plasmoid config: It's just Feren OS's default - the only Notifications Plasmoid instance visibly used is in the Latte Dock up top. The bottom is a standard Plasma panel with notifications disabled in System Tray.
Comment 4 The Feren OS Dev 2020-02-13 16:30:59 UTC
So, it seems there was a secret Notifications Plasmoid instance running this whole time... nevermind then. So that's why this bug was occuring. Marking as Resolved Downstream.
Comment 5 The Feren OS Dev 2020-02-13 16:31:15 UTC
(Resetting the Desktop Layout fixed it)
Comment 6 idimitro 2021-02-08 19:33:14 UTC
@The Feren OS Dev  Could you please clarify what did you mean by (Resetting the Desktop Layout...)? 
I am on Plasma 5.20.5 and I've been getting this message from at least 5.19.