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.


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:


This is displayed as:

Full rows

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


This is displayed as:

Results (1 - 3 of 2402)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#2707 fixed session_info.py, line 659, in <genexpr> RuntimeError: deque mutated during iteration Antoine Martin stdedos
"Xpra-Python3-x86_64_4.0-r25898\xpra_cmd" attach ssh://user@ip/2 --ssh="plink -ssh -agent" --modal-windows=no --title="@title@ on @hostname@/@server-display@" --opengl=no

2020-04-03 09:27:43,797 Xpra GTK3 client version 4.0-r25898 64-bit
2020-04-03 09:27:43,799  running on Microsoft Windows 10
2020-04-03 09:27:43,917 Warning: failed to import opencv:
2020-04-03 09:27:43,918  No module named 'cv2'
2020-04-03 09:27:43,918  webcam forwarding is disabled
2020-04-03 09:27:45,028 GStreamer version 1.16.2 for Python 3.8.2 64-bit
2020-04-03 09:27:45,399 keyboard layout code 0x409
2020-04-03 09:27:45,400 identified as 'United States - English' : us
2020-04-03 09:27:45,969  keyboard settings: layout=us
2020-04-03 09:27:45,972  desktop size is 4160x1440 with 1 screen:
2020-04-03 09:27:45,973   Default (1100x381 mm - DPI: 96x96) workarea: 4160x1400
2020-04-03 09:27:45,973     Generic PnP Monitor 1600x900 at 0x534 (309x174 mm - DPI: 131x131) workarea: 1600x860
2020-04-03 09:27:45,973     C32JG5x 2560x1440 at 1600x0 (697x392 mm - DPI: 93x93) workarea: 2560x1400
2020-04-03 09:28:01,139 enabled remote logging
2020-04-03 09:28:01,141 Xpra GTK3 X11 server version 3.0.8-r25767 64-bit
2020-04-03 09:28:01,141  running on Linux Ubuntu 16.04 xenial
2020-04-03 09:28:01,149 Attached to
2020-04-03 09:28:01,151  (press Control-C to detach)

(xpra_cmd:9440): Pango-WARNING **: 09:28:01.977: couldn't load font "Bitstream Vera Sans Not-Rotated 14.662109375", falling back to "Sans Not-Rotated 14.662109375", expect ugly output.
2020-04-03 09:28:03,013 UI thread is now blocked
2020-04-03 09:28:03,540 UI thread is running again, resuming
2020-04-03 09:28:32,427 server is not responding, drawing spinners over the windows
2020-04-03 09:28:38,724 server is OK again
2020-04-03 09:32:54,841 UI thread is now blocked
2020-04-03 09:32:55,133 UI thread is running again, resuming
2020-04-03 09:33:20,449 server is not responding, drawing spinners over the windows
2020-04-03 09:33:21,488 server is OK again
2020-04-03 09:33:32,495 server is not responding, drawing spinners over the windows
2020-04-03 09:33:34,023 server is OK again
2020-04-03 09:33:37,653 server is not responding, drawing spinners over the windows
2020-04-03 09:33:38,176 server is OK again
2020-04-03 11:29:56,152 unknown string message: 0xc26b / 0x0 / 0x0
2020-04-03 11:32:58,923 unknown string message: 0xc26b / 0x0 / 0x0
Traceback (most recent call last):
  File "E:\Xpra\trunk\src/xpra/client/gtk_base/session_info.py", line 659, in populate
  File "E:\Xpra\trunk\src/xpra/client/gtk_base/session_info.py", line 659, in <genexpr>
RuntimeError: deque mutated during iteration
2020-04-03 12:34:07,227 unknown string message: 0xc151 / 0x1 / 0x1
2020-04-03 12:34:07,310 unknown string message: 0xc151 / 0x2 / 0x0
2020-04-03 13:17:42,642 system is suspending
2020-04-03 15:07:20,836 Warning: long timer waiting time,
2020-04-03 15:07:21,523  UI thread polling waited 6575.4 seconds longer than intended (6575.9 vs 0.5)
2020-04-03 15:07:29,828 UI thread is now blocked
2020-04-03 15:07:33,714 UI thread is running again, resuming
2020-04-03 15:07:35,043 UI thread is now blocked
2020-04-03 15:07:36,298 UI thread is running again, resuming
2020-04-03 15:08:20,983 server ping timeout - waited 60 seconds without a response

was: "C:\Users\stavros.ntentos\Documents\xpra-clients\Xpra-Python3-x86_64_4.0-r25898\xpra_cmd" start ssh://user@ip/2 --ssh="plink -ssh -agent" --modal-windows=no --title="@title@ on @hostname@/@server-display@" --opengl=no

#2706 fixed disabling "Modal windows" in tray needs re-initialize Antoine Martin mviereck

Related to #2255 Seen with xpra v3.0.8-r25889 and xpra v4.0-r25629 on Debian bullseye.

I have an application (kaptain) that sets the modal-windows flag and causes issues with keyboard and mouse focus. Disabling modal windows fixes the issue.

I did not set --modal-windows=no, so I had to disable it in the xpra tray menu. But that does not fix the issue. I also have to re-initialize the windows using the tray menu. xpra should do that automatically.

Side note: Although I reported #2255 myself, I stumbled over the modal-windows issue again and it took me some time to figure out why the windows do not respond. For some days I used ssh -X instead of xpra because xpra was unusable. It might be reasonable to set --modal-windows=no as a default because the solution for this issue is not obvious to users.

#2702 fixed Keypad number are translate to letter windows managed by Xpra Antoine Martin carlos4313

When using the keypad with NumLock on the number from the keypad do not display the good information on the terminal managed by Xpra. I.e pressing 5 display E.

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