Sven Arvidsson wrote: > Thanks for your bug report. I'm afraid I can't seem to reproduce this.
Hello! I just wanted to write, that the problem diappeared. But then I found out that eog only shows this behaviour when started by doubleclicking the image file from an open nautilus showing my home directory. The same file copied to ~/Desktop or /tmp and doubleclicked from there, doesn't make eog act that bad. Image sizes are not relevant. I just tried with smaller images, the same. So the combination of nautilus pointed to my ~ and eog seems to cause that problem. I tried the "debug recipe" from Bug #411801, but I just don't have any gdb debugging and very little C-programming experience, so this didn't enlighten me... I am now using eog version 2.16.3-2 and the rest of the system is also up-to-date from etch. > What settings do you use with eog? You can list them by running > gconftool-2 -R /apps/eog from a terminal. /apps/eog/ui: image_collection = false info_collection = true toolbar = true statusbar = true info_image = false /apps/eog/full_screen: seconds = 5 upscale = true loop = true /apps/eog/window: open_new_window = true geometry_singleton = 960x797+312+165 geometry_collection = 767x948+256+25 /apps/eog/view: transparency = CHECK_PATTERN trans_color = #000000 interpolate = true > Does eog start eating memory directly, or after a certain operation, > such as resizing or rotating? It starts about 2-3 seconds after opening the file without any interaction. Best regards, Andreas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
