Bug 390562 - Network Management Notification Connection Event
Summary: Network Management Notification Connection Event
Status: RESOLVED DUPLICATE of bug 389284
Alias: None
Product: frameworks-knotifications
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-16 14:56 UTC by Nick Cross
Modified: 2018-02-16 17:45 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Cross 2018-02-16 14:56:30 UTC 
Using a fully updated Fedora 27 Plasma 5.11.5 I have customised the Network Management , Event Notification and Actions options so that on "Connection Activated" it also :
Logs to a file (/tmp/connection-activated)
And runs a script (e.g. /bin/notify-send "testmessage" )

While it successfully logs to a file it does not seem to pop up the notification correctly from the notify-send i.e. the command is not run. This seems to happen with any script.

To avoid settings pollution (etc) I reproduced this within a VM as well.
Comment 1 Nick Cross 2018-02-16 14:57:36 UTC 
This used to be working fine prior to some recent updates in Plasma.
Comment 2 David Edmundson 2018-02-16 15:20:28 UTC 
There's a commit

2690452736956f73c2348357e5e45b9f643e7f95

    Fix loading NotifyByExecute

Yet ironically, it seems to have broken it.
Comment 3 Kai Uwe Broulik 2018-02-16 15:49:18 UTC 
Depends. It was fine up until 5.41, then it was broken in 5.42 and only fixed in just released 5.43. I suspect Fedora is still shipping 5.42 (judging from the fact it's Plasma 5.11) which is the broken version.

Can you confirm your KDE Frameworks version?
Comment 4 Nick Cross 2018-02-16 15:57:18 UTC 
I've added an upstream issue in https://bugzilla.redhat.com/show_bug.cgi?id=1546197

Info centre shows KDE Frameworks version at 5.42.0.
Comment 5 Rex Dieter 2018-02-16 17:45:41 UTC 

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