Kobo Bug thread

[Orn8one]

Thanks you Lucas and Robco.
@Robco, thank you understood re how sync works now. I'll re-set the KT and update all on my iPad and sync. Fingers crossed! As for the kobo server causing the shelf issue that has made up my mind to finish the unread books on my KT and buy a Kindle. I use Amazon mainly for my research into books. Kobo's loss as I am the simple customer who buys books always on Kobo but the KT shelf issue and miserable search on Kobo.com has pushed me over the edge.
@Lucas thank you too. I had actually read your post before but I have no idea how to do anything with the database. I just buy books and read them. I love how simple that proceedure has become, that I no longer have to use ADE and load my reader up before a holiday and I can just buy and read. A year ago everything worked seamlessly now it's a mess. Well done Kobo!

[Lucas Malor]

How to reset the sqlite database:

1. Connect your Kobo reader to your computer or any other device
2. open the .kobo folder.
3. copy KoboReader.sqlite (the database) to you hard disk
4. unmount and disconnect the device
5. Go to the reader settings -> Account
6. sign out
7. restart
8. sign in again

If nothing changes, restore the backup.

If you know how to do, you can try to dump the db and import it in a new db (backup it before anyway)

[Ken Maltby]

And when you have a clean new database save a copy of that on your PC, as well.

Luck;
Ken

[tharael89]

Originally Posted by juliana000

I'm having these problens with the Firmware 2.8.1 with kepubs
1- when I close the book in the middle of a chapter (even when I bookmark) and open it again it always go back to the beginning of the chapter
....

i've got the same problem on my aura hd 2.8.1 firmware.
right % on the home but chapter restart on opening.
i'm using only kepub manually converted from epub using sigil.
stylesheet is quite simple and i'm not having reading problems.
only the restart of any book from the last chapter.
i've tried with in-chapter toc but it doesn't work for the restart.

note: every chapter is a xhtml file so maybe the reader it's not able restart the book from the right place because of this.
ps: i've read the conversion is done by pasting a simple *properties="cover-image"* on the content.opf in the *<item href="Images/Cover.jpg" id="Cover.jpg" media-type="image/jpeg"...* line.
do i have to put some other code somewhere else or is this also a corrupted database?

pps: i'll try to relog after the aura is full charged

EDIT: nothing changed even after relog. just like before when i open a kepub it restarts from the first page of the chapter and even the bookmark goes there.

[Orn8one]

Thank you again for your help and instructions Lucas and also Ken.
I don't actually have a PC to connect to! Since I have had the Kobo, wifi and the iPad for browsing, buying and searching I haven't needed a PC for home use. I haven't missed having one for 18 months until I read your post!
Will the multiple shelf issue be reported as a bug on the KT? I won't feel I have wasted your time on the bug thread if it is!

[donnieparker]

Bug: When woken up from sleep, epub books display Adobe epub page numbers even when previously turned off, and when reaching a new chapter, the font changes to something small and different from what I originally chose (for example, if I am reading with a middle-sized Caecillia, it reverts to some weird, small serif when you get to a new chapter). This happens virtually every time i wake the device from sleep when in the middle of a book.
Product: Kobo Aura
Firmware: 2.9.0
Plugins: None
File types: epub
Sideloaded or from Kobobooks: Sideloaded
On external SD: External SD
Steps to reproduce:

1. Open book
2. Put device to sleep with top switch or close sleep cover
3. Wake device
4. Bug appears immediately

