I have seen xpra auto-assume low number displays:
u@h:/etc/xpra/conf.d$ xpra start --attach=yes --start=gnome-terminal xpra for python 2.7 is not installed retrying with python3 Entering daemon mode; any further errors will be reported to: /run/user/1000/xpra/display-S6777-$TIMESTAMP.log u@h:/etc/xpra/conf.d$ Actual display used: :4 Actual log file name is now: /run/user/1000/xpra/display-:4-$TIMESTAMP.log u@h:/etc/xpra/conf.d$ xpra upgrade :4 xpra for python 2.7 is not installed retrying with python3 WARNING: low display number: 4 You are attempting to run the xpra server against a low X11 display number: ':4'. This is generally not what you want. You should probably use a higher display number just to avoid any confusion and this warning message. Entering daemon mode; any further errors will be reported to: /run/user/1000/xpra/display-:4-$TIMESTAMP.log
... and when upgrading, this happens. Is it a problem if xpra becomes pedantic and prefer higher number displays? (I think it was >:10 or something?)
That was already fixed in trunk by r24808, now backported to v3 in r25671.
Are those warnings expected?
u@h:~$ cat /run/user/1000/xpra/display-:2-$TIMESTAMP.log 2020-03-16 21:37:16,265 created unix domain socket '/run/user/1000/xpra/userlinux-precision-t3620-2' 2020-03-16 21:37:16,265 created unix domain socket '/run/xpra/userlinux-precision-t3620-2' 2020-03-16 21:37:16,337 pointer device emulation using XTest 2020-03-16 21:37:16,380 serving html content from '/usr/share/xpra/www' 2020-03-16 21:37:16,389 xvfb pid=21682 2020-03-16 21:37:16,390 found previous Xpra instance 2020-03-16 21:37:16,923 Warning: OpenGL support check failed: 2020-03-16 21:37:16,923 unknown error 2020-03-16 21:37:17,152 Warning: failed to load the mdns publisher 2020-03-16 21:37:17,153 No module named 'avahi' 2020-03-16 21:37:17,153 either install the 'python-avahi' module 2020-03-16 21:37:17,153 or use the 'mdns=no' option 2020-03-16 21:37:17,169 D-Bus notification forwarding is available (Xpra:25752): Gtk-CRITICAL **: gtk_widget_realize: assertion 'widget->priv->anchored || GTK_IS_INVISIBLE (widget)' failed 2020-03-16 21:37:17,184 printer forwarding enabled using postscript and pdf 2020-03-16 21:37:17,185 Warning: cannot watch for application menu changes without pyinotify: 2020-03-16 21:37:17,185 No module named 'pyinotify' 2020-03-16 21:37:17,210 xpra is ready. 2020-03-16 21:37:17,211 xpra GTK3 X11 version 3.0.7-r25609 64-bit 2020-03-16 21:37:17,425 uid=1000 (userlinux), gid=1000 (userlinux) 2020-03-16 21:37:17,426 running with pid 25752 on Linux Ubuntu 16.04 xenial 2020-03-16 21:37:17,426 connected to X11 display :2 with 24 bit colors 2020-03-16 21:37:17,812 Warning: icon is quite large (273 KB): 2020-03-16 21:37:17,813 '/usr/share/pixmaps/com.visualstudio.code.insiders.png' 2020-03-16 21:37:18,567 62.7GB of system memory
Warning: OpenGL support check failed: unknown error
run xpra opengl-probe
from within the xpra session to get more details
Warning: failed to load the mdns publisher ...
Follow the instructions in that message to get rid of the warning.
(Xpra:25752): Gtk-CRITICAL **: gtk_widget_realize: assertion 'widget->priv->anchored || GTK_IS_INVISIBLE (widget)' failed
Some GTK internal thing we cannot silence, safe to ignore.
Warning: cannot watch for application menu changes without pyinotify: No module named 'pyinotify'
Install python-pyinotify
.
Warning: icon is quite large (273 KB): '/usr/share/pixmaps/com.visualstudio.code.insiders.png'
We send the icons to the client when sending the start menu data... 273KB for a single start menu icon is excessive.
Replying to Antoine Martin:
Warning: OpenGL support check failed: unknown errorrun
xpra opengl-probe
from within the xpra session to get more details
$ xpra opengl-probe xpra for python 2.7 is not installed retrying with python3 (Xpra:12211): Gdk-ERROR **: The program 'Xpra' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 194 error_code 2 request_code 151 (GLX) minor_code 3) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Trace/breakpoint trap (core dumped)
I keep disabling it, since I think downscaling works worse on OpenGL.
Shouldn't that be handled more gracefully though? (at xpra level or lower)
Warning: failed to load the mdns publisher ...
Follow the instructions in that message to get rid of the warning.(Xpra:25752): Gtk-CRITICAL **: gtk_widget_realize: assertion 'widget->priv->anchored || GTK_IS_INVISIBLE (widget)' failedSome GTK internal thing we cannot silence, safe to ignore.
Warning: cannot watch for application menu changes without pyinotify: No module named 'pyinotify'Install
python-pyinotify
.Warning: icon is quite large (273 KB): '/usr/share/pixmaps/com.visualstudio.code.insiders.png'We send the icons to the client when sending the start menu data... 273KB for a single start menu icon is excessive.
Okay, it seems all of them are coming also normally regardless; I thought they were related to the upgrade operation.
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/2654