On 12/24/2010 01:16 PM, MR ZenWiz wrote:
I updated from RC1 to RC2 on both of my (64-bit) Ubuntu machines and
got this error on both machines:
Processing triggers for shared-mime-info ...
Unknown media type in type 'all/all'
Unknown media type in type 'all/allfiles'
Unknown media type in type 'uri/mms'
Unknown media type in type 'uri/mmst'
Unknown media type in type 'uri/mmsu'
Unknown media type in type 'uri/pnm'
Unknown media type in type 'uri/rtspt'
Unknown media type in type 'uri/rtspu'
Unknown media type in type 'fonts/package'
Unknown media type in type 'interface/x-winamp-skin'
...
I know this is a followup to an old post, but I'd forgotten the issue
until I installed a kde app on gnome. The problem is not LO, but instead
kde4libs. See:
<https://bugs.launchpad.net/ubuntu/+source/kde4libs/+bug/289592>
[Unknown media types in /usr/share/mime/packages/kde.xml]
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=469833
["Unknown media type" output message]
<https://bugs.freedesktop.org/show_bug.cgi?id=16816>
[ [PATCH] Add -q option to update-mime-database]
Also see:
https://bugs.launchpad.net/ubuntu/+source/kde4libs/+bug/268956
You can replicate by:
$ sudo update-mime-database /usr/share/mime
--
Unsubscribe instructions: E-mail to users+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/users/
*** All posts to this list are publicly archived for eternity ***
Context
- [libreoffice-users] Re: Error when updating to RC2 · NoOp
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.