--- Log opened Sat Jul 29 00:00:08 2017 01:45 -!- noradtux [~noradtux@2a02:2028:521:ab01:b899:86ff:feb1:b813] has quit [Ping timeout: 240 seconds] 01:49 -!- noradtux [~noradtux@port-10608.pppoe.wtnet.de] has joined #navit 04:06 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit 05:15 -!- deep-book-gk_ [~1wm_su@159.122.132.44] has joined #navit 05:17 -!- deep-book-gk_ [~1wm_su@159.122.132.44] has left #navit [] 08:20 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.] 20:41 -!- bzed [~bzed@217.196.148.210] has quit [Ping timeout: 255 seconds] 20:44 -!- bzed [~bzed@shell.bzed.at] has joined #navit 21:11 -!- bzed_ [~bzed@shell.bzed.at] has joined #navit 21:12 -!- bzed [~bzed@shell.bzed.at] has quit [Remote host closed the connection] 21:12 -!- bzed_ is now known as bzed 22:23 #navit: * tryagain wonders if current freshly installed navit is able to start without a crash on android if /sdcard/navit does not exist or does not have navit.xml inside 22:24 #navit: < tryagain> I have some apk dated 2015 which is able to start. Other apks, about a year old and current all crash, unless I have put some config file to /sdcard/navit 22:41 #navit: * tryagain facepalms as the bug could have been introduced with https://github.com/navit-gps/navit/commit/30bcb605c13b8e73c297e7cbf9de4ac2f01e4546#diff-066284896cf9e1846c96bcb93aa2aea5 23:17 -!- Horwitz [~mich1@p200300800E718A00022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 255 seconds] 23:29 -!- Horwitz [~mich1@p200300800E46E300022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit 23:29 -!- mode/#navit [+o Horwitz] by ChanServ --- Log closed Sun Jul 30 00:00:10 2017