View Single Post
Old 12-24-2022, 12:04 AM   #39
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,450
Karma: 171313058
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
So could it be a corrupt file that gets fixed after a reboot?
I would disagree with the issue being a corrupted file. The more likely explanation to me is that if the flag (likely a single bit) gets set when an invalid rights.xml file is detected in normal operation, Nickel/RMSDK are aware that it has been set and clear it before opening the next book. If the flag is set due to a bug/error, it is not cleared and will remain set until memory is cleared during the restart.

I added a DRMmed epub to my Sage and am going to try opening it on the next occurrence to see if that will clear the flag. Unfortunately, it's been a couple of months and still hasn't happened.
DNSB is offline   Reply With Quote