xpra icon
Bug tracker and wiki

Version 7 (modified by Antoine Martin, 6 years ago) (diff)

--

Reporting Bugs


Guidelines

If you are reporting a bug, it generally means that you want something investigated and changes to take place. If you have not read it yet, please take a moment to read Smart Questions - it is a very good read and will be helpful to you well beyond the scope of this project.


Here is some information which is often relevant and should therefore be included in most tickets to save time:

  • what operating system is used on both the client and server, including the full version details, the desktop environment, and anything that would make this setup unusual, number of screens, resolution, etc
  • the network setup, bandwidth constraints
  • the full command lines used both on the server and client
  • "xpra info" for this session
  • how the software was installed and what version (in full)
  • is this a new problem or a regression?
  • are there other bugs that are slightly similar?
  • are there other unusual issues / behaviour apart from this particular bug?
  • is it reproducible reliably? and if so, how?
  • does this happen with all picture encodings?
  • does switching off certain features make a difference (ie: clipboard)
  • include relevant parts of the log files - including enough context to investigate (not just the last line showing the error message, but not necessarily the whole log file either)
  • does re-connecting help?
  • does it happen with other type of clients (different OS, etc)
  • The debugging instructions can be used to add a lot more detailed information

The best way to ensure that the information is clear and detailed is often to just paste the command lines used to get the information directly. ie: rather than saying "I have the latest version installed" (which by definition, changes all the time), paste something like this:

$ rpm -qa | grep xpra
xpra-0.7.6-4.fc18.x86_64

Obviously, the type of information needed varies depending on the type of bug - see keyboard bugs for example.


OK, now feel free to file a bug.

Login required due to spam - sorry!

Due to the high level of trac spam, you must register to create new tickets. Sorry.
It will ask you to provide an email address to verify your account. In case you lose the link, the verification page is here
Note: if you do not get the email within 5 minutes, check you spam folder.. If it still fails contact us: xpra@devloop.org.uk
Your email address will not be used for anything else, and will not be passed on to anyone, for any reason.

Attachments (1)

Download all attachments as: .zip