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:

Results (1 - 3 of 2088)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#2358 fixed audio server test crash Antoine Martin Antoine Martin
#2355 fixed record cpuinfo Antoine Martin Antoine Martin
#2353 fixed Character encoding problem when connecting to server Antoine Martin psycho_zs
1 2 3 4 5 6 7 8 9 10 11

Full rows

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


This is displayed as:

Results (1 - 3 of 2088)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#2358 fixed audio server test crash Antoine Martin Antoine Martin

Something X11 display related.

Traceback (most recent call first):
  File "/usr/lib64/python3.7/site-packages/xpra/sound/pulseaudio/pulseaudio_common_util.py", line 34, in get_x11_property
    root = X11Window.getDefaultRootWindow()
  File "/usr/lib64/python3.7/site-packages/xpra/sound/pulseaudio/pulseaudio_common_util.py", line 59, in get_pulse_id_x11_property
    return get_x11_property("PULSE_ID")
  File "/usr/lib64/python3.7/site-packages/xpra/sound/pulseaudio/pulseaudio_pactl_util.py", line 120, in get_pulse_id
    return get_pulse_id_x11_property()
  File "/usr/lib64/python3.7/site-packages/xpra/sound/pulseaudio/pulseaudio_pactl_util.py", line 195, in get_info
    "id"        : get_pulse_id(),
  File "/usr/lib64/python3.7/site-packages/xpra/server/mixins/audio_server.py", line 293, in init_sound_options
    pa_info = get_pa_info()
  File "/usr/lib64/python3.7/site-packages/xpra/server/mixins/audio_server.py", line 59, in setup
  File "/home/antoine/projects/Xpra/trunk/src/unittests/unit/server/mixins/servermixintest_util.py", line 86, in _test_mixin_class
  File "./unittests/unit/server/mixins/audio_test.py", line 31, in test_audio
    }, AudioMixin)
  File "/usr/lib64/python3.7/unittest/case.py", line 615, in run
  File "/usr/lib64/python3.7/unittest/case.py", line 663, in __call__
    return self.run(*args, **kwds)
  File "/usr/lib64/python3.7/unittest/suite.py", line 122, in run
  File "/usr/lib64/python3.7/unittest/suite.py", line 84, in __call__
    return self.run(*args, **kwds)
  File "/usr/lib64/python3.7/unittest/suite.py", line 122, in run
  File "/usr/lib64/python3.7/unittest/suite.py", line 84, in __call__
    return self.run(*args, **kwds)
  File "/usr/lib64/python3.7/unittest/runner.py", line 176, in run
  File "/usr/lib64/python3.7/unittest/main.py", line 271, in runTests
    self.result = testRunner.run(self.test)
  File "/usr/lib64/python3.7/unittest/main.py", line 101, in __init__
  File "./unittests/unit/server/mixins/audio_test.py", line 39, in main
  File "./unittests/unit/server/mixins/audio_test.py", line 43, in <module>
Program received signal SIGSEGV, Segmentation fault.
0x00007fffe9a63e06 in XDefaultRootWindow (dpy=0x555555893f90) at Macros.c:52
52	    return (RootWindow(dpy,DefaultScreen(dpy)));
#2355 fixed record cpuinfo Antoine Martin Antoine Martin

Makes it easier to know what we're dealing with when getting xpra info or server log samples.

Added in r23050 + r23073.

Problem is that this now causes random server segfaults during startup, possibly as a result of #2341.

(gdb) py-bt
Traceback (most recent call first):
  File "/usr/lib64/python3.7/site-packages/gi/overrides/GLib.py", line 602, in idle_add
    return GLib.idle_add(priority, function, *user_data)
  File "/usr/lib64/python3.7/site-packages/xpra/child_reaper.py", line 150, in sigchld
    self.glib.idle_add(self._sigchld, signum, str(frame))
  File "/usr/lib64/python3.7/selectors.py", line 275, in _key_from_fd
    def _key_from_fd(self, fd):
  File "/usr/lib64/python3.7/selectors.py", line 425, in select
    key = self._key_from_fd(fd)
  File "/usr/lib64/python3.7/multiprocessing/connection.py", line 920, in wait
    ready = selector.select(timeout)
  File "/usr/lib64/python3.7/multiprocessing/popen_fork.py", line 45, in wait
    if not wait([self.sentinel], timeout):
  File "/usr/lib64/python3.7/multiprocessing/process.py", line 140, in join
    res = self._popen.wait(timeout)
  File "/usr/lib/python3.7/site-packages/cpuinfo/cpuinfo.py", line 1297, in _get_cpu_info_from_cpuid
  File "/usr/lib/python3.7/site-packages/cpuinfo/cpuinfo.py", line 2152, in get_cpu_info
    CopyNewFields(info, _get_cpu_info_from_cpuid())
  File "/usr/lib64/python3.7/site-packages/xpra/server/mixins/networkstate_server.py", line 124, in init_cpuinfo
    self.cpu_info = get_cpu_info()
  File "/usr/lib64/python3.7/site-packages/gi/overrides/Gtk.py", line 1630, in main
    return _Gtk_main(*args, **kwargs)
  File "/usr/lib64/python3.7/site-packages/xpra/server/gtk_server_base.py", line 107, in do_run
  File "/usr/lib64/python3.7/site-packages/xpra/server/server_core.py", line 420, in run
  File "/usr/lib64/python3.7/site-packages/xpra/scripts/server.py", line 973, in do_run_server
    r = app.run()
  File "/usr/lib64/python3.7/site-packages/xpra/scripts/server.py", line 445, in run_server
    return do_run_server(error_cb, opts, mode, xpra_file, extra_args, desktop_display)
  File "/usr/lib64/python3.7/site-packages/xpra/scripts/main.py", line 440, in run_mode
    return run_server(error_cb, options, mode, script_file, args, current_display)
  File "/usr/lib64/python3.7/site-packages/xpra/scripts/main.py", line 105, in main
    return run_mode(script_file, err, options, args, mode, defaults)
  File "/usr/bin/xpra", line 26, in <module>
    sys.exit(main(sys.argv[0], sys.argv))
#2353 fixed Character encoding problem when connecting to server Antoine Martin psycho_zs

Using xpra 2.5.2+dfsg1-2 (currently in Debian unstable), also tested 2.5.2-r22875-1.

Connection to server is impossible, server reports:

Error: processing new connection from Protocol(unix-domain socket:/run/xpra/hostname-100):
 'latin-1' codec can't encode characters in position 0-6: ordinal not in range(256)
Disconnecting client Protocol(unix-domain socket:/run/xpra/hostname-100):

2.4.3 works fine

custom configuration, aside from key shortcuts and vars:

pulseaudio = no
dpi = 96
desktop-scaling = on
xsettings = no
start-new-commands = yes
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