Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1338057

Summary: Warning on console each time a dnf transaction runs update-mime-database
Product: [Fedora] Fedora Reporter: Hans de Goede <hdegoede>
Component: epiphanyAssignee: Michael Catanzaro <mcatanzaro+wrong-account-do-not-cc>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: gecko-bugs-nobody, mcatanzaro+wrong-account-do-not-cc, rob.townley
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-21 14:45:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Hans de Goede 2016-05-21 10:32:28 UTC
Each time a dnf transaction runs update-mime-database (even if the transaction does not include epiphany) the following warning is printed:

Warning in file "/usr/share/applications/epiphany.desktop": usage of MIME type "multipart/related" is discouraged ("multipart" is a media type that probably does not make sense in this context)

Please fix this (remove the bogus multipart/related mime-type from the list of mime-types in the .desktop file). See: http://pkgs.fedoraproject.org/cgit/rpms/gnumeric.git/commit/?id=f17620fc592fc8f03f9e5a559f89ed3aef7886fd

For an example fixing a similar bug.

Comment 1 Michael Catanzaro 2016-05-21 14:45:42 UTC
Note it's not bogus; we really do support that MIME type.

Comment 2 Michael Catanzaro 2016-05-21 14:48:11 UTC

*** This bug has been marked as a duplicate of bug 1291783 ***