Bug's / Problems

MyTourbook is becoming more and more complex with each new release, therefore it's difficult to test every possible situation.

There are some logging features which show additional information, this is helpfull for the application developer when the application does not work as it should.

 

Show Log Console

The application can be run with an additional terminal window which shows logging information.

Windows

• add the arguments -debug and -consolelog to the command line

 

Linux

• start mytourbook in a terminal and add the arguments -debug and -consolelog to the command line

 

Mac OSX

• open Finder
• select folder: Applications/MyTourbook
• select file: mytourbook.app
• open context menu and select Show Package Contents
• in the opened folder select folder Contents/MacOS
• open mytourbook.ini with
  sudo /Applications/TextEdit.app/Contents/MacOS/TextEdit /Applications/MyTourbook.app/Contents/MacOS/mytourbook.ini
• edit & save the file mytourbook.ini and remove the comment character # from the line #-debug, keep the string -debug
• double-click mytourbook in the same folder this will start the application with the console

 

Open Error Log

An error log can also be viewed within the application

• in the menu select Help/About
• press button: Configuration Details
• select tab: Configuration
  
• press button: View Error Log

 

Known Bugs

Knows bugs are documented here

 

Problems

MyTourbook stops during startup

Error message in the log:
Could not connect to Derby Network Server on host 127.0.0.1, port 1527: Connection refused

Solution

This problem can occure on Linux systems and could be solved by adding the following line into mytourbook.ini

-Djava.net.preferIPv4Stack=true