Bug 684029 - [abrt] openoffice.org-brand-1:3.3.0-20.2.fc14: Process /usr/lib64/openoffice.org3/program/soffice.bin was killed by signal 7 (SIGBUS)
Summary: [abrt] openoffice.org-brand-1:3.3.0-20.2.fc14: Process /usr/lib64/openoffice....
Keywords:
Status: CLOSED DUPLICATE of bug 674416
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:bd02aa4694059d7751a713b2e8b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-10 22:32 UTC by Jeffrey S Austin
Modified: 2011-03-11 08:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-11 08:28:11 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (36.56 KB, text/plain)
2011-03-10 22:32 UTC, Jeffrey S Austin 		no flags Details
View All

Description Jeffrey S Austin 2011-03-10 22:32:33 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 37439 bytes
cmdline: /usr/lib64/openoffice.org3/program/soffice.bin -quickstart -nologo -nodefault
component: openoffice.org
Attached file: coredump, 54280192 bytes
crash_function: bridges::cpp_uno::shared::VtableFactory::initializeBlock
executable: /usr/lib64/openoffice.org3/program/soffice.bin
kernel: 2.6.35.11-83.fc14.x86_64.debug
package: openoffice.org-brand-1:3.3.0-20.2.fc14
rating: 4
reason: Process /usr/lib64/openoffice.org3/program/soffice.bin was killed by signal 7 (SIGBUS)
release: Fedora release 14 (Laughlin)
How to reproduce: Don't know.
time: 1299772496
uid: 501
Comment 1 Jeffrey S Austin 2011-03-10 22:32:35 UTC 
Created attachment 483587 [details]
File: backtrace
Comment 2 Caolan McNamara 2011-03-11 08:28:11 UTC 
We get an occasional report of this, but there should be no particular reason for this to happen, unless e.g. the home dir is for some reason on a file system which claims that it could mmap a fail, but then fails on access of it. 

Is your home dir mounted over samba or nfs or anything exotic ?

*** This bug has been marked as a duplicate of bug 674416 ***
Note You need to log in before you can comment on or make changes to this bug.