| 2014-11-20 14:38:31 |
xenocrates |
description |
Description: Ubuntu 14.04.1 LTS
Release: 14.04
nautilus-dropbox:
Installed: 1.6.1-1
Candidate: 1.6.1-1
Version table:
*** 1.6.1-1 0
500 http://dk.archive.ubuntu.com/ubuntu/ trusty/multiverse amd64 Packages
500 http://archive.ubuntu.com/ubuntu/ trusty/multiverse amd64 Packages
100 /var/lib/dpkg/status
I have a couple of shared folders and multiple machines with the same account logged on (Windows and Ubuntu) When using nautilus-dropbox, none of the changes made to local dropbox folders on my ubuntu machine are committed to the cloud service or to any other machine that shares either account or just has access to a shared folder. Changes made on other non-linux machines are committed and synced just fine across all machines. |
Description: Ubuntu 14.04.1 LTS
Release: 14.04
nautilus-dropbox:
Installed: 1.6.1-1
Candidate: 1.6.1-1
Version table:
*** 1.6.1-1 0
500 http://dk.archive.ubuntu.com/ubuntu/ trusty/multiverse amd64 Packages
500 http://archive.ubuntu.com/ubuntu/ trusty/multiverse amd64 Packages
100 /var/lib/dpkg/status
I have a couple of shared folders and multiple machines with the same account logged on (Windows and Ubuntu) When using nautilus-dropbox, none of the changes made to local dropbox folders on my ubuntu machine are committed to the cloud service or to any other machine that shares either account or just has access to a shared folder. Changes made on other non-linux machines are committed and synced just fine across all machines.
Restarting the dropbox service will force it to commit any local changes made since the service was last started, but any changes made after the service was started will not be committed before another restart.
Specifically, I have to quit dropbox and then run "dropbox start" or "dropbox start -i" to force the local changes to be committed to the cloud.
The bug persists after both reinstall and update to version 2.10.0.
dropbox:
Installed: 2.10.0
Candidate: 2.10.0
Version table:
*** 2.10.0 0
500 http://linux.dropbox.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status |
|
| 2014-11-20 14:40:27 |
xenocrates |
description |
Description: Ubuntu 14.04.1 LTS
Release: 14.04
nautilus-dropbox:
Installed: 1.6.1-1
Candidate: 1.6.1-1
Version table:
*** 1.6.1-1 0
500 http://dk.archive.ubuntu.com/ubuntu/ trusty/multiverse amd64 Packages
500 http://archive.ubuntu.com/ubuntu/ trusty/multiverse amd64 Packages
100 /var/lib/dpkg/status
I have a couple of shared folders and multiple machines with the same account logged on (Windows and Ubuntu) When using nautilus-dropbox, none of the changes made to local dropbox folders on my ubuntu machine are committed to the cloud service or to any other machine that shares either account or just has access to a shared folder. Changes made on other non-linux machines are committed and synced just fine across all machines.
Restarting the dropbox service will force it to commit any local changes made since the service was last started, but any changes made after the service was started will not be committed before another restart.
Specifically, I have to quit dropbox and then run "dropbox start" or "dropbox start -i" to force the local changes to be committed to the cloud.
The bug persists after both reinstall and update to version 2.10.0.
dropbox:
Installed: 2.10.0
Candidate: 2.10.0
Version table:
*** 2.10.0 0
500 http://linux.dropbox.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status |
Description: Ubuntu 14.04.1 LTS
Release: 14.04
nautilus-dropbox:
Installed: 1.6.1-1
Candidate: 1.6.1-1
Version table:
*** 1.6.1-1 0
500 http://dk.archive.ubuntu.com/ubuntu/ trusty/multiverse amd64 Packages
500 http://archive.ubuntu.com/ubuntu/ trusty/multiverse amd64 Packages
100 /var/lib/dpkg/status
I have a couple of shared folders and multiple machines with the same account logged on (Windows and Ubuntu) When using nautilus-dropbox, none of the changes made to local dropbox folders on my ubuntu machine are committed to the cloud service or to any other machine that shares either account or just has access to a shared folder, even though the dropbox service reports all files are up to date when prompted. Changes made on other non-linux machines are committed and synced just fine across all machines.
Restarting the dropbox service will force it to commit any local changes made since the service was last started, but any changes made after the service was started will not be committed before another restart.
Specifically, I have to quit dropbox and then run "dropbox start" or "dropbox start -i" to force the local changes to be committed to the cloud.
The bug persists after both reinstall and update to version 2.10.0.
dropbox:
Installed: 2.10.0
Candidate: 2.10.0
Version table:
*** 2.10.0 0
500 http://linux.dropbox.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status |
|
