Quote:
Originally Posted by pazos
No bug is special (or all of them are  ). Some of them are tricky to reproduce.
A bug report requires a test case or, at least, the steps to reproduce it (see https://github.com/koreader/koreader.../bug_report.md).
Github is probably the best place to talk about bugs. The forum is *ok* as long as you fill the same info (device, program version ...)
So, the steps you'll need to do:
1. Reduce your paragraph to a test case or a number of steps to trigger the bug.
2. Check that you can reproduce the bug against the very last version of the program.
3. Attach a bug report (here or github) with all the info needed, including a debug log and your current settings.
Also, please don't mix bug reporting with guesses about how the program works or how the bug could be fixed. It usually doesn't help to understand the bug. Much better to stick with bug templates. |
Yes, you are right, correcting a bug is relaltively easy if you have these pieces of information. (I am actually a developer but unfortunately in very different environment, otherwise I would do my contribution to KOreader for sure, and would chase this bug by myself.) But as I mentioned, I do not have a definite step sequence to trigger the bug. It seems to be random, which rather means there are too much factors (or think of a bug which only happens when a limit in a code is exceeded, you cannot always say when it happens exactly, like when something would run out). You can easily do the same steps again and you will get stuck on a very different point, or it is even possible that it won't happen in a reading period, then more times in the next.
OK, so this bug will remain with us for a while.
Then please, answer a question. this kind of problem could be seen in the debug log? So if I keep using my dictionaries and when the "directory lookup canceled" will be stuck again, could it be something in the debug log which couls show what triggered the "directory lookup canceled" at the very beginnign of the search? (Because it is not something which ends up in an error message or a crash of the application.)