Red Hat Bugzilla – Bug 92044
koffices apps fail to start
Last modified: 2007-04-18 12:54:11 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225
Description of problem:
When starting koffice apps from the command line nothing seems to happen: it
silently returns to the command prompt after a delay of a few seconds. This is
for a clean everything install of Red Hat 9 with the glibc errata applied.
This is probably the same as bug # 84678, however I cannot add this add as a
comment due to bugzilla bug # 88502.
Is there any additional useful information I could supply?
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. open gnome-terminal
2. execute command "kword"
3. command prompt returns after 3 seconds with no other result
Actual Results: nothing happened
Expected Results: kword should have started
strange, this issuse only appears on my machine if kdebase is not installed. I
already added requires kdebase in koffice-1.2.1-7.
Is kdebase installed on your machine?
For debugging i need some informations:
please give me rpm package list on your machine (rpm -qa)?
And strace log (strace -o kword.log kword)
sorry, works for me. any more specific way to reproduce this ? reopen then.
Created attachment 92176 [details]
List of installed packages
Created attachment 92177 [details]
strace log on kword
Sorry for the delay in replying, but it still doesn't work for me. I have
attached my package list and strace log, as suggested. Anything else I can do?
does it work for you if you start kdeinit first and then kword?
or does it work for you if you start it in KDE desktop Enviroment?
Running kdeinit first (in gnome) does not work either.
I then started a KDE session and kword works fine. This was the first time I ran
a KDE session in this install of RedHat Linux. Going back to a gnome session,
all koffice apps now work.
So the problem seems to be that koffice is not properly initialised unless run
first in a KDE session.
ok, i have found the bug now. it should be fixed in koffice-1.2.1-13. thanks for