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

Notification: 'Read empty file' and crashes #68

Open
glocalglocal opened this issue Oct 19, 2021 · 3 comments
Open

Notification: 'Read empty file' and crashes #68

glocalglocal opened this issue Oct 19, 2021 · 3 comments

Comments

@glocalglocal
Copy link

Every few minutes DecSyncCC generates this notification:
Read empty file: org.decsync.library.RealFileSys@b...

The message is truncated and I can't read the rest.

This has been happening for weeks. 2-3 days ago DecSyncCC also started stopping immediately every time I tap on its icon, but it seems to do the job in the background, updating the calendar as it did before (ie not very well, with lots of triplicates, ghost events of deleted entries etc (see my earlier issues that may help explain the notification and clashes).

I updated to v2.0.1 earlier today but there was no improvement on any front.

(Android 7)

@jluttine
Copy link

jluttine commented Nov 3, 2021

I have the same issue. DecSyncCC 2.1.0 installed from F-Droid. I'm running LineageOS 18.1 (Android 11). Let me know if I can help with debugging somehow.

The notification issue started with 2.1.0 (not earlier), but the app has been unable to open for a longer time - so probably the two issues are separate. Here's my older issue about the crashing: #59

39aldo39 added a commit to 39aldo39/libdecsync that referenced this issue Nov 5, 2021
39aldo39 added a commit to 39aldo39/libdecsync that referenced this issue Nov 5, 2021
@39aldo39
Copy link
Owner

39aldo39 commented Nov 5, 2021

It means that there is an empty file, which should never occur (it should delete it instead), but apparently it can happen... If you are on LInux on the desktop you can easily find the empty file by executing find .local/share/decsync -empty. (The notification should give the path of the file, but there was a bug in it.) If it is a .decsync-sequence file you can safely remove it. The next update will ignore the empty files, meaning it won't crash anymore.

@glocalglocal
Copy link
Author

I searched through my Windows 10 files and found an empty info. I deleted it and DecSyncCC stopped crashing. Not sure if this is related but I recently updated radicale_storage_decsync as well and suddenly most of the many problems I had disappeared (several missing calendars appeared, duplicate/triplicate etc events are gone, syncing from the mobile to the PC works). Only thing remaining is the many syncthing conflicts (20-30 conflict files per day). The big test will be when I add another 2 devices to the current 3 devices (incl a Raspberry Pi). Many thanks.

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