Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 21558 - koffice (lib kofficecore): ERROR: Couldn't find the native MimeType in karbon's desktop file. Check your installation !
Summary: koffice (lib kofficecore): ERROR: Couldn't find the native MimeType in karbon...
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo KDE team
Depends on:
Reported: 2003-05-23 12:12 UTC by Michael Collins
Modified: 2005-12-25 06:04 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Michael Collins 2003-05-23 12:12:32 UTC
Post successful emerge of koffice, you get this error when you try to run any koffice app: 
koffice (lib kofficecore): ERROR: Couldn't find the native MimeType in <app>'s desktop file. Check 
your installation ! 
The solution for me was to run: 
Apparently, this rebuilds the system confiruration cache. 
It might be a good idea to have the ebuild run this automatically after install. 
That way, everyone else won't have to spend hours and hours trying to figure out why their freshly 
emerged koffice suite won't work, like I did.  ;) 
Michael W. Collins 

Reproducible: Always
Steps to Reproduce:
Comment 1 SI Reasoning 2003-09-17 02:05:34 UTC
This did not work for me, but I think I found the culprit... openoffice 
[sczjd@gentoo sczjd]$ kbuildsycoca 
kbuildsycoca running... 
kio (KService*): WARNING: The service/mime type config file 
does not contain a ServiceType=... 
or MimeType=... entry 
[sczjd@gentoo sczjd]$ kword 
koffice (lib kofficecore): ERROR: Couldn't find the native MimeType in kword's 
desktop file. Check your installation ! 
Comment 2 Maurice van der Pot (RETIRED) gentoo-dev 2004-10-24 07:14:43 UTC
Michael, could you please tell us what version of kde/koffice/etc this bug report is about and also if you experienced this problem also with newer versions?
Comment 3 Dan Armak (RETIRED) gentoo-dev 2004-12-25 09:38:51 UTC
Ancient bugreport we didn't act on in time. Nothing to be done now without more
Comment 4 Lawrence Kesteloot 2005-07-08 23:10:24 UTC
I just ran into this problem.  I had emerged kdebase-startkde (3.4.1) and
koffice-meta (1.3.5).  I did a search for "*kword*.desktop" and didn't find
anything in $HOME/.kde or /usr/kde.  Running kbuildsycoca as root didn't help. 
Running kbuildsycoca as myself fixed the problem (though with a ton of warnings).

Gentoo Base System version 1.6.12
Portage (default-linux/x86/2005.0, gcc-3.3.5-20050130,
glibc-, 2.6.9-gentoo-r9 i686)
System uname: 2.6.9-gentoo-r9 i686 AMD Athlon(tm) XP 3200+
Python:              dev-lang/python-2.3.5 [2.3.5 (#1, Jul  4 2005, 18:39:24)]
dev-lang/python:     2.3.5
sys-apps/sandbox:    [Not Present]
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.5, 1.8.5-r3, 1.6.3, 1.7.9-r1, 1.4_p6, 1.9.5
sys-devel/libtool:   1.5.18-r1
CFLAGS="-mcpu=athlon-xp -O3 -fomit-frame-pointer -pipe"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env
/usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-mcpu=athlon-xp -O3 -fomit-frame-pointer -pipe"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms strict"
USE="x86 X alsa apache2 apm arts avi berkdb bitmap-fonts crypt cups curl emboss
encode fam foomaticdb fortran gdbm gif gpm imagemagick imlib ipv6 java jpeg
junit kde libg++ libwww mad mikmod motif mp3 mpeg ncurses nls noantlr nobcel
nobeanutils nobsh nocommonslogging nocommonsnet nojdepend nojsch nojython
nolog4j nooro noregexp norhino noxalan noxerces oggvorbis oss pam pdflib perl
png python qt quicktime readline samba sdl spell ssl tcpd tiff truetype
truetype-fonts type1-fonts xml2 xmms zlib userland_GNU kernel_linux elibc_glibc"

Comment 5 Gregorio Guidi (RETIRED) gentoo-dev 2005-07-09 02:34:34 UTC
Probably this happens if you compile koffice against kde 3.4 and run it in a 
kde 3.3 session, or viceversa. I don't think there's something we can do for 
Comment 6 Lawrence Kesteloot 2005-07-09 15:29:48 UTC
I only have kde3.4 on my machine.  It's a relatively fresh Gentoo install. 
Gentoo, then startkde, then koffice-meta.  What gave you the impression that
kde3.3 was involved?

(Actually, it was more like gentoo, then kde, then unmerge kde, then startkde,
then koffice, then unmerge koffice, then koffice-meta.)

And I can think of two things you can do: add a kbuildsycoca step in the koffice
emerge, or change the koffice warning to suggest running kbuildsycoca (or see
this bug).
Comment 7 Gregorio Guidi (RETIRED) gentoo-dev 2005-07-09 16:16:09 UTC
You're right, this error just comes from the fact that those files are not 
recognized immediately after they are installed. 
It's not possible to run kbuildsycoca automatically (the cache is user 
specific); also, this potentially affects any kde application, not just 
koffice, and adding a warning to each of them is a bit much... after all this 
is just a matter of logging out and relogging... 
Comment 8 Carsten Lohrke (RETIRED) gentoo-dev 2005-12-25 06:04:08 UTC
Close dead old bug originally resolved "needinfo".