mirror of
https://github.com/koreader/koreader
synced 2024-11-10 01:10:34 +00:00
e98bf342e7
Otherwise, stuff that inherits logger functions on require don't get logged (i.e., framebuffer), and the debug guards aren't hooked.
42 lines
1.3 KiB
Markdown
42 lines
1.3 KiB
Markdown
---
|
|
name: Bug report
|
|
about: Create a bug report to help us improve the application
|
|
title: ''
|
|
labels: ''
|
|
assignees: ''
|
|
|
|
---
|
|
|
|
* KOReader version:
|
|
* Device:
|
|
|
|
#### Issue
|
|
|
|
#### Steps to reproduce
|
|
|
|
##### `crash.log` (if applicable)
|
|
`crash.log` is a file that is automatically created when KOReader crashes. It can normally be found in the KOReader directory:
|
|
|
|
* `/mnt/private/koreader` for Cervantes
|
|
* `koreader/` directory for Kindle
|
|
* `.adds/koreader/` directory for Kobo
|
|
* `applications/koreader/` directory for Pocketbook
|
|
|
|
Android logs are kept in memory. Please go to [Menu] → Help → Bug Report to save these logs to a file.
|
|
|
|
Please try to include the relevant sections in your issue description.
|
|
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`.
|
|
You'll need to restart KOReader after toggling these on.
|
|
|
|
If you instead opt to inline it, please do so behind a spoiler tag:
|
|
<details>
|
|
<summary>crash.log</summary>
|
|
|
|
```
|
|
<Paste crash.log content here>
|
|
```
|
|
</details>
|