Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MIME Type Mismatch?

Status
Not open for further replies.

Kirsle

Programmer
Jan 21, 2006
1,179
US
Hi, I'm currently running on Fedora Core 6, but I've noticed this problem on Core 5 as well...

Sometimes when I double-click on a file to open it, it pops up an error message about the types not matching up. For instance, when I double-click to open an OpenOffice file, I get this message:

Code:
Cannot open IT116.odt

The filename "IT116.odt" indicates that this file is of type "ODT document". The contents of the file indicate that the file is of type "Java Archive". 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 "Java Archive", then open the file normally. Alternatively, use the Open With menu to choose a specific application for the file.

[Cancel]

I've also gotten a similar error with ZIP files, with it mistaking them for Java Archives.

I've also run into this problem with Windows EXE files, which would run under WINE. In that case, it says that the file extension is of type "Executable" but the content suggests it's of type "Application/DOS Executable" or something along those lines.

Is there any way to make Linux stop doing this? It should just go by the file extension, and only come up with a type based on the content if there is no extension.

-------------
Cuvou.com | The NEW Kirsle.net
 
I found /usr/share/application-registry/gnome-vfs.applications
which belong to the gnome-mime-data package that seems to have information about applications and their mime types. You could try editing this file manually to see if it fixes your problem.

--== Anything can go wrong. It's just a matter of how far wrong it will go till people think its right. ==--
 
I couldn't find anything in that file that would relate to this problem...

I googled some of the error text, and the most common theory as to what this is, is its somehow a bug with Nautilus... apparently on KDE this kind of thing never happens. However, I haven't found any useful info on Google about how to get rid of it, or if Nautilus has ever fixed the bug yet.

-------------
Cuvou.com | The NEW Kirsle.net
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top