Bug 680957 - [abrt] openoffice.org-impress-1:3.2.0-12.35.fc13: SfxViewShell::GetController: Process /usr/lib64/openoffice.org3/program/simpress.bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] openoffice.org-impress-1:3.2.0-12.35.fc13: SfxViewShell::GetController...
Keywords:
Status: CLOSED DUPLICATE of bug 674330
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 13
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:fbf7c50ab977f684872b29dd8d6...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-28 16:06 UTC by Leonardo Brenta
Modified: 2011-02-28 18:15 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-28 18:15:43 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (58.57 KB, text/plain)
2011-02-28 16:06 UTC, Leonardo Brenta
no flags Details

Description Leonardo Brenta 2011-02-28 16:06:13 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/openoffice.org3/program/simpress.bin -impress file:///home/lbrenta/.evolution/cache/tmp/evolution-lbrenta-aBKc6q/PUBLICIDADES_IMPACTANTES.pps
component: openoffice.org
crash_function: SfxViewShell::GetController
executable: /usr/lib64/openoffice.org3/program/simpress.bin
kernel: 2.6.34.7-66.fc13.x86_64
package: openoffice.org-impress-1:3.2.0-12.35.fc13
rating: 4
reason: Process /usr/lib64/openoffice.org3/program/simpress.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1298906661
uid: 500

How to reproduce
-----
1.
2.
3.
0

Comment 1 Leonardo Brenta 2011-02-28 16:06:18 UTC
Created attachment 481404 [details]
File: backtrace

Comment 2 David Tardon 2011-02-28 18:15:43 UTC
We have workaround for this crash, but we would still like to know how it happens. Can you reproduce it?

*** This bug has been marked as a duplicate of bug 674330 ***


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