From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040207 Firefox/0.8 Description of problem: If I open a file in Nautilus for which there is no configured apploication, I am prompted to either Associate Application or Cancel. If I click the button to Associate Application, I am presented with a crash window for gnome-file-types-properties. This seems to be limited to certain files or file types. Specific files this has been consistent on are /usr/share/alsa/asla.conf and /usr/share/alsa/sndo-mixer.alisp. A file which Nautilus has not given me the crash dialog for, but has still failed to launch the gnome-file-type-properties application, are /usr/share/doc/alsa-utils-1.0.2. This happens in both Browse view, and whatever the new default behavior for Nautilus is called. Version-Release number of selected component (if applicable): control-center-2.5.2-5 How reproducible: Always Steps to Reproduce: 1. Open Nautilus and navigate to /usr/share/alsa 2. Click, or double-click depending on settings, on alsa.conf 3. Click the button for Associate Application Actual Results: a crash dialog is presented, giving me the option to dismiss or file a bug report. Expected Results: gnome-file-type-properties should launch so I can associate an application. Additional info:
Ugh, should have previewed better, the file which doesn't crash, but also doesn't launch gnome-file-types-properties, is /usr/share/doc/alsa-utils-1.0.2.
Well, I guess bugzilla just doesn't like the filename I gave it. I think it was c hangelog. Anyhow, all those files listed have mime types for them now after updating what seems like everything. control-center is now at 2.5.3-1 and I haven't found a file yet to crash it. Consider it fixed.
I've seen this issue with .spec not being associated, making Nautilus segfault. Can't reproduce it anymore, so I also think it has been fixed by now.
I think this was fixed with a recent nautilus upgrade.
I know I tested this after a big update a while ago, and seem to remember adding a comment that it had been fixed, but I don't see that comment. So I agree, I think it has been fixed.