* Evgeni Golov <evg...@debian.org>, 2010-01-23, 15:54:
This seems to happen when mirage loads a cached image and does not update self.currimg_name. The attached patched updates this and thus fixes the bug. However I do not think this is the best way to fix this. ;)I tried to debug this issue some time ago, and I came into conclusion that this whole cache system is broken beyond all repair. I can't remember details, but all “obvious” solutions I tried triggered other, more or less subtle, bugs. I don't claim that your patch doesn't work, but I urge you to test it thoroughly before uploading.Well, until now I only tested that the patch fixes the issue you described in the bug and mirage still works for displaying random images :)
I played around with patched mirage, and it indeed works fine. I didn't notice anything unusual. :)
Could you forward this to upstream? I do not have a berlios account. Let's see what he thinks. I'll test in the meantime, that everything works.
Done. However, upstream looks a bit dead, so I wouldn't expect any feedback.
BTW, There's another upstream report about the very same bug: http://developer.berlios.de/bugs/?func=detailbug&bug_id=16676&group_id=6637 -- Jakub Wilk
signature.asc
Description: Digital signature
