Quote:
Originally Posted by ownedbycats
I believe that's what davidfor said in another thread, yes.
Even if you can perfectly reproduce the conditions (specific hardware of the computer the device is being ejected from, the exact books on the device, the exact books being imported to the device, the current phase of the moon, etc etc), if that only triggers the problem 50% of the time, it's very hard to test for.
|
Or looking at the glass half full.
Quote:
Originally Posted by Lusephur
Sure they can come round to me and I'll physically show them the issue happening again and again and again. Absolutely no worries it being 100% repeatable.
|
Quote:
Originally Posted by meeera
I'm gonna guess that it would be the same here. Had three corrupted database incidents just using my usual workflow (yes I always eject properly etc), was thinking something was badly wrong with my new Libra 2, then read the threads here and realised what was wrong.
Rolled back, and zero problems ever since.
|
If Kobo wanted to chase this down, they should be able to. If Kobo can't reproduce it themselves, contact some customers and do some builds with more debug information.
And I don't want to hear about adding debugging information may make the problem go away.
