kobo claims all sideloaded epubs need adobe permission, until rebooted

[JSWolf]

I suggest loading this ePub into Calibre's editor and using Calibre's error checker and epubcheck to check for errors and if there are any, fix them and then try again.

I have never had my Kobo tell me an ePub has DRM when it doesn't.

[ghira]

Most of the times this happens to me it says _all_ sideloaded epubs (well all the ones I check) are drm protected. Reboot fixes it. The most recent incident is the first time I recall seeing it claim just one file was. And "most of the times" is... you know... an average of about once a year? So it's a bit vexing but not a huge problem. It would be nice for it to stop happening, clearly,

[DNSB]

Originally Posted by JSWolf

I suggest loading this ePub into Calibre's editor and using Calibre's error checker and epubcheck to check for errors and if there are any, fix them and then try again.

I have never had my Kobo tell me an ePub has DRM when it doesn't.

Been there, done that. It seems to have nothing to do with any errors in the epub. Once the error occurs, even a test epub that simply displays an SVG cover page comes up with the DRM error even though there is no encryption.xml file in the epub container.

[JSWolf]

Originally Posted by DNSB

Been there, done that. It seems to have nothing to do with any errors in the epub. Once the error occurs, even a test epub that simply displays an SVG cover page comes up with the DRM error even though there is no encryption.xml file in the epub container.

I wonder what causes this DRM error. I suggest having a look at these ePub and see what might be at fault. Does it happen if the cover is not using an SVG container?

[Quoth]

It seems random:
1t's very rare vs hours of reading dozens of books
The SAME book with no change worked OK after a reboot.
I have had malformed books refuse to go past a a particular page or seem to freeze the GUI, but not cause this error. No ebook will once it happens, or I think so. But it's very rare.

[DNSB]

Originally Posted by JSWolf

I wonder what causes this DRM error. I suggest having a look at these ePub and see what might be at fault. Does it happen if the cover is not using an SVG container?

Jon, it has nothing to do with the structure of the epub. Once it occurs on the first book that triggers the erroneous DRM popup, any epub that is opened will give the same error.

When experimenting with this, I played with the rights.xml and encryption.xml files and while modifying rights.xml made it easy to get the DRM popup, the flag was cleared when I opened another epub and it would open without the error. It appears that when the flag is set in error, a restart is needed to clear the flag.

[JSWolf]

Originally Posted by DNSB

Jon, it has nothing to do with the structure of the epub. Once it occurs on the first book that triggers the erroneous DRM popup, any epub that is opened will give the same error.

When experimenting with this, I played with the rights.xml and encryption.xml files and while modifying rights.xml made it easy to get the DRM popup, the flag was cleared when I opened another epub and it would open without the error. It appears that when the flag is set in error, a restart is needed to clear the flag.

So could it be a corrupt file that gets fixed after a reboot?

[NiLuJe]

No, it's a Nickel (or nickel-adjacent, at least, e.g., RMSDK) bug, the actual state of the files, filesystem, or Nickel db has zero bearings on it.

[DNSB]

Originally Posted by JSWolf

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.