+++ This bug was initially created as a clone of Bug #751355 +++ Yet again, notify-send suddenly stopped working for me over SSH in an F17 installation. Workaround for me was to add yet another env variable (beside XAUTHORITY and DISPLAY currently used): > export $(cat /proc/$(pidof openbox)/environ | xargs -0 -I '{}' echo '{}' \ > | grep DBUS_SESSION) This will export DBUS_SESSION_BUS_ADDRESS so remote notify-send will not try to communicate with D-Bus for another session (new?), but rather will connect to the main one related to my desktop session. Despite this might be a good step security-wise (enforcing separation of D-Bus sessions), this is clearly a regression. Admittedly, this regression may have been introduced completely outside the scope of notify-send (libnotify), however notify-send is the final component suffering from this in the user's eyes. - on the target machine where I run notify-send (through SSH session): $ rpm -q libnotify notification-daemon dbus openssh libnotify-0.7.5-1.fc17.x86_64 notification-daemon-0.7.4-1.fc17.x86_64 dbus-1.4.10-7.fc17.x86_64 openssh-5.9p1-28.fc17.x86_64 # grep -e "libnotify" -e "notification-daemon" -e "dbus" -e "openssh" \ /var/log/yum.log Feb 25 15:05:23 Installed: libnotify-0.7.5-1.fc17.x86_64 - on the machine I'm ssh'ing from: $ rpm -q openssh openssh-5.3p1-81.el6_3.x86_64
This was changed by dbus maintainers/upstream on purpose.
*** Bug 869268 has been marked as a duplicate of this bug. ***
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
Hm, strange. Now I'm able to run against both F17 and F18: ssh $HOST 'DISPLAY=:0 notify-send foo' i.e., no explicit setting of XAUTHORITY nor DBUS_SESSION_BUS_ADDRESS (checked also env) ... and it works. Might be related to my previous experiments with dbus-launch, but this behavior persisted even if I killed all recent processes containing "dbus".
... or might be related to something not being settled properly upon libnotify update (cf. bug creation date and the grep'd line from /var/log/yum.log in CET/+0200).
Just hit this issue on a newly installed F21. I have a remote notify script which uses notify-send over ssh that worked in F20. Now it no longer works. I can verify doing manual commands too. What works - local notify-send 1 - open terminal 2 - Run 'notify-send test' 3 - See test message on local screen What doesn't - remote login notify-send 1 - from a remote host, ssh into the local box as the locally logged in user (in fact ssh@localhost works too) 2 - Run 'notify-send test' 3 - No message Even attempted setting $DISPLAY with no luck. Verions: libnotify-0.7.6-4.fc21.x86_64
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.
Reproduced on F23
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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.
I was unable to reproduce this on F25. Seems to be fixed there.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.