Bug 110493 – KWord (and all koffice programs) fail to start

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description Rob Smith 2005-10-25 17:10:48 UTC]

when running kword or any koffice program, it fails to start with a bunch of 
errors

Reproducible: Always
Steps to Reproduce:
1. emerge koffice
2. run kword

Actual Results:  
kormoc@kormoc ~ $ kword
koffice (lib kofficecore): WARNING: Got no results with [X-KDE-NativeMimeType] 
== 'application/x-kword' or 'application/x-kword' in [X-KDE-
ExtraNativeMimeTypes]
koffice (lib kofficecore): ERROR: Found no KOffice part able to handle 
application/x-kword!
koffice (lib kofficecore): ERROR: Check your installation (does the desktop file 
have X-KDE-NativeMimeType and KOfficePart, did you install KOffice in a 
different prefix than KDE, without adding the prefix to /etc/kderc ?)

Expected Results:  
kword would run

kormoc@kormoc ~ $ emerge info
Portage 2.0.53_rc6 (default-linux/x86/2005.1, gcc-3.4.4, glibc-2.3.5-r2, 2.6.13.
1 i686)
=================================================================
System uname: 2.6.13.1 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz
Gentoo Base System version 1.12.0_pre9
ccache version 2.4 [enabled]
dev-lang/python:     2.3.5, 2.4.2
sys-apps/sandbox:    1.2.13
sys-devel/autoconf:  2.13, 2.59-r7
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.16.1
sys-devel/libtool:   1.5.20
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O3 -march=pentium4 -mmmx -msse -msse2 -mno-sse3 -mno-3dnow -
mfpmath=sse,387 -fomit-frame-pointer -maccumulate-outgoing-args"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.5/env /usr/kde/3.5/
share/config /usr/kde/3.5/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="-O3 -march=pentium4 -mmmx -msse -msse2 -mno-sse3 -mno-3dnow -
mfpmath=sse,387 -fomit-frame-pointer -maccumulate-outgoing-args"
DISTDIR="/tmp/disfiles"
FEATURES="autoconfig ccache digest distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://gentoo.mirrors.tds.net/gentoo"
MAKEOPTS="-j2"
PKGDIR="/tmp/packages"
PORTAGE_TMPDIR="/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.us.gentoo.org/gentoo-portage"
USE="x86 X alsa apm avi bitmap-fonts crypt cups curl eds emboss encode fam flac 
foomaticdb fortran gd gif gstreamer gtk gtk2 imagemagick imlib java jpeg libg++ 
libwww mad mikmod mmx mmx2 motif mp3 mpeg mysql ncurses nls ogg oggvorbis opengl 
oss pam pdflib perl pic png python qt quicktime readline ruby samba sdl speex 
spell sse ssl tcltk tcpd tiff truetype truetype-fonts type1-fonts udev vorbis 
xine xinerama xml2 xmms xv zlib userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS

This is from within xfce with kde 3.5 beta 2 installed. I am running kword from 
konsole, so kde's libs are loaded and running.

It appears that koffice is merged into /usr/bin (which kword shows /usr/bin/
kword) and kde expects it to have gone into /usr/kde/version/bin?

I noticed another bug, #4287 (http://bugs.gentoo.org/show_bug.cgi?id=4287) was 
very similar, but exporting KDEDIRS=/usr did not fix the issue.

Thanks

[Comment 1 Gregorio Guidi (RETIRED) 2005-10-26 02:04:28 UTC]

Can you check that koffice was compiled against the same kde that is running 
(3.5_beta2)? See also bug 96932. 

[Comment 2 Rob Smith 2005-10-26 09:54:50 UTC]

(In reply to comment #1)
> Can you check that koffice was compiled against the same kde that is running 
> (3.5_beta2)? See also bug 96932. 

It was compiled against 3.5 beta 2.

As per the other bug,
kormoc@kormoc ~ $ kde-config --path services
/home/kormoc/.kde/share/services/:/usr/share/services/:/usr/kde/3.5/share/
services/

So it is looking in both services directorys.

KDEDIRS is set to /usr in /dev/env.d/99kde-env

I shall compile it again to make sure.

[Comment 3 Rob Smith 2005-10-26 11:02:30 UTC]

Okay... I recompiled it and it seems to work now. I did restart X this time, so 
maybe it was related to that. In any case, it's all working now, so I'll close 
this bug.