xpra icon
Bug tracker and wiki

Trac Ticket Queries

In addition to reports, Trac provides support for custom ticket queries, which can be used to display tickets that meet specified criteria.

To configure and execute a custom query, switch to the View Tickets module from the navigation bar, and select the Custom Query link.

Filters

When you first go to the query page, the default filter will display tickets relevant to you:

  • If logged in then all open tickets, it will display open tickets assigned to you.
  • If not logged in but you have specified a name or email address in the preferences, then it will display all open tickets where your email (or name if email not defined) is in the CC list.
  • If not logged in and no name/email is defined in the preferences, then all open issues are displayed.

Current filters can be removed by clicking the button to the left with the minus sign on the label. New filters are added from the pulldown lists at the bottom corners of the filters box; 'And' conditions on the left, 'Or' conditions on the right. Filters with either a text box or a pulldown menu of options can be added multiple times to perform an Or on the criteria.

You can use the fields just below the filters box to group the results based on a field, or display the full description for each ticket.

After you have edited your filters, click the Update button to refresh your results.

Some shortcuts can be used to manipulate checkbox filters.

  • Clicking on a filter row label toggles all checkboxes.
  • Pressing the modifier key while clicking on a filter row label inverts the state of all checkboxes.
  • Pressing the modifier key while clicking on a checkbox selects the checkbox and deselects all other checkboxes in the filter.

The modifier key is platform and browser dependent. On Mac the modified key is Option/Alt or Command. On Linux the modifier key is Ctrl + Alt. Opera on Windows seems to use Ctrl + Alt, while Alt is effective for other Windows browsers.

Clicking on one of the query results will take you to that ticket. You can navigate through the results by clicking the Next Ticket or Previous Ticket links just below the main menu bar, or click the Back to Query link to return to the query page.

You can safely edit any of the tickets and continue to navigate through the results using the Next/Previous/Back to Query links after saving your results. When you return to the query any tickets which were edited will be displayed with italicized text. If one of the tickets was edited such that it no longer matches the query criteria , the text will also be greyed. Lastly, if a new ticket matching the query criteria has been created, it will be shown in bold.

The query results can be refreshed and cleared of these status indicators by clicking the Update button again.

Saving Queries

Trac allows you to save the query as a named query accessible from the reports module. To save a query ensure that you have Updated the view and then click the Save query button displayed beneath the results. You can also save references to queries in Wiki content, as described below.

Note: one way to easily build queries like the ones below, you can build and test the queries in the Custom report module and when ready - click Save query. This will build the query string for you. All you need to do is remove the extra line breaks.

Note: you must have the REPORT_CREATE permission in order to save queries to the list of default reports. The Save query button will only appear if you are logged in as a user that has been granted this permission. If your account does not have permission to create reports, you can still use the methods below to save a query.

You may want to save some queries so that you can come back to them later. You can do this by making a link to the query from any Wiki page.

[query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0]

Which is displayed as:

Active tickets against 1.0

This uses a very simple query language to specify the criteria, see Query Language.

Alternatively, you can copy the query string of a query and paste that into the Wiki link, including the leading ? character:

[query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner]

Which is displayed as:

Assigned tickets by owner

Customizing the table format

You can also customize the columns displayed in the table format (format=table) by using col=<field>. You can specify multiple fields and what order they are displayed in by placing pipes (|) between the columns:

[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter)]]

This is displayed as:

Full rows

In table format you can also have full rows by using rows=<field>:

[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter,rows=description)]]

This is displayed as:

Results (1 - 3 of 2219)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#2487 duplicate HTML5 session disconnects spontaneously then tries to reconnect and hits client decoding error, triggering reconnection failure. Antoine Martin alas
Description

Launched a 4.0-r24425 Fedora 30 server with the command-

