Nautilus Sync daemon for network folders
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntuone-client (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: nautilus
I have a network consisting of desktop computers and laptops. Laptops are not always online or they are used by the other users on the go. In most networks every user in the network is allowed to store data in separate network folders on every existing laptop (peer-to-
If user's B laptop is disconnected to the network user A gets now the useless message: „network connection can't be setup. Mounting impossible“ (or something like that). Consequently user A has to check over and over again when user's B laptop is online and has then to repeat after positive feedback the drag-and-drap file transfer. That is inconvenient and wastes lots of working time.
Because of that mess, Ubuntu should have a sync daemon in nautilus, too, comparable to the sync daemon for the Ubuntu cloud. Every time user A starts to copy a file to user's B laptop and when this laptop is offline, nautilus should offer:
„Network folder is unavailable. Synchronization will start immediately after network folder's reconnection to the network.“ [Yes] – [No]
A successful date transfer with the daemon should be reported by the Ubuntu indicator system: "Data transfer of file ... to network folder ... is now completed."
ProblemType: Bug
Architecture: amd64
Date: Tue Oct 13 10:30:53 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.28.0-0ubuntu5
ProcEnviron:
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: nautilus
Uname: Linux 2.6.31-13-generic x86_64
summary: |
- Nautilus Sync daemon for network laptops by network connections. + Nautilus Sync daemon for network folders |
affects: | nautilus (Ubuntu) → ubuntuone-client (Ubuntu) |
Thank you for taking the time to submit this bug report. We appreciate the interest in Ubuntu One and think syncing across the local network makes a lot of sense. We have this on our roadmap. I'm going to mark this bug as a duplicate of an earlier one so it is tracked properly. Thank you, Joshua