Bug 657008 - [abrt] libreoffice-core-3.2.99.3-1.fc15: Process /usr/lib64/libreoffice/program/soffice.bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] libreoffice-core-3.2.99.3-1.fc15: Process /usr/lib64/libreoffice/progr...
Keywords:
Status: CLOSED DUPLICATE of bug 610103
Alias: None
Product: Fedora
Classification: Fedora
Component: libreoffice
Version: rawhide
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:0f81192cb6c39c99de656ea41df...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-24 17:00 UTC by Horst H. von Brand
Modified: 2010-11-24 20:47 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-24 20:16:55 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (27.02 KB, text/plain)
2010-11-24 17:00 UTC, Horst H. von Brand
no flags Details

Description Horst H. von Brand 2010-11-24 17:00:21 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/libreoffice/program/soffice.bin -quickstart -nologo -nodefault
component: libreoffice
executable: /usr/lib64/libreoffice/program/soffice.bin
kernel: 2.6.36.1-7.rc1.fc15.x86_64
package: libreoffice-core-3.2.99.3-1.fc15
reason: Process /usr/lib64/libreoffice/program/soffice.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 15 (Rawhide)
time: 1290617876
uid: 500

How to reproduce
-----
1. Started oocalc in a gnome-terminal (finishes inmediately), started ooffice (same), clicked the icon
2.
3.

Comment 1 Horst H. von Brand 2010-11-24 17:00:24 UTC
Created attachment 462699 [details]
File: backtrace

Comment 2 Horst H. von Brand 2010-11-24 17:07:44 UTC
This is today's update. Downgraded (i.e., 'yum -y downgrade --nogpg libreoffice-"*"') to 3.2.99.2-6.fc15.x86_64 and it works.

Comment 3 David Tardon 2010-11-24 17:57:37 UTC
The backtrace is unusable, but the "wrong library or version mismatch?" warnings from gdb suggest it might be bug 610103.

Comment 4 Caolan McNamara 2010-11-24 20:16:55 UTC

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


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