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.

Sign up for GitHub

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

Jump to bottom

Joplin Cloud: Joplin v3.2: Sync fails with "syncLockGone: User does not have write access to this share" #11594

Open
personalizedrefrigerator opened this issue Jan 6, 2025 · 2 comments
Open

Joplin Cloud: Joplin v3.2: Sync fails with "syncLockGone: User does not have write access to this share" #11594

personalizedrefrigerator opened this issue Jan 6, 2025 · 2 comments
Labels
high High priority issues sync sync related issue v3.2

Comments

@personalizedrefrigerator
Copy link
Collaborator

Operating system

Windows

Joplin version

v3.2.6

Original report

The profile started was that of a basic user who only has read-only rights to my shares.
He got the error message:

Remote-Elemente aktualisiert: 1.
Abgeschlossen: 2025-01-04 18:58 (1s)
Letzte Fehlermeldung: Sync target lock error: syncLockGone. Original error was: user does not have write access to this share
Anhänge abrufen: 3/5437

Joplin 3.2.6 (prod, win32)

Client-ID: xxx
Sync-Version: 3
Profil-Version: 47
Unterstützter Schlüsselbund: Ja

Revision: 40914be

Backup: 1.4.2
Conflict Resolution: 1.2.3
Diff view: 0.1.0
Freehand Drawing: 2.13.0
Joplin debug tool: 0.2.0

Originally posted by @CoffeeHT in #11457 (comment)

Analysis

  • The "syncLockGone" portion of this error seems to indicate that the relevant sync error reporting logic needs to be updated — sync locks should no longer be used. The error logger currently assumes that a sync lock should be present during sync.
  • Based on earlier reports, it's also likely that:
    1. E2EE is enabled for both clients.
    2. The share contains items with deleted_time ≠ 0.
@personalizedrefrigerator personalizedrefrigerator added sync sync related issue high High priority issues v3.2 labels Jan 6, 2025
@personalizedrefrigerator
Copy link
Collaborator Author

This might be a regression from v3.1.x — I'm tagging this with [v3.2].

@CoffeeHT
Copy link

CoffeeHT commented Jan 7, 2025 •
edited
Loading

E2EE is enabled for both clients.

Yes, that's true in my case.

personalizedrefrigerator added a commit to personalizedrefrigerator/joplin that referenced this issue Jan 8, 2025
@personalizedrefrigerator
Desktop: Fixes laurent22#11594: Fix syncLockGoneError on sync with ce…
67572e1 
…rtain share

config

Note: I was able to reproduce the original issue with the following
steps:
1. Create two users on the same team (team user A, team user B).
2. Enable end-to-end encryption for both users.
3. Share a notebook in read-only mode from user A to user B.
4. Accept the share and sync.
5. Share a notebook in writable mode from user B to user A.
6. Accept the share and sync.
7. As user A, make a change to a note from the notebook shared in step 5.
   - Specifically, mark a previously complete task as incomplete.
8. Sync.
9. Observe the "syncLockGone" error.

While this commit seems to fix the error, all changes made from user A
to the modifiable notebook from step 5 are marked as conflicts and
unapplied on sync. As such, I suspect that there is also a bug related
to local (app not server) handling of sync permissions in the 3.2 release.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
high High priority issues sync sync related issue v3.2
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@personalizedrefrigerator @CoffeeHT