= We have moved =
This page has been moved to
[https://github.com/Xpra-org/xpra/wiki/Reporting-Bugs]

[[BR]]
[[BR]]
[[BR]]
[[BR]]
[[BR]]
[[BR]]
[[BR]]
[[BR]]
[[BR]]
[[BR]]
[[BR]]
[[BR]]
[[BR]]
[[BR]]
[[BR]]
[[BR]]
[[BR]]
[[BR]]
[[BR]]
[[BR]]
[[BR]]
[[BR]]
[[BR]]
[[BR]]
[[BR]]

''Archived copy:''

[[Image(https://xpra.org/icons/bugs.png)]]
= Reporting Bugs =

[[BR]]
See also: [/wiki/SessionInfo Session Info]

[[BR]]
[[BR]]

{{{#!div class="box"
== 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 [http://www.catb.org/esr/faqs/smart-questions.html#beprecise 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
* changes made to the default configuration, if any. This can be shown with the command: "xpra showconfig"
* the desktop environment, window manager used - if applicable
* anything that would make the setup unusual: number of screens, resolution, virtualization software, access via another remote desktop tool (VNC, RDP, ..), etc
* the network setup, bandwidth constraints (ie: LAN or DSL)
* the full command lines used both on the server and client
* the server log file (or output if no log file is used)
* the environment (ie: {{{%PATH%}}} on MS Windows, {{{$PATH}}} and {{{$LD_LIBRARY_PATH}}} on Linux, etc)
* "{{{xpra info}}}" for the session
* how the software was installed and what version (in full)
* is this a new problem or a regression? (if a regression, when did it start?)
* are there other bugs that are 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: sound, opengl, 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)
* try to include the output of some of the diagnosis tools we bundle (ie: {{{Network_Info.exe}}} and {{{Encoding_Info.exe}}} on MS Windows, {{{net_util.py}}} and {{{loader.py}}} everywhere else)
* if possible, follow the [/wiki/Debugging debugging instructions]
* [http://who-t.blogspot.com/2016/12/please-dont-use-pastebins-in-bugs.html please don't use pastebins]

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, varies depending the platform, architecture, distributiun channel), 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 [/wiki/Keyboard#ReportingBugs keyboard bugs] for example.

[[BR]]

OK, now feel free to [/register] (or [/login]) then [/newticket file a bug].
}}}


{{{#!div class="box"
== Bug Report Tool ==

The bug report tool is shipped with all installations and it allows you to collect a lot of useful information in one place.

[[Image(bug-report-tool-screenshot.png)]]

You can access it from the tray menu, using the ''Alt+Shift+F3'' key shortcut, or launch it separately.
On MS Windows, run {{{Bug_Report.exe}}}, on other platforms with version 2.5 or later just run {{{xpra bug-report}}}.
}}}


{{{#!div class="box"
== Registration required due to spam - sorry! ==
Due to the high level of [/wiki/TicketSpam trac ticket spam], you must [/register register] to create new tickets. Sorry.
[[BR]]
It will ask you to provide an email address to verify your account. In case you lose the link, the verification page is [/verify_email here]
[[BR]]
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}}}
[[BR]]
Your email address will not be used for anything else, and will not be passed on to anyone, for any reason.
}}}