Bug 4287 – KWord fails to start (using Gentoo 1.3a - GCC3)

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description David Nielsen 2002-06-28 08:49:51 UTC]

/usr/qt/3/plugins/styles/keramik.so: Feature Keramik already defined in 
/usr/qt/3/plugins//styles/keramik.so! 
koffice (lib kofficecore): WARNING: Got no results with [X-KDE-NativeMimeType] 
== 'application/x-kword' 
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 ?) 
Mutex destroy failure: Device or resource busy 
 
It seems that the lastest ebuild of KOffice (1.2beta2) breaks KWord so that it 
can't start.

[Comment 1 Jon Nelson (RETIRED) 2002-08-21 18:43:08 UTC]

I get a different but similar error:

jnelson@host jnelson $ kword
DCOPServer up and running.
koffice (lib kofficecore): ERROR: Couldn't find the native MimeType in kword's
desktop file. Check your installation !
Mutex destroy failure: Device or resource busy
jnelson@host jnelson $ 


Does something else have to be running for kword to work?

[Comment 2 Dan Armak (RETIRED) 2002-09-15 04:48:31 UTC]

Jon: seems like you run it outside of kde. If you're not diong it from a login 
shell, try doing "export KDEDIRS=/usr" first. Otherwise what's your setup? 
 
David: may be a longshot but, this could happen if koffice is the first/only 
kde app you emerged that isn't a part of kde-base, and you haven't restarted 
your KDE since. Try re-logging into KDE to update your environment if so. 
Or: are you also running kword from a non-inheriting shell? If so try exporting 
KDEDIRS=/usr, too. 
 
 

[Comment 3 Dan Armak (RETIRED) 2002-11-23 14:34:02 UTC]

Is this still relevant? If there is no reply I will close the bugreport. 

[Comment 4 Bart Verwilst 2003-01-05 06:36:47 UTC]

SInce there hasn't been an answer for over a month, i'm closing this bug