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. ;)
Regards Evgeni -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mirage depends on: ii libc6 2.10.2-5 Embedded GNU C Library: Shared lib ii libx11-6 2:1.3.3-1 X11 client-side library ii python 2.5.4-6 An interactive high-level object-o ii python-gtk2 2.16.0-1 Python bindings for the GTK+ widge ii python-support 1.0.6 automated rebuilding support for P mirage recommends no packages. mirage suggests no packages.
--- mirage-0.9.3/mirage.py 2008-03-27 05:05:28.000000000 +0100 +++ mirage-0.9.3.patched/mirage.py 2010-01-23 13:53:30.000000000 +0100 @@ -3892,6 +3892,7 @@ self.last_image_action_was_smart_fit = False elif self.open_mode == self.open_mode_1to1 or (self.open_mode == self.open_mode_last and self.last_mode == self.open_mode_1to1): self.last_image_action_was_fit = False + self.currimg_name = str(self.image_list[self.curr_img_in_list]) else: # Need to load the current image self.currimg_pixbuf = None