Created attachment 274553 [details] emerge --info f-spot is unable to export files to FTP shares mounted with gvfs. f-spot is able export to local folders, so I'm not sure whether this is an f-spot issue or a gvfs issue. The FTP directory has permissions set to 777, so permissions should not be an issue. I am also able to copy local files to the FTP directory with Nautilus, so permissions again should not be the issue. This error occurs regardless of export method (Standalone gallery, files only, gallery using "Original" Step 1: Select images in f-spot to export Step 2: File>Export>Export to Folder Step 3: Select directory within (already connected) FTP location* Step 4: Click 'Export' Expected result: Photos and any supporting files (e.g. html files for a gallery) are created within the FTP location Actual result: f-spot crashes before any files are created. f-spot produces the following error in the terminal: ############################################# [Info 21:43:43.071] Initializing Mono.Addins (f-spot:4992): GdkPixbuf-WARNING **: GdkPixbufLoader finalized without calling gdk_pixbuf_loader_close() - this is not allowed. You must explicitly end the data stream to the loader before dropping the last reference. (f-spot:4992): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated [Error 21:44:32.928] System.ArgumentNullException: Argument cannot be null. Parameter name: path1 at System.IO.Path.Combine (System.String path1, System.String path2) [0x00000] in <filename unknown>:0 at FSpot.Exporters.Folder.FolderExport.Upload () [0x00000] in <filename unknown>:0 Unhandled Exception: System.IO.DirectoryNotFoundException: Directory '/tmp/f-spot-original-634418702555777450' not found. at System.IO.Directory.ValidateDirectoryListing (System.String path, System.String searchPattern, System.Boolean& stop) [0x00000] in <filename unknown>:0 at System.IO.Directory.GetFileSystemEntries (System.String path, System.String searchPattern, FileAttributes mask, FileAttributes attrs) [0x00000] in <filename unknown>:0 at System.IO.Directory.GetDirectories (System.String path, System.String searchPattern) [0x00000] in <filename unknown>:0 at System.IO.Directory.GetDirectories (System.String path) [0x00000] in <filename unknown>:0 at System.IO.Directory.RecursiveDelete (System.String path) [0x00000] in <filename unknown>:0 at System.IO.Directory.Delete (System.String path, Boolean recursive) [0x00000] in <filename unknown>:0 at FSpot.Exporters.Folder.FolderExport.Upload () [0x00000] in <filename unknown>:0 at System.Threading.Thread.StartUnsafe () [0x00000] in <filename unknown>:0 #############################################
How about collecting 'strace' dumps to get a little more information on where the difference comes up. Here's a strategy to try to avoid dumps being too huge: 1. start up f-spot, and get to where you are just about to export the files to a local folder 2. attach strace to the running f-spot processes strace -f -p $PARENT_PID -s100 -o /tmp/TRACE.f-spot.works 3. export to a local folder 4. stop the strace 5. prepare to export the files to ftp folder 6. attach strace again strace -f -p $PARENT_PID -s100 -o /tmp/TRACE.f-spot.works 7. attempt export to ftp folder 8. attach both dump files to bug
Ugh I meant the second strace output file to be /tmp/TRACE.f-spot.crashes
Also, what is mounted where, exactly?
