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: kbuildsycoca 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: 1. 2. 3.
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 application/x-staroffice.desktop 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 !
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?
Ancient bugreport we didn't act on in time. Nothing to be done now without more info.
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 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc-2.3.4.20041102-r1, 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/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.8.1-r4 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-mcpu=athlon-xp -O3 -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" 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" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" 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" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
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 it.
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).
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...
Close dead old bug originally resolved "needinfo".
