Bug 408579 - MellowPlayer don't shows in notification app list
Summary: MellowPlayer don't shows in notification app list
Status: RESOLVED DUPLICATE of bug 407716
Alias: None
Product: plasmashell
Classification: Plasma
Component: Notifications (show other bugs)
Version: 5.16.0
Platform: Neon Linux
: NOR normal
Target Milestone: 1.0
Assignee: Kai Uwe Broulik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-11 18:59 UTC by boingo-00
Modified: 2019-06-12 08:58 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
History list (21.54 KB, image/jpeg)
2019-06-11 18:59 UTC, boingo-00
Details
App list (8.40 KB, image/jpeg)
2019-06-11 19:00 UTC, boingo-00
Details

Note You need to log in before you can comment on or make changes to this bug.
Description boingo-00 2019-06-11 18:59:41 UTC
Created attachment 120795 [details]
History list

SUMMARY
I want disable notification history for MellowPlayer, but it don't show in app list

STEPS TO REPRODUCE
1. Get notification in history
2. go to settings

OBSERVED RESULT
MellowPlayer in list, disabling history


EXPECTED RESULT
MellowPlayer isn't in list


SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.16
KDE Plasma Version: 5.16.0
KDE Frameworks Version: 5.59.0
Qt Version: 5.12.3
Kernel Version: 5.1.9-050109-generic
OS Type: 64-bit
Processors: 4 × AMD Phenom(tm) II X4 955 Processor
Memory: 7,8 ГиБ


ADDITIONAL INFORMATION
MellowPlayer 3.5.4.0
Comment 1 boingo-00 2019-06-11 19:00:16 UTC
Created attachment 120797 [details]
App list
Comment 2 Kai Uwe Broulik 2019-06-11 21:22:34 UTC
It doesn't seem to send a desktop-entry in its notification. This is likely an application bug.
Comment 3 Kai Uwe Broulik 2019-06-11 21:27:30 UTC
Probably needs a 
notify_notification_set_hint (n, "desktop-entry", QGuiApplication::desktopFileName());
here: https://gitlab.com/ColinDuquesnoy/MellowPlayer/blob/master/src/lib/presentation/src/Notifications/Presenters/Linux/LibnotifyPresenter.cpp#L59

Please file a bug report against MellowPlayer, thanks!
Comment 4 Kai Uwe Broulik 2019-06-12 08:58:05 UTC
Turns out, that was already reported and supposedly fixed in a newer version. Thanks anyway

*** This bug has been marked as a duplicate of bug 407716 ***