Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: All of the following work on RHEL 6 under GNOME when logged in as "testuser" (meaning that DISPLAY is properly set for each command): $ notify-send test $ su - Password: # notify-send test # su testuser -c "notify-send test" Only the following work on F17: $ notify-send test $ su - Password: # su testuser -c "notify-send test" But under F18 sending notifications to the desktop user as root with notify-send does not work with either of the commands working on RHEL 6. Is this to be expected? If yes then what's the recommended way to send notifications to the user as root on F18 instead of notify-send? Thanks.
# su mclasen -c "notify-send test" works fine here. What error are you seeing ?
I don't see anything, i.e., no notification, no error, but strace output reveals: "The name org.freedesktop.Notifications was not provided by any .service files" And it can be seen also that notification-daemon is not running altough the package is installed. This is on freshly installed F18 + all available updates installed. Please let me know if you need any additional details or logs. Thanks.
gnome-shell is providing org.freedesktop.Notifications on the session bus. Isn't gnome-shell running ?
(In reply to comment #3) > gnome-shell is providing org.freedesktop.Notifications on the session bus. > Isn't gnome-shell running ? It is. Selected GNOME desktop during installation but no add-ons, then all defaults till the first login to discover that notify-send fails for root but not for the testuser. Putting SELinux in Permissive doesn't help. Thanks.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Problem is reproducible with Rawhide (20130224). Haven't checked F18. All of the following doesn't manage to send any notification: $ su - Password: # notify-send blubb # su mygnomeuser -c "notify-send blubb" # Only the currently logged in GNOME user can send notifications.
*** This bug has been marked as a duplicate of bug 915346 ***