GNOME Bugzilla – Bug 541288
CRash on copying photos with the same name
Last modified: 2010-11-14 02:56:39 UTC
Steps to reproduce: Some cameras can put images to several folder naming files uniquely in the folder, not in all folders. 1. Make sure that card contains two folders and least two files having the same file name 2. Insert card into reader 3. Start copying files 4. "File already exists" exception appears Stack trace: Other information:
can you please run f-spot from terminal with --debug and post the stacktrace of the error? thanks
(In reply to comment #1) > can you please run f-spot from terminal with --debug and post the stacktrace of > the error? > thanks > It seems that I cannot reproduce the bug anymore. What I got is that now it creates separate folders for different dates and then copying goes smoothly. Actually problem is in 'f-spot-import' application, not in 'f-spot' itself. I don't know how to force it to copy all files to the same destination folder from different source folders.
Created attachment 113875 [details] error message that f-spot-import shows
(In reply to comment #1) > can you please run f-spot from terminal with --debug and post the stacktrace of > the error? > thanks > Please find attached screenshot. The problem appears only when inserting card into reader (not starting importing function from f-spot). Crash shows when starting copying photos to just created folder (not to existing one.
(In reply to comment #1) > can you please run f-spot from terminal with --debug and post the stacktrace of > the error? > thanks > More info: An unhandled exception was thrown: Object reference not set to an instance of an object at FileImportBackend.Prepare () [0x00000] at ImportCommand.DoImport (.ImportBackend imp) [0x00000] at ImportCommand.ImportFromPaths (.PhotoStore store, System.String[] paths, FSpot.Tag[] tags, Boolean copy) [0x00000] at ImportCommand.ImportFromPaths (.PhotoStore store, System.String[] paths, FSpot.Tag[] tags) [0x00000] at FSpot.CameraFileSelectionDialog.ImportFiles () [0x00000] at FSpot.CameraFileSelectionDialog.Run () [0x00000] at MainWindow.ImportCamera (System.String camera_device) [0x00000] at FSpot.Core+ImportCommand.Execute () [0x00000] at FSpot.Core.Import (System.String path) [0x00000] at FSpot.Driver.Main (System.String[] args) [0x00000] .NET Version: 2.0.50727.42 Assembly Version Information: libgphoto2-sharp (1.0.3058.27698) FolderExport (0.0.0.0) FlickrExport (0.0.0.0) PicasaWebExport (0.0.0.0) CDExport (0.0.0.0) SmugMugExport (0.0.0.0) GalleryExport (0.0.0.0) pango-sharp (2.12.0.0) FSpot.Query (0.0.0.0) SemWeb (0.7.1.0) glade-sharp (2.12.0.0) gtkhtml-sharp (3.16.0.0) System.Transactions (2.0.0.0) System.Data (2.0.0.0) Mono.Data.SqliteClient (2.0.0.0) System.Configuration (2.0.0.0) System.Xml (2.0.0.0) NDesk.DBus.Proxies (0.0.0.0) gconf-sharp (2.20.0.0) FSpot.Utils (0.0.0.0) gdk-sharp (2.12.0.0) gnome-vfs-sharp (2.20.0.0) Mono.Addins (0.3.0.0) NDesk.DBus.GLib (1.0.0.0) NDesk.DBus (1.0.0.0) System (2.0.0.0) Mono.Posix (2.0.0.0) Cms (0.0.0.0) FSpot.Core (0.0.0.0) atk-sharp (2.12.0.0) gtk-sharp (2.12.0.0) Mono.Addins.Setup (0.3.0.0) gnome-sharp (2.20.0.0) glib-sharp (2.12.0.0) f-spot (0.4.3.1) mscorlib (2.0.0.0) Platform Information: Linux 2.6.24-19-generic i686 unknown GNU/Linux Distribution Information: [/etc/debian_version] lenny/sid [/etc/lsb-release] DISTRIB_ID=Ubuntu DISTRIB_RELEASE=8.04 DISTRIB_CODENAME=hardy DISTRIB_DESCRIPTION="Ubuntu 8.04.1" Hope, this helps.
This bug was reported against a version which is not supported any more. Developers are no longer working on this version so there will not be any bug fixes for it. Can you please check again if the issue you reported here still happens in a recent version of GNOME and update this report by adding a comment and adjusting the 'Version' field? Again thank you for reporting this and sorry that it could not be fixed for the version you originally used here. Without feedback this report will be closed as INCOMPLETE after 6 weeks.
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!