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 335090 - Crashes when a new version is needed but the target directory isn't writable.
Crashes when a new version is needed but the target directory isn't writable.
Status: RESOLVED FIXED
Product: f-spot
Classification: Other
Component: Editing
0.1.10
Other All
: Normal critical
: ---
Assigned To: F-spot maintainers
F-spot maintainers
Depends on:
Blocks:
 
 
Reported: 2006-03-19 07:55 UTC by srn
Modified: 2006-05-24 18:54 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description srn 2006-03-19 07:55:48 UTC 
Steps to reproduce:
1. Select a photo whose directory isn't writable by the running user.
2. Click on convert to B&W (or edit with the gimp or anything else).
3. See crash


Stack trace:
None given :(

Other information:
f-spot correctly displays an error if you try to create the new version from the
File menu, which is how I eventually worked this out.
Comment 1 Bengt Thuree 2006-03-21 08:45:36 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 322541 ***
Comment 2 srn 2006-03-21 23:28:54 UTC 
No, it's not a duplicate.

In my case the directory on which the photodb lives is fine, but the directory into which the new photo is to be created wasn't writable.

So, it was creating the image, not updating the DB that caused the problem. I doubt it's the same bug.
Comment 3 Bengt Thuree 2006-03-21 23:45:51 UTC 
Sorry, Yes, you are right.

This was the one I was looking for. Bug #168088
Comment 4 Bengt Thuree 2006-05-17 15:29:45 UTC 
Another one

Bug #322805 regarding photo stored on removable media
Comment 5 Larry Ewing 2006-05-24 18:54:19 UTC 
This should be fixed now in cvs.  Please test and reopen if it isn't.