After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 760868 - shotwell cannot write to vboxfs
shotwell cannot write to vboxfs
Status: RESOLVED FIXED
Product: shotwell
Classification: Other
Component: import
0.26.x
Other Linux
: Normal minor
: 0.28
Assigned To: Shotwell Maintainers
Shotwell Maintainers
Depends on: 656225
Blocks:
 
 
Reported: 2016-01-20 00:36 UTC by bugzilla.gnome.phil
Modified: 2017-06-03 11:32 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Use traditonal copy if target fs does not support GIO (4.62 KB, patch)
2017-05-25 20:46 UTC, Jens Georg
none Details | Review
Fixes issue (4.67 KB, patch)
2017-06-03 11:29 UTC, Jens Georg
committed Details | Review

Description bugzilla.gnome.phil 2016-01-20 00:36:21 UTC
I'm using shotwell as provided by ubuntu (shotwell -V: Shotwell 0.22.0; Version of deb file: 0.22.0-2ubuntu1).

When importing Pictures to a a folder on a vboxfs mounted folder, the import fails (no pictures are added).

Host system is Windows 10, file system is NTFS, client system is Ubuntu.

using SHOTWELL_LOG=1 shotwell and cat .cache/shotwell/shotwell.log shows:

[...]
L 8414 2016-01-20 01:14:15 [MSG] LibraryFiles.vala:86: There was a problem copying /home/<someusername>/Downloads/<somepicture>.jpg: Error renaming temporary file: Text file busy
L 8414 2016-01-20 01:14:15 [DBG] BatchImport.vala:1967: Importing /home/<someusername>/Pictures/<somedate>/<somepicture>.jpg
L 8414 2016-01-20 01:14:15 [WRN] Photo.vala:1182: Unable to interrogate photo file /home/<someusername>/Pictures/<somedate>/<somepicture>.jpg: Unexpected early end-of-stream
L 8414 2016-01-20 01:14:15 [DBG] BatchImport.vala:1987: Deleting failed imported copy /home/<someusername>/Pictures/<somedate>/<somepicture>.jpg
[...]

likely related bug:

https://bugzilla.gnome.org/show_bug.cgi?id=656225

The proposed glib patch was not included upstream, for geany there is a workaround "Edit > Prefs > Various > use_atomic_file_saving: checked".

As glib seemingly wont fix this soon, this might be an easy fix for shotwell as well.

Thanks in advance.
Comment 1 Jens Georg 2017-05-25 20:46:31 UTC
Created attachment 352591 [details] [review]
Use traditonal copy if target fs does not support GIO
Comment 2 Jens Georg 2017-06-03 11:29:13 UTC
Created attachment 353109 [details] [review]
Fixes issue