Date-modified images are not refiled in correct year etc

[RayArdia]

An image is scanned and then imported into Shotwell. Date/Time it is filed under No Event.
When, later. the image is given a date and Time, instead of refiling to its correct Year, Month and Day the image simply remains in No Events.
I understand that Shotwell is to be modified/upgraded to allow this 'refiling to occur, but in the meantime can you help me with a work-around?
Ray Allinson

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: shotwell 0.11.4-0ubuntu1 [modified: usr/share/glib-2.0/schemas/gschemas.compiled]
ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
Uname: Linux 3.0.0-13-generic i686
ApportVersion: 1.23-0ubuntu4
Architecture: i386
Date: Sat Nov 26 17:34:55 2011
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: shotwell
UpgradeStatus: No upgrade log present (probably fresh install)

[RayArdia (theallinsons)]

After the addition (via exiftool) of DateTimeOriginal data, Images are often filed in incorrect events, sometimes in No Event.

[Clint Rogers (clinton-yorba)]

Hi, and thank you for reporting this.

I've been following the original thread on the mailing list as well, and, unfortunately, short of adding time/date data via an EXIF-writing tool, which you've already tried, there isn't a workaround that I'm aware of.

When you say you're having images get filed into incorrect events, what do you mean? Are the events that are chosen not matching the dates you're setting via exiftool? If so, this is a bug and we need to correct it.

If you feel comfortable doing so, would you mind posting one or two of the affected images so we can reproduce the issue here? (If you'd rather not share them, please feel free to email them directly to <email address hidden> and I will treat them as confidential.)

[Adam Dingle (adam-yorba)]

Also: this bug has been reported upstream at http://redmine.yorba.org/issues/1940, and has already been reported in Launchpad as bug #696138. If you're looking for a workaround, then instead of filing a duplicate bug report it would be better to ask for help on the mailing list and/or post a comment to the existing bug entry.

So this bug was originally a duplicate, but we can keep it open while we investigate the behavior you described in comment #2.