xpra icon
Bug tracker and wiki

This bug tracker and wiki are being discontinued
please use https://github.com/Xpra-org/xpra instead.

Version 6 (modified by Antoine Martin, 7 years ago) (diff)


[[Image(...)]] Session Info

The "Session Info" dialog is accessible in the following ways:

  • Under "Session Info" in the xpra system tray menu
  • Using the key shortcut Meta + Shift + F11 when an xpra window has the input focus
  • Using the xpra control command "show_session_info" on the server, ie:
    xpra control :10 client show_session_info

It looks like this: small screenshot for the overview


The software pane lists the versions of the most important components of the system for both the client and server: Xpra, (Py)GTK components, (Py)GStreamer, OpenGL, etc..

It allows you to quickly verify that the system is up to date.

You can see a screenshot here


The features pane shows more details about sound and picture encoding support and status, packet compression support, client OpenGL library version, bell, cursor, clipboard and mmap features, etc.

You can see a screenshot here


The connection pane shows information about the connection status: the endpoint location, server load, how old the session is and how long it has been connected, the number of packets and bytes received and sent, the type of connection, the encryption used (if any) and the packet compression and encoding algorithms in use, as well as the state of the sound buffers (if used).

You can see a screenshot here


The statistics pane shows various latency and quality data from the server, it can be used to monitor how well the system is self tuning to adapt to the network conditions:

  • Server Latency (ms): this is a measure of how long it takes for:
    • the client to send a "ping" packet
    • the server to receive it, process it and send the "echo" response
    • the client to process the response and calculate the latency It is very different from an ICMP Ping because it includes on both ends: the full operating system network stack, the operating system scheduler, the Python interpreter with its threads and locking, TCP re-transmits. On a busy system, this value may well go up as other packets are ahead of the send queue at either end. A modern CPU should be able to keep this value around 50ms plus the TCP connection latency (TCP packet drops can cause this value to increase more dramatically).

You can see a screenshot here

Attachments (6)

Download all attachments as: .zip