Bug 697176 - [abrt] openoffice.org-brand-1:3.3.0-20.5.fc14: implts_setDockingAreaWindowSizes killed by signal 11 (SIGSEGV)
Summary: [abrt] openoffice.org-brand-1:3.3.0-20.5.fc14: implts_setDockingAreaWindowSiz...
Keywords:
Status: CLOSED ERRATA
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:90e3618fc79117d99cbfe025913...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-16 11:54 UTC by Marjan Grman
Modified: 2011-09-07 00:20 UTC (History)
1 user (show)

Fixed In Version: openoffice.org-3.3.0-20.7.fc14
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-07 00:20:24 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (88.21 KB, text/plain)
2011-04-16 11:54 UTC, Marjan Grman
no flags Details
pdf and doc file that tried to be open, in that order (105.87 KB, application/zip)
2011-04-17 07:41 UTC, Marjan Grman
no flags Details

Description Marjan Grman 2011-04-16 11:54:37 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 90332 bytes
cmdline: /usr/lib64/openoffice.org3/program/soffice.bin -quickstart -nologo -nodefault
comment: OO suite crashed, when I tried to open a doc file with a picture.
component: openoffice.org
Attached file: coredump, 132800512 bytes
crash_function: framework::LayoutManager::implts_setDockingAreaWindowSizes
executable: /usr/lib64/openoffice.org3/program/soffice.bin
kernel: 2.6.35.12-88.fc14.x86_64
package: openoffice.org-brand-1:3.3.0-20.5.fc14
rating: 4
reason: Process /usr/lib64/openoffice.org3/program/soffice.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1302954348
uid: 500

How to reproduce
-----
1. Ran OO Write from quick menu
2. Than tried to open .doc file from MS Word 2003
3. Than tried to open OO  spreadsheat from quick menu and than Write,... etc.

Comment 1 Marjan Grman 2011-04-16 11:54:40 UTC
Created attachment 492575 [details]
File: backtrace

Comment 2 Caolan McNamara 2011-04-16 14:00:05 UTC
If there is a specific document that triggers this, please attach one.

Comment 3 Marjan Grman 2011-04-17 07:41:32 UTC
Created attachment 492676 [details]
pdf and doc file that tried to be open, in that order

"pdf" created in fedora.
"doc" file created in MS Word 2003 format.

Comment 4 Marjan Grman 2011-04-17 07:42:04 UTC
Yes there is. And there is also a pdf file that I tried to open prior to that .doc file, so I am attacing that one as well, as it might come handy... It was created in fedora also by print command. I forgot to mention that, because so much happened, before it crashed. This pdf file was tried to be open by accidental click on it.

Comment 5 Caolan McNamara 2011-08-03 08:05:43 UTC
Can't reproduce this, but I can surmise that xDockAreaWindow is !is() at line 6060 for some reason

Comment 6 Caolan McNamara 2011-08-03 08:17:32 UTC
added bandaid in, will be in >= 3.3.0-20.7 if we do another update for F-14. Same code doesn't exist in later versions

Comment 7 Fedora Update System 2011-08-24 09:07:58 UTC
openoffice.org-3.3.0-20.7.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/openoffice.org-3.3.0-20.7.fc14

Comment 8 Fedora Update System 2011-08-26 19:05:35 UTC
Package openoffice.org-3.3.0-20.7.fc14:
* should fix your issue,
* was pushed to the Fedora 14 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing openoffice.org-3.3.0-20.7.fc14'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/openoffice.org-3.3.0-20.7.fc14
then log in and leave karma (feedback).

Comment 9 Fedora Update System 2011-09-07 00:19:53 UTC
openoffice.org-3.3.0-20.7.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.


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