flickrfs won't list sets and therefore stops working

[Sancho]

I installed flickrfs from both the repository and the CVS, the error is the same.
I mount the filesystem (I already possess the correct authentication token) using flickrfs ~/flickr
I can see the log trying to sync my sets, however, after quite a while (approx. 200 sets synced) I can see error messages like
07/04/13 13:58:03 INFO Syncing set /sets/20130629 u Sasi s Lolou
07/04/13 13:58:03 DEBUG Retry attempt 0 for func <bound method Flickrfs.__sync_set_in_background of <__main__.Flickrfs object at 0x1120410>>
07/04/13 13:58:03 INFO Syncing set /sets/20100525 trosku prsalo
07/04/13 13:58:03 DEBUG Retry attempt 0 for func <bound method Flickrfs.__sync_set_in_background of <__main__.Flickrfs object at 0x1120410>>
07/04/13 13:58:03 INFO Syncing set /sets/20100515 malujeme Daskinu izbu
07/04/13 13:58:03 DEBUG Retry attempt 0 for func <bound method Flickrfs.__sync_set_in_background of <__main__.Flickrfs object at 0x1120410>>
07/04/13 13:58:03 DEBUG Retry attempt 0 for func <bound method Flickrfs.__sync_set_in_background of <__main__.Flickrfs object at 0x1120410>>
07/04/13 13:58:03 INFO Syncing set /sets/20120817 spolu v ruzovom
07/04/13 13:58:03 DEBUG Retry attempt 0 for func <bound method Flickrfs.__sync_set_in_background of <__main__.Flickrfs object at 0x1120410>>

The process seems to hang or something.
When I try to list the directory, the log has no new input, but the command
ls -al ~/flickr
hangs.
The only way to fix it is to use sudo umount -f ~/flickr
I googled the error message and found some record stating it has already been fixed, however, the bug persists for me both in the .deb version and within the CVS.
Can anyone help?

Verified on two systems:
LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch
Distributor ID: Ubuntu
Description: Ubuntu 12.10
Release: 12.10
Codename: quantal

and

Distributor ID: Ubuntu
Description: Ubuntu 12.04.2 LTS
Release: 12.04
Codename: precise

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Davy39 (davy39)]

Exactly same problem for me on ubuntu 13.04 installing from official repositories.
Does anyone know what happen ?

[Andrius (3-andrius)]

I had exactly same problem on ubuntu 12.10 and flickrfs installed from official repositories. I have solved this issue inserting "time.sleep(0.7)" after line #358 in "/usr/share/pyshared/flickrfs/flickrfs.py" file. I don't know what exactly causes this issue, but it depends on how quickly threads are being created. For example, on my computer 0.5 timeout does not solve the issue.

--- flickrfs.py.orig 2013-08-11 00:06:27.461206731 +0300
+++ flickrfs.py 2013-08-11 02:01:51.981314517 +0300
@@ -356,6 +356,7 @@
         curdir = "/sets/" + a['id']
       set_id = a['id']
       background(self.__sync_set_in_background, set_id, curdir)
+ time.sleep(0.7)
     log.info('sync_sets_thread finished')

   def sync_stream_thread(self):

[mark (tiberopoulos)]

Andrius' fix stopped the hanging after an ls on the ~/Flickr dir, but flickrfs still did not sync any sets. Tried on 12.10 and 13.04. Both x64. Attached is my log file in case it helps. With Flickr now giving 1TB free, I imagine there's quite a few people looking to sync their entire collection so it's def worthwhile fixing this if someone with the knowledge would be good enough to have a go.

[riban (brian-riban)]

I wonder if this is affected by the quantity of files stored on the flickrfs. Things worked okay for me at first but after uploading several hundred files I started to suffer from this issue. Sets are detected and populated (or partially populated) then this exception occurs. Specifically, I get the message (twice):

Retry attempt 0 for func <bound method Flickrfs.__sync_set_in_background of <__main__.Flickrfs object at 0x85a4a4c>>

[moli (f-launchpad-moli-hu)]

> "I wonder if this is affected by the quantity of files stored on the flickrfs. Things worked okay for me at first but after uploading several hundred files I started to suffer from this issue."

I've got 1 image in my account and i'm affected by this bug, so no.

[Alejandro Mery (amery)]

still broken in 14.04

[Giorgio Borgonovo (borgonovo)]

Is there any update?

[Eric Smith (prlj13)]

I'm having the same issue in 14.04 LTS. Any update?

[Timo Jyrinki (timo-jyrinki)]

The support for https (now required) was just committed to Ubuntu 15.04, and it seemed to work for me fine for basic usage at first. I do also see this however (maybe I have some borderline amount of photos), so I believe this is still a valid upstream problem. Unfortunately the original upstream does not seem very active, so a developer would be needed to pick it up.