xpra icon
Bug tracker and wiki

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

Opened 7 years ago

Closed 7 years ago

Last modified 16 months ago

#1021 closed enhancement (invalid)

xpra control debug enable - doesn't seem to be taking multiple arguments at once

Reported by: alas Owned by: Antoine Martin
Priority: major Milestone: 0.16
Component: android Version: trunk
Keywords: Cc:


Testing with win client 0.16.0 r11118 against fedora 21 0.16.0 r11118 it doesn't look like the xpra control channel is taking multiple debug flags in one command.

Running xpra control :13 debug enable encoding,regiondetect on the server, for instance, outputs logging enabled for encoding,regiondetect immediately, but produces the following output from the server:

2015-11-02 19:14:46,058 New unix-domain connection received on /home/tlaloc/.xpra/jimador-13
2015-11-02 19:14:46,059 New unix-domain connection received on /home/tlaloc/.xpra/jimador-13
2015-11-02 19:14:46,064 Connection lost
2015-11-02 19:14:46,081 enabled debugging for: []
2015-11-02 19:14:46,168 Connection lost

Trying xpra control :13 debug enable encoding, regiondetect. in case the syntax was just off, immediately outputs logging enabled for encoding, + regiondetect, but the same enabled debugging for: [] from the server.

  • If I try one at a time, however: xpra control :13 debug enable encoding, for instance, then it works as expected.

Change History (2)

comment:1 Changed 7 years ago by Antoine Martin

Resolution: invalid
Status: newclosed
Type: defectenhancement

The control channel is working as designed: when more than one logging category is supplied it will try to find loggers that match all the categories supplied and only enable/disable those.
If you want to enable multiple categories, you have to call it multiple times.

The syntax was command line arguments (space separated), with r11119 you can now also use comma separated values.

comment:2 Changed 16 months ago by migration script

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1021

Note: See TracTickets for help on using tickets.