Opened 4 years ago

Closed 15 months ago

#1132 closed defect/bug (fixed)

Setting a destination causes Navit to crash

Reported by: phil Owned by: KaZeR
Priority: major Milestone:
Component: core Version: git master
Severity: normal Keywords:


Every time I try to set a destination, Navit crashes hard with this stack trace:

I'm using this config file, which is like the default, but modified in a few ways: (dbus and null graphics plugins enabled, gpsd vehicle replaced with demo, and enabling a mapset I downloaded myself.) Nothing which should affect stability as far as I can tell.

Note that the crash happens whether I set the destination using the GTK UI or over dbus using dbus-send --print-reply --session --dest=org.navit_project.navit /org/navit_project/navit/default_navit org.navit_project.navit.navit.set_destination string:"geo: 48.0 -122.0" string:"comment" as described on the wiki.

I'm running navit from Debian Wheezy, which is version 0.5.0~svn5126+dfsg.1-3.

Change History (3)

comment:1 Changed 4 years ago by phil

I tried this again with the latest built from SVN and got a much shorter stack trace:

phil@enigma ~/opt $ bin/navit -c $HOME/src/jarvis/navit-full.xml 
config file n is set to `/home/phil/src/jarvis/navit-full.xml'
navit:main_real:Loading /home/phil/src/jarvis/navit-full.xml
navit:navit_get_user_data_directory:creating dir /home/phil/.navit
vehicle_demo:vehicle_demo_set_attr_do:unsupported attribute active
navit:main_real:Using config file '/home/phil/src/jarvis/navit-full.xml'
binding_dbus:request_navit_set_destination: destination -> comment
navit:coord_rect_overlap:/home/phil/src/navit/navit/coord.c:106 assertion failed:r2->lu.y >= r2->rl.y

comment:2 Changed 4 years ago by phil

I've downloaded a fresh map, and now setting a destination in the GUI works. Using the dbus invocation above still causes the "assertion failed" crash, which makes me think maybe the dbus docs are outdated? Perhaps the format for the coordinates has changed?

comment:3 Changed 15 months ago by kazer

  • Resolution set to fixed
  • Severity set to normal
  • Status changed from new to closed

Hi Phil,

Sorry for the late reply, this ticket went unnoticed :(

I checked the documentation at and it is correct. The format is "geo: <longitude> <latitude>"

In your example, you switched the two items ( coordinates are indeed often refered to as in latitude longitude instead ).

Just tested on my dev box :

 $ dbus-send --print-reply --session --dest=org.navit_project.navit /org/navit_project/navit/default_navit org.navit_project.navit.navit.set_destination string:"geo: 48.0 -122.0" string:"comment"
Error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)

 $ dbus-send --print-reply --session --dest=org.navit_project.navit /org/navit_project/navit/default_navit org.navit_project.navit.navit.set_destination string:"geo: -122.0 48.0" string:"comment"
method return sender=:1.2 -> dest=:1.3 reply_serial=2
Note: See TracTickets for help on using tickets.