xpra icon
Bug tracker and wiki

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

Version 3 (modified by trac, 5 years ago) (diff)


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 2683)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#3006 fixed python2-lz4 in centos 7.9 Caleb Khor Caleb Khor
#3004 invalid xpra cannot be built TCH68k TCH68k
#2999 fixed after xpra-server upgrade it fails to start tomuxi tomuxi
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 2683)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#3006 fixed python2-lz4 in centos 7.9 Caleb Khor Caleb Khor

I've noticed the following for the packaging for Centos 7.x versions of xpra:

  • Centos 7.6: lz4 and python2-lz4 are from xpra. Latest xpra version is 3.0.13.
  • Centos 7.7: lz4 and python2-lz4 are from xpra. Latest xpra version is 3.0.9
  • Centos 7.8: python2-lz4 is from xpra. lz4 is absent. latest xpra version is 3.0.13
  • Centos 7.9: python2-lz4 and lz4 are both absent. latest xpra version is 3.0.13

It seems that the version of python2-lz4 (2.2.1) is critical for xpra to work, not so for lz4, as it can be swapped with the system version.

While 3.0.13 largely worked on Centos 7.9, there is a bug when xpra shadow is invoked (both via the command line and gui), the xpra session just crashes after a while during launch. It just terminates itself without any reason, and UNKNOWN sessions were created (which of course cleaned up later). It seems that restoring python2-lz4 (2.2.1) (obtained from the other distros) makes it work again.

It is in my view that for the Centos 7.9 distribution, perhaps python2-lz4 should be included?

#3004 invalid xpra cannot be built TCH68k TCH68k


I am trying to build xpra, but it keeps failing at the final linking with this message:

/usr/bin/ld: /usr/local/lib/libx264.a(cabac-a.o): relocation R_X86_64_PC32 against symbol `x264_cabac_range_lps' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: Bad value
collect2: error: ld returned 1 exit status
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1

The command line was ./setup.py --without-strict build. I tried options --without-dec_avcodec2, --without-csc_swscale, --without-enc_ffmpeg and even --with-PIC, though i saw in the source that it is the default. Tried them separately, together, whatever. It keeps failing.

I did not set any milestone or version, because i've tried it with 2.0.3, 2.5.3 and 3.0.13 and all of them did this. I need at least xpra 2.0, so i did not tried below and 4.0 refused to compile by telling Python 3.6 is the minimum (it is installed), so i did not try above either. Most probably all versions are affected, or at least all of them from 2.0.0 to 3.0.13.

The build switches and "diagnostics" dumped on the terminal at the start of the build:

Xpra version 2.0.3
found pkg-config version: 0.29
build switches:
* enc_x264             : Y
* enc_x265             : Y
* enc_ffmpeg           : Y
* nvenc7               : N
* cuda_rebuild         : Y
* vpx                  : Y
* pillow               : Y
* jpeg                 : N
* v4l2                 : Y
* dec_avcodec2         : Y
* csc_swscale          : Y
* csc_libyuv           : N
* bencode              : Y
* cython_bencode       : Y
* vsock                : Y
* mdns                 : Y
* clipboard            : Y
* server               : Y
* client               : Y
* dbus                 : Y
* x11                  : Y
* gtk_x11              : Y
* service              : Y
* gtk2                 : Y
* gtk3                 : N
* html5                : Y
* minify               : Y
* pam                  : Y
* sound                : Y
* opengl               : Y
* printing             : Y
* webcam               : Y
* rebuild              : Y
* annotate             : Y
* warn                 : Y
* strict               : N
* shadow               : Y
* proxy                : Y
* debug                : N
* PIC                  : Y
* Xdummy               : Auto
* Xdummy_wrapper       : Auto
* verbose              : N
* tests                : N
* bundle_tests         : N
error running (['uglifyjs', '--version'],),{'stderr': -1, 'stdout': -1}: [Errno 2] No such file or directory
Warning: uglifyjs failed and return -1
Warning: yuicompressor module not found, cannot minify
'nvcc --version' failed with return code 127
stderr: None
updated ./xpra/build_info.py with:
* BUILD_BIT            = 64bit
* BUILD_CPU            = AMD FX(tm)-8350 Eight-Core Processor
* BUILD_DATE           = 2021-01-17
* BUILD_MACHINE        = x86_64
* BUILD_OS             = Linux Devuan 2.1 ascii
* BUILD_TIME           = 20:43
* BUILT_BY             = root
* BUILT_ON             = Csabi
* COMPILER_VERSION     = gcc (Debian 7.3.0-1~mx17+1) 7.3.0
* CYTHON_VERSION       = 0.25.2
* LINKER_VERSION       = GNU ld (GNU Binutils for Debian) 2.28
* PYTHON_VERSION       = 2.7.13
* RELEASE_BUILD        = True
* lib_pygobject        = 2.28.6
* lib_pygtk            = 2.24.0
* lib_vpx              = 1.6.1
* lib_x11              = 1.6.4
* lib_x264             = 0.142.x
* lib_x265             = 0.0
* lib_xcomposite       = 0.4.4
* lib_xdamage          = 1.1.4
* lib_xext             = 1.3.3
* lib_xfixes           = 5.0.3
* lib_xkbfile          = 1.0.9
* lib_xrandr           = 1.5.1
* lib_xtst             = 1.2.3
found gcc version: 7.3.0
#2999 fixed after xpra-server upgrade it fails to start tomuxi tomuxi

With default configuration, after upgrading server from 3.0.12-10.20201007r27627xpra1.el7_8.x86_64 to 3.0.13-10.r28292xpra1.el7_9.x86_64 it fails to start with error OSError: [Errno 13] Permission denied

with previously working command line

xpra start :22 --no-html --no-file-transfer --no-microphone --no-speaker --start=terminator
2021-01-11 09:58:07,134 cannot access python uinput module:
2021-01-11 09:58:07,134  No module named uinput
xpra main error:
Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/xpra/scripts/main.py", line 117, in main
    return run_mode(script_file, err, options, args, mode, defaults)
  File "/usr/lib64/python2.7/site-packages/xpra/scripts/main.py", line 451, in run_mode
    return run_server(error_cb, options, mode, script_file, args, current_display)
  File "/usr/lib64/python2.7/site-packages/xpra/scripts/server.py", line 340, in run_server
    return do_run_server(error_cb, opts, mode, xpra_file, extra_args, desktop_display)
  File "/usr/lib64/python2.7/site-packages/xpra/scripts/server.py", line 643, in do_run_server
    uid, gid, username, xauth_data, uinput_uuid)
  File "/usr/lib64/python2.7/site-packages/xpra/x11/vfb_util.py", line 293, in start_Xvfb
    stdin=PIPE, preexec_fn=preexec)
  File "/usr/lib64/python2.7/subprocess.py", line 711, in __init__
    errread, errwrite)
  File "/usr/lib64/python2.7/subprocess.py", line 1327, in _execute_child
    raise child_exception
OSError: [Errno 13] Permission denied
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