After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 553856 - gives incorrect warning when opening .m example
gives incorrect warning when opening .m example
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: general
2.22.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-09-25 22:23 UTC by Sebastien Bacher
Modified: 2008-09-26 09:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Sebastien Bacher 2008-09-25 22:23:32 UTC 
the bug has been described on https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/112228

"To reproduce:
1. Try to open the file attached below by double clicking it in nautilus.
2. See the error message:

"The filename "covariance.m" indicates that this file is of type "Objective-C source code". The contents of the file indicate that the file is of type "MATLAB script/function". If you open this file, the file might present a security risk to your system.

http://launchpadlibrarian.net/7547017/covariance.m

After a fresh GNU-Linux installation, Nautilus correctly opened xxx.m files with gedit, without complaining.
After I played around with "Open With" feature (I wanted to make Scite the default application for such files) Nautilus started showing that useless warning message."
Comment 1 Sebastien Bacher 2008-09-25 22:26:07 UTC 
The warning seems to be due to the fact that there is dismatch between the applications used to open text/x-objcsrc and text/x-matlab, there are both text formats though and it should not trigger a warning there.

The warning is not displayed on nautilus 2.24 but that's likely due to bug #553852
Comment 2 Sebastien Bacher 2008-09-26 09:43:18 UTC 
the glib issue was not a bug but a design change and that fixes this bug