Nautilus crash on image properties.

[adebened]

Hi all,

I've noticed that nautilus crashes often (SL 5.8) when selecting "properties" from the right-click menu with many images. It doesn't happen with all images (eg. some jpg's are OK, some crash. The same with other image file types). Other types of files, including videos, don't seem to cause a crash. I tried deleting thumbnails, thinking that the preview image on the properties dialog could be the problem, but that didn't work. This has been happening for at least a month, but maybe longer. The following is the output from BugBuddy:

CODE

Distribution: Scientific Linux release 5.8 (Boron) Gnome Release: 2.16.0 2007-03-26 (Red Hat, Inc) BugBuddy Version: 2.16.0 Memory status: size: 156057600 vsize: 0 resident: 156057600 share: 0 rss: 58576896 rss_rlim: 0 CPU usage: start_time: 1340298035 rtime: 0 utime: 156 stime: 0 cutime:143 cstime: 0 timeout: 13 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/nautilus' [Thread debugging using libthread_db enabled] 0x00fd0410 in __kernel_vsyscall () #0  0x00fd0410 in __kernel_vsyscall () #1  0x00cdfadb in waitpid () from /lib/libpthread.so.0 #2  0x04860c26 in ?? () from /usr/lib/libgnomeui-2.so.0 #3  <signal handler called> #4  0x08074b70 in ?? () #5  0x05fcee63 in ?? () from /usr/lib/libgnomevfs-2.so.0 #6  0x00000046 in ?? () #7  0x00000000 in ?? () Thread 1 (Thread 0xb7fb3a10 (LWP 5074)): #0  0x00fd0410 in __kernel_vsyscall () No symbol table info available. #1  0x00cdfadb in waitpid () from /lib/libpthread.so.0 No symbol table info available. #2  0x04860c26 in ?? () from /usr/lib/libgnomeui-2.so.0 No symbol table info available. #3  <signal handler called> No symbol table info available. #4  0x08074b70 in ?? () No symbol table info available. #5  0x05fcee63 in ?? () from /usr/lib/libgnomevfs-2.so.0 No symbol table info available. #6  0x00000046 in ?? () No symbol table info available. #7  0x00000000 in ?? () No symbol table info available. A debugging session is active. Inferior 1 [process 5074] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal]

I'm curious if anyone else has experienced this and/or if anyone has a suggestion as to the origin of the problem?

Thank you,

[zxq9]

I get the feeling that most folks around here are using a 6.x version, not 5, but in any case, it looks like there is a problem with whatever Nautilus is using to scan the file.

Do you only get this on image files? When did the problem start?

It should be pretty easy to nail this down, if not fix it.

[adebened]

QUOTE (zxq9 @ Jun 21 2012, 06:26 PM)

Do you only get this on image files? When did the problem start?

Hello,

Thanks for the reply. It only happens with image files (at least that's all I've noticed) and it only happens with some images. It does not seem to depend on the actual format of the image (jpg, gif etc.). I first noticed this problem about a month ago (maybe a little bit more).

Thanks,

[zxq9]

That is interesting. A few more questions.

• Do you have thumbnails set to be displayed as well? ...and do they work?)
• Do other file browsers like Dolphin, Konqueror and Thunar work OK?
• When Nautilus crashes, is it just the one window, or does your whole Gnome desktop flash blank for a few seconds and then spin back up? This usually takes all other open Nautilus windows with it -- if you're on a fast system you might need to open two naultius browsing windows and see if both die when one crashes to test this.
• "Files that crash Nautilus" is still sort of undefined. If a file crashes Nautilus does it always crash Nautilus or does it crash it one time and not another?

That last question is an important detail, because I think what's happening is a module supporting nautilus (but probably not nautilus itself unless nautilus.InfoProvider is acting up) is encountering a bad jump -- like a pointer that points to junk but expects to continue execution from there and is instead sliding down the padding until crashing out at the bottom of the relative addresses.

[adebened]

Thank you. I'll answer in the order you asked.
1) Yes, and they work.
2) Konqueror works fine. (no crashes).
3) After clicking "send" or "cancel" on BugBuddy, the whole desktop automatically re-starts.
4) From my experimenting with this, if a file crashes nautilus, that same file always crashes nautilus. I'd say about 70% of image files are causing this.

I should maybe add that this happens on both machines I have running SL5.8

Thanks in advance for any help/advice.