Bug 80926 - Kword doesn't start from Gnome
Kword doesn't start from Gnome
Product: Red Hat Public Beta
Classification: Retired
Component: koffice (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Ngo Than
Depends On:
Blocks: 79578
  Show dependency treegraph
Reported: 2003-01-02 09:25 EST by Gerry Tool
Modified: 2008-05-01 11:38 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-02-03 08:38:40 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Gerry Tool 2003-01-02 09:25:48 EST
Description of problem:
If I try to run Kword from Gnome, I get the following:
[gerry@gstpc gerry]$ which kword
[gerry@gstpc gerry]$ /usr/bin/kword &
[1] 6592
[gerry@gstpc gerry]$ DCOPServer up and running.
kdeinit: Fatal IO error: client killed
kdeinit: sending SIGHUP to children.
kdeinit: sending SIGTERM to children.
kdeinit: Exit.
[1]+  Exit 1                  /usr/bin/kword
[gerry@gstpc gerry]$
If I run it from KDE, it works as expected.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Use Gnome desktop
2.Execute kword
Actual results:
KWord tries to start and dies

Expected results:
KWord should open an application window

Additional info:
Works correctly on the KDE desktop
Comment 1 Warren Togami 2003-01-23 05:13:27 EST
Confirmed.  When you attempt to debug this, it causes a gdb internal error (Bug
Comment 2 Warren Togami 2003-01-24 14:44:06 EST
When using koffice from a LTSP client logged into KDE I get the following error.

[patron32@kcc3 patron32]$ kword
Xlib:  extension "GLX" missing on display "ws244.ltsp:0.0".
Xlib:  extension "GLX" missing on display "ws244.ltsp:0.0".

Kword fails to start.
Comment 3 Ngo Than 2003-02-03 08:38:40 EST
please upgrade the current kde 3.1/koffice-1.2.1 from rawhide, It seems to be
fixed in this release. I cannot reproduce it anymore.

Note You need to log in before you can comment on or make changes to this bug.