Thread: NickelMenu: An integrated launcher for Kobo eReaders
View Single Post
Old 03-24-2024, 05:05 PM   #1228
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,160
Karma: 169815798
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by JSWolf View Post
Given this is not an all the time problem, how will we know if it's fixed? If NickelMenu could detect these files and let us know, then we could reboot. Also, if NickelMenu keeps telling us these files do not exist, then after long enough, we can say it's fixed.
The idea is to make sure the database has no connections and is properly closed during the USB connect process. Removing the last connection to the database files triggers the cleanup procedure but that is not something that would be done during normal operations when the database would be in use. If the database is in use, you could still see those files before attempting a USB connect so your suggested test would be basically meaningless. The only way to be certain the database was properly closed would be if you did not see the .sqlite-wal and .sqlite-shm files after the connect.
DNSB is offline   Reply With Quote