Open luixxiul opened 3 months ago
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.
After updating to the latest version, the notes and notebooks started to be displayed, but Error: Error: Error: ENOTSUP: operation not supported on socket, read. Path: /media/sf_Syncthing/Notes/info.json. Path: /media/sf_Syncthing/Notes/info.json
keeps to be displayed on the UI (left-bottom, where the sync status is rendered).
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.
This does not seem to have been fixed yet.
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.
This does not seem to have been fixed yet.
Operating system
Linux
Joplin version
3.0.13
Desktop version info
Joplin 3.0.13 (prod, linux)
Client ID: 9c3199ec203e4f018c9bff8ffe4b5288 Sync Version: 3 Profile Version: 47 Keychain Supported: No
Revision: 599cf5b
Backup: 1.4.1
Current behaviour
Notes are not displayed due to the error below:Expected behaviour
The error should not happen and the notes should be displayed
Logs
No response