Closed Bug 582525 Opened 15 years ago Closed 15 years ago

[Linux] openSUSE rpm for Firefox registers wrong MIME-type

Categories

(Firefox :: Installer, defect)

3.6 Branch
x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: hendrik, Unassigned)

Details

After install of latest FF via openSUSE rpm, I got an error message saying FF wanted to register an obsolete MIME type: x-directory, and that a newer one should be used. # zypper in -f MozillaFirefox Loading repository data... Reading installed packages... Forcing installation of 'MozillaFirefox-3.6.6-1.2.i586' from repository 'openSUSE-11.3-Oss'. Resolving package dependencies... The following package is going to be reinstalled: MozillaFirefox 1 package to reinstall. Overall download size: 855.0 KiB. No additional space will be used or freed after the operation. Continue? [y/n/?] (y): Retrieving package MozillaFirefox-3.6.6-1.2.i586 (1/1), 855.0 KiB (3.4 MiB unpacked) Retrieving: MozillaFirefox-3.6.6-1.2.i586.rpm [done (790.5 KiB/s)] Installing: MozillaFirefox-3.6.6-1.2 [done] Additional rpm output: Warning in file "/usr/share/applications/nautilus-folder-handler.desktop": usage of MIME type "x-directory/gnome-default-handler" is discouraged ("x-directory" is an old media type that should be replaced with a modern equivalent) Warning in file "/usr/share/applications/nautilus-folder-handler.desktop": usage of MIME type "x-directory/normal" is discouraged ("x-directory" is an old media type that should be replaced with a modern equivalent)
That error is from the package manager and is regarding the package from the openSUSE rpm which is not maintained by Mozilla. To get this fixed you'll need to notify the maintainers of the rpm.
Summary: Firefox registers wrong MIME-type → [Linux] openSUSE rpm for Firefox registers wrong MIME-type
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
Just to clarify it here that this is not an issue within the Firefox distribution at all. All the warnings are about another package.
You need to log in before you can comment on or make changes to this bug.