Xpra: Ticket #83: dbus notification forwarding stops working after some time

Steps to reproduce:

Expected results:

Actual results:

More info:



Tue, 28 Feb 2012 10:25:09 GMT - Antoine Martin: status, description changed

I don't have a "notification-properties" here, will have to find out how to get it.. To make it easier to reproduce in a VM: what distro version should I use? (and what specific commands?) No idea what :1.62 is, were you using DISPLAY=:62? If so, where is the :1 from!?

Do you have a dedicated dbus running for the xpra session? If not this will not work.. (and maybe should be made clearer in the docs)


Tue, 28 Feb 2012 12:54:53 GMT - Timo Juhani Lindfors:

this is normal debian squeeze. The command is notification-properties. ":1.62" is dbus busname?

I use "env DISPLAY=:7 dbus-launch screen -S X" and run "xpra start :7" and all my graphical applications from that screen.

dbus-monitor has things like

signal sender=org.freedesktop.DBus -> dest=(null destination) serial=9 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged
   string "org.freedesktop.Notifications"
   string ":1.67"
   string ""
signal sender=org.freedesktop.DBus -> dest=(null destination) serial=10 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged
   string ":1.67"
   string ":1.67"
   string ""
signal sender=org.freedesktop.DBus -> dest=(null destination) serial=11 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged
   string ":1.68"
   string ":1.68"
   string ""

so maybe the notification-daemon leaves the bus and joins with another busname?


Mon, 05 Mar 2012 10:46:05 GMT - Antoine Martin:

before r583 we were always claiming the notification dbus name, which made it far too easy to stop notifications from working on the client or server (simply running xpra start ... would stop notifications from working where this was invoked if it had access to the dbus instance used by a real desktop as it would replace it).

Since re-connecting the client fixes the problem above, there may be another issue here: we may need to detect when the connection to dbus is dead and re-connect..


Mon, 05 Mar 2012 11:22:28 GMT - Antoine Martin: status changed; resolution set

In the end, testing for this was quite easy:

The fix in r585 simply detects when the notification service is not answering and attempts to re-connect to it.


Mon, 05 Mar 2012 11:30:47 GMT - Antoine Martin: milestone changed


Sat, 23 Jan 2021 04:45:03 GMT - migration script:

this ticket has been moved to: ‚Äčhttps://github.com/Xpra-org/xpra/issues/83