syncdaemon does not clear up stale lock files
Bug #377026 reported by
Nick Lally
This bug report is a duplicate of:
Bug #369267: syncdaemon does not get started by client-applet after relogging (stalled lock file).
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu One Client |
New
|
Undecided
|
Unassigned | ||
Bug Description
I just encountered a situation where the ubuntu one client was running, but the syncdaemon was not, so it was silently failing to connect/sync (I suggest it should not do so silently).
The cause was that the syncdaemon was refusing to start because there was a .lock file in ~/cache/
The daemon should really check to see if there is a process running when it finds a .lock file, and if not, clear up after the previous failure.
| tags: | added: chicharra |
Revision history for this message
| Guillermo Gonzalez (verterok) wrote | #1 |
To post a comment you must log in.
Hi Nick,
Thanks for reporting this issue.
This issue was fixed a while ago, and now dbus is used to handle this.
Please update the client to the latest version.
Regards,