Kobo Bug thread

[Lucas Malor]

I'm happy you know how to use bold and shift but I think it's better to discuss bugs in their own threads.

[Thalinor]

https://www.mobileread.com/forums/sho...d.php?t=200668

Sideloaded epubs still often skip pages when reopening (after sleep, power off, or returning to the homescreen) with books on the Glo.

[Urdu]

Bug: Chess game: Board goes blank after playing check.
Status: Confirmed
Device: Glo, Touch
From Firmware: 2.4.0

[Lucas Malor]

@Thalinor: bug added here.
@Urdu: bug added here.

[Ripplinger]

Originally Posted by Lucas Malor

@Ripplinger: added. Could you create also a test document with Sigil?

Bug: If a special character is followed by a tag and a word and no whitespace, word is wrapped anyway to the next line
Status: Confirmed
Device: Glo, Mini, Touch
From Firmware: 2.5.1

@anyone: the fact the database seems to get corrupted very easily seems to me a big bad bug...

Let me experiment a bit and see if I can come up with a text that will consistently do it without any copyright issues (copyright is the main concern, or I could just upload my current book I'm reading). It will have to be just the right length to catch the split and certain size font, and that font size will change somewhat if you change fonts.

It's definitely not an issue of a corrupt database at all, it's just bad software that splits in places it shouldn't be splitting at.

Edit: Created a very short 2 page epub that will show the beginning quote on one line and the following word falling on the next line for 2 instances. There's also images showing where the bug is in the text (with a bug to indicate it, of course!), and also an image of the font settings. It happens no matter what font you use, if the beginning quote will fall towards the end of the line, it will be split. In the images I have it set to full justify, but it makes no difference if you have justify off, set to left or set to right, it happens with all settings. The stylesheet for the epub does not specify any justification at all, I left it up to the reader software.

The stylesheet is as simple as possible, the only styles used in the book are <p> and <i> for italics:

p { 
display: block;
margin-top: 0em;
margin-bottom: 0em;
margin-left: 0em;
margin-right: 0em;
text-indent: 1.5em;
 }

[taming]

Originally Posted by Lucas Malor

@davidfor: I played a lot with my Glo, so my personal db troubles don't count. But I read many problems with db on the forum, it seems a common problem.

I have not had a broken Db in probably 18 months, with the exception of a problem after downloading a (legitimately purchased) bad book. I think you may underestimate the number of people who download books that have undergone problematic conversions or who play with things in ways that are not supported.

Responding to another post: if you think that each bug should have its own thread, ask the mods to create a bug subforum (like the one for developers).

[icallaci]

Originally Posted by Ripplinger

Edit: Created a very short 2 page epub that will show the beginning quote on one line and the following word falling on the next line for 2 instances. There's also images showing where the bug is in the text (with a bug to indicate it, of course!), and also an image of the font settings. It happens no matter what font you use, if the beginning quote will fall towards the end of the line, it will be split. In the images I have it set to full justify, but it makes no difference if you have justify off, set to left or set to right, it happens with all settings. The stylesheet for the epub does not specify any justification at all, I left it up to the reader software.

The stylesheet is as simple as possible, the only style used in the book is p and i for italics:

p { 
display: block;
margin-top: 0em;
margin-bottom: 0em;
margin-left: 0em;
margin-right: 0em;
text-indent: 1.5em;
 }

Thank you for creating this example. I have seen the same problem on my Aura, and it is very distracting. I was going to try to create something myself to show this bug, but you did all the hard work first! Thanks.

[Lucas Malor]

@Ripplinger: great! Can you attach it to your first post of the bug thread? Thank you

@taming: I'm discussing that here.

[Ripplinger]

Originally Posted by Lucas Malor

@Ripplinger: great! Can you attach it to your first post of the bug thread? Thank you

Done.

[Anak]

Product: Touch/Glow/Mini/Aura
Firmware: 2.5.2 and previous
Plugins: n/a
File types: kepub (epub2, css2.1, html4.x)
Sideloaded or from Kobobooks: Kobobooks (kepub)
On external SD: n/a
Steps to reproduce: See original thread
Current result: if the document default font is set to use the default ua serif font and headlines should use the default ua sans-serif font only the document default font is used. Not limited to headlines: applies to all css classes in which a different font family is defined than the document default font family.
Workaround: n/a
Remarks: this problem only happens with kepubs, epubs are fine.

[Lucas Malor]

I confirm the bug. It happens to every element that has font-family: sans-serif. I tested it with an html5 document, a version of your code:

Spoiler:

PHP Code:

<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="utf-8">
    <title>Some title</title>
    
    <style type="text/css">
        p 
        {
            font-family: sans-serif;
        }
        h1, h2, h3, h4 
        {
            font-family: serif;
        }
    </style>
    
  </head>
  <body>
    <h2>This headline should have a serif font.</h2>
    <p>This paragraph should have a sans-serif font.</p>
  </body>
</html> 


Can you add your informations in the original post? Thanks

EDIT: ah, if I set both h2 and p with sans-serif, text is displayed as serif anyway, so it's not caused by the use of two different families.

[Anak]

This bug has been fixed in 2.5.2. So it is only fair to mention that in the list.

Bug: Text in dictionary popup gets cut on the right

@Lucas Malor. Maybe you can add two categories to your first post: open bugs and solved bugs?
Don't delete solved bugs from the list as they may reappear again in future firmware releases.

[Lucas Malor]

Done!

[JSWolf]

Is it OK to put in feature requests?

[Lucas Malor]

What?