Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add location of Crash log on reMarkable to issue template #8902

Closed
wants to merge 1 commit into from

Conversation

qubist
Copy link
Contributor

@qubist qubist commented Mar 14, 2022

to issue template


This change is Reviewable

@pazos
Copy link
Member

pazos commented Mar 14, 2022

The rest of locations are relative paths from a USB mountpoint. They're intended for platforms where it is possible to export the koreader install path over USB.

Other platforms, like Cervantes or Remarkable, have limitations on this regard and I'm not sure if providing the full path to crash.log is enough for non-tech users to know how to do it.

Maybe we should create a wiki page with generic instructions to get crash.log (either from USB mountpoint or using SSH) and just point to that document on the template ¿?

@qubist
Copy link
Contributor Author

qubist commented Mar 14, 2022

Gotcha. Since the audience is non-tech users reporting a bug, making a wiki page on getting the crash log sounds right. I'm happy to contribute reMarkable instructions

@poire-z
Copy link
Contributor

poire-z commented Jun 25, 2022

Should we keep this PR open?

@Frenzie
Copy link
Member

Frenzie commented Jun 25, 2022

We could stick something like this on a wiki page perhaps? (Plus some stuff about those paths.)

https://freshrss.github.io/FreshRSS/en/contributing.html

@pazos
Copy link
Member

pazos commented Aug 3, 2022

We could stick something like this on a wiki page perhaps? (Plus some stuff about those paths.)

https://freshrss.github.io/FreshRSS/en/contributing.html

Created https://github.com/koreader/koreader/wiki/Report-a-bug as a proof of concept

@poire-z
Copy link
Contributor

poire-z commented Oct 25, 2022

As it seems to have turned into adding documentation to the Wiki, closing this.

@poire-z poire-z closed this Oct 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants