Difference between revisions of "Reporting Bugs"

From Navit's Wiki
Jump to: navigation, search
(Undo revision 14942 by Mcr (talk))
(Mention forum, autotools -> cmake)
Line 9: Line 9:
 
Note: It doesn't seem possible to log in at the moment (17 Jan 2013) into the Trac system using the Navit wiki accounts. The only available option is an OpenID account. I wish someone would amend the Trac front page with this information as well - as I've spent a lot of time looking for a way to log into the Trac system using the Navit wiki account.
 
Note: It doesn't seem possible to log in at the moment (17 Jan 2013) into the Trac system using the Navit wiki accounts. The only available option is an OpenID account. I wish someone would amend the Trac front page with this information as well - as I've spent a lot of time looking for a way to log into the Trac system using the Navit wiki account.
  
Note that you can also head over to the [[Contacts#IRC| IRC channel]] if you want to discuss the bug before submitting a report - for example, it may just be that your local configuration is wrong, which can quickly be diagnosed by the developers on the channel. If there is a bug in Navit, it often gets fixed on the spot if reported on the [[Contacts#IRC | IRC channel]].
+
Note that you can also head over to the [[Contacts#IRC| IRC channel]] or to the [[Contacts#Forums|Forums]] if you want to discuss the bug before submitting a report - for example, it may just be that your local configuration is wrong, which can quickly be diagnosed by the developers on the channel. If there is a bug in Navit, it often gets fixed on the spot if reported on the [[Contacts#IRC | IRC channel]].
  
 
=Information you should provide=
 
=Information you should provide=
Line 15: Line 15:
  
 
==For compile/install problems==
 
==For compile/install problems==
Make sure you have re-run ''autogen.sh'' and ''configure'' after an svn update
+
First, please perform a "clean" build: Delete and recreate your build directory, then perform a complete build (cmake + make). Normally, re-running ''cmake'' after an svn update or other change should be enough, but if you run into problems, a clean build is better.
~$ svn up && ./autogen.sh && ./configure
 
 
* Which version of navit you are using.
 
* Which version of navit you are using.
 
* What operating system and distribution you are using, and what platform.
 
* What operating system and distribution you are using, and what platform.
Line 27: Line 26:
 
* What operating system and distribution you are using, and what platform.
 
* What operating system and distribution you are using, and what platform.
 
* The output of the ''locale'' command if using an Unix-based OS (Linux/Mac).
 
* The output of the ''locale'' command if using an Unix-based OS (Linux/Mac).
* Preferably include your complete navit.xml, or at least what you have changed in the shipped navit.xml (as verbose as possible). Please '''attach''' this to the ticket.
+
* Ideally, reproduce your problem with the shipped navit.xml. If that is not possible, try to find the minimal change necessary to reproduce it. If you are unable to narrow down the problem, include your complete navit.xml, as an attachment to the ticket.
 
* What maps you have used, and where you have downloaded them from (if applicable).
 
* What maps you have used, and where you have downloaded them from (if applicable).
  

Revision as of 18:51, 9 July 2013

All bugs and feature requests are to be reported to the Navit developers through Trac. Please read the guidlines below before submitting your bug - this is so that the developers receive a clear and helpful bug report.

Reporting a bug

  1. Register on this wiki, choosing a suitable username and password
  2. Head over to http://trac.navit-project.org and login with the same username and password
  3. Read the guidelines below
  4. Create and compile your bug report, and submit it

Note: It doesn't seem possible to log in at the moment (17 Jan 2013) into the Trac system using the Navit wiki accounts. The only available option is an OpenID account. I wish someone would amend the Trac front page with this information as well - as I've spent a lot of time looking for a way to log into the Trac system using the Navit wiki account.

Note that you can also head over to the IRC channel or to the Forums if you want to discuss the bug before submitting a report - for example, it may just be that your local configuration is wrong, which can quickly be diagnosed by the developers on the channel. If there is a bug in Navit, it often gets fixed on the spot if reported on the IRC channel.

Information you should provide

The following information for each type of problem will enable the developers to very quickly isolate the section of code which is causing problems, and hopefully fix it. Please provide the requested information in your bug report.

For compile/install problems

First, please perform a "clean" build: Delete and recreate your build directory, then perform a complete build (cmake + make). Normally, re-running cmake after an svn update or other change should be enough, but if you run into problems, a clean build is better.

  • Which version of navit you are using.
  • What operating system and distribution you are using, and what platform.
  • The source of the sourcecode or installation files (provide a link if possible).
  • The complete output of configure (if you don't know how to do this, leave this step out).
  • The complete output of make (if you don't know how to do this, leave this step out).

For usage problems

  • Which version of navit you are using, and whether you have compiled it yourself or where you downloaded the install file from.
  • What operating system and distribution you are using, and what platform.
  • The output of the locale command if using an Unix-based OS (Linux/Mac).
  • Ideally, reproduce your problem with the shipped navit.xml. If that is not possible, try to find the minimal change necessary to reproduce it. If you are unable to narrow down the problem, include your complete navit.xml, as an attachment to the ticket.
  • What maps you have used, and where you have downloaded them from (if applicable).

In addition, please provide the following (where appropriate):

Reporting coordinates for problems

Assuming a fresh install of Navit:

  • GTK GUI:
    1. Right click on the map at the specific position.
    2. The first item on the context menu is Point - enter this submenu.
    3. The coordinates are shown as the second and third items of the subsequent menu (Degrees/Minutes/Seconds format and decimal degrees format respectively)
  • Internal GUI:
    1. Drag and zoom the map to the right coordinate, and enter the menu by clicking on the map at correct position.
    2. Go into the Actions Menu.
    3. The coordinates are displayed under the globe in Degrees/Minutes/Seconds format.

You could add a bookmark to save you from writing down the coordinates.

Routing errors

Problems may include illegal routes (such as the wrong way on a one-way road), routes which are sub-optimum or no route found at all!

Navigation errors

Problems may include missing announcements, wrong and/or misleading announcements, and unnecessary announcements. Please enable the navigation map to diagnose such problems.

  • GTK GUI:
    1. Click on the Map item in the toolbar.
    2. Enable the navigation:' map.
  • Internal GUI:
    1. Click anywhere on the map to enter the menu.
    2. Enter the Settings submenu, followed by the Maps submenu.
    3. Enable the Navigation map.

You should see a navigation symbol at every point where an action is required. If the map looks correct, but Navit provided an incorrect announcement, the problem is most likely tracking and/or announcement related

Note that quite a few navigation problems occur due to bad map data - this can only be solved by improving the data in OpenStreetMap or FreeOpenStreetMap

Tracking errors

Problems may include the indication of an incorrect vehicle position, or jumping between correct and incorrect positions.

Announcement errors

Problems may include announcements too early, announcements too late, incorrect announcements, repeated announcements, missing announcements etc.