The log message you're seeing is coming from Exiv2, meaning that it encountered some piece of metadata in a photo file that it couldn't parse. This is harmless and doesn't affect Shotwell's operation in any way.
Import can take a while with a large photo library. Shotwell shouldn't be completely unresponsive while it's importing. Can you tell me how many photos you're attempting to import? How many photos are in your library before you start the import? -- Jim On Wed, Nov 28, 2012 at 8:11 PM, Scott <[email protected]> wrote: Hi all - a progress update... I'm happy to say that it was importing while updating the library, but nothing was telling me what it was doing during this time. Apparently according to the logs it was skipping a directory with around 8k files in it which doesnt exist as far as i know. Does this line in the log mean anything to anyone? L 3327 2012-11-29 14:59:51 [CRT] Directory NikonPreview with 8224 entries considered invalid; not read. This particular one there is over 2000 log entries in 2 minutes. Could explain the high CPU usage... In the previous log file (while i was having the initial unresponsiveness of the first e-mail) it was this one: L 3433 2012-11-27 01:48:23 [CRT] Directory Panasonic with 14848 entries considered invalid; not read. I know my own library structure well and I certainly dont have any directories Panasonic or NikonPreview, although I have once owned a Panasonic and my current camera is a Nikon DSLR, so could this be to do with reading the EXIF or something? Either way, this tends to stall the import process for a long, long time. In the case of the auto-import it was well over an hour of inactivity, in the ase of this current import in progress now it is more like 5-10 minutes. Either way, it is a long time to wait for an unresponsive program to respond... Thanks for the initial help, Scott. On Tue 27 Nov 2012 01:01:43 EST, Scott wrote: > > Sorry, Rookie error. moved contents, but not directories themselves. > However the problem still stands. The log has been silent, as has CPU > usage and disk stall for a full 20 minutes, plus progress bar has > stalled, and absolutely no thumbnails are showing up now. As it is now > 1am here i am going to go to bed, and leave this running overnight > (again) to test the theory. I will post results in the morning (my time). > > Scott. > > On Tue 27 Nov 2012 00:19:24 EST, Scott wrote: >> >> >> Joe, >> >> Thanks for the reply, i had a look at the log. The last things i get >> before it starts chewing through CPU (jumps to about 60-90% of a Core2 >> 2.0Ghz from an avg of around 10%) are these lines: >> >> L 22473 2012-11-26 23:52:32 [WRN] DirectoryMonitor.vala:912: Skipping >> hidden file/directory >> /media/Buffalo_1TB/Shotwell_Library/2011/2011-07-10/.rawstudio >> L 22473 2012-11-26 23:52:40 [WRN] DirectoryMonitor.vala:912: Skipping >> hidden file/directory >> /media/Buffalo_1TB/Shotwell_Library/2011/2011-08-14/.rawstudio >> L 22473 2012-11-26 23:52:42 [WRN] DirectoryMonitor.vala:912: Skipping >> hidden file/directory >> /media/Buffalo_1TB/Shotwell_Library/2011/2011-06-18/.rawstudio >> L 22473 2012-11-26 23:52:47 [WRN] DirectoryMonitor.vala:912: Skipping >> hidden file/directory >> /media/Buffalo_1TB/Shotwell_Library/2011/2011-07-09/.rawstudio >> >> Reproducable every time, and the same four directories cause the >> problems... This also causes the process to need to be killed. These >> directories have been moved, and i am still getting the same results: >> >> L 22949 2012-11-27 00:12:52 [WRN] DirectoryMonitor.vala:912: Skipping >> hidden file/directory >> /media/Buffalo_1TB/Shotwell_Library/2011/2011-08-14/.rawstudio >> L 22949 2012-11-27 00:12:53 [WRN] DirectoryMonitor.vala:912: Skipping >> hidden file/directory >> /media/Buffalo_1TB/Shotwell_Library/2011/2011-06-18/.rawstudio >> L 22949 2012-11-27 00:12:57 [WRN] DirectoryMonitor.vala:912: Skipping >> hidden file/directory >> /media/Buffalo_1TB/Shotwell_Library/2011/2011-07-09/.rawstudio >> >> The CPU spikes, disk read stalls and process needs to be killed. I >> can watch this happening in real time with the log open and system >> load indicator showing CPU usage, disk write and memory at 500ms >> intervals. >> >> >> Scott. >> >> On Mon 26 Nov 2012 23:49:33 EST, Joseph Bylund wrote: >>> >>> >>> Scott, >>> >>> It's likely it's importing and the progress bar is hung (that's what I >>> saw). Can you do "export SHOTWELL_LOG=1" and watch >>> ~/.cache/shotwell/shotwell.log during import? If you're continually >>> seeing it talk about new photos then it's probably not hung (but the >>> bar may be). >>> >>> To share your backtrace you can upload to dropbox and get a link or >>> email shotwell@yorba. >>> >>> -Joe >>> >>> On 11/26/2012 06:50 AM, Scott wrote: >>>> >>>> >>>> Hi all, >>>> >>>> My 0.13.1 install from Yorba PPA running on Ubuntu 12.04LTS seems to >>>> hang on import of anything. What will happen is it will try to get >>>> the photo's off the SD Card, it will get some of the thumbnails, but >>>> will freeze half way through. The progress bar will stop moving and >>>> no more thumbnails will appear. Whats more, when i try to exit, the >>>> process will not actually quit, until i use either top or >>>> gnome-system-monitor to kill it manually. I have done a full >>>> backport, but as i have absolutely no idea what i am looking at, i >>>> cant tell if it is helpful or not. I also believe that this list >>>> doesnt allow attachments, is there somewhere i could e-mil them to? >>>> Is anyone else experiencing this? >>>> >>>> On a possibly unrelated note, the library is on an external USB, with >>>> the database in my home directory. The problem is that i >>>> accidentally opened shotwell the other day not knowing that the >>>> external hdd had not been mounted correctly, and as a result the >>>> entire library has now been shown to be missing, and no matter how >>>> long I wait, the library will not update itself. Is there a way to >>>> force shotwell to attempt to locate these? Or could there be in a >>>> future release? Normally, a workaround i find is to re-import (this >>>> does happen occasionally if i accidentally insert the SD card before >>>> the hdd), but with all imports hanging i cannot get my photos to >>>> refresh themselves... >>>> >>>> Thanks, >>>> Scott. >>>> >>>> _______________________________________________ >>>> Shotwell mailing list >>>> [email protected] >>>> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell >>> >>> >>> >> >> >> _______________________________________________ >> Shotwell mailing list >> [email protected] >> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell > > _______________________________________________ > Shotwell mailing list > [email protected] > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell _______________________________________________ Shotwell mailing list [email protected] http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell _______________________________________________ Shotwell mailing list [email protected] http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
