Bug 494950 - Flatpak apps don't get their own entry in the applications notifications settings
Summary: Flatpak apps don't get their own entry in the applications notifications sett...
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: Notifications (other bugs)
Version First Reported In: master
Platform: Debian stable Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-10-17 18:50 UTC by kde
Modified: 2024-11-19 06:23 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Demonstration of the bug after triggering a notification from the Plexamp flatpak (903.88 KB, video/x-matroska)
2024-10-17 18:56 UTC, kde
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kde 2024-10-17 18:50:51 UTC
SUMMARY
Flatpak apps don't get their own entry in the applications notifications settings.
Instead - notifications are sent from Plasma Workspace and thus always have sounds and cannot be configured otherwise.

STEPS TO REPRODUCE
1.  Download a flatpak application
2.  Launch the application and trigger a notification from that app

OBSERVED RESULT
When pressing the configure button on the notification, it appears that the notification is sent from Plasma Workspace and not from the app itself. Furthermore, an entry for the application in the applications notifications settings is not being created.

EXPECTED RESULT
Notifications are sent from the flatpak app itself and an entry is created in the applications notifications settings so we can configure it as we wish.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version:  5.27.5
KDE Frameworks Version:  5.103.0
Qt Version:  5.15.8

ADDITIONAL INFORMATION
This doesn't happen in GNOME. In GNOME each flatpak app gets its own notification entry as expected.
Comment 1 kde 2024-10-17 18:56:47 UTC
Created attachment 174957 [details]
Demonstration of the bug after triggering a notification from the Plexamp flatpak
Comment 2 Nate Graham 2024-11-13 02:17:00 UTC
IIRC apps that can send notifications need to be given access to the notification server in the Flatpak manifest.
Comment 3 TraceyC 2024-11-18 23:29:42 UTC
Tested the assertions:
1. When pressing the configure button on the notification, it appears that the notification is sent from Plasma Workspace and not from the app itself. 
2. An entry for the application in the applications notifications settings is not being created.

I am not able to reproduce this on git-master.

Tested with the Tidal flatpak on git-master, which allows a notification on every song change
The notification has the title "Tidal Hi-Fi" (not Plasma Workspace)
Clicking on the settings brings up "Application Settings" and I see the entry for Tidal with its icon and title
Same for Spotify

Neither app show the ability to edit sound events. Where this section is for other apps in that window you'll see 
"This application does not support configuring notifications on a per-event basis"

What flatpak application have you installed that shows the behavior described?
Comment 4 kde 2024-11-19 06:23:15 UTC
Hi, thanks for the comments.
I've moved to Fedora with KDE Plasma 6.2.3 since opening this bug report and it works perfectly fine there.
So unless another user encounters it, this can be considered as resolved.