FYI, upstream [1] provides a series of patches now which are addressing
the problem and should fix it both for remote and local filesystems
which can be affected under certain circumstances as well.
The developer is asking everyone who was affected, especially people
deploying GNOME in a
Indeed that looping behaviour is not bound to occur only on remote file
systems, but it is caused by the current version of the database file
(like home) not referring to the redo log (like home-01234567.log)
that is currently opened by the gvfsd (because it was referred to by the
database at the
Le mercredi 06 février 2013 à 20:03 +0100, Michael Karcher a écrit :
There at least two different possible scenarios, how the mismatch could
arise on a local file system, too:
a) The local file system is exported, and the log has been rotated by a
remote machine.
b) The gvfs-metadata
3 matches
Mail list logo
