If we could, what one bug would you like to see fixed?

[Terisa de morgan]

Originally Posted by JSWolf

The bugs that are reproducible are the ones that should be fixed. It just seems silly that bugs come and go with different firmware versions.

Yes? Really? It looks normal for me

[ottdmk]

PDF performance. It's the only thing keeping me off of 3.8 right now.

[DNSB]

Originally Posted by treadlightly

I would like to remove the requirement to be logged in to a Kobo Account. On the two occasions that my device spontaneously logged out of my account and the database became corrupted*, I had to open the Kobo Desktop to get past the log in phase, which then causes me to need to update the Desktop, and then forcefully updates the device, losing my patched version, etc. This part of the software is a nightmare for someone who leaves wireless off and only wants to update firmware when they so desire.

*This has only happened twice in three years of use, which is far less than either my KK or Sony T1 ever crashed and rebooted, so I feel particularly whiny complaining about it, but it was traumatic when it happened while I was away from a computer.

Not really a bug though, more of a let's try to tie them to our ecosystem.

Hmmmm... twice in 3 years. I admit the way I treat my ereaders might be a factor but I've managed to corrupt my database about 8 times in the last year. Some weird items such as having books that are on the device, are readable but Calibre doesn't seem to know where they live. Perhaps, I should start reading more and playing less? Give up multibooting, alternate readers, modifying firmware?

Regards,

David

[DNSB]

My three choices would be:

1. Annotations bug. They seem to work okay with .kepub so fix them with .epub.

2. Fewer regression errors -- the one where they fix a bug and then another bug fix/code change resurrects the older bug. OTOH, I spent much of the Windows 95 beta complaining about the same thing. Some things just don't change.

3. Fewer reproducible bugs surviving through multiple firmware revisions.

Regards,

David

[John F]

Originally Posted by PeterT

Sigh... Never happen, especially when some bugs are not reproducible.

I'm trying to be something that a lot of you aren't ... realistic

Seems "ALL" is a little unresonable, but the other requests seem reasonable?

Although prioritizing annotation bugs first seems unreasonable, as "nobody" uses annotations.

[treadlightly]

Originally Posted by DNSB

Not really a bug though, more of a let's try to tie them to our ecosystem.

Hmmmm... twice in 3 years. I admit the way I treat my ereaders might be a factor but I've managed to corrupt my database about 8 times in the last year. Some weird items such as having books that are on the device, are readable but Calibre doesn't seem to know where they live. Perhaps, I should start reading more and playing less? Give up multibooting, alternate readers, modifying firmware?

Regards,

David

Yes, you might be asking for a few issues The "bug" I'm talking about isn't so much in the log in, I suppose, but in the fact that the reader can get into that corrupted state that requires the log in subsequent to the initial install. I know it's not just me, as I am the Troubleshooter and Problemsolver for two other Glos in my family and they've done the same thing.

[ewphoenix123]

Originally Posted by treadlightly

I would like to remove the requirement to be logged in to a Kobo Account. On the two occasions that my device spontaneously logged out of my account and the database became corrupted*, I had to open the Kobo Desktop to get past the log in phase, which then causes me to need to update the Desktop, and then forcefully updates the device, losing my patched version, etc. This part of the software is a nightmare for someone who leaves wireless off and only wants to update firmware when they so desire.

*This has only happened twice in three years of use, which is far less than either my KK or Sony T1 ever crashed and rebooted, so I feel particularly whiny complaining about it, but it was traumatic when it happened while I was away from a computer.

Just check this thread. I'm on my third Kobo device and don't even have a kobo account.

I don't use annotations so this major bug doesn't affect me, I guess I'll go with proper sorting functions in collections.

[DNSB]

Originally Posted by ewphoenix123

Just check this thread. I'm on my third Kobo device and don't even have a kobo account.

I don't use annotations so this major bug doesn't affect me, I guess I'll go with proper sorting functions in collections.

Whereas I don't use collections -- search by series, title or author keeps me happy.

And you are right in that you can modify the database to use a dummy user so a Kobo account is not necessary. OTOH, Kobo does no checking so you can use any dummy email account to create your Kobo account without needing to worry about which firmware revision you are using.

Regards,

David

[treadlightly]

Originally Posted by ewphoenix123

Just check this thread. I'm on my third Kobo device and don't even have a kobo account.

I don't use annotations so this major bug doesn't affect me, I guess I'll go with proper sorting functions in collections.

So when your database gets corrupted, do you have to open with sqlite and add the command again? Or is the user info permanently stored somewhere?

[Rand Brittain]

I wish they'd get Kobo Nickel working properly again, if only because it's a bit ridiculous that such a noticeable bug involving a font they went to the trouble of commissioning for themselves has gone unfixed for years.

[DNSB]

Originally Posted by treadlightly

So when your database gets corrupted, do you have to open with sqlite and add the command again? Or is the user info permanently stored somewhere?

You'd have to add it again. One friend of mine has the factory restore database with the modified user information saved. When he does a factory reset, he copies that database over to his Glo along with the firmware update he wants to use and the activation.xml file.

If he ran into issues away from his laptop, that could cause problems but separating him from his laptop is going to require a heavy crowbar.


Regards,

David

[eschwartz]

Originally Posted by JSWolf

With Amazon, you get collections deleted when they are created with the wifi off and then you turn on wifi to buy an eBook.

Um.... yeah... sure, whatever.

Never, ever, EVER seen this, despite an extensive usage of collections creation/deletion/modification while offline.

[treadlightly]

Originally Posted by DNSB

You'd have to add it again. One friend of mine has the factory restore database with the modified user information saved. When he does a factory reset, he copies that database over to his Glo along with the firmware update he wants to use and the activation.xml file.

If he ran into issues away from his laptop, that could cause problems but separating him from his laptop is going to require a heavy crowbar.


Regards,

David

And that's why I'm calling it a bug. If the database was corrupted while on a week long trip, my reader would be toast unless I had access to wi-fi or my computer. I would not be pleased.

[jackastor]

Well aside from what you guys have mentioned... I can think of nothing as there really has been nothing of any significance for me at least.. I tend not to push the features you all employ so that's the main reason. Not saying that there are no bugs, just have never Knowingly encountered them

regards

JAck

[Alastair_S]

The bookmark/annotation crashing bug is certainly the most disruptive bug so should be the one that is tackled first.