I think I found a bug, how can I submit a report?
prefuse | documentation > frequently asked questionsUse the Bug Tracker on SourceForge. Please be as specific as possible in posting your bug report, including what is necessary to reproduce the bug. Also feel free to post to the Help Forum.
Related QuestionsHow do I submit a bug report?
AspectJ Frequently Asked QuestionsYou can submit a bug from http://bugs.eclipse.org/bugs/enter_bug.cgi?product=AspectJ . If it seems to be a bug in the compiler, please attach a small test case (source code) to reproduce the problem. For more information on writing compiler test cases, see Q:How do I write bugs for the AspectJ compiler?.
Related QuestionsPostgreSQL: Frequently Asked Questions (FAQ) for PostgreSQLVisit the PostgreSQL bug form at http://www.postgresql.org/support/submitbug. Also check out our ftp site ftp://ftp.PostgreSQL.org/pub/ to see if there is a more recent PostgreSQL version. Bugs submitted using the bug form or posted to any PostgreSQL mailing list typically generates one of the following replies:Related Questions
How should I report a bug?
Frequently Asked Questions about PhysioNetIf you have not read How to Report Bugs Effectively, please take a few minutes to do so. (Important: do not send bug reports about PhysioNet to the author of How to Report Bugs Effectively; he is an innocent bystander.) Bug reports should provide enough specific information to permit duplicating your problem.
Related QuestionsPostgreSQL FAQAlso check out our ftp site ftp://ftp.PostgreSQL.org/pub to see if there is a more recent PostgreSQL version or patches.Related Questions
TivoWebPlus FAQBefore you report a bug, always follow these steps and make sure you can duplicate it. This simple step will resolve some difficulties. If you happen to discover a bug or have a problem with TivoWebPlus, there are certain things that we need to know in order to properly diagnose your problem. So, when reporting a bug or a problem, please provide the following information: steps we should take to duplicate your problem (i.e.Related Questions
Cyberduck HelpOpen a new ticket using the issue tracker with a description of what you have a done and what went wrong. Make sure to look or search for existing tickets first.Related Questions
How do I submit a proper bug report?
Exult - Exult F.A.Q. (frequently asked questions)Read the Documentation and this FAQ to see if that is not already covered and you have all set up correctly. Before you report a bug to the bug tracker please try the latest snapshot. If the bug still occurs make sure that no one else already reported the bug (in the bug tracker). If you are not a SourceForge member please include your e-mail address. This is important so we can get back to you. If you are a SourceForge member please log in before submitting a bug.
Related QuestionsPostgreSQL: Frequently Asked Questions (FAQ) for PostgreSQLVisit the PostgreSQL bug form at http://www.postgresql.org/support/submitbug. Also check out our ftp site ftp://ftp.postgresql.org/pub/ to see if there is a more recent PostgreSQL version. Bugs submitted using the bug form or posted to any PostgreSQL mailing list typically generates one of the following replies:Related Questions
What should I include in my bug report?
FAQ - MercurialEnough information to reproduce or diagnose the bug. If you can, try using the hg -v and hg -d switches to figure out exactly what Mercurial is doing. If you can reproduce the bug in a simple repository, that is very helpful. The best is to create a simple shell script to automate this process, which can then be added to our test suite.
Related QuestionsI think I've found a bug - how do I report it?
FAQ - Q4MAXThe first thing to do is to check the bugs forum, since its possible someone else has already reported it. If so, we may have a work around - and if so, the solution will have been posted there. Next thing to do is to create a thread in the bugs forum. Please describe in as much detail as you can what is wrong, and what was happening when you saw it. Check your console for an error message - often there will be one there.
Related QuestionsWhere can I post a bug report?
FrequentlyAskedQuestions - MediaPortal Wiki DocumentationFirst of all, please check if a bug has not already been reported on the normal forums, on the test team forum or at the bugtracker. If your bug is not reported there, please read the bug template thoroughly and post your bug to the bug section on the normal forums or, even better, to the test team forum. Posting to the test team forum ensures that the test team will try to reproduce your bug and hand the necessary information over to the developers to fix it.
Related QuestionsFeed Me Links FAQ : Frequently Asked QuestionsIf you're sure you've found a bug, please check first that it hasn't been reported already by someone else. To see the list of reported bugs/issues, view the list of open tickets.Related Questions
Mckoi SQL Database - Frequently Asked Questions (FAQ)Bug reports can either be sent to the mailing list or sent personally to the developer at toby@mckoi.com. If the report includes attachments that are larger than 50K in size then send it to the developer rather than the list. Bug reports are a great way to contribute to the project. When submitting a bug report include as much information as you can on the circumstances that caused the error. It is often useful to include a cut and paste from the 'debug.Related Questions
I think I have located a bug. How do I submit a bug report?
LispWorks Frequently Asked QuestionsPlease note: the most common cause of delays in fixing problems and helping users is failure to follow these instructions.
Related QuestionsHow do I submit a bug report for Protégé?
Protégé FAQBugs that are specific to the Protégé-OWL editor should be reported on the protege-owl mailing list. All other bugs should be reported on the protege-discussion mailing list. You can view the current bug list and feature request list in Bugzilla.
Related QuestionsHow do I submit a bug report or or feature request?
HDBStat! - Frequently Asked QuestionsEasy! Just log in to our bugzilla server and submit a bug report or an RFE (request for enhancement). For bug reports, you should include the following information: The more the complete the initial bug report, the faster the bug can be reproduced, found, and fixed.
Related QuestionsI'm sure I've found a bug. How do I submit a report?
MySQL++We'll want some code that demonstrates the bug. No doubt you'd rather not send us a copy of your database and user table, so the best thing is to modify one of the MySQL++ examples so that it reproduces the problem you're seeing. This lets the people that can help you reproduce the problem on their machines, without needing your proprietary data. Once you have your problem boiled down to a simple example, send the modified program source code to the mailing list along with a detailed report.
Related QuestionsWhen do I submit a support case versus a bug report?
VMukti Frequently Asked Questions - voip-info.orgWhen in doubt, submit a support case instead of a bug report. VMukti support representatives can determine if your support case should result in a bug report, and will gladly file a bug report on your behalf when appropriate. If you have a question about installing, configuring, or using VMukti, and you have already reviewed the documentation, VMukti University, and the VMukti Wiki, then you should submit a support case.
Related QuestionsHow can I submit a bug fix or a new feature?
prefuse | documentation > frequently asked questionsYou can e-mail suggested bug fixes or new feature implementations to prefuse-admin (at) lists (dot) sourceforge (dot) net. New features may or may not be incorporated into the toolkit proper, if not, they can be shared as external extensions available from the prefuse website. Also feel free to post it to the Help Forum.
Related QuestionsI found a bug, where do I submit it?
The GNU-Darwin DistributionThis depends on the bug. If it's something in the kernel, feedback should go to Apple. Bugs in the distribution should be submitted to the GNU-Darwin bug tracker.
Related QuestionsI think I found a bug, how do I report it?
The linux-kernel mailing list FAQADB) A bug differs very slightly from an oops, actually. An oops is when the kernel detects that something has gone wrong. A bug is when something (in the kernel, presumably) doesn't behave the way it should, either with a driver or in some kernel algorithm. If you can detect this misbehaviour, you may or may not be getting an oops. Perhaps the most important step is to determine under which conditions this misbehaviour can be triggered, and whether it is reproducible.
Related QuestionsWhat information should go in a bug report?
The linux-kernel mailing list FAQADB) Does it affect system security? Is it related to a specific driver/hardware configuration? Did you manage to identify the piece(s) of kernel code concerned? It really depends on the kind of bug you found. TYT) Please follow general good bug reporting guidelines: remember, the developers don't have access to your system, and they're not mind readers. Tell us which kernel version, and what your hardware is (if you're not sure, more detail is better than less).
Related Questions