Current result: Adobe epub page numbers appear (even if you've turned them off previously), and the font gets screwed up when reaching a new chapter
Workaround: When the bug is active, change the font to something else and then change back to desired font. Also, if you send the device back to the home screen, then reopen your book, the bug goes away.

[Lucas Malor]

@tharael89: ok, try first to reset database
@donnieparker: I have some similar bugs. To be sure, try to reset the database you too.
(davidfor, where you are? ^^)
@Orn8one: well, I'm sure you can find some device where you can connect your Kobo, since it requires an USB connection Go to a friend or an internet point.

About bug reporting, this thread is made by users for users. I think that some Kobo developers take a look to it, but its main scope is to have a community support and a list of bugs for deciding to upgrade or not to a X.Y firmware. If you want to report the bug to Kobo devs, read the first post

[glos]

I've been having something similar to what previously described... just adding what happens to my kobo.
With a sideloaded kepub (and it looks like it's only this book, BUT i'd been reading it for a while and it wasn't doing it from the start) via Calibre with the extended plugin, I stop reading on ch5, go to home, and the % is 0 and it reopens at the beginning. I then go to ch5 via TOC. If I put a bookmark on ch5 and go out again the % is still 0. It shows there's a bookmark but when I open it it tells me there is no bookmark and again it opens the book at the beginning.
I've tried first switching on/off and then a factory reset, this one book is still doing it (and it was working fine before... before I went 2.8.1 but even the first few days of 2.8.1 !) while another one I tried is not. Mah.

[davidfor]

@glos: This sounds like the device can't work out and store the reading position. Or if it stores it, it can't be reoponed to that point. The main times I have seen that problem is after replacing a version of the book without deleting it first. But, as the book didn't work after a factory reset, that isn't the case.

As it is one book that this is a problem for, then it probably is something about the book. And as you are sending it as a kepub via the extended driver, it might be something in how the kepub is created. I would recommend discussing this in the extended driver thread or raising a bug and supplying the original epub to the developer.

[gargoyle67]

So this is the footer bug in the new Aura ? I notices that on certain font sizes that I was missing 1 to 2 lines on the next page. I'm on fw v 2.9.0, is there a quick fix for this ?
You will notice in the pic below it actually has the top part of the next line of text obscured :
(it's an epub btw)

[davidfor]

@gargoyle67: Yes, this seems to be a new bug in 2.9.0. It has been discussed in https://www.mobileread.com/forums/sho...d.php?t=223396.

[gargoyle67]

Oh ok thanks for confirming Dave

[tharael89]

ok. in my case i've resolved the problem.
found out that the kepub code has a lot of id location just like this <span class="koboSpan" id="kobo.1.1"> that seems to let the reader remember pages and annotation.
bad news: to resolve you have to use calibre kepub conversion from your normal epub. the "problem" is that calibre adds a lot of junk in the conversion. it removes the original css for the calibre own and adds the [class="calibreNUMBER"] everywhere.
solution: if u don't have to use sigil for further editing you can just upload it on the device. on the other hand i've got to do it so i've used the sigil feature "find & replace" set on all the html files (right under the "replace" box) with all the [class="calibreNUMBER"].

this is for the problems with converted kepub for the annotations and page restarting problems.

now i've got a new problem.
i've tried to upload the converted kepub on the device but it freezes. on the other hand if i add use the kepub.epub extension on the kepub from calibre all works fine.
for information i've not bought or downloaded any kepub until now; i'm using newly converted o created ones by myself. so a question.
i've to put the .kepub on a particular folder in the sd card (i'm using it) or do i add to every .kepub the .epub extension?

sorry for the wt

[glos]

Originally Posted by davidfor

@glos: This sounds like the device can't work out and store the reading position. Or if it stores it, it can't be reoponed to that point. The main times I have seen that problem is after replacing a version of the book without deleting it first. But, as the book didn't work after a factory reset, that isn't the case.

As it is one book that this is a problem for, then it probably is something about the book. And as you are sending it as a kepub via the extended driver, it might be something in how the kepub is created. I would recommend discussing this in the extended driver thread or raising a bug and supplying the original epub to the developer.

thanks david, I'll do more testing and update everything first (calibre, plugin) and if it still persist I'll open a bug or ask for ideas there I can live with it if it's only that one book, anyway

[Jukets]

For Kobo Glo 2.8.1.
If you open sleepcover with light, Glo will not to sleep after a few tens seconds, but turn off the light instead.