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

Kicking out of the book after turning on... #172

Open
br45rm opened this issue Feb 9, 2024 · 12 comments
Open

Kicking out of the book after turning on... #172

br45rm opened this issue Feb 9, 2024 · 12 comments

Comments

@br45rm
Copy link

br45rm commented Feb 9, 2024

After a successful installation of KoboCloud, anytime I turn on my kobo libra h2o after about 5 seconds I get kicked out from the book to the main screen. If I open the book again I can continue reading until the next turning-off/turning-on cycle. Uninstalling the KoboCloud solves the problem.

Reader: Kobo Libra H2O
Latest release from Sep 9, 2023 installed on MacOS Sonoma. No issues during the installation.

Things I've tried so far:

  • delete all files from google drive -> didn't help
  • uninstall -> helped
  • fresh installation of the same version from Sep 9, 2023 -> didn't help
@ospring
Copy link
Contributor

ospring commented Mar 25, 2024

I am experiencing the same problem with my Libra 2 and a Google drive folder sync.

@ospring
Copy link
Contributor

ospring commented Mar 27, 2024

Also I have noticed that the device sometimes wakeups from sleep and never go back to sleep alone… however I have to do some more tests to understand the circonstances and if it is related to kobocloud install. I wonder if the recent use of NickelDbus could be related to the problem….

@ospring
Copy link
Contributor

ospring commented Apr 6, 2024

@br45rm can you try the latest release with the fix #177 ? I solved my issue making this fix.

@klement
Copy link

klement commented Dec 8, 2024

I am experiencing this same issue, which is compounded by KoboCloud ignoring sync settings - I've turned off automatic syncing, but it still seems to run - and close my currently opened book. My situation is extremely annoying, as I'm reading a material where I have to hop back and forth and closing the book makes the reader forget one of the places, requiring me to go into bookmarks (and keep a bookmark all the time).

I've installed KoboCloud last month, so I'm presuming #177 is not a (complete) fix.

@ospring
Copy link
Contributor

ospring commented Dec 8, 2024

What does the log file says (get.log in /.add/kobocloud ) ?
"No Library Change. skipping rescan" ?
"Library has changed, rescan needed" ?

@klement
Copy link

klement commented Dec 9, 2024

I dug a bit around get.log and I saw that it was unsuccessfully trying to sync some files with UTF-8 characters in them, which were in DropBox, but not on reader. So I used detox to transliterate to ASCII and now I see the files on the reader, but it still says

Library has changed, rescan needed
timeout expired after 3000 milliseconds
2024-12-09_09:48:57 done

at the end of the file. I've no idea what timeout is mentioned.

@ospring
Copy link
Contributor

ospring commented Dec 9, 2024

Can you find in the log the 2 folder listings : the one before the sync and the one after ? Can you find the difference that leaded to the « library has changed » decision ?

@klement
Copy link

klement commented Dec 9, 2024

Here's the redacted get.log. I've replaced names of ebooks and the dropbox identifiers.

~ % cat get.log
2024-12-09_18:43:20 waiting for internet connection
NickelDBus found
/mnt/onboard/.add/kobocloud/Library:
total 240
-rwxr-xr-x    1 0        0            93955 2024-12-09 07:48:17 +0100 Book1.epub
-rwxr-xr-x    1 0        0            61809 2024-12-09 07:48:14 +0100 Book2.epub
-rwxr-xr-x    1 0        0            54136 2024-12-09 07:48:16 +0100 Book3.epub
-rwxr-xr-x    1 0        0               50 2024-12-09 18:43:20 +0100 filesList.log
Reading # Add your URLs to this file
Comment found
Reading # Remove the # from the following line to uninstall KoboCloud
Comment found
Reading #UNINSTALL
Comment found
Reading # Remove the # from the following line to delete files when they are no longer on the remote server
Comment found
Reading DropboxApp:XXXXXXXXXXXXXXX:XXXXX-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-XXXXXX-XXXXXXX
Getting DropboxApp:XXXXXXXXXXXXXXX:XXXXX-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-XXXXXX-XXXXXXX
outFileName: Book2.epub
outFileSize: 61809
existingFileSize: 61809
File Book2.epub is up to date
Appended /mnt/onboard/.add/kobocloud/Library/Book2.epub to filesList
outFileName: Book3.epub
outFileSize: 54136
existingFileSize: 54136
File Book3.epub is up to date
Appended /mnt/onboard/.add/kobocloud/Library/Book3.epub to filesList
outFileName: Book1.epub
outFileSize: 93955
existingFileSize: 93955
File Book1.epub is up to date
Appended /mnt/onboard/.add/kobocloud/Library/Book1.epub to filesList
Reading REMOVE_DELETED
Will match remote
Matching remote server
Book1.epub found
Book2.epub found
Book3.epub found
filesList.log found
/mnt/onboard/.add/kobocloud/Library:
total 240
-rwxr-xr-x    1 0        0            93955 2024-12-09 07:48:17 +0100 Book1.epub
-rwxr-xr-x    1 0        0            61809 2024-12-09 07:48:14 +0100 Book2.epub
-rwxr-xr-x    1 0        0            54136 2024-12-09 07:48:16 +0100 Book3.epub
-rwxr-xr-x    1 0        0              303 2024-12-09 18:43:28 +0100 filesList.log
Library has changed, rescan needed
timeout expired after 3000 milliseconds
2024-12-09_18:43:35 done

@ospring
Copy link
Contributor

ospring commented Dec 9, 2024 via email

@klement
Copy link

klement commented Dec 10, 2024

Your assumption is true on my reader. With REMOVE_DELETED commented out, I'm no longer being "kicked out" of book on waking up the reader - I'm assuming it means the rescan is not being triggered.

@ospring
Copy link
Contributor

ospring commented Dec 10, 2024 via email

@ospring
Copy link
Contributor

ospring commented Dec 11, 2024

@klement try the latest version. It includes the fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants