Please consider supporting forwarding original notification app name (the field represented by
notify-send -a ).
Currently all forwarded notifications have 'Xpra' as their application name. Might be handy if it would read
$ORIGINAL_APPNAME (on $REMOTE_HOSTNAME), akin how window managers name remote windows.
The application name is already forwarded to the platform specific notification API.
Please provide more details as per wiki/ReportingBugs
Debian testing, Xpra 2.1.2, displaying notifications via dunst.
notify-send -a apptest test test
If run locally, notification is received with:
If run in remote session, notification is received with: application: Xpra summary: test body: test
Notifications from other apps in remote session are also displayed as coming from 'Xpra'.
Test application name is mentioned in client debug log:
2017-09-18 16:34:34,104 _process_notify_show(['notify_show', 'unix:abstract=/tmp/dbus-swCyiCvbB0,guid=67f6a91b10b2c27f09998bb559bf73e3', 9, 'apptest', 0, '', 'test', 'test', -1]) notifier=<xpra.client.notifications.dbus_notifier.DBUS_Notifier object at 0x7f35f27a5490>, server_supports_notifications=True 2017-09-18 16:34:34,106 notification reply: (dbus.UInt32(73L),)
So, problem might be on the client side.
Does r16909 fix things?
Yes, it works!
app_name + " (via Xpra)" (or mentioning remote hostname)?
ie: you can change the string using
XPRA_NOTIFICATION_APP_NAME="Hello %s (via Xpra" xpra attach ...
We can't use the remote host name because it isn't available to the notification backends at present.
It works, thanks!
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1647