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 78778 - User created MIME types don't work [as well as other MIME type problems]
User created MIME types don't work [as well as other MIME type problems]
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: File and Folder Operations
0.x.x [obsolete]
Other other
: Urgent major
: 2.0.x
Assigned To: Jody Goldberg
Nautilus Maintainers
Depends on: 75620 78045 79389
Blocks:
 
 
Reported: 2002-04-15 16:46 UTC by Philippe A
Modified: 2006-12-26 18:26 UTC
See Also:
GNOME target: Old
GNOME version: ---



Description Philippe A 2002-04-15 16:46:12 UTC
Nautilus keeps complaning it has "no installed viewer" for the file 
types I have created a MIME for.

Very simple to reproduce and happens all the time:
- Creating a MIME type for image/x-yuv I call 000.
- Adding extension "yuv".
- Adding application "myviewer". Note that something wrong already 
happens at this point. After I create and select the default 
application, the default action in the MIME list stays to "default". 
The default action is updated only after I select the "use viewer" 
button and come back to "open with application".
- I click ok and close the control center to make sure the change was 
effective.
- I open a new Nautilus window, I browse to a yuv file, double click 
on it. Nautilus complains about that file type without opening it.

Version returned by rpm -qi is : 1.4.0.1.
Comment 1 Luis Villa 2002-04-23 00:37:31 UTC
Jody: could you please make sure this works in 2.0? Thanks.
Comment 2 Jody Goldberg 2002-04-23 00:55:18 UTC
I can replicate this.  The type is not recognized even when restarting
nautilus.  While doing it a few bugs came up.  I'll use this as a
place holder for all the other brokenness.

1) selecting an app to use for a new mime-type generated a filesel
warning (should be easy)

2) 'Apply' from the main file-type dialog after adding the new type
generated hash warnings that the hash == NULL
Comment 3 Jody Goldberg 2002-05-24 15:19:07 UTC
1 & 2 are fixed.
The new type works now, but we need to get nautilus to refresh its 
idea of what mime types are associated with things.  It does not get 
updated that the file now has the new type.  I'll keep poking at 
this, but will refile it as a nautilus bug.