xpra icon
Bug tracker and wiki

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


Custom Query (2683 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (43 - 45 of 2683)

Ticket Resolution Summary Owner Reporter
#1733 needinfo Bad word-choice in error messages: FAILURE Boruch Boruch
Description

The STDERR messages seem to be more alarmist than necessary, and give me a false feeling that xpra itself may have failed, or that some critical feature has failed, when such does not seem to be the case. The following sample paste of an xpra STDERR illustrates with two examples:

1511 $2018-01-03 00:02:08,828 server failure: disconnected before the session could be established
2018-01-03 00:02:08,830 server requested disconnect: server error (error accepting new connection)
2018-01-03 00:02:08,846 server failure: disconnected before the session could be established
2018-01-03 00:02:08,847 server requested disconnect: server error (error accepting new connection)
Warning: cannot use the system proxy for 'start' subcommand,
 FAILURE

1] The initial messages indicate that the server experienced a failure, but the server seems fine.

2] The final message issues a warning, followed by a cryptic (and alarming) "FAILURE".

This choice of words does xpra a dis-service, in that it makes me (and probably other users) unsure and uncomfortable with the product's stability and functionality.

My suggestion is to reserve the word 'failure' for situations that render the software unusable. Maybe otherwise use the word "error". Alternatively, a term such as "non-critical failure" might be appropriate.

#1744 fixed Add python2-websockify to centos repository Chris Hills Chris Hills
Description

It would be useful if python2-websockify was in the winswitch centos repository as it is not available in the base centos repo in order to make installation more straightforward.

#1809 fixed Remote windows jump back into screen Cigaes Cigaes
Description

Hi.

If I have a remote window forwarded by Xpra and for some reason I move it entirely beyond the right edge of the screen, then it immediately jumps back into the screen, on the right side.

To make things more explicit: if the window is 800×600 on a 1920×1200 screen, if I move the window to x=1919, it stays there, but if I move it to x≥1920, then it immediately jumps back to x=1120.

The same happens vertically when I move the window beyond the bottom of the screen.

It happens a lot with Fvwm's viewport scrolling (it is implemented by moving all the windows in the opposite direction): if I have a window on the current screen and I scroll to a screen on the left, the window follows, almost as if it was sticky.

But the problem is not specific to Fvwm: I just reproduced it starting the Xpra client in Xephyr without a window manager and moving the window with xdotool:

DISPLAY=:1 xdotool windowmove 0x200081 1279 10
DISPLAY=:1 xdotool windowmove 0x200081 1280 10

After the first command, the left edge of the window is still visible on the right of the screen. After the second command, the window jumps back immediately. On the other hand, nothing happens if I move the window to a negative position, even way beyond the edge of the screen.

The Xpra version I am using is 0.17.6+dfsg-1+b3 from Debian on both client and server, but I observed the problem with older versions.

The window manager I use is Fvwm but as I explained above the problem can be reproduced without a window manager.

The command line I used to start it was:

xpra --exit-with-children --start-child=xterm start ssh:ssecem:11

The console output is:

2018-04-16 16:08:25,753 Xpra gtk2 client version 0.17.6-r14322
2018-04-16 16:08:25,753  running on Linux debian buster/sid
2018-04-16 16:08:26,448 GStreamer version 1.14 for Python 2.7
2018-04-16 16:08:26,772 PyOpenGL warning: missing accelerate module
2018-04-16 16:08:26,788 OpenGL support is missing:
2018-04-16 16:08:26,788  vendor 'VMware, Inc.' is blacklisted!
2018-04-16 16:08:26,850 failed to instantiate the dbus notification handler:
2018-04-16 16:08:26,850  you may need to start a notification service for 'org.freedesktop.Notifications'
2018-04-16 16:08:26,850  disable notifications to avoid this warning
2018-04-16 16:08:26,862  detected keyboard: rules=evdev, model=pc105, layout=us
2018-04-16 16:08:26,863  desktop size is 1280x800 with 1 screen:
2018-04-16 16:08:26,863   :1.0 (433x271 mm - DPI: 75x74)
2018-04-16 16:08:26,863     monitor 1 (339x212 mm - DPI: 95x95)
Entering daemon mode; any further errors will be reported to:
  /home/cigaes/.xpra/:11.log
2018-04-16 16:08:31,914 Xpra X11 server version 0.17.6-r14322
2018-04-16 16:08:31,914  running on Linux debian buster/sid
2018-04-16 16:08:31,915 enabled remote logging

I do not see anything interesting in ~/.xpra/:11.log.

Note: See TracQuery for help on using queries.