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 141509 - "Can not open file" message shows file type "(null)"
"Can not open file" message shows file type "(null)"
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: File and Folder Operations
0.x.x [obsolete]
Other All
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-04-30 16:52 UTC by Alexander Kirillov
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8

Attachments
Another example of this annoying bug (62.46 KB, image/png)
2004-07-07 14:44 UTC, Bruce-Robert Pocock 		  Details
Proposed patch. (1.26 KB, patch)
2004-07-21 19:11 UTC, Christian Neumair 		none Details | Review

Description Alexander Kirillov 2004-04-30 16:52:18 UTC 
Steps to reproduce: 
1. create a shell script and name it INSTALL
2. Double-click on it in Nautilus. You get the following message: 

------------------
Cannot open INSTALL

The filename "INSTALL" indicates that this file is of type "Software
installation instructions". The contents of the file indicate that the file is
of type "(null)". If you open this file, the file might present a security risk
to your system.

Do not open the file unless you created the file yourself, or received the file
from a trusted source. To open the file, rename the file to the correct
extension for "(null)", then open the file normally. Alternatively, use the Open
With menu to choose a specific application for the file.
--------------------

Yet, if you right-click on the file and choose "properties", it correctly shows
file type as application/x-shellscript - not "(null)". And Nautilus uses shell
script icon for the file.
Comment 1 Bruce-Robert Pocock 2004-07-07 14:44:41 UTC 
Created attachment 29322 [details]
Another example of this annoying bug

Here's a similar example, where a "Windows Write" file (ironically, from the
Bitstream Vera release tarball for GNOME) is correctly identified as a (more or
less) Microsoft Word document -- but the ".wri" extension is "recognized" as
"(null)." There are other examples.

If Nautilus doesn't recognize the extension, I don't think we should be seeing
this dialog. Likewise for filenames with no extension -- or which don't have an
extension, but do happen to have a "." in the name ('Photo of 3.5" Floppy
disc') ...
Comment 2 Christian Neumair 2004-07-21 19:11:58 UTC 
Created attachment 29760 [details] [review]
Proposed patch.

The problem is that some MIME types have no description, because Nautilus
doesn't fetch the shared-mime-info description. Instead, it uses that from
gnome-mime-info, which isn't always in sync with shared-mime-info. The patch
aims to display the MIME type itself if no description is available.
Comment 3 Alexander Kirillov 2004-07-22 14:44:13 UTC 
I am rather ignorant, but is there a way to make Nautilus use the
shared-mime-info description, thus eliminating the syncing problem??
Comment 4 Christian Neumair 2004-07-22 15:31:14 UTC 
You are far away from being ignorant :). That will be done in GNOME 2.8. But
still, the issue remains that the description could be NULL.

regs,
 Chris
Comment 5 Alexander Larsson 2004-08-16 10:40:09 UTC 
Patch commited to cvs. Thanks.