MobileRead Forums - View Single Post

tshering · 03-19-2014, 05:08 AM

Another idea would be to use strace. You can find instructions and a link to the executable in this thread. The strace log will show you at which point nickel opens (and tries to open) a certain font file. However, I don't know exactly whether and how these information can help you solve your problem.
In this case I would not follow the instructions, but start strace from the rcS, in order to see also the start up process.
I would be something like

Code:

logfile=/mnt/onboard/.kobo/log_nickel_strace.txt
/mnt/onboard/.kobo/strace -o $logfile /usr/local/Kobo/nickel -qws -skipFontLoad

Modify the paths accordingly.
Generally, I would recommend using the Kobo Start Menu for this kind of job, but it is having problems with FW 3.2.0.

03-19-2014, 05:08 AM	#6
tshering Wizard Posts: 3,489 Karma: 2914715 Join Date: Jun 2012 Device: kobo touch	Another idea would be to use strace. You can find instructions and a link to the executable in this thread. The strace log will show you at which point nickel opens (and tries to open) a certain font file. However, I don't know exactly whether and how these information can help you solve your problem. In this case I would not follow the instructions, but start strace from the rcS, in order to see also the start up process. I would be something like Code: logfile=/mnt/onboard/.kobo/log_nickel_strace.txt /mnt/onboard/.kobo/strace -o $logfile /usr/local/Kobo/nickel -qws -skipFontLoad Modify the paths accordingly. Generally, I would recommend using the Kobo Start Menu for this kind of job, but it is having problems with FW 3.2.0. Last edited by tshering; 03-19-2014 at 05:23 AM.