--- Log opened Mon Jun 11 00:00:12 2018 00:06 -!- mvglasow [~mvglasow@dslb-188-104-118-094.188.104.pools.vodafone-ip.de] has quit [Quit: Leaving] 03:39 #navit: <+jkoan> Hi dak 03:40 #navit: <+jkoan> Good that you said that you are reading the logs, so I can answer right now :) 03:43 #navit: <+jkoan> The version 0.5.0 is a bit outdated and the Navit Sourcecode got updated quite a lot. I can't say right now if you're specific problem was fixed. But as far I know we haven't had such a problem recently. Our last release is the. 0.5.1 which can be found on GitHub. Are you able to compile and test this one out? 03:47 #navit: <+jkoan> This release is not in the Ubuntu/debian repos since it is new and the maintainer currently has some trouble with packing it up, so we should do a 0.5.2 also quite soon 05:10 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit 05:10 -!- mode/#navit [+v xenos1984] by ChanServ 07:25 -!- Horwitz [~mich1@p200300800E75CB00022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 245 seconds] 08:41 -!- naggety [~naggety@227.red-80-27-40.dynamicip.rima-tde.net] has joined #navit 11:28 -!- dak` [~user@x5ce41ace.dyn.telefonica.de] has joined #navit 11:29 #navit: < dak`> Ok, got the message. I am not thrilled about the prospect of compiling myself: I'd expect the same problems precluding packaging to affect a self-compilation. 11:30 #navit: < dak`> Basically, I was hoping about this being some compatibility problem between Gtk versions that could be fixed with a few lines in a config file. I think there once was something like that with file selectors. 11:33 #navit: < dak`> Given that Ubuntu is not exactly an outlandish distribution, I am a bit surprised that I should be the first having a problem. Admittedly, getting navit to run using the Gtk interface was not exactly standard fare either. Others might have given up before getting and configuring proper maps and finding out where to enable the Gtk interface (the delivered /etc/navit/navit.xml is hardwired to the Internal interface 11:33 #navit: < dak`> which is in an optional package: a setup not exactly lending itself to convincing a user that this is a working application) 11:38 #navit: < dak`> While I am at it: I have an Ericsson f5521gw GSM card with UPS which is half in the hands of ModemManager and its device management is a mess that needs a lot of manual help (I am trying to script around by and by) in order to talk to gpsd. Any plans of using, say, the geoclue library or similar means of getting at the GPS data? 11:38 #navit: < dak`> Uh, with GPS, not UPS. 12:22 -!- naggety [~naggety@227.red-80-27-40.dynamicip.rima-tde.net] has quit [Ping timeout: 264 seconds] 12:23 -!- naggety [~naggety@205.red-95-125-66.dynamicip.rima-tde.net] has joined #navit 12:55 -!- dak` [~user@x5ce41ace.dyn.telefonica.de] has quit [Ping timeout: 240 seconds] 13:16 -!- dak` [~user@x5ce41ace.dyn.telefonica.de] has joined #navit 13:54 -!- naggety [~naggety@205.red-95-125-66.dynamicip.rima-tde.net] has quit [Quit: Konversation terminated!] 14:23 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.] 14:50 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit 14:50 -!- mode/#navit [+v xenos1984] by ChanServ 14:54 #navit: <+jkoan> I didn't know geoclue but it sounds cool 15:36 #navit: <@KaZeR> hi there 15:37 #navit: <@KaZeR> dak`: yeah geoclue shouldn't be difficult to set up. IIRC, it uses dbus 15:38 #navit: <@KaZeR> dak`: your issue with GTK is indeed surprising. Maybe we can troubleshoot it in real time 15:42 #navit: < dak`> Well, I'd expect geoclue to use dbus at least for talking to ModemManager. I think that's what gnome-maps does (which can also do navigation) but gnome-maps needs to be online for access to OpenStreetMap tiles and it switches off its display the second you are offline, so you cannot even just use the maps it cached while still being online at home and doing the routing. As I only have on-demand GSP Internet (and i 15:42 #navit: < dak`> t's expensive), I'd rather work offline and just use GPS. 15:46 #navit: < dak`> Most of geoclue's sources require being online, so its main incentive for me would be that it gets along smoothly with my GPS modem while gpsd is sort of a royal PITA to use with it. 16:05 #navit: < dak`> So, uh, for me talking to ModemManager (which is also using dbus I think) would be equivalently useful. No idea whether others would like being able to use other location services (like looking up current WiFi beacons in a database). That would likely work reasonably well when on the train or bus with Hotspot there for the database lookup. 16:51 #navit: <@KaZeR> well i remember looking into geoclue myself some time ago as a way to speed up gps signal acquisition 16:51 #navit: <@KaZeR> so it shouldn't be too hard to get going 18:15 -!- noradtux [~noradtux@port-56488.pppoe.wtnet.de] has quit [Ping timeout: 240 seconds] 18:19 -!- noradtux [~noradtux@2a04:4540:8c00:4001:b5f2:e9ae:5080:d905] has joined #navit 18:24 #navit: < dak`> I've put up a video showing the behavior: https://youtu.be/AdgQ4XEg1Ys 18:25 #navit: <+ilovekiruna> hi all 18:25 #navit: <+ilovekiruna> hi KaZeR, hi dak` 18:25 #navit: < dak`> One thing that may contribute is that I have to correct the country setting since the locale is consulted regarding the _language_ rather than more reliable indicators than, say, the time zone 18:26 #navit: < dak`> Sorry: I complained about the gtk interface of the 0.5.0 coming with Ubuntu 18:26 #navit: <+jkoan> dak`: try to click on DE in the list 18:26 #navit: <+ilovekiruna> hi jkoan 18:26 #navit: <+jkoan> oh, okay 18:26 #navit: <+jkoan> hi ilovekiruna 18:26 #navit: < dak`> You'll see that I tried that as well. No dice. 18:27 #navit: <+ilovekiruna> jkoan: is there an update about the merging of the navit.xml split? 18:27 #navit: <+jkoan> dak`: yeah, seems really broken 18:27 #navit: <+jkoan> ilovekiruna: no 18:27 #navit: <+ilovekiruna> jkoan: btw: i was looking a bit on the profile of redmusic 18:27 #navit: <+ilovekiruna> seems like he requested many projects when he also approached us 18:30 #navit: <+jkoan> yes, but now he was very inactive 18:31 #navit: <+ilovekiruna> i know, was just wondering about his motivation 18:31 #navit: <+ilovekiruna> more like a temporary one 18:31 #navit: <+ilovekiruna> his profile was also pretty new that time 18:31 #navit: <+ilovekiruna> for example wesnoth refused him 18:32 #navit: <+jkoan> yes,probably to build a profile 18:32 #navit: <+ilovekiruna> i know i was quite inactive, but now at least finished one important project at work 18:32 #navit: <+ilovekiruna> hope, now i can look on my navit.xml topic again 18:33 #navit: <+ilovekiruna> btw: is there any special tag in openstreetmap that we use for routing with the bike profile? 18:37 #navit: <+jkoan> i dont know 18:46 #navit: <@KaZeR> dak`: i can't reproduce your issue with a recent version of Navit 18:46 #navit: <@KaZeR> can you tell me which version you are using? `navit -v` 18:47 #navit: <@KaZeR> dak`: thanks for the video btw, it definitely helps seeing the issue 18:50 #navit: < dak`> navit 0.5.0+git:0000- 18:53 #navit: <@KaZeR> thanks. i was hoping to get a git sha here. no big deal 18:55 #navit: < dak`> Well, Ubuntu's fault. dpkg -l navit shows 0.5.0+dfsg.1-2build1 which likely isn't overly helpful either, but the "dfsg" weakly suggests that they've taken a Debian package to start with 18:56 #navit: <@KaZeR> i 18:56 #navit: <@KaZeR> i'm actually a bit puzzled by your issue. Looking at the history between 0.5.0 and now, i don't see changes related to the gtk destination dialog 18:57 #navit: <@KaZeR> which version of ubuntu are you running? i'll set up one in a virtual machine to try to reproduce your issue 18:57 #navit: <@KaZeR> i 18:57 #navit: <@KaZeR> it'll make troubleshooting easier too 18:58 #navit: <@KaZeR> our dpkg maintainer is traveling currently.. iirc he'll be back in a week or two, so hopefully we'll be able to push 0.5.1 out to the ubuntu repos 18:58 #navit: < dak`> 18.04 LTS 18:59 #navit: <@KaZeR> thanks 18:59 #navit: < dak`> You'll need maps and edit /etc/navit/navit.xml to select the gtk interface. But you probably know that better than I do 19:00 #navit: <@KaZeR> i'm quite familiar with it :) 19:00 #navit: <@KaZeR> i reckon that the xml edition is annoying. from a user's point of view, how would you like to do? 19:01 #navit: < dak`> As I said, I suspect this may be related to some gtk version incompatibility. That stuff would crop up exactly _because_ nothing has been changed. 19:01 #navit: < dak`> Oh, before I forget it: amd64 architecture. But probably most people use that these days. 19:02 #navit: <@KaZeR> mmm. could you expand a bit on your gtk idea? 19:03 #navit: < dak`> Not really. I know that there was some problem at some point of time in relation to Emacs (file selection box or what?) that one was supposed to address with some gtk config file. Hm. Maybe I should try with a fresh user account in case that something old is haunting me here. 19:18 -!- dak` [~user@x5ce41ace.dyn.telefonica.de] has quit [Remote host closed the connection] 19:23 -!- dak` [~user@x5ce41ace.dyn.telefonica.de] has joined #navit 19:25 #navit: < dak`> Ok, just tested a fresh "Ubuntu Studio Session" account: same behavior. So it's not likely some holdover user configuration that causes my problem. 19:26 #navit: < dak`> For whatever it's worth, my locale is listed as 19:26 #navit: < dak`> LANG=en_US.UTF-8 19:26 #navit: < dak`> LANGUAGE=en 19:26 #navit: < dak`> LC_CTYPE="en_US.UTF-8" 19:26 #navit: < dak`> LC_NUMERIC=POSIX 19:26 #navit: < dak`> LC_TIME=de_DE.UTF-8 19:26 #navit: < dak`> LC_COLLATE="en_US.UTF-8" 19:26 #navit: < dak`> LC_MONETARY=de_DE.UTF-8 19:26 #navit: < dak`> LC_MESSAGES="en_US.UTF-8" 19:26 #navit: < dak`> LC_PAPER=de_DE.UTF-8 19:26 #navit: < dak`> LC_NAME=de_DE.UTF-8 19:26 #navit: < dak`> LC_ADDRESS=de_DE.UTF-8 19:26 #navit: < dak`> LC_TELEPHONE=de_DE.UTF-8 19:49 #navit: <@KaZeR> thanks dak` 19:49 #navit: <@KaZeR> the locale should only affect the default country but shouldn't prevent you from seleting another one 19:54 #navit: < dak`> Well, in case that having to select a different country triggers the problem in the first place. 20:00 #navit: <+ilovekiruna> KaZeR: can you tell me where i find the code to draw the background map? 20:15 #navit: <+ilovekiruna> is background_gc still current or was it removed? Wiki claims it to be removed soon, already back in 2012 21:18 -!- dak` [~user@x5ce41ace.dyn.telefonica.de] has quit [Ping timeout: 264 seconds] 21:28 -!- mvglasow [~mvglasow@dslb-188-104-118-094.188.104.pools.vodafone-ip.de] has joined #navit 21:28 #navit: < mvglasow> hi all 21:29 #navit: < mvglasow> ilovekiruna: to answer your question about bike routing 21:29 #navit: <+ilovekiruna> hi mvglasow 21:29 #navit: < mvglasow> any tag processing would happen in maptool 21:30 #navit: < mvglasow> routing works just based on vehicleprofiles defined in navit.xml 21:30 #navit: < mvglasow> the vehicleprofile needs to enumerate itens which are valid ways for that mode of transportation 21:30 #navit: < mvglasow> as well as access flags which need to be in place 21:31 #navit: < mvglasow> one specialty of the default bike profile is that it ignores oneway flags 21:31 #navit: <+ilovekiruna> mvglasow, so could it be limited only to bike routes excluding standard roads? 21:32 #navit: < mvglasow> you mean, building a bike profile which avoids, say, primary roads? 21:32 #navit: <+ilovekiruna> yes 21:32 #navit: < mvglasow> that could be done by removing the corresponding type (shoud be street_4_city and street_4_land) from the vehicleprofile 21:32 #navit: <+ilovekiruna> wow, that simple? 21:33 #navit: < mvglasow> yes, quite an easy one 21:33 #navit: < mvglasow> however, if you have a bike path running parallel to a primary road and mapped as a separate way, it would still be considered for routing 21:33 #navit: < mvglasow> because it's just a bike path to Navit 21:34 #navit: <+ilovekiruna> cool 21:34 #navit: <+ilovekiruna> was wondering recently while biking, seemed like it just wanted to guide me on ordinary roads 21:34 #navit: <+ilovekiruna> maybe was wrong, but will check next time when i drive the same route again 21:35 #navit: < mvglasow> you could also try messing with maxspeed and route_weight 21:35 #navit: < mvglasow> not sure about how exactly route_weight works, though 21:35 #navit: <+ilovekiruna> actually i have a gps track of where i was driving 21:35 #navit: <+ilovekiruna> code i test the algorithm with that? 21:36 #navit: < mvglasow> I think there's a way to use canned GPS data with Navit 21:36 #navit: <+ilovekiruna> great 21:36 #navit: < mvglasow> but if you just want to test routing, all you need is to set a position and destination 21:36 #navit: < mvglasow> you don't even need a valid GPS source 21:37 #navit: <+ilovekiruna> wont help, sometiems navit doesnt like my route ;-) 21:37 #navit: <+ilovekiruna> happens always when i drive to my real home or from there 21:40 #navit: < mvglasow> I had the opposite issue last year: Navit insisted sending me over gravel road in the woods and through the mud when the primary road would have been the much smoother ride 21:41 #navit: <+ilovekiruna> u fixed it? 21:41 #navit: < mvglasow> but Navit apparently had figured out the woods should have taken a few seconds less 21:41 #navit: < mvglasow> unfortunately, no fix 21:42 #navit: < mvglasow> I'd have to analyze the item types along each of the two paths 21:43 #navit: <+ilovekiruna> actually for such things, would be nice to have different alternative routes to choose from before navigating 21:43 #navit: <+ilovekiruna> right now I try to fix auxmap 21:54 #navit: < mvglasow> anyways, gotta go now 21:54 #navit: < mvglasow> bye 21:54 #navit: <+ilovekiruna> goodnigh mvglasow 21:54 -!- mvglasow [~mvglasow@dslb-188-104-118-094.188.104.pools.vodafone-ip.de] has quit [Quit: Leaving] 22:41 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.] --- Log closed Tue Jun 12 00:00:13 2018