Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
I get this:
*** glibc detected *** /usr/lib64/openoffice.org3/program/swriter.bin: malloc(): memory corruption (fast): 0x00007f52f5bfbc40 ***
/usr/lib64/openoffice.org3/program/soffice: line 123: 10534 Segmentation fault (core dumped) "$sd_prog/$sd_binary" "$@"
or this:
swriter.bin: ath.c:193: _gcry_ath_mutex_lock: Assertion `*lock == ((ath_mutex_t) 0)' failed.
/usr/lib64/openoffice.org3/program/soffice: line 123: 10645 Aborted (core dumped) "$sd_prog/$sd_binary" "$@"
crash when I try to copy text from http://pruned.blogspot.com/2011/04/atomic-gardens.html.
I selected everything from "\\\\\ Atomic Gardens" to "peter" at the end -> Ctrl-C and then Ctrl-V in oowriter, then immediately scrolled upwards and got the crash. Similar issue is on Fedora-16 with LO but there I saw SIGSEGV in Java in ~/.xsession-errors, unlike here.
The last I can see before crash is loading of remote images, it may be related to the crash.
Version-Release number of selected component (if applicable):
openoffice.org-core-3.2.1-19.6.el6_0.5.x86_64
java-1.6.0-openjdk-1.6.0.0-1.41.1.10.4.el6.x86_64
How reproducible:
always
Probably gcrypt + neon + cups locking woes, e.g. bug #553834, bug #569803 but #544619 and so forth. See https://bugs.g10code.com/gnupg/issue1197 for some discussion. We can backport some of the extra "treat neon as thread-unsafe and lock it ourselves" workarounds we have in later versions of LibreOffice to help.
If you have a Fedora 16 crash, let the abrt tool report it for you so we can get the backtrace for it.
(In reply to comment #2)
> If you have a Fedora 16 crash, let the abrt tool report it for you so we can
> get the backtrace for it.
Unfortunately it wasn't caught by ABRT on F-16 since the crash was in Java (I think there are some limitation to treating Java SEGV in ABRT). But I'll investigate it for sure.
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.