Quote from: Christoph on January 10, 2014, 02:31:37 PM

About the logs:

Code:

ls -l *log*
-rw-r--r-- 1 christoph christoph 514486 Jan 10 06:39 armorycpplog.txt
-rw-r--r-- 1 christoph christoph 1408612 Jan 10 14:59 armorylog.txt
-rw-r--r-- 1 christoph christoph 1078697 Nov 17 00:02 ArmoryQt.py.log.txt

As you can see, the last one hasn't changed since november, is that due to a change of the filename between versions, or are there configuration options for different types of logs, and which one do you need in this case?

I cannot do anything productive in the GUI as soon as the buggy behaviour is triggered,

I've managed to open the export window, and found there that the middle log file should be the correct one, so I've sent this one via email.

Christoph