xpra start :13 --no-daemon --bind-tcp=0.0.0.0:1234 --bind-ws=0.0.0.0:1237 --bind-wss=0.0.0.0:1239 --ssl-cert=/etc/xpra/148-ssl.pem  --start-child=xterm --start-child=xterm --exit-with-children -d clipboard

Connected with a Firefox html5 client with client-side debugging enabled. Launched gedit from one of the xterms, and then went slowly through the now familiar clipboard tests (type & copy 'one' in gedit application, shift focus to a local text editor, Word in this case, and pasted with control-v, then typed and copied 'two', then shifted focus back to gedit server-side by clicking at the end of the still highlighted 'one' text, used arrow key to get to next line and tried to paste with right-click menu, then used keyboard to add a space, then pasted with control-v, successfully pasting 'two'... then shifted focus to a new putty window to check the exact xpra version).

Before I could do anything to sort through putty window server logs - the session disconnected with the following errors in the server logs.

2019-11-18 14:01:55,892 Handshake complete; enabling connection
2019-11-18 14:01:55,894 Disconnecting client 10.0.4.54:54818:
2019-11-18 14:01:55,894  new client (the new client does not wish to share)
2019-11-18 14:01:55,894 client None is the clipboard peer, helper=X11Clipboard
2019-11-18 14:01:55,894 enabling selections:
2019-11-18 14:01:55,894 X11ClipboardProxy(CLIPBOARD).set_enabled(False)
2019-11-18 14:01:55,895 X11ClipboardProxy(PRIMARY).set_enabled(False)
2019-11-18 14:01:55,895 X11ClipboardProxy(SECONDARY).set_enabled(False)
2019-11-18 14:01:55,896 xpra client 1 disconnected.
2019-11-18 14:01:55,907 client clipboard: enabled=True, notifications=False
2019-11-18 14:01:55,907 client clipboard: greedy=True, want_targets=True, client_selections=['CLIPBOARD', 'PRIMARY'], contents_slice_fix=True
2019-11-18 14:01:55,908 HTML5 Microsoft Windows Firefox client version 3.0
2019-11-18 14:01:55,914 client ClientConnection(2 : WebSocket(wss socket: 10.0.3.148:1239 <- 10.0.4.54:54989)) is the clipboard peer, helper=X11Clipboard
2019-11-18 14:01:55,914  greedy=True
2019-11-18 14:01:55,914  want targets=True
2019-11-18 14:01:55,914  server has selections: CLIPBOARD, PRIMARY, SECONDARY
2019-11-18 14:01:55,914  client initial selections: CLIPBOARD, PRIMARY
2019-11-18 14:01:55,914 X11ClipboardProxy(CLIPBOARD).set_greedy_client(True)
2019-11-18 14:01:55,914 X11ClipboardProxy(PRIMARY).set_greedy_client(True)
2019-11-18 14:01:55,914 X11ClipboardProxy(SECONDARY).set_greedy_client(True)
2019-11-18 14:01:55,914 set_want_targets_client(True)
2019-11-18 14:01:55,914 enabling selections: CLIPBOARD, PRIMARY
2019-11-18 14:01:55,915 X11ClipboardProxy(CLIPBOARD).set_enabled(True)
2019-11-18 14:01:55,915 X11ClipboardProxy(PRIMARY).set_enabled(True)
2019-11-18 14:01:55,915 X11ClipboardProxy(SECONDARY).set_enabled(False)
2019-11-18 14:01:55,915 keyboard mapping already configured (skipped)
2019-11-18 14:01:55,916  client root window size is 1024x576 with 1 display:
2019-11-18 14:01:55,916   HTML (271x152 mm - DPI: 95x96)
2019-11-18 14:01:55,916     Canvas
2019-11-18 14:01:55,966 server virtual display now set to 1024x576
2019-11-18 14:01:55,973 clipboard_helper=X11Clipboard, clipboard_client=ClientConnection(2 : WebSocket(wss socket: 10.0.3.148:1239 <- 10.0.4.54:54989)), source=ClientConnection(2 : WebSocket(wss socket: 10.0.3.148:1239 <- 10.0.4.54:54989)), clipboard=True
2019-11-18 14:01:55,973 get_loop_uuids()={'CLIPBOARD': 'Xpra-Clipboard-Loop-Detection:740370c6c9244ce599ee66f77bcd9ba1', 'PRIMARY': 'Xpra-Clipboard-Loop-Detection:d67265c836834f92b9b51a5c9982d1a6', 'SECONDARY': 'Xpra-Clipboard-Loop-Detection:2d7acd2a663a4564b98a3330c2989db2'}
2019-11-18 14:01:55,973  automatic picture encoding enabled, also available:
2019-11-18 14:01:55,974   jpeg, png, rgb32, h264, mpeg1
2019-11-18 14:01:56,004 DPI set to 96 x 96
2019-11-18 14:01:56,018 Warning: failed to add virtual printer 'HTML5 client'
2019-11-18 14:01:56,018  failed to connect to server
2019-11-18 14:01:56,075 client   2 received xdg start menu data
2019-11-18 14:01:56,119 Error: wss request failure
2019-11-18 14:01:56,119  errno=0
2019-11-18 14:01:56,119  for client 10.0.4.54:55022:
2019-11-18 14:01:56,119  request as hex: '160301021501000211030385ab1a8761223364d84d6bf1'
2019-11-18 14:01:56,119  [Errno 0] Error
2019-11-18 14:01:56,149 set_session_driver(ClientConnection(2 : WebSocket(wss socket: 10.0.3.148:1239 <- 10.0.4.54:54989))) clipboard_enabled=True, clipboard helper=X11Clipboard
2019-11-18 14:01:56,149 selections: ['CLIPBOARD', 'PRIMARY']
2019-11-18 14:01:56,150 client   2 startup complete
2019-11-18 14:01:56,153 client   2 connection-established
2019-11-18 14:01:56,154 client   2 update encodings: [object Object]
2019-11-18 14:01:56,634 client   2 XpraWindow.prototype.do_paint@https://xpra-bob.mycyberinc.com:1239/js/Window.js:1:30651
2019-11-18 14:01:56,634 client   2 XpraWindow.prototype.may_paint_now@https://xpra-bob.mycyberinc.com:1239/js/Window.js:1:25552
2019-11-18 14:01:56,634 client   2 XpraWindow.prototype.paint@https://xpra-bob.mycyberinc.com:1239/js/Window.js:1:25179
2019-11-18 14:01:56,634 client   2 XpraClient.prototype._process_draw_queue@https://xpra-bob.mycyberinc.com:1239/js/Client.js:2:26605
2019-11-18 14:01:56,634 client   2 XpraClient.prototype._process_draw@https://xpra-bob.mycyberinc.com:1239/js/Client.js:2:24984
2019-11-18 14:01:56,635 client   2 XpraClient.prototype._route_packet@https://xpra-bob.mycyberinc.com:1239/js/Client.js:1:10733
2019-11-18 14:01:56,635 client   2 XpraProtocolWorkerHost.prototype.open/<@https://xpra-bob.mycyberinc.com:1239/js/Protocol.js:1:707
2019-11-18 14:01:56,659 client   2 error painting scroll TypeError: Argument 1 of CanvasRenderingContext2D.drawImage could not be converted to any of: HTMLImageElement, SVGImageElement, HTMLCanvasElement, HTMLVideoElement, ImageBitmap.
2019-11-18 14:01:56,660 Warning: client decoding error:
2019-11-18 14:01:56,660  TypeError: Argument 1 of CanvasRenderingContext2D.drawImage could not be converted to any of: HTMLImageElement, SVGImageElement, HTMLCanvasElement, HTMLVideoElement, ImageBitmap.
2019-11-18 14:01:57,824 client   2 XpraWindow.prototype.do_paint@https://xpra-bob.mycyberinc.com:1239/js/Window.js:1:30651
2019-11-18 14:01:57,824 client   2 XpraWindow.prototype.may_paint_now@https://xpra-bob.mycyberinc.com:1239/js/Window.js:1:25552
2019-11-18 14:01:57,825 client   2 XpraWindow.prototype.paint@https://xpra-bob.mycyberinc.com:1239/js/Window.js:1:25179
2019-11-18 14:01:57,825 client   2 XpraClient.prototype._process_draw_queue@https://xpra-bob.mycyberinc.com:1239/js/Client.js:2:26605
2019-11-18 14:01:57,825 client   2 XpraClient.prototype._process_draw@https://xpra-bob.mycyberinc.com:1239/js/Client.js:2:24984
2019-11-18 14:01:57,825 client   2 XpraClient.prototype._route_packet@https://xpra-bob.mycyberinc.com:1239/js/Client.js:1:10733
2019-11-18 14:01:57,826 client   2 XpraProtocolWorkerHost.prototype.open/<@https://xpra-bob.mycyberinc.com:1239/js/Protocol.js:1:707
2019-11-18 14:01:57,842 client   2 error painting scroll TypeError: Argument 1 of CanvasRenderingContext2D.drawImage could not be converted to any of: HTMLImageElement, SVGImageElement, HTMLCanvasElement, HTMLVideoElement, ImageBitmap.
2019-11-18 14:01:57,843 Warning: client decoding error:
2019-11-18 14:01:57,843  TypeError: Argument 1 of CanvasRenderingContext2D.drawImage could not be converted to any of: HTMLImageElement, SVGImageElement, HTMLCanvasElement, HTMLVideoElement, ImageBitmap.
2019-11-18 14:01:59,034 client   2 XpraWindow.prototype.do_paint@https://xpra-bob.mycyberinc.com:1239/js/Window.js:1:30651
2019-11-18 14:01:59,035 client   2 XpraWindow.prototype.may_paint_now@https://xpra-bob.mycyberinc.com:1239/js/Window.js:1:25552
2019-11-18 14:01:59,035 client   2 XpraWindow.prototype.paint@https://xpra-bob.mycyberinc.com:1239/js/Window.js:1:25179
2019-11-18 14:01:59,035 client   2 XpraClient.prototype._process_draw_queue@https://xpra-bob.mycyberinc.com:1239/js/Client.js:2:26605
2019-11-18 14:01:59,036 client   2 XpraClient.prototype._process_draw@https://xpra-bob.mycyberinc.com:1239/js/Client.js:2:24984
2019-11-18 14:01:59,036 client   2 XpraClient.prototype._route_packet@https://xpra-bob.mycyberinc.com:1239/js/Client.js:1:10733
2019-11-18 14:01:59,036 client   2 XpraProtocolWorkerHost.prototype.open/<@https://xpra-bob.mycyberinc.com:1239/js/Protocol.js:1:707
2019-11-18 14:01:59,037 client   2 error painting scroll TypeError: Argument 1 of CanvasRenderingContext2D.drawImage could not be converted to any of: HTMLImageElement, SVGImageElement, HTMLCanvasElement, HTMLVideoElement, ImageBitmap.
2019-11-18 14:01:59,037 Warning: client decoding error:
2019-11-18 14:01:59,037  TypeError: Argument 1 of CanvasRenderingContext2D.drawImage could not be converted to any of: HTMLImageElement, SVGImageElement, HTMLCanvasElement, HTMLVideoElement, ImageBitmap.
2019-11-18 14:02:00,218 client   2 XpraWindow.prototype.do_paint@https://xpra-bob.mycyberinc.com:1239/js/Window.js:1:30651
2019-11-18 14:02:00,218 client   2 XpraWindow.prototype.may_paint_now@https://xpra-bob.mycyberinc.com:1239/js/Window.js:1:25552
2019-11-18 14:02:00,219 client   2 XpraWindow.prototype.paint@https://xpra-bob.mycyberinc.com:1239/js/Window.js:1:25179
2019-11-18 14:02:00,219 client   2 XpraClient.prototype._process_draw_queue@https://xpra-bob.mycyberinc.com:1239/js/Client.js:2:26605
2019-11-18 14:02:00,219 client   2 XpraClient.prototype._process_draw@https://xpra-bob.mycyberinc.com:1239/js/Client.js:2:24984
2019-11-18 14:02:00,219 client   2 XpraClient.prototype._route_packet@https://xpra-bob.mycyberinc.com:1239/js/Client.js:1:10733
2019-11-18 14:02:00,220 client   2 XpraProtocolWorkerHost.prototype.open/<@https://xpra-bob.mycyberinc.com:1239/js/Protocol.js:1:707
2019-11-18 14:02:00,235 client   2 error painting scroll TypeError: Argument 1 of CanvasRenderingContext2D.drawImage could not be converted to any of: HTMLImageElement, SVGImageElement, HTMLCanvasElement, HTMLVideoElement, ImageBitmap.
2019-11-18 14:02:00,236 Warning: client decoding error:
2019-11-18 14:02:00,236  TypeError: Argument 1 of CanvasRenderingContext2D.drawImage could not be converted to any of: HTMLImageElement, SVGImageElement, HTMLCanvasElement, HTMLVideoElement, ImageBitmap.
2019-11-18 14:02:01,043 client None is the clipboard peer, helper=X11Clipboard
2019-11-18 14:02:01,044 enabling selections:
2019-11-18 14:02:01,044 X11ClipboardProxy(CLIPBOARD).set_enabled(False)
2019-11-18 14:02:01,044 X11ClipboardProxy(PRIMARY).set_enabled(False)
2019-11-18 14:02:01,044 X11ClipboardProxy(SECONDARY).set_enabled(False)
2019-11-18 14:02:01,045 xpra client 2 disconnected.

