abrt version: 1.1.14 architecture: x86_64 Attached file: backtrace cmdline: /usr/lib64/openoffice.org3/program/soffice.bin -quickstart -nologo -nodefault component: openoffice.org crash_function: bridges::cpp_uno::shared::VtableFactory::initializeBlock executable: /usr/lib64/openoffice.org3/program/soffice.bin kernel: 2.6.35.10-74.fc14.x86_64.debug package: openoffice.org-brand-1:3.3.0-19.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: 1296414030 uid: 501
Created attachment 476471 [details] File: backtrace
A SIGBUS is typically unavoidable by an app, e.g. mmap of a file and the filesystem disappears. Is your /home dir a network mount over samba of nfs or anything odd like that ?
Shouldn't have SIGBUSed clearly, but OOo follows the same pattern as libgcj to get some filesystem on which it can mmap some executable memory, i.e. http://www.akkadia.org/drepper/selinux-mem.html I don't think we can do more than that.
*** Bug 684029 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 767708 ***