---- Reported by adam@yorba.org 2011-01-26 10:54:00 -0800 ----

Original Redmine bug id: 3130
Original URL: http://redmine.yorba.org/issues/3130
Searchable id: yorba-bug-3130
Original author: Adam Dingle
Original description:

The following behavior occurs both in 0.8.1 and in trunk:

Make sure that auto-import is disabled.

Start Shotwell with an empty library.

Import a photo in place (without copying) which is not in the library
directory.

Close Shotwell.

In Nautilus, move the photo into the library directory.

Start Shotwell.

Select the photo and view its extended information.

Shotwell has found the photo in the library directory.

Instead, I expected that the photo would now be missing. It seems that
Shotwell is scanning the library directory and finding missing files, even
when auto-import is disabled. This was surprising to me. Jim, let's discuss
more when you're around.

Related issues:
related to shotwell - 5972: Shotwell is unresponsive with big photo
library (Open)
related to shotwell - Feature #2790: monitor outside library directory (Open)
duplicated by shotwell - 3568: Updating library on every start (Duplicate)
duplicated by shotwell - 6157: Updating library take long time (Duplicate)
duplicated by shotwell - Feature #4754: optionally skip startup scan (Duplicate)



---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-16 14:33:00 -0700 ----

### History

####

#1

Updated by Jim Nelson almost 3 years ago

This behavior is inherited from 0.7, where the startup scan would detect if
any photo (in the library directory or not) was online/offline and mark it as
such.

As part of the startup scan's logic in 0.8 I added checking if the photo file
has moved. (Essentially, the startup scan mirrors the functionality of the
runtime monitoring code, which includes detecting moves.) Because the startup
scan reads all files in the library directory, it can detect if a photo
outside the directory has moved into it, but not vice-versa.

Startup scan is a necessary component of runtime monitoring, which is always
on. Auto-importing is a separate feature. What occurred in the steps above is
not considered auto-import (by the code).

I'll leave this ticket open, in case this is not considered desirable
behavior.

####

#2

Updated by Adam Dingle over 2 years ago

  * **Target version** deleted (<strike>_0.9_</strike>)

####

#3

Updated by Jim Nelson 11 months ago

  * **Description** updated (diff)
  * **Target version** set to _0.14.0_

####

#4

Updated by Jim Nelson 11 months ago

  * **Category** set to _library-mode_

####

#5

Updated by Jim Nelson 11 months ago

  * **Subject** changed from _Shotwell scans library directory even when auto-import disabled_ to _Disable runtime monitoring (don't scan library directory at startup)_

I've updated the ticket title to reflect what is really being asked for.

####

#6

Updated by Jim Nelson 11 months ago

  * **Tracker** changed from _Bug_ to _Feature_

####

#7

Updated by Jim Nelson 11 months ago

I should also note for anyone who wants this now: Shotwell has a --no-runtime-
monitoring command-line option which will prevent the startup scan. This
ticket is for adding this to the Preferences dialog (probably right above the
"Watch library directory for new files" checkbox).

####

#8

Updated by rv - 10 months ago

Maybe you will also need a button like "Synchronize now".

Does the "no-runtime-monitoring" also means "no watch library directory for
new files" or is it completly independant?

####

#9

Updated by Jim Nelson 10 months ago

Runtime monitoring is independent of watching the library for new files. The
first watches for changes to files in Shotwell's library (modified, renamed,
moved, or deleted). The second is commonly known as auto-import.

####

#10

Updated by Jim Nelson 10 months ago

  * **Target version** changed from _0.14.0_ to _0.15.0_

####

#11

Updated by Jim Nelson 6 months ago

  * **Target version** deleted (<strike>_0.15.0_</strike>)



--- Bug imported by chaz@yorba.org 2013-11-25 21:49 UTC  ---

This bug was previously known as _bug_ 3130 at http://redmine.yorba.org/show_bug.cgi?id=3130

Unknown version " in product shotwell. 
   Setting version to "!unspecified".
Unknown milestone "unknown in product shotwell. 
   Setting to default milestone for this product, "---".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Resolution set on an open status.
   Dropping resolution