On 09/27/2010 10:14 PM, Jim Nelson wrote: > First, Shotwell will never delete a master/original file without the user's > consent. Even then, Shotwell will move the master to the desktop trash
Well, $something deleted those files, but unfortunately at this point it's pretty much impossible to figure out what happened on this case. I have been way too busy to try to replicate this, so all I have is an experiment. Anyways, I imported photos via remote system (NFS-access), and this has been working just fine, shotwell said that it imported XX photos and everything seemed to go trough just fine. The result is however that the files are missing. > Still, Shotwell won't do this without asking the user first. So, unless > there's some other step here, I don't believe Shotwell has deleted the file. Just to be sure: 1. Open shotwell with laptop which has /media/Photo and ~/.shotwell on NFS -mount 2. Import photos from SD-card 3. Wait (forever) for import to complete 4. Machine was up and running for few hours after that for web browsing etc various tasks 5. Shutdown laptop 6. Open shotwell at workstation (NFS-server) ...? -> Missing files > directory on your server. Are you sharing that directory with multiple > instances of Shotwell? That could be a big problem, especially if those > multiple instances are running at the same time. The Shotwell private > directory wasn't designed for this kind of usage. I am sharing it with multiple "instances" to maintain database sync, but if I try to access database with multiple clients it'll fail due to locked database. So, it's impossible to start multiple instances at the same time, and even if this is potentially dangerous, it allows usage from multiple computers. However, there's a lots of issues with this, so usability is something between unusable and poor, specially over ethernet/wlan link. -- Take _______________________________________________ Shotwell mailing list [email protected] http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