Not sure why it dosconnected like that, perhaps wss error because I had to click through a cert error (no SAN in cert causing a problem, as a guess?)... which is leading to wss errors (which I'll add below as well)?

The apparent attempt to configure the HTML5 client as a printer seems likely to be part of the problem - 2019-11-18 14:01:56,018 Warning: failed to add virtual printer 'HTML5 client'?

The wss error which I was trying to ignore- which I saw on initial connection, and also saw just prior to the new round of clipboard tests.

2019-11-18 13:58:34,620 Error: wss request failure
2019-11-18 13:58:34,620  errno=0
2019-11-18 13:58:34,620  for client 10.0.4.54:54833:
2019-11-18 13:58:34,620  request as hex: '1603010215010002110303c7e46ddb61ac4b1cec65d97fba7ef2db662a4e20a36999fbd19e77db5948cf40200bea8b495e59be203f35a8aed7455fc5286b45598861d306f331bf1dd06303130024130113031302c02bc02fcca9cca8c02cc030c0'
2019-11-18 13:58:34,620 setting response 'None' to property GDK_SELECTION of window 'gedit' as None
2019-11-18 13:58:34,620 set_selection_response(<GdkX11.X11Window object at 0x7f23a12ddb40 (GdkX11Window at 0x557ede8a72a0)>, TARGETS, GDK_SELECTION, None, None, "'None'", 2634287383)
2019-11-18 13:58:34,620  [Errno 0] Error

... it looks like this error was triggered on the connection that seemed to work, as well as the spontaneous reconnection attempt. Seems unlikely to be the trigger, but perhaps contributing?

(I'll attach the parsed clipboard test logs that preceded this in #2452, in case those might also be contributing factors... though the timing seems wrong.)

#2486 fixed macos client: connection form and password dialogue usually open behind other windows sto6 sto6
Description

Using macos client, xpra v3.0.2-r24371 python2.7 64bit on macos 10.13.6 (High Sierra) and server version on centos-6, xpra v1.0.14-r24088 (xpra.x86_64 1.0.14-1.r24088.el6_6).

I launch client connection-form from a dot-xpra file in the Dock (without autoconnect). The form typically displays behind other windows. I usually just click the dock-icon again to raise it.

When I make connection (ssh), if it needs to prompt for a password, that dialogue is even behind the connection-form itself (both centered, so connection form always nicely hides the password dialogue).

Can take me a short while staring stupidly at the screen to recall this issue (vs believing its connecting but just being slow to show any change on screen).

This is a minor annoyance.

#2485 fixed cmd-line xpra doesn't nicely handle stdout pipe-closed. Antoine Martin sto6
Description

Using macos client, xpra v3.0.2-r24371 python2.7 64bit on macos 10.13.6 (High Sierra) and server version on centos-6, xpra v1.0.14-r24088 (xpra.x86_64 1.0.14-1.r24088.el6_6).

On server or client, at command line, commands likes 'xpra info ...', 'xpra showconfig' throw repeating IOErrors if stdout closed early (suspect as many errors as there are remaining lines of output).

Server example (usually I pipe into less, but quit the less early, this simulates that):

$ (xpra info :3 | head) |& head -50
batch.delay.50p=35
batch.delay.80p=46
batch.delay.90p=53
batch.delay.avg=29
batch.delay.cur=2
batch.delay.max=62
batch.delay.min=2
batch.locked=False
batch.max-delay=500
batch.min-delay=5
Traceback (most recent call last):
  File "/usr/lib64/python2.6/logging/__init__.py", line 808, in emit
    self.flush()
  File "/usr/lib64/python2.6/logging/__init__.py", line 770, in flush
    self.stream.flush()
IOError: [Errno 32] Broken pipe
... [repeated IOError's deleted]

Client example:

% ( xpra showconfig | head -2 ) | & head -30
add-printer-options            = '-E', '-o printer-is-shared=false', '-u allow:$USER'
attach                         =
Traceback (most recent call last):
  File "logging/__init__.pyc", line 892, in emit
  File "logging/__init__.pyc", line 852, in flush
IOError: [Errno 32] Broken pipe
... [repeated IOError's deleted]

This is a minor annoyance.

1 2 3 4 5 6 7 8 9 10 11

Query Language

query: TracLinks and the [[TicketQuery]] macro both use a mini “query language” for specifying query filters. Filters are separated by ampersands (&). Each filter consists of the ticket field name, an operator and one or more values. More than one value are separated by a pipe (|), meaning that the filter matches any of the values. To include a literal & or | in a value, escape the character with a backslash (\).

The available operators are:

= the field content exactly matches one of the values
~= the field content contains one or more of the values
^= the field content starts with one of the values
$= the field content ends with one of the values

All of these operators can also be negated:

!= the field content matches none of the values
!~= the field content does not contain any of the values
!^= the field content does not start with any of the values
!$= the field content does not end with any of the values

The date fields created and modified can be constrained by using the = operator and specifying a value containing two dates separated by two dots (..). Either end of the date range can be left empty, meaning that the corresponding end of the range is open. The date parser understands a few natural date specifications like "3 weeks ago", "last month" and "now", as well as Bugzilla-style date specifications like "1d", "2w", "3m" or "4y" for 1 day, 2 weeks, 3 months and 4 years, respectively. Spaces in date specifications can be omitted to avoid having to quote the query string.

created=2007-01-01..2008-01-01 query tickets created in 2007
created=lastmonth..thismonth query tickets created during the previous month
modified=1weekago.. query tickets that have been modified in the last week
modified=..30daysago query tickets that have been inactive for the last 30 days

See also: TracTickets, TracReports, TracGuide, TicketQuery

Last modified 3 years ago Last modified on 11/23/16 15:37:19