Bug 160412 - [x86_64]openoffice.org segfaults during startup
[x86_64]openoffice.org segfaults during startup
Status: CLOSED DUPLICATE of bug 160290
Product: Fedora
Classification: Fedora
Component: openoffice.org (Show other bugs)
4
x86_64 Linux
medium Severity high
: ---
: ---
Assigned To: Caolan McNamara
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-06-14 18:15 EDT by Samuli Järvinen
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-06-15 03:45:12 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Samuli Järvinen 2005-06-14 18:15:01 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4

Description of problem:
Openoffice segfaults during startup on fresh FC4 install. Arch is x86_64.

Version-Release number of selected component (if applicable):
openoffice.org-core-1.9.104-2

How reproducible:
Always

Steps to Reproduce:
1. Fresh install of FC4
2. Start openoffice via panel or in a terminal (Doesn't matter which component)
3. Segmentation fault.
  

Actual Results:  /usr/lib/openoffice.org1.9.104/program/soffice: line 247:  2325 Segmentation fault      "$sd_prog/$sd_binary" "$@"


Expected Results:  Openoffice should have started. (selected component)

Additional info:
Comment 1 Caolan McNamara 2005-06-14 18:59:45 EDT
please do...
gdb /usr/lib/openoffice.org1.9.104/program/soffice.bin
(gdb) run
(gdb) bt
and put the output here.

I bet you have a nvidia driver.
Comment 2 Mark Adams 2005-06-15 02:55:43 EDT
I've encountered the same bug, and your bet is correct for me. If I disable the
Nvidia driver, then OpenOffice will start.

Here's the backtrace you requested:
----------------------------------
(gdb) bt
#0  0x00000000 in ?? ()
#1  0x006e3955 in pthread_once () from /lib/libpthread.so.0
#2  0xf75fa95e in glXChannelRectSyncSGIX () from /usr/lib/libGL.so.1
#3  0xf762c2b8 in ?? () from /usr/lib/libGL.so.1
#4  0xf75facb0 in _init () from /usr/lib/libGL.so.1
#5  0xffff9f10 in ?? ()
#6  0x00000000 in ?? ()
-----------------------------------
Any workarounds possible, or am I stuck choosing between 3D support or a word
processor at this point?
Comment 3 Caolan McNamara 2005-06-15 03:45:12 EDT
SAL_NOOPENGLyou can try and disable OOO's 3d support with 
export SAL_NOOPENGL=true


*** This bug has been marked as a duplicate of 160290 ***

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