Kobo Bug thread

[arspr]

Product: At least AuraHD and H2O
Firmware: It's been here for some time. Now I'm in 3.11
Plugins: None
File types: At least in sideloaded kepubs
Sideloaded or from Kobobooks: Sideloaded
On external SD: No
Steps to reproduce: No know trigger
Current result:

This is a small issue but I've seen it for a long time in my old HD and it also happens in my new H2O.

Sometimes the cover in the Sleeping / Powered off screen is corrupted somehow. It's substituted by a blank rectangle.

If you don't have the setting about showing covers in sleeping / power off screen, you can also detect that this issue has happened because instead of a simple "Sleeping / Powered off" text, you also get the blank rectangle (I insist, even if you DON'T have the show cover option enabled).

Workaround: A simple power off / on cycle restores the normal behaviour.

[Anak]

Product: all Kobo readers running fw
Firmware: 3.11.0
Plugins: n/a
File types: epub (not tested with kepub; but very likely also affected)
Sideloaded or from Kobobooks: sideloaded
On external SD: n/a
Steps to reproduce:

1. load a dutch language book, or
2. fake this by setting the overall language (in content.opf) to Dutch ("nl", "nl-NL", or "nl-BE")

Current result: the build-in or supplied hyphenation file (hyph_nl.dic) does not work.
Reason: The file format is not correct.

1. The file (hyph_nl.dic) is saved as ANSI but this should be UTF8 w/o BOM;
2. The first line of the file states ISO8859-1 but should be UTF8.

Workaround: manually patching the firmware to replace the hyphenation file with the correct one.

The correct files are attached.

I attached two hyphenation dictionaries:

1. Kobo hyphenation NL default
2. Kobo hyphenation NL Adobe

'Default' is a converted hyph_nl.dic file to UT8 w/o BOM and first line to UTF8.
'Adobe' is as default, but with the addition of LeftHyphenMin and RightHyphenMin. The user is able to modify the behaviour of hyphenation to her or his personal preferences. A lower value means a more aggressive hyphenation. Adobe default is 5.

UTF-8
LEFTHYPHENMIN 5
RIGHTHYPHENMIN 5

[ethan3686]

Whenever i go into the browser of my kobo glo and search MARS [planet] or any other topic on wikipedia website it tries to load it but the screen freezes in loading. I have to charge or reset the kobo glo to bring it back from the freeze state or it just crashes and automatically goes back to kobo home screen and work normal again. Why is this happening?

[jbennion]

I am finding a bug on my Kobo Aura HD, and I am not sure if it is the KEPUB conversion in the Calibre Enhanced Kobo Driver, or if it's some bug in my Kobo itself. On this certain book I'm reading (which I purchased on Kindle), downloaded into Calibre, and then sent to my Kobo (converting it into a kepub in the process). The problem comes towards the end of every chapter, it cuts off about 1/2 to 1 1/2 pages before the end of the chapter. It's just missing, and page swipes move to the beginning of the chapter. I can read these chapter ends correctly in the Calibre epub viewer application (after changing the file extension from .kepub to .epub), and it also looks fine on my Kindle. But reading it on the Kobo itself, it cuts off the ends of the chapters. I can send the original (non DRMed) Kf8 file and the kepub file via PM.

[April112]

My Kobo Wireless (yes super old) is not recognized by Calibre.

Here what I get running a Debug:

calibre 2.12 [64bit] isfrozen: True is64bit: True
Windows-7-6.1.7601-SP1 Windows ('64bit', 'WindowsPE')
('Windows', '7', '6.1.7601')
Python 2.7.8
Windows: ('7', '6.1.7601', 'SP1', 'Multiprocessor Free')
USB devices on system:
[u'usb\\root_hub20&vid8086&pid1e26&rev0004',
u'usb\\root_hub20&vid8086&pid1e2d&rev0004',
u'usb\\vid_046d&pid_c52b&rev_1201',
u'usb\\vid_046d&pid_c52b&rev_1201&mi_00',
u'usb\\vid_046d&pid_c52b&rev_1201&mi_01',
u'usb\\vid_046d&pid_c52b&rev_1201&mi_02',
u'usb\\vid_04f2&pid_b2f4&rev_1118',
u'usb\\vid_04f2&pid_b2f4&rev_1118&mi_00',
u'usb\\vid_8087&pid_0024&rev_0000',
u'usb\\vid_8087&pid_0024&rev_0000',
u'usb\\vid_8087&pid_07da&rev_7869']
Traceback (most recent call last):
File "site-packages\calibre\devices\scanner.py", line 85, in __call__
DriveError: No removable drives found
Drives detected:

No disabled plugins
Looking for devices of type: MTP_DEVICE
The Windows WPD service says there are no portable devices connected

Looking for devices...

Devices possibly connected: None

Help!

[davidfor]

Originally Posted by April112

My Kobo Wireless (yes super old) is not recognized by Calibre.

Here what I get running a Debug:

calibre 2.12 [64bit] isfrozen: True is64bit: True
Windows-7-6.1.7601-SP1 Windows ('64bit', 'WindowsPE')
('Windows', '7', '6.1.7601')
Python 2.7.8
Windows: ('7', '6.1.7601', 'SP1', 'Multiprocessor Free')
USB devices on system:
[u'usb\\root_hub20&vid8086&pid1e26&rev0004',
u'usb\\root_hub20&vid8086&pid1e2d&rev0004',
u'usb\\vid_046d&pid_c52b&rev_1201',
u'usb\\vid_046d&pid_c52b&rev_1201&mi_00',
u'usb\\vid_046d&pid_c52b&rev_1201&mi_01',
u'usb\\vid_046d&pid_c52b&rev_1201&mi_02',
u'usb\\vid_04f2&pid_b2f4&rev_1118',
u'usb\\vid_04f2&pid_b2f4&rev_1118&mi_00',
u'usb\\vid_8087&pid_0024&rev_0000',
u'usb\\vid_8087&pid_0024&rev_0000',
u'usb\\vid_8087&pid_07da&rev_7869']
Traceback (most recent call last):
File "site-packages\calibre\devices\scanner.py", line 85, in __call__
DriveError: No removable drives found
Drives detected:

No disabled plugins
Looking for devices of type: MTP_DEVICE
The Windows WPD service says there are no portable devices connected

Looking for devices...

Devices possibly connected: None

Help!

That doesn't show any USB devices that look like they could be the WiFi. Does Windows mount it as a drive? If not, that is the problem as calibre can only access the device if the OS being used can see it.

Also, this is not really the right thread for this problem. Problems like this have been discussed in both Kobo and calibre forums. If a search doesn't find an answer, I'd suggest opening thread a thread to discuss the problem.

[throsu]

Device: Kobo Aura H2O
Firmware version: 3.12

Since last night I've noticed that my settings of a certain font type and dimension, as well as the paragraph setting doesn't produce any changes in the document (especially epub; however, for mobi files it does seem to work). I wonder what's wrong, given that there are exactly the same epub(s) that previously worked just fine in terms of these adjustments.

Thanks a lot!

[throsu]

Originally Posted by throsu

Device: Kobo Aura H2O
Firmware version: 3.12

Since last night I've noticed that my settings of a certain font type and dimension, as well as the paragraph setting doesn't produce any changes in the document (especially epub; however, for mobi files it does seem to work). I wonder what's wrong, given that there are exactly the same epub(s) that previously worked just fine in terms of these adjustments.

Thanks a lot!

Apparently, everything is fine now, just by powering off and then restarting the device. No reset whatsoever was needed...

The initial lack of response in terms of setting the font size or the line spacing might be related to the use of the Kobo cover, which only implies a sleeping off the device but not a complete power off. Does this make any sense?

[JSWolf]

I think I may have found a rather serious bug.

I've created an ePub that specifies specific font sizes and it doesn't display properly. On the H2O, all I get is whatever the font size is via the font size slider. I cannot get specific font sizes via em, pt, or px. Nothing works. There has to be a way to specify a specific font size. But if there is, I have no idea what it is.

[Rev. Bob]

Originally Posted by JSWolf

I think I may have found a rather serious bug.

I've created an ePub that specifies specific font sizes and it doesn't display properly. On the H2O, all I get is whatever the font size is via the font size slider. I cannot get specific font sizes via em, pt, or px. Nothing works. There has to be a way to specify a specific font size. But if there is, I have no idea what it is.

With only that information to go on, I'm more prone to expect that the bug is in your CSS than in the reader.

[Josieb1]

I've got the duplicated shelves problem back on my Kobo Aura H20 as a result 3.12. I mistakenly left the wifi on

I can't remember how to fix it, can anyone enlighten me, shelves are impossible now I've got 260 instead of three pages.

[JSWolf]

Originally Posted by Rev. Bob

With only that information to go on, I'm more prone to expect that the bug is in your CSS than in the reader.

CSS...

p {
margin-top: 0;
margin-bottom: 0;
text-indent: 1.2em
}
.f15px {
font-size: 15px
}
.f20px {
font-size: 20px
}

XML...

<p class="f15px">The quick brown fox jumped over the lazy dog. The quick brown fox jumped over the lazy dog. The quick brown fox jumped over the lazy dog. The quick brown fox jumped over the lazy dog. The quick brown fox jumped over the lazy dog.</p>
<p class="f20px">The quick brown fox jumped over the lazy dog. The quick brown fox jumped over the lazy dog. The quick brown fox jumped over the lazy dog. The quick brown fox jumped over the lazy dog. The quick brown fox jumped over the lazy dog.</p>

All I get is whatever font size is specified by the font size slider. Both paragraphs will be the exact same size. If you see a bug in either the CSS or the code or know of a different way of doing this, please let me know.

[Rev. Bob]

Originally Posted by JSWolf

All I get is whatever font size is specified by the font size slider. Both paragraphs will be the exact same size. If you see a bug in either the CSS or the code or know of a different way of doing this, please let me know.

Well, aside from the usually ill-advised practice of specifying hard pixel sizes (VERY user-unfriendly, with a couple of exceptions), that code looks sound. On the "check the power cord" front, have you made sure that, if the CSS is in its own file, the HTML document calls that file? Have you tried bigger differences between the sizes, to make sure they're not getting rounded together in rendering? Have you set the base font size in pixels at the BODY level, so the renderer can associate a relative size with an absolute one? (Shouldn't be necessary, and I wouldn't do it for release, but it'd help nail down the problem.)

Oh, and try terminating every CSS property with a semicolon. Yes, I know you technically don't need it on the last property in a set...do it anyway. It's good form.

[JSWolf]

Originally Posted by Rev. Bob

Well, aside from the usually ill-advised practice of specifying hard pixel sizes (VERY user-unfriendly, with a couple of exceptions), that code looks sound. On the "check the power cord" front, have you made sure that, if the CSS is in its own file, the HTML document calls that file? Have you tried bigger differences between the sizes, to make sure they're not getting rounded together in rendering? Have you set the base font size in pixels at the BODY level, so the renderer can associate a relative size with an absolute one? (Shouldn't be necessary, and I wouldn't do it for release, but it'd help nail down the problem.)

Oh, and try terminating every CSS property with a semicolon. Yes, I know you technically don't need it on the last property in a set...do it anyway. It's good form.

In my CSS, I specified all sizes from 1px to 30px. I even tried em and pt. I also tried with and with an ending semicolon. I did not specify any font size in body as these are not relative sizes but absolute sizes (except for em).

They all came out at whatever size was specified by the font size slider.

[Rev. Bob]

Originally Posted by Josieb1

I've got the duplicated shelves problem back on my Kobo Aura H20 as a result 3.12. I mistakenly left the wifi on

I can't remember how to fix it, can anyone enlighten me, shelves are impossible now I've got 260 instead of three pages.

The last time this happened to me, I did two things to fix it.

0. If you have a recent backup of the database, restore it; problem solved. If not, smack yourself gently on the face with a red snapper.

1. Use an SQLite utility to go to the database table (make a backup first!) that has all the shelves, mark everything "false" in the "_IsSynced" column, and mark everything "true" in the "_IsDeleted" and "_IsVisible" columns. (You can do that with one statement for each column, but the syntax eludes me at the moment.) Then go through and find the shelves you want to keep, marking them "false" in the "_IsDeleted" field. Make another backup, then disconnect the reader and see if the shelf list matches what you want. If it doesn't, try again until it does. Sync the reader to send the changes up to the cloud, and make sure nothing changed on the reader in the process. If you're good, delete the two backup databases and make a fresh backup of the "blessed by sync" version.

2. Make periodic backups, at least of the database. How periodic? Only you can answer that, but "after significantly changing the contents of the reader" is a good time. Note that with the Kobo, this means after letting it scan newly-added books, so the database is up to date and won't have to start by adding several entries. Yes, you'll have to reconnect the device to the computer. Small price to pay.