Bug 707580 - [abrt] openoffice.org-writer-1:3.3.0-20.5.fc14: SwModify::Add: Process /usr/lib/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] openoffice.org-writer-1:3.3.0-20.5.fc14: SwModify::Add: Process /usr/l...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:643079098fc9d7438a722835e2d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-25 12:40 UTC by David Tonhofer
Modified: 2011-08-03 09:44 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-03 09:44:38 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (52.64 KB, text/plain)
2011-05-25 12:40 UTC, David Tonhofer
no flags Details
Document that caused, recovered (as far as I know) (15.47 KB, application/vnd.oasis.opendocument.text)
2011-05-27 12:49 UTC, David Tonhofer
no flags Details

Description David Tonhofer 2011-05-25 12:40:39 UTC
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 53901 bytes
cmdline: /usr/lib/openoffice.org3/program/swriter.bin -writer file:///home/hobbes/original_speak_description.odt
component: openoffice.org
Attached file: coredump, 106967040 bytes
crash_function: SwModify::Add
executable: /usr/lib/openoffice.org3/program/swriter.bin
kernel: 2.6.35.13-91.fc14.i686
package: openoffice.org-writer-1:3.3.0-20.5.fc14
rating: 4
reason: Process /usr/lib/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: 1. Selecting/Marking tables 
time: 1306324536
uid: 500

Comment 1 David Tonhofer 2011-05-25 12:40:41 UTC
Created attachment 500799 [details]
File: backtrace

Comment 2 David Tardon 2011-05-26 10:30:49 UTC
Can you reproduce the crash? It didn't happen when "selecting tables", but when copying (a part of) a table from one document to another. I could put in a band-aid to avoid this particular crash quite easily, but it would be much better to know why it happened.

Comment 3 David Tonhofer 2011-05-26 10:44:20 UTC
Hi David,

I can try. Note that what happened was an accident - an intempestive mouse movement selecting and possibly copying tables in about a quarter of a second also resulting in a dangerous movement of the coffee mug.

Will be back if I can reproduce it (or not)

Comment 4 David Tonhofer 2011-05-26 20:36:55 UTC
So far, no accident.

Would it help if I sent you the recovered doc (at least I think it is the recovered doc; I don't seem to have worked on it...) It's not exactly confidential.

Comment 5 David Tardon 2011-05-27 04:13:17 UTC
Probably not, but it is worth a try. Just add it as an attachment here.

Comment 6 David Tonhofer 2011-05-27 12:49:19 UTC
Created attachment 501297 [details]
Document that caused, recovered (as far as I know)

Comment 7 Caolan McNamara 2011-08-03 09:44:38 UTC
Was't able to reproduce this, valgrind is silent.


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