Bug 190023 - [x86_64] openoffice.org crashes at start
[x86_64] openoffice.org crashes at start
Status: CLOSED DUPLICATE of bug 157024
Product: Fedora
Classification: Fedora
Component: openoffice.org (Show other bugs)
5
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Caolan McNamara
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-04-26 15:01 EDT by Joachim Kunze
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-04-28 04:10:28 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 Joachim Kunze 2006-04-26 15:01:43 EDT
Description of problem:
oowriter crashes at start with the following message:
/usr/lib/openoffice.org2.0/program/soffice: line 151: 28766
Speicherzugriffsfehler  "$sd_prog/$sd_binary" "$@"

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

How reproducible:
just start OO under FC5 ...
Comment 1 Caolan McNamara 2006-04-27 03:00:37 EDT
please do...
gdb /usr/lib/openoffice.org2.0/program/soffice.bin
(gdb) run
(gdb) bt
and put the output here.

I bet you have a nvidia driver.
Comment 2 Caolan McNamara 2006-04-28 04:10:28 EDT
I have to assume that it's issue 157024

*** This bug has been marked as a duplicate of 157024 ***
Comment 3 Joachim Kunze 2006-04-28 13:41:13 EDT
Yes, I do run nvidia drivers ...

The output is as follows:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 4160550576 (LWP 28455)]
0x00000000 in ?? ()
(gdb) bt
#0  0x00000000 in ?? ()
#1  0x00d3f2e5 in pthread_once () from /lib/libpthread.so.0
#2  0xf7c768ce in glXChannelRectSyncSGIX () from /usr/lib/libGL.so.1
#3  0xf7cab498 in ?? () from /usr/lib/libGL.so.1
#4  0xf7c76c50 in _init () from /usr/lib/libGL.so.1
#5  0xffff9764 in ?? ()
#6  0x00000000 in ?? ()

... as I don't have an Issue-Tracer account I cannot see bug-# 157024
Comment 4 Caolan McNamara 2006-04-28 13:49:20 EDT
sorry, bug 157024 not issue 157024

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