Bug 809552
| Summary: | Could not find mime types inode/directory etc after update | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | James Hogan <james> |
| Component: | libreoffice | Assignee: | Caolan McNamara <caolanm> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | caolanm, dennis, dtardon, erack, ltinkl, mstahl, sbergman |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-06-08 14:32:49 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
James Hogan
2012-04-03 16:05:45 UTC
Okay after some more searching (I searched for a good half an hour before, honestly) I found the following command fixes it: sudo update-mime-database /usr/share/mime I'm guessing this should have been done automatically by one of the packages I installed. Anything else I can provide to help? Cheers James We've got...
%post core
update-mime-database %{_datadir}/mime &> /dev/null || :
update-desktop-database %{_datadir}/applications &> /dev/null || :
%postun core
update-mime-database %{_datadir}/mime &> /dev/null || :
update-desktop-database %{_datadir}/applications &> /dev/null || :
in the libreoffice.spec anyway, so I don't think it was our fault. (?)
... unless some of our mime files have bad syntax and that causes update-mime-database to explode. But of course we would not know that because of that idiotic "&> /dev/null || :" idiom... A manual touch /usr/share/mime/packages/libreoffice.xml && update-mime-database /usr/share/mime doesn't show anything wrong either though If we do manually what the libreoffice spec does then we get no side-effects. Given that LibreOffice is a popular enough component to install and update I'd sort of expect a load of duplicates if it was related to LibreOffice and a common occurrence. Sadly I have no idea what actually triggered this or how to reproduce it to prove that claim that something else was to blame :-( |