Thread: Firmware 4.31.19086
View Single Post
Old 04-06-2022, 09:58 AM   #658
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by John F View Post
While I can appreciate that it may be hard to reproduce consistently, 50% of the time sounds rather good for reproducing a bug.

And if there are user's who can reproduce it 100% of the time, Kobo could reach out to the users for help in reproducing it.

If they thought it was worth it.

Although being fed bug reports with a silver spoon is always nice.
That's 50% of my times. Not 50% of everyone's connections. And overall, it was less than 10% of the connections when there was an real problem. The dirty-bit wasn't really an issue. It was when either the database became corrupt, or the file-system was remounted read-only. So, a lot harder to track down. I was never able to reproduce it consistently. And I know Kobo were not either.
davidfor is offline   Reply With Quote