Bug 693265 - [abrt] openoffice.org-writer-1:3.3.0-20.2.fc14: unhandled exception in graphic swapin (SIGSEGV)
Summary: [abrt] openoffice.org-writer-1:3.3.0-20.2.fc14: unhandled exception in graphi...
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:ebcb0d4aec45b5ba1f896e9ac84...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-04 04:10 UTC by Mohammed Arafa
Modified: 2011-09-07 00:20 UTC (History)
2 users (show)

Fixed In Version: openoffice.org-3.3.0-20.7.fc14
Clone Of:
Environment:
Last Closed: 2011-09-07 00:20:19 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (126.73 KB, text/plain)
2011-04-04 04:10 UTC, Mohammed Arafa
no flags Details

Description Mohammed Arafa 2011-04-04 04:10:05 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 129775 bytes
cmdline: /usr/lib64/openoffice.org3/program/swriter.bin -writer '/tmp/kde-marafa/arkFU6Ih3//New p770 Frame Build.doc'
component: openoffice.org
Attached file: coredump, 198017024 bytes
crash_function: getTypeName
executable: /usr/lib64/openoffice.org3/program/swriter.bin
kernel: 2.6.35.11-83.fc14.x86_64
package: openoffice.org-writer-1:3.3.0-20.2.fc14
rating: 4
reason: Process /usr/lib64/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1301887224
uid: 500

How to reproduce
-----
1.
2.
3. opened a docx.zip file that was extracted

Comment 1 Mohammed Arafa 2011-04-04 04:10:09 UTC
Created attachment 489701 [details]
File: backtrace

Comment 2 David Tardon 2011-04-04 05:21:42 UTC
Exactly how the zip file was extracted? The path '/tmp/kde-marafa/arkFU6Ih3//New p770 Frame Build.doc' suggests automatic extraction from a file manager (I guess the file manager in KDE, whatever it is called these days). The stack looks like the .doc was removed after opening, so Writer was not able to get an image from it (images are loaded on demand, when the page they are on is actually displayed). I do not think it should crash in that situation, though :)

Can you reproduce the crash? If yes, could you write a bit more detailed steps to reproduce? Did you perhaps close the file manager's window after the file was opened? This would probably cause the temp. extracted file to be deleted...

Comment 3 Mohammed Arafa 2011-04-06 00:52:54 UTC
ok i havent attempted to reproduce the bug. but what you say sounds very much like what i did. and yes i did use ark - the kde archiver to extract the file.

it was an attachment in gmail which was opened with ark then double clicking on the file within the archiver opened ooffice.

i guess i then closed ark

Comment 4 Caolan McNamara 2011-08-02 16:05:20 UTC
Fix to avoid crash will be in >= 3.3.0-20.7 if we do another update for F-14

Comment 5 Fedora Update System 2011-08-24 09:07:53 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 6 Fedora Update System 2011-08-26 19:05:29 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 7 Fedora Update System 2011-09-07 00:19:47 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.