-
-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mate-notification-daemon fails to start on fedora f28 if multiple Desktops (mate, kde,gnome) #133
Comments
Works fine on my machine using Debian Unstable. I think the daemon is only supposed to start when a notification is actually sent. See if it is actually functional on your machine: open to mate-control-center, open "popuip notifications: and click the "preview" button. You should see a "Notification Test" popup on your screen at the position shown in the "position" button. You can select any of the four corners of the screen, and one of four themes. If you get NO popup notification on "preview" than the daemon is not starting when a notification is sent to it either. I saw on another issue report that dbus is used to activate this as needed, and it exits when the notification is done, rather than running as a fulltime daemon. |
Did you file out a redhat bugzilla report? |
Using notify-send from command line forks here out of box in f28.
|
Hi! I'm using MATE desktop since 2013 and I love it! Thank you, teams! This issue is one of the most annoying problems in MATE. Fortunately, the following workaround I found today worked for me: mkdir -p ~/.local/share/dbus-1/services/
ln -vnsfr $(rpm -ql mate-notification-daemon|grep Notifications.service) ~/.local/share/dbus-1/services/org.freedesktop.Notifications.service
Hope this helps. |
I think this is a kind of race condition. On one of my three Fedora Desktops (since at least F28) I need to remove I think the work around from the previous comment defines a higher priority definition for all services found in And just for clarification ... mate-notification-daemon does not stay in background nor needs to be started on session startup. It exists after some seconds anyway and gets started again by dbus if a message arrives. |
Note that I do NOT have kde installed, so might have avoided the race condition, assuming some difference in Debian would not prevent it anyway |
Will be fixed with #214 |
Relying on D-Bus activation to launch org.freedesktop.Notifications can result in selecting the wrong implementation if multiple daemons are installed. Fix this by launching m-n-d with the session rather than depending on D-Bus activation. We keep D-Bus activation for the moment for backward compatibility and to re-start the daemon in otherwise non-problematic situations if it crashes. Fixes #133 and #174.
Relying on D-Bus activation to launch org.freedesktop.Notifications can result in selecting the wrong implementation if multiple daemons are installed. Fix this by launching m-n-d with the session rather than depending on D-Bus activation. We keep D-Bus activation for the moment for backward compatibility and to re-start the daemon in otherwise non-problematic situations if it crashes. Fixes #133 and #174.
Expected behaviour
Expect mate-notification daemon to start allowing notify-send to function
Actual behavior
Mate-notification daemon never starts
Steps to reproduce the behaviour
Installed F27 upgrade to F28 then sudo dnf groupinstalll "Mate Desktop"
MATE general version
v 1.20
Package version
mate-notification-daemon.x86_64 1.20.0-1.fc28 @fedora
Linux Distribution
Link to downstream report of your Distribution
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: