Abiword 2.8.1 freezes with document lost when help is clicked or F1 is pressed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
AbiWord |
Fix Released
|
Medium
|
|||
Release Notes for Ubuntu |
Fix Released
|
Undecided
|
Unassigned | ||
abiword (Fedora) |
Fix Released
|
High
|
|||
abiword (Ubuntu) |
Fix Released
|
Critical
|
Andrew Starr-Bochicchio | ||
Lucid |
Fix Released
|
Critical
|
Martin Erik Werner |
Bug Description
PROBLEM
Every time help is clicked, including all items under Help in the menu, except 'About Abiword', Abiword freezes and the document you are working in is lost.
TEST CASE
1. Launch Abiword
2. Press [F1]
* Abiword locks up
PATCH
Patch by Michal Schmidt from https:/
"remove harmful calls to xml{Init,
...And were not originally related to the specific crash reported here (it seems).
OTHER
ProblemType: Bug
Architecture: i386
Date: Tue Feb 9 15:42:15 2010
DistroRelease: Ubuntu 10.04
InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/
Package: abiword 2.8.1-2ubuntu1
ProcEnviron:
PATH=(custom, user)
LANG=en_US.utf8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: abiword
Uname: Linux 2.6.32-12-generic i686
Changed in abiword (Ubuntu): | |
importance: | Undecided → High |
Changed in abiword: | |
status: | Unknown → Confirmed |
tags: | added: iso-testing |
Changed in abiword (Ubuntu Lucid): | |
status: | Confirmed → Triaged |
tags: | added: xubuntu |
Changed in abiword: | |
status: | Confirmed → Unknown |
Changed in abiword: | |
status: | Unknown → Fix Released |
Changed in abiword (Ubuntu): | |
assignee: | nobody → arand (arand) |
status: | Triaged → In Progress |
Changed in abiword (Ubuntu): | |
assignee: | arand (arand) → Andrew Starr-Bochicchio (andrewsomething) |
tags: |
added: verification-done removed: verification-needed |
Changed in abiword: | |
importance: | Unknown → Medium |
Changed in abiword (Fedora): | |
importance: | Unknown → High |
status: | Unknown → Fix Released |
Heya, abiword should not call xmlCleanupParser(), otherwise it will break PA because it deletes TLS variables that do not belong to it. See the end of this clone bug report:
+++ This bug was initially created as a clone of Bug #532307 +++
abrt detected a crash.
How to reproduce
-----
1.
2.
3.
Comment
-----
I was not working with Empathy when this crash happened, it ran on background.
Additional information
======
Attached files
----
backtrace
cmdline
-----
empathy
component
-----
empathy
executable
-----
/usr/bin/empathy
kernel 5-96.fc12. i686.PAE
-----
2.6.31.
package 2.28.1. 1-3.fc12
-----
empathy-
reason
-----
Process was terminated by signal 6
--- Additional comment from <email address hidden> on 2009-11-01 14:14:52 CET ---
Created an attachment (id=367009)
File: backtrace
--- Additional comment from <email address hidden> on 2009-11-04 14:24:14 CET ---
Again the same crash today.
--- Additional comment from <email address hidden> on 2009-11-04 19:24:45 CET ---
Looking at the backtrace it looks like this crash is caused by pulseaudio. Reassigning bug.
--- Additional comment from <email address hidden> on 2009-11-05 02:49:33 CET ---
Hmm, that's pthread_ setspecific( ) failing. I don't see how that could ever fail, especially since we call pthread_ getspecific( ) right before.
Is there any reliable way to reproduce this? I'd be very interested in the exact return value if pthread_ setspecific( ) there.
--- Additional comment from <email address hidden> on 2009-11-05 07:27:51 CET ---
It crashes about once a day. I'll try get the return value.
--- Additional comment from <email address hidden> on 2009-11-08 21:39:43 CET ---
*** Bug 533726 has been marked as a duplicate of this bug. ***
--- Additional comment from <email address hidden> on 2009-11-08 21:44:31 CET ---
*** Bug 533576 has been marked as a duplicate of this bug. ***
--- Additional comment from <email address hidden> on 2009-11-09 20:55:44 CET ---
*** Bug 533923 has been marked as a duplicate of this bug. ***
--- Additional comment from <email address hidden> on 2009-11-10 03:41:15 CET ---
Any luck so far?
--- Additional comment from <email address hidden> on 2009-11-10 09:58:10 CET ---
It seems this bug is triggered much less when Empathy runs within gdb. setspecific( ) return value (gdb crashed when I tried to reload debug infos).
It crashed on Friday, but I failed to get the pthread_
I still run Empathy with gdb.
I'll try to add some debugging output to PulseAudio and recompile it. Then I can run it without gdb.
--- Additional comment from <email address hidden> on 2009-11-11 21:20:46 CET ---
When I download pulseaudio fedora CVS repository, run "make local" in F-12 and install the result (all rpms, or just the pulseaudio-0.9.19-2 rpm, or just libpulsecore-*.so), the pulseaudio daemon cannot start.
Nov 11 21:03:33 localhost pulseaudio[2718]: fdsem.c: Assertion 'pa_atomic_dec(&f fdsem.c: 283, function pa_fdsem_before
->data->waiting) >= 1' failed at pulsecore/
_poll(). Aborting.
Is there some other way to run the patched version?
--- Additional comment from <email address hidden> on 2009-11-16 15:49:16 CET ---
This bug appears to have been reported against 'rawhide' during the Fedora ...