After the Python runtime error is reported, flickrfs exits with code 0.
This makes flickrfs unusable, as flickrfs must remain running for the
FUSE filesystem to work. Once flickrfs has exited, an attempt to list
the contents of the flickrfs mountpoint hangs indefinitely.
This bug occurs on Jaunty 9.04 using flickrfs 1.3.9.1-8.
To reproduce:
* install flickrfs: sudo apt-get install flickrfs
* Create a mountpoint, make it world-readable: sudo mkdir /media/flickrfs &&
sudo chmod 777 /media/flickrfs
* Start flickrfs: flickrfs /media/flickrfs
* In another terminal, follow the flickrfs log: tail -F ~/.flickrfs/log.
Nothing in the log indicates the problem.
An attempt to unmount the flickrfs mount using fusermount fails with the
following error message:
$ fusermount -u /media/flickrfs
umount: /media/flickrfs: device is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
lsof and fuser report that the process using the mount is gvfs-hal-
volume-monitor.
--
Error when mounting flickrfs
https://bugs.launchpad.net/bugs/399452
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
