Bug 1577571

Summary: After update f27 to f28 notify-send times out with error
Product: [Fedora] Fedora Reporter: Steve Foster <steve_a_foster>
Component: libnotifyAssignee: Kalev Lember <klember>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 28CC: alexl, dhgutteridge, john.j5live, klember, rhughes, rstrode, sandmann, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-28 23:32:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Steve Foster 2018-05-13 04:34:46 UTC
Description of problem:
notify-send non-functional (timeout accesssing mate-notification-daemon)

May 12 21:27:24 pita-24 dbus-daemon[25403]: [session uid=1003 pid=25403] Activating service name='org.freedesktop.Notifications' requested by ':1.187' (uid=1003 pid=40497 comm="notify-send crap ")
May 12 21:28:24 pita-24 plasma_waitforname[40501]: org.kde.knotifications: WaitForName: Service was not registered within timeout
May 12 21:28:24 pita-24 dbus-daemon[25403]: [session uid=1003 pid=25403] Activated service 'org.freedesktop.Notifications' failed: Process org.freedesktop.Notifications exited with status 1



Version-Release number of selected component (if applicable):
mate ver 1.20

How reproducible:
every time

Steps to Reproduce:
1. update f27 to F28
2.
3.

Actual results:
tries to load kde notify

Expected results:
should be using mate-notification-daemon

Additional info:

Comment 1 Wolfgang Ulbrich 2018-05-13 06:22:22 UTC
I don't see that issue here if kde isn't installed.

[root@mother rave]# dnf provides */notify-send
Last metadata expiration check: 0:45:32 ago on Sun May 13 07:34:56 2018.
libnotify-0.7.7-5.fc28.x86_64 : Desktop notification library
Repo        : @System
Matched from:
Filename    : /usr/bin/notify-send

Comment 2 David H. Gutteridge 2018-06-27 04:23:25 UTC
Confirming I can reproduce this issue on a machine that has both Mate and KDE installed (along with four other desktop environments).

Comment 3 Ben Cotton 2019-05-02 20:03:59 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Ben Cotton 2019-05-28 23:32:22 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.