I don't mean to suggest that's what caused your problem in particular,
only that the reason Shotwell doesn't support sharing the database among
multiple users can lead to a lot of problems, both data corruption and
database incoherence.
--
You received this bug notification because you are a memb
Weird... During the NTFS-over-NFS segfault there was only single
instance of shotwell running. Could be there are multiple threads that
interact with the database?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shotwell in Ubuntu.
htt
Remember, Shotwell doesn't do the file locking, SQLite does. I don't
know how it handles the problem if file locking fails, or even if the
file sharing stack is reporting an error.
More importantly, Shotwell is not designed to work this way. Shotwell
keeps a lot of the database in memory for spe
It would be nice if shotwell check whether underlying filesystem
supports necessary locking semantics and show informative error message
if it is not the case.
Doesn't explicit file lock operation returns error if file locking
failed??
--
You received this bug notification because you are a memb
** Changed in: shotwell (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/bugs/1127521
Title:
shotwell crashes after a while of "Updating library...
This bug is about inability of shotwell to have its database on a network drive
(NTFS-over-NFS).
The low-level problem is with sqlite though:
http://stackoverflow.com/questions/9907429/locking-sqlite-file-on-nfs-filesystem-possible
Close the bug please if no immediate solution is in sight.
--
Y
This is not a recommended use case, see
http://redmine.yorba.org/projects/shotwell/wiki/ShotwellFAQ#Can-I-access-a
-Shotwell-library-across-a-network-possibly-from-multiple-machines and
http://www.sqlite.org/whentouse.html.
We do have a ticket for making this work by allowing multiple Shotwell
app
With db a local ext4 filesystem (shotwell -d /var/tmp/shotwell/)
shotwell worked perfectly. Downside of the approach is that the db is
not accessible by other computers on the network.
I really want the db to sit on the NTFS-over-NFS partition, so other
members of the family can manage the photos
Ok, let us know know what you find.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/bugs/1127521
Title:
shotwell crashes after a while of "Updating library..."
To manage notifications
The DB area have been emptied before, so the DB have been created from scratch.
There is no problems with disk space, dmesg shows only the segfault message
(BTW, segfault is not the best way to exit, even when an error occured).
The filesystem is NTFS-over-NFS, so could be it lacks locking semant
Shotwell could do better error reporting in this case:
http://redmine.yorba.org/issues/6400
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/bugs/1127521
Title:
shotwell crashes after a
That's a fatal error being reported by SQLite, the embedded database
Shotwell uses to store its library information. SQLite's result code 10
(from this page: http://www.sqlite.org/c3ref/c_abort.html)
#define SQLITE_IOERR 10 /* Some kind of disk I/O error occurred
*/
That plus dmesg tells
12 matches
Mail list logo
