MobileRead Forums - View Single Post - Touch Kobo Touch crashing (segfault) when loading converted epub

davidfor · 10-26-2017, 06:43 AM

I'll have a look at the books in a little bit, but the stack dump says the book is a kepub. Are you sending the book to the device using the KoboTouchExtended driver? And did you delete the book from the device before resending it after the conversion? If you didn't, try that.

The reason for the delete is that the conversion will change the internal structure of the book. When a book is added to the device, it is imported and the entries are put into the database for the ToC and internal file structure. Resending a book from calibre doesn't trigger this happening, so the database will have the file structure and ToC from the first version. The conversion will have restructured the book and rebuilt the ToC. The error looks like the device is trying to reopen the book to your last reading location and failing. That location no longer exists, and the crash happens.

That's my theory until I have a chance to test.

10-26-2017, 06:43 AM	#2
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	I'll have a look at the books in a little bit, but the stack dump says the book is a kepub. Are you sending the book to the device using the KoboTouchExtended driver? And did you delete the book from the device before resending it after the conversion? If you didn't, try that. The reason for the delete is that the conversion will change the internal structure of the book. When a book is added to the device, it is imported and the entries are put into the database for the ToC and internal file structure. Resending a book from calibre doesn't trigger this happening, so the database will have the file structure and ToC from the first version. The conversion will have restructured the book and rebuilt the ToC. The error looks like the device is trying to reopen the book to your last reading location and failing. That location no longer exists, and the crash happens. That's my theory until I have a chance to test.