Red Hat Bugzilla – Bug 145347
openoffice.org: mailcap not populated
Last modified: 2007-11-30 17:07:15 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041020
Description of problem:
I installed nahant-beta2 and I'm completely up-to-date. No
/etc/mailcap entries are in place for Open Office extensions or
traditional Microsoft document extensions. This means applications
like Evolution only offer the "Save As" option for attachments. I
believe /etc/mailcap should be populated with entries upon
installation of openoffice.org and the entries should point .sxw,
.xls, .ppt, .doc, etc to office.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install openoffice.org.
2. Receive email with .xls attachment in Evolution
3. Click on attachment.
Actual Results: Only "Save As" option is offered.
Expected Results: "Open in OpenOffice.org" option should also be offered.
Actually, Evolution should be pulling its mime-types from
shared-mime-data and redhat-menus packages (from the OOo .desktop
files) rather than mimecap. Modifying mimecap on the fly was a hack
and not very maintainable.
If there aren't options for "Open in OpenOffice.org Writer" coming up
when you click on the attachment button in Evolution, then we need to
figure out what the mime-type of the document you're trying to open
is, and add that type to the OOo .desktop file. OOo should nto be
modifying mimecap any more, it should all get pulled from the new mime
system at this time.
Note that I did fix a couple of problems with this, and it might be
the case that RHEL4-RC1 already fixes this problem, but that it was
broken for Beta2. The correct package versions you need are:
redhat-menus-3.7.1-2 or higher
Those packages should be present in the RC and later builds and should
fix this bug. Whenever you get those builds, could you verify that
this bug is/is not fixed and update this issue?
Dan, I'm running the following:
I do not believe the RC is publicly available, so I guess I'm SOL for now.
Hmm, yeah :( Should be fairly soon though. I'll close as "fixed"
then, feel free to reopen if it persists in RC or later.