Xpra: Ticket #1688: warning notifications

If something goes wrong, the message ends up in the console output and server log (via remote logging), but most users won't look there and will therefore be unaware of the problem.

We should add an option to allow notifications to be used for major events, ie: another user joined the session, file uploads (#1375), the connection is having problems (#401)

The initial warnings during the client startup could be bunched up together to avoid spamming the notification system with multiple messages on startup. In any case, this should probably be rate limited and controllable from the system tray menu.


See also: #1492, #1305

Tue, 14 Nov 2017 14:10:33 GMT - Antoine Martin: status, description changed

Sun, 26 Nov 2017 13:05:22 GMT - Antoine Martin: milestone changed

Mon, 22 Jan 2018 15:50:28 GMT - Antoine Martin:

Large change in r18110: refactoring + a user joining the session will trigger a notification message sent to:

Still TODO:

Tue, 23 Jan 2018 12:52:02 GMT - Antoine Martin:

Still TODO:

Fri, 26 Jan 2018 15:25:58 GMT - Antoine Martin:

Tue, 30 Jan 2018 08:10:47 GMT - Antoine Martin: owner, status changed

The new "-d bandwidth" debug switch can be used to see how we try to manage the bandwidth.

From now on, we can easily add more warning notifications as we go along.

To test:

All of this should work equally well on all platforms, including the html5 client. But full backwards compatibility with older clients is not possible and those will just not be aware of the notification actions.

Thu, 01 Feb 2018 23:52:22 GMT - J. Max Mena: owner changed

Okay I've tested this on every platform I have available to me immediately:

Everything appears to be working as expected. Is there anything left to do or should I close this?

Fri, 02 Feb 2018 04:32:41 GMT - Antoine Martin: status changed; resolution set

Fri, 02 Feb 2018 12:01:36 GMT - Antoine Martin:

Also use notifications for reporting failures in:

Minor related fixes:

Sat, 23 Jan 2021 05:31:07 GMT - migration script:

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1688