Bug 591862 - [abrt] crash in SelectionEngine::SetSelectionMode
Summary: [abrt] crash in SelectionEngine::SetSelectionMode
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org   
(Show other bugs)
Version: 12
Hardware: i686 Linux
low
medium
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:3666b6f725d5c1d24a3ae8459f7...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-13 11:35 UTC by Manoj Kumar Suyal
Modified: 2010-05-18 11:59 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-18 11:59:12 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (55.83 KB, text/plain)
2010-05-13 11:35 UTC, Manoj Kumar Suyal
no flags Details

Description Manoj Kumar Suyal 2010-05-13 11:35:43 UTC
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/lib/openoffice.org3/program/scalc.bin -calc file:///home/manoj/Downloads/JAF%20ANI(INS)(29.04.2010).xls
component: openoffice.org
crash_function: SelectionEngine::SetSelectionMode
executable: /usr/lib/openoffice.org3/program/scalc.bin
global_uuid: 3666b6f725d5c1d24a3ae8459f74d4d50d9a3ae1
kernel: 2.6.32.11-99.fc12.i686
package: openoffice.org-calc-1:3.1.1-19.28.fc12
rating: 4
reason: Process /usr/lib/openoffice.org3/program/scalc.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

Comment 1 Manoj Kumar Suyal 2010-05-13 11:35:47 UTC
Created attachment 413723 [details]
File: backtrace

Comment 2 David Tardon 2010-05-13 13:03:18 UTC
Looks like a crash on opening a spreadsheet. Can you reproduce it with the same file? If yes, could you attach the file here?

Comment 3 Caolan McNamara 2010-05-18 11:59:12 UTC
Can't reproduce this. I think we need the document that triggered this. Feel free to reopen this issue if you can provide that document.


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