2020-06-22 06:31:54 +00:00
---
name: Bug report
2022-10-05 15:37:33 +00:00
about: Create a bug report to help us improve the application
2020-06-22 06:31:54 +00:00
title: ''
labels: ''
assignees: ''
---
2016-02-17 23:45:04 +00:00
* KOReader version:
* Device:
#### Issue
#### Steps to reproduce
2017-10-04 15:22:08 +00:00
##### `crash.log` (if applicable)
2022-10-05 15:37:33 +00:00
`crash.log` is a file that is automatically created when KOReader crashes. It can normally be found in the KOReader directory:
2017-10-04 15:22:08 +00:00
2019-12-21 19:51:31 +00:00
* `/mnt/private/koreader` for Cervantes
2017-10-04 15:22:08 +00:00
* `koreader/` directory for Kindle
* `.adds/koreader/` directory for Kobo
* `applications/koreader/` directory for Pocketbook
2022-10-05 15:37:33 +00:00
Android logs are kept in memory. Please go to [Menu] → Help → Bug Report to save these logs to a file.
2019-12-21 19:51:31 +00:00
2017-10-04 15:22:08 +00:00
Please try to include the relevant sections in your issue description.
2022-10-05 15:37:33 +00:00
You can upload the whole `crash.log` file (zipped if necessary) on GitHub by dragging and dropping it onto this textbox.
If your issue doesn't directly concern a Lua crash, we'll quite likely need you to reproduce the issue with *verbose* debug logging enabled before providing the logs to us.
To do so, from the file manager, go to [Tools] → More tools → Developer options, and tick both `Enable debug logging` and `Enable verbose debug logging` .
2022-10-27 20:22:44 +00:00
You'll need to restart KOReader after toggling these on.
2021-05-03 03:20:14 +00:00
If you instead opt to inline it, please do so behind a spoiler tag:
< details >
< summary > crash.log< / summary >
2021-05-22 23:20:13 +00:00
2021-05-03 03:20:14 +00:00
```
< Paste crash . log content here >
```
< / details >
