#2339 closed defect (fixed)
xpra control does not output error messages
Reported by: | stdedos | Owned by: | stdedos |
---|---|---|---|
Priority: | minor | Milestone: | 3.0 |
Component: | server | Version: | 2.5.x |
Keywords: | Cc: |
Description
From #2338: Running:
$ xpra control 0 clipboard-direction help $
Gives no output, but, in logs:
72 │ 2019-06-19 12:22:45,821 error processing control command 'clipboard-direction' 73 │ Traceback (most recent call last): 74 │ File "/usr/lib/python2.7/dist-packages/xpra/server/server_core.py", line 672, in process_control_command 75 │ v = command.run(*args[1:]) 76 │ File "/usr/lib/python2.7/dist-packages/xpra/server/control_command.py", line 69, in run 77 │ return super(ArgsControlCommand, self).run(*args) 78 │ File "/usr/lib/python2.7/dist-packages/xpra/server/control_command.py", line 31, in run 79 │ return self.do_run(*args) 80 │ File "/usr/lib/python2.7/dist-packages/xpra/server/mixins/server_base_controlcommands.py", line 452, in control_command_clipboard_direction 81 │ assert direction in DIRECTIONS, "invalid direction '%s', must be one of %s" % (direction, csv(DIRECTIONS)) 82 │ AssertionError: invalid direction 'help', must be one of to-server, to-client, both, disabled
Change History (5)
comment:1 Changed 3 years ago by
comment:2 Changed 3 years ago by
Owner: | changed from Antoine Martin to stdedos |
---|
I see:
$ xpra control :2 clipboard-direction help server returned error code 127 error processing control command: invalid direction 'help', must be one of to-server, to-client, both, disabled
Which is fine.
I originally changed it in r22995, but r22996 reverts it to ensure that we return a non-zero exit code when things fail.
Please provide more details so I can reproduce: commands used, exact version, exit code, etc..
comment:3 Changed 3 years ago by
Server version is v3.0-r22963. So, I guess you can close as already fixed?
comment:4 Changed 3 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:5 Changed 16 months ago by
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/2339
Note: See
TracTickets for help on using
tickets.
I also got this from the client:
(I don't know if it helps with anything)