Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Piotrek Marciniak
    @ptrm
    while ["screen_dpi"] = 200 is still there in the settings.reader.lua
    I mean, the merge happened yesterday ;)
    Piotrek Marciniak
    @ptrm
    Reverting this line manually seems to help only with displaying the checkbox properly beside custom 200 dpi setting, the actual screen dpi remains bigger, though
    Piotrek Marciniak
    @ptrm
    most of the above rant is in koreader/koreader#4726 ;)
    Frans de Jonge
    @Frenzie
    @NiLuJe Your 8-bit patch is causing some incorrect rotation on exit.
    Also I saw fbink painting on the screen in landscape.
    although that was on startup
    Anyway, I think there should be enough baggage in the history to solve the problem with relative ease. :-)
    prog20901
    @prog20901
    thank you @pazos
    Piotrek Marciniak
    @ptrm
    Today I got my Clara HD hanging up and becoming irresponsive (to touches and lock button as well, shutting down with long press works). Any clues what could be the reason from here: https://gist.github.com/ptrm/771eb58722b754d43f9638ea83d7ec9a ? It started getting extremely slow when extracting today's update at around 67% (-173), however after unzipping -161 back, it still hangs. Nickel, on the other hand, works fine. KOReader freezes withing ~2 minutes. And Forma works smoothly after installing today's nightly :o
    Frans de Jonge
    @Frenzie
    Is the problem localized to a specific file or user style?
    Piotrek Marciniak
    @ptrm
    Not really. Now I tried renaming the custom font dirs and koreader/styletweaks to mass disable them, and it hung starting after a reboot on a different epub, the whole of which I was reading thruoghout last week. My question would be now if I can make the logs more verbose than the -d flag and whether it would make any sense ;)
    *it hung several seconds after starting
    Piotrek Marciniak
    @ptrm
    unzipping -130 brought things back to normal. But since the log didn't output anything obviously crashing/stalling, I would still be grateful for hints :)
    Frans de Jonge
    @Frenzie

    Given the dates you mention (-130 is koreader/koreader@93422d0), the most likely culprit would be koreader/koreader#4580 or possibly something related to koreader/koreader#4637

    Also quite odd is that (naturally) @houqp, @poire-z, myself, and by now presumably plenty of other people already tested those changes.

    And you say today's nightly works? That doesn't really make any sense.
    Unless it's somehow related to that custom screen DPI thing.
    Piotrek Marciniak
    @ptrm
    @Frenzie No, I say that -130 made Clara HD stable again, but on Forma today's nightly works fine :)
    The stall was only ClaraHD-related ;)
    And I myself don't rule out some hardware issues or anything like that, but I was curious if there is another way to catch the last operations before stalling
    Frans de Jonge
    @Frenzie

    You could make the logs more verbose for crengine specifically by recompiling it with DEBUG_CRENGINE (see https://github.com/koreader/koreader-base/blob/f549ca8922f92a70986082a1d2023de3e7cd9a68/cre.cpp#L2823-L2826) but other than that not really. It is however quite easy to do some gdb remote debugging, to the extent that you know gdb anyway.

    https://github.com/koreader/koreader-base/wiki/Remote-debugging-with-gdbserver

    Is the program being killed by the kernel or something?
    Piotrek Marciniak
    @ptrm
    And regarding Clara HD: yesterday it worked fine with -161, today I upgraded to -173 via OTA, started stalling, unzipped -161, still stalling, and then -150 stopped stalling ;) That made things inconsequential a bit to me ;)
    Frans de Jonge
    @Frenzie
    Enough disk space?
    Piotrek Marciniak
    @ptrm
    yeah, /dev/root 75% occupied, and over 5G on /mnt/onboard
    *over 5g free
    Frans de Jonge
    @Frenzie
    Oh nice, my H2O only has 4 GB total. :)
    Piotrek Marciniak
    @ptrm
    But yours has a SD socket ;)
    Frans de Jonge
    @Frenzie
    Oh, it's one of those. :-P
    Piotrek Marciniak
    @ptrm
    yeah, not waterproof, but no SD socket ;)
    which leads me to a thought I used my Clara in a heavy drizzle yesterday ;>
    Frans de Jonge
    @Frenzie
    Could be related. yeah. Your description definitely points at something hardware-related anyway. :-/ (E.g., the OTA update is Zsync + Tar, KOReader isn't really involved anyway.)
    Piotrek Marciniak
    @ptrm
    (yeah, I mentioned that it started with OTA because it never unpacked that slow)
    Piotrek Marciniak
    @ptrm
    oh, and the 8bit space enforcing can be disabled, that's a start. I still hope it's something about the software or that the device simply needed a long time to dry off
    NiLuJe
    @NiLuJe
    @ptrm: Might be helpful to have a shell open on the Clara, and check if that isn't the blitting code being blacklisted. (Basically, luajit will spike to 100% CPU, but your shell should still be responsive (-ish)).
    NiLuJe
    @NiLuJe
    @ptrm: Also, what -150? I see a -130 and a -155 ;).
    NiLuJe
    @NiLuJe
    But, yeah, if it started getting sluggish during an OTA, that's somewhat suspicious, as KOReader indeed does nothing at that time ;).
    Frans de Jonge
    @Frenzie
    @NiLuJe I thought you also had an H2O? The issue I'm talking about is (afaik) exclusive to the Kobo Aura HD (dragon) and Kobo Aura H2O (dahlia).
    Anyway, I'll get you a log, hang on.
    Umm, now it seems to not be misbehaving. Let me save this log and restart. :-D
    Frans de Jonge
    @Frenzie
    @NiLuJe Alright, we're back with KSM upside down. Log incoming.
    or it would be if I hadn't forgotten to turn on SSH and now the screen's upside down >_>
    It could be some kind of bug in KSM though.
    Frans de Jonge
    @Frenzie
    @NiLuJe Anyway, let me know if you need any debugging output from fbink or something.