First of all: please do not e-mail bug reports directly to the developers. A much
better place to report bugs is the Bug Tracker
on the SourceForge.net site (see the details below). In addition, you might want to send a
message to the TightVNC mailing list.
Using the Bug Tracker
The tracker helps to keep all the bug reports in one place. Go through the following
steps when reporting a new bug:
- Ask yourself is it really a bug. Maybe it's rather a misconfiguration or a
hardware failure etc. Double-check that.
- If you have not registered on the SourceForge.net Web site, please do that before posting a
bug report (see more information below).
- Go to the bug
- Make sure you are logged in.
- Search existing bug reports for similar problems. If it's already there, just
post another comment, instead of adding a similar report.
- If you have not found an existing report on your problem, consider adding a new bug
- Choose an informative subject line.
- Describe the problem, trying to provide enough information to let a tester reproduce the bug.
Why Registration Is Necessary?
Technically, it could be possible to allow posting bug reports anonymously. The registration
simply enables sending you notifications on any changes in the bug status. Also, as a
registered user, you will automatically receive all the comments attached to your bug
report. Note that such comments can include clarification inquires from project developers,
or information on possible workarounds.
Remote Ripple, our new VNC Viewer for Android, perfect mobile companion to TightVNC!
by TightVNC Group:
An easy way to broadcast your Windows desktop to the local network.
Share this page:
We have open vacancies!
Join the TightVNC project and GlavSoft company in Tomsk, Russia! [rus]