Bug 19067 - can't chaneg video/mpeg mime types
Summary: can't chaneg video/mpeg mime types
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gmc
Version: 7.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Havoc Pennington
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-10-13 17:56 UTC by Need Real Name
Modified: 2008-05-01 15:37 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2001-01-15 23:14:30 UTC
Embargoed:


Attachments (Terms of Use)

Description Need Real Name 2000-10-13 17:56:45 UTC
This happens with both 6.2 and 7.0, but I can't seem to select both. I
always select individual packages to install and don't have a log handy of
either install. The problem is that I can't change the Open/View action for
the video/mpeg mime type. I first try using Gnome Control Center. The
default is xanim, but I don't like that, I change it to use mtvp (MpegTV).
In the dialog, whatever I type in is remembered. I then go to a gmc window
and double-click an mpeg file, depending on whether xanim is installed, the
file is eithered opened with xanim or I'm given an error the xanim can't be
started. I have tracked it down to (I think) /usr/share/mime-info/mc.keys,
which sets the mim-type video/* to use xanim. Changing these lines in any
way doesn't seem to remove that mime-type association, however, instead it
just breaks it. I've tried commenting them out and gievn open/view settings
for each individual video/<type> mime-type, but they don't take. This is
the only file I can find that is setting this association. I hope I've been
as specific as you will need, but don't hesitate to request more
information should you need it. I can be reached at
jgeorgeson. Thanks.

Comment 1 Havoc Pennington 2001-01-15 23:14:25 UTC
Maybe jrb has ideas....

Comment 2 Havoc Pennington 2001-07-12 20:17:35 UTC
we are deprecating gmc in favor of nautilus, given that this bug is not critical.


Note You need to log in before you can comment on or make changes to this bug.