Custom Query (2683 matches)

Hi,

having problems to get the nvenc proxy feature ready:

server xenial 16.04 client xenial 16.04 xpra version: xpra proxy version 2.0.1-r15494 64-bit

i start the Proxy Server with:

xpra proxy :100 --bind-ssl=0.0.0.0:443 --auth=multifile:filename=./xpra-auth --ssl=on --ssl-cert=/home/${USERNAME}/gpunode.crt --ssl-key=/home/${USERNAME}/gpunode.key --no-daemon -d encoding 

and i will get no nvenc accl.

2017-04-04 16:30:07,595 created unix domain socket: /root/.xpra/fb06389bf2ef-100
2017-04-04 16:30:07,595 created unix domain socket: /var/run/xpra/fb06389bf2ef-100
2017-04-04 16:30:07,608 Warning: failed to load the mdns avahi publisher:
2017-04-04 16:30:07,608  No module named avahi
2017-04-04 16:30:07,608  either fix your installation or use the 'mdns=no' option
2017-04-04 16:30:07,632 xpra proxy version 2.0.1-r15494 64-bit
2017-04-04 16:30:07,632  uid=0 (root), gid=0 (root)
2017-04-04 16:30:07,632  running with pid 2622 on Linux Ubuntu 16.04 xenial
2017-04-04 16:30:07,632 xpra is ready.
2017-04-04 16:30:16,928 New SSL connection received from 141.3.42.171:52244
2017-04-04 16:30:16,933 Authentication required by multi password file authenticator module
2017-04-04 16:30:16,934  sending challenge for username 'postatom' using hmac+sha512 digest
2017-04-04 16:30:17,294 video_init() loading codecs
2017-04-04 16:30:17,466 CUDA initialization (this may take a few seconds)
2017-04-04 16:30:17,786 CUDA 8.0.0 / PyCUDA 2016.1.2, found 1 device:
2017-04-04 16:30:17,786   + GeForce GTX 980 Ti @ 0000:04:00.0 (memory: 96% free, compute: 5.2)
2017-04-04 16:30:17,967 NVidia driver version 375.39
2017-04-04 16:30:20,829 Warning: hardware or nvenc library version does not support YUV444
2017-04-04 16:30:21,090 NVENC successfully initialized
2017-04-04 16:30:21,111 video_init() will try video encoders: none
2017-04-04 16:30:21,112 encoder types found: ()
2017-04-04 16:30:21,112 proxy video encoders: 
2017-04-04 16:30:21,112 new proxy instance started
2017-04-04 16:30:21,112  for client SSL socket: 172.17.0.4:443 <- 141.3.42.171:52244
2017-04-04 16:30:21,112  and server tcp socket: 172.17.0.4:58496 <- 172.17.0.3:10002
2017-04-04 16:30:21,115 proxy instance now also available using unix domain socket:
2017-04-04 16:30:21,115  /home/xpradistributor/.xpra/fb06389bf2ef-proxy-2639

maybe any hint?

greets

Version: Xpra gtk2 client version 2.1.3-r17247 64-bit Platform: Debian Stretch / Devuan Ascii Kernel: Linux 4.9.0-3-amd64 [Debian version: 4.9.30-2+deb9u5 (2017-09-19)]

Running more than one xpra instance yields a separate system tray icon for each; however, I don't see any useful or immediate indication anywhere which system tray belongs to which instance.

The only visual association between a tray and an xpra instance seems to require first selecting the tray menu item "raise windows", which will switch focus to that instance's xpra window, if that's noticeable.

There are two textual indications, but they aren't very useful (to me as a user, at least):

1) there is a tooltip on mouse hover over each tray icon which by default indicates the X display number only.

1.1) One can invoke a server or client with the option "--session-name"; however, once a session has started and client attached, I see no way to name the session, or to rename the session.

2) The same limited information is deep in the system tray menu. Select tray menu item "session info", then select tab "connections", then observe the server / client display. If you remember which is which, that would be useful, I guess, in a very delayed manner. However, on that screen, session names do not appear.

3) When a session is named on the server side, ie. when invoking xpra start, the system tray menu labels its second menu item as "session info". However, when naming the session on the client side, ie. when invoking xpra attach, that menu item is labeled "info: <session-name>", which is much more useful.

Suggestions:

A] Combine all system trays into a single icon, in order to reduce clutter in the system tray, and have the menu cascaded, where the first level indicates the X display --AND-- some other identifier for the instance, such as the session name or the name of the program initially launched.

B] Set a session name by default instead of having it blank. Maybe use the command line of the program launched.

C] Allow renaming live sessions, from the system tray and from the command line.

D] Include session-name in the output of xpra list

E] Include session-name in the display tabs of the "session-info"

• It would be a convenience for users to be able to perform command-line actions such as xpra attach or xpra stop by referring to a session-name instead of a display-id.

• It would also be convenient to be able to specify more than one session-name or display-id for a command, and for such commands to fork asynchronously (multi-core micro-processors and all that), eg. xpra attach :1 :2 :3

• It would also be convenient to be able to refer to all sessions, eg. xpra stop all