mergen3107

I have a suspicion that this is touch driver is acting up. I remembered another time when it froze like this last week: when I hit a link in the...

I suspect two-finger swipes are somehow tripping the touch input device. I see some messages in first log like “Restoring Kindle input” and “Inhibiting touch input” or something like that....

So, it turns out verbose log was 0 KB on Kindle as well. However, I got the same-looking freeze today during OTA update from 63 to 80 nightly. It downloaded...

> So, it turns out verbose log was 0 KB on Kindle as well. @NiLuJe First, this file I lost was a result of me renaming crash.log to that new...

So, to make it clear: crash.log itself was populated alright. Maybe then kterm messed up?

I did it via `cp file1 file2`

@NiLuJe For a start, here is a strace from `htop -p $(pidof reader.lua)` (then pressed `s`) when I exit normally, FWIW:  [TRACE_OK.txt](https://github.com/koreader/koreader/files/14483161/TRACE_OK.txt) Meanwhile I am trying to catch the...

I haven't been able to catch another freeze yet (moved to 2024.03 stable), but I got an idea. Can it be that it is not the `reader.lua` that freezes, but...

Is there a way I can send a command (say, "next page") via ssh in KOReader?

> If the input device is a virtual or uinput I think we figured out that these `/dev/input/eventX` are not virtual ones, right? Because virtual ones are in `/sys/class/input/`