abort on read-only DB
Submitted by an unknown user
Link to original bug (#717649)
Description
---- Reported by shotwell-maint@gnome.bugs 2011-04-04 06:42:00 -0700 ----
Original Redmine bug id: 3462
Original URL: http://redmine.yorba.org/issues/3462
Searchable id: yorba-bug-3462
Original author: Jani Monoses
Original description:
I tried shotwell -d /path/to/.shotwell on an accidentally read-only FS mount.
- ERROR **: DatabaseTable.vala:53: execute_update_by_id: r8 attempt to write a readonly database
aborting…
I obviously don't expect Shotwell to be able to write to such a DB but I wonder if crashing is the only option – it helpfully brings up an error dialog already. Shotwell working in read/only browse mode and an error telling the user they probably run the db from a partition with wrong mount permissions would be nicer.
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:47:00 -0700 ----
History
Comment 1
Updated by Adam Dingle over 2 years ago
- Status changed from Open to 5
- Resolution set to duplicate
- % Done changed from 0 to 100
This is basically a duplicate of #2999 (closed).
Comment 2
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Duplicate
--- Bug imported by chaz@yorba.org 2013-11-25 21:53 UTC ---
This bug was previously known as bug 3462 at http://redmine.yorba.org/show_bug.cgi?id=3462
Unknown Component Using default product and component set in Parameters Unknown version " in product shotwell. Setting version to "!unspecified". Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Resolution: RESOLVED DUPLICATE