Bug 80926 - Kword doesn't start from Gnome
Summary: Kword doesn't start from Gnome
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: koffice
Version: phoebe
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 79578
TreeView+ depends on / blocked
 
Reported: 2003-01-02 14:25 UTC by Gerry Tool
Modified: 2008-05-01 15:38 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2003-02-03 13:38:40 UTC
Embargoed:


Attachments (Terms of Use)

Description Gerry Tool 2003-01-02 14:25:48 UTC
Description of problem:
If I try to run Kword from Gnome, I get the following:
===============
[gerry@gstpc gerry]$ which kword
/usr/bin/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:
Always

Steps to Reproduce:
1.Use Gnome desktop
2.Execute kword
3.
    
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 10:13:27 UTC
Confirmed.  When you attempt to debug this, it causes a gdb internal error (Bug
82477).


Comment 2 Warren Togami 2003-01-24 19:44:06 UTC
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 Than Ngo 2003-02-03 13:38:40 UTC
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.