View Single Post
Old 11-30-2017, 03:34 AM   #908
tshering
Wizard
tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.
 
Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
Quote:
Originally Posted by Question Mark View Post
However, just a few minutes ago after checking my CPU in KSM, I went back into Nickel and got the popup box telling me that a computer had been detected and did I want to connect to it. However, I didn't have anything plugged into my KA1. Weird.

Just repeated the process and everything worked as expected. No popup box this time.

Not sure whether I should roll back to an earlier firmware now or just continue as is.
I think the problem is the fault-prone usage of fmon (filemonitor) to associate certain pngs with scripts. After the FW update there was evidently some need to create one or several new thumb images, or to reindex some files. This triggered the script associated with simulate_usb_connection.png to run. You can try to start nickel by selecting
  • "tools" > "nickel diverse.msh" > "start nickel no fmon.sh."
This will start nickel without associating the images with scripts. Therefore you can comfortably visit these images in the library, open them, so that they appear on the home screen, also as part of a collection (if they are part of one), and give nickel a chance to reindex them and create thumb images if necessary.

If you do not need simulate_usb_connection.png, just delete it from kbmenupngs. By this is one source of error removed.

Last edited by tshering; 11-30-2017 at 03:37 AM.
tshering is offline   Reply With Quote