Issue with driverinfo.kte

Leonatus · 04-10-2023, 04:12 AM

Happy Easter to everyone!
As a USB drive went broken lately, I had to restore a book by exporting the epub format out of my Calibre library. Everything is good, so far, and all the checks don't leave to an error message, so I needn't have to worry, but it bothers me that every time I open the book in Sigil, I receive the message:

Code:

Epub contains not manifested files. They will not be saved.

And when I look into the details, I see that it is the "driverinfo.kte" that causes the issue.
Looking across the epub, I can't find this "driverinfo.kte" anywhere, and S/R doesn't help either.
No problem, as I mentioned, but out of interest I would really like to know what it is about with this file.
Would someone enjoy to enlighten me?

DiapDealer · 04-10-2023, 06:47 AM

Never seen that before. Could it be some sort of artifact of the KoboTouchExtended driver plugin being installed/used on calibre?

DiapDealer · 04-10-2023, 10:34 AM

It is most definitely a temporary file used and created by the kobotouchextended driver plugin for calibre.

https://github.com/jgoguen/calibre-k...driver.py#L262

You're not going to see the file unless you open the epub as a zip archive. It is my understanding, however, that the plugin does not modify an epub in calibre's library. It updates epubs when they are sent to a kobo device. To support "extra" kobo features. If that's true, you must be using eboubs that were a) delivered to your Kobo using the KoboTouchExtended driver, and then b) subsequently pulled off of your Kobo before editing with Sigil.

Leonatus · 04-10-2023, 11:20 AM

Quote:

Originally Posted by DiapDealer

It is most definitely a temporary file used and created by the kobotouchextended driver plugin for calibre.

You're not going to see the file unless you open the epub as a zip archive. It is my understanding, however, that the plugin does not modify an epub in calibre's library. It updates epubs when they are sent to a kobo device. To support "extra" kobo features. If that's true, you must be using eboubs that were a) delivered to your Kobo using the KoboTouchExtended driver, and then b) subsequently pulled off of your Kobo before editing with Sigil.

Yes, that's true. I didn't have thought of it any more, because it's quite usual to me. Just for fun, I'll try to open it as a zip archive and see what happens.
Thank you!

DiapDealer · 04-10-2023, 11:49 AM

You should probably keep originals of your epubs to use for editing purposes. Only send the modified--kobo proprietary--epubs to your Kobo device(s) for viewing/reading purposes.

Leonatus · 04-11-2023, 03:36 AM

@DiapDealer: Of course, and that's what I had done. But the USB drive where the epub had been stored was broken, unluckily.

By the way: As far as I know, the KobotouchExtended driver takes effect only at sending the book to the device. The exported epub, however, came immediately from the Calibre library.

Leonatus · 04-11-2023, 04:08 AM

Now, I copied the epub, changed the file ending in .zip (ignoring the warning), deleted the driverinfo.kte, renamed the file ending to .epub, and all went right! Thanks again!

DiapDealer · 04-11-2023, 07:18 AM

Quote:

Originally Posted by Leonatus

By the way: As far as I know, the KobotouchExtended driver takes effect only at sending the book to the device. The exported epub, however, came immediately from the Calibre library.

That's the way I understood it was supposed to work, too. Perhaps one book just managed to make it back from the Kobo to calibre somehow. *shrug*

All's well that ends well, though!

Leonatus · 04-11-2023, 10:11 AM

Quote:

Originally Posted by DiapDealer

Perhaps one book just managed to make it back from the Kobo to calibre somehow.

That's something for crime fiction authors; anyway, it must have been something like this.

04-10-2023, 04:12 AM	#1
Leonatus Wizard Posts: 1,023 Karma: 10963125 Join Date: Mar 2013 Location: Guben, Brandenburg, Germany Device: Kobo Clara 2E, Tolino Shine 3	Issue with driverinfo.kte Happy Easter to everyone! As a USB drive went broken lately, I had to restore a book by exporting the epub format out of my Calibre library. Everything is good, so far, and all the checks don't leave to an error message, so I needn't have to worry, but it bothers me that every time I open the book in Sigil, I receive the message: Code: Epub contains not manifested files. They will not be saved. And when I look into the details, I see that it is the "driverinfo.kte" that causes the issue. Looking across the epub, I can't find this "driverinfo.kte" anywhere, and S/R doesn't help either. No problem, as I mentioned, but out of interest I would really like to know what it is about with this file. Would someone enjoy to enlighten me?

04-10-2023, 10:34 AM	#3
DiapDealer Grand Sorcerer Posts: 27,549 Karma: 193191846 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	It is most definitely a temporary file used and created by the kobotouchextended driver plugin for calibre. https://github.com/jgoguen/calibre-k...driver.py#L262 You're not going to see the file unless you open the epub as a zip archive. It is my understanding, however, that the plugin does not modify an epub in calibre's library. It updates epubs when they are sent to a kobo device. To support "extra" kobo features. If that's true, you must be using eboubs that were a) delivered to your Kobo using the KoboTouchExtended driver, and then b) subsequently pulled off of your Kobo before editing with Sigil. Last edited by DiapDealer; 04-10-2023 at 10:40 AM.

04-11-2023, 03:36 AM	#6
Leonatus Wizard Posts: 1,023 Karma: 10963125 Join Date: Mar 2013 Location: Guben, Brandenburg, Germany Device: Kobo Clara 2E, Tolino Shine 3	@DiapDealer: Of course, and that's what I had done. But the USB drive where the epub had been stored was broken, unluckily. By the way: As far as I know, the KobotouchExtended driver takes effect only at sending the book to the device. The exported epub, however, came immediately from the Calibre library. Last edited by Leonatus; 04-11-2023 at 03:39 AM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Kindle 4 Cant reach certain buttons issue and opening keyboard issue	Thefirebeast	KOReader	6	06-26-2021 12:46 AM
issue converting from azw3 to mobi (ccs and font issue)	fatkinglet	Conversion	3	10-15-2020 10:13 PM
stylesheet issue ... plus dumb user issue	x2far	Sigil	7	03-09-2013 10:09 PM
Nook Simple Touch Glowlight - technological issue or quality-control issue?	Dr. Drib	Barnes & Noble NOOK	1	12-04-2012 01:32 PM
Hyperlinks Issue in NLT Bible (ebook or software issue)?	myet01	Kobo Reader	5	07-29-2011 08:47 AM

04-10-2023, 06:47 AM	#2
DiapDealer Grand Sorcerer Posts: 27,549 Karma: 193191846 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	Never seen that before. Could it be some sort of artifact of the KoboTouchExtended driver plugin being installed/used on calibre?

04-10-2023, 11:49 AM	#5
DiapDealer Grand Sorcerer Posts: 27,549 Karma: 193191846 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	You should probably keep originals of your epubs to use for editing purposes. Only send the modified--kobo proprietary--epubs to your Kobo device(s) for viewing/reading purposes.

04-11-2023, 04:08 AM	#7
Leonatus Wizard Posts: 1,023 Karma: 10963125 Join Date: Mar 2013 Location: Guben, Brandenburg, Germany Device: Kobo Clara 2E, Tolino Shine 3	Now, I copied the epub, changed the file ending in .zip (ignoring the warning), deleted the driverinfo.kte, renamed the file ending to .epub, and all went right! Thanks again!

Advert

Advert