Bug 506239 - soffice bug report from system
Summary: soffice bug report from system
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 11
Hardware: i386
OS: Linux
low
low
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-16 09:49 UTC by Cyrus Taraporvala
Modified: 2009-06-18 16:29 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-06-18 16:29:11 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
soffice-bugreport (604.35 KB, text/plain)
2009-06-16 09:49 UTC, Cyrus Taraporvala
no flags Details

Description Cyrus Taraporvala 2009-06-16 09:49:20 UTC
Created attachment 348074 [details]
soffice-bugreport

Description of problem: Received a crash report from the system, after I closed OpenOffice Writer.


Version-Release number of selected component (if applicable): Current with F11 release


How reproducible: Closed an OpenOffice Writer document and re ceived this enclosed report. 


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Caolan McNamara 2009-06-17 13:36:20 UTC
Hmm, this particular crash report is unusual as I would have expected to see a different crash reporter dialog in the case of OOo crashing. Does OOo always crash if you load that document up in it and then try and close OOo ? If it does can you attach the document here ?

Comment 2 Cyrus Taraporvala 2009-06-18 04:50:58 UTC
No , it doesn't always crash. I have upgraded to F11 from F10 through 'preupgrade' only recently.

I cannot remember which 'Writer' document this relates to, as I have a few in relation to university work. I know that when I closed the document (I save them as .doc), I closed it from the browser window (X), and not 'File >> Quit'.

Sorry that I cannot provide any more information, just that the system asked me to send that report in, and I did so.

Thanks,

Cyrus Taraporvala

Comment 3 Caolan McNamara 2009-06-18 16:29:11 UTC
Ah well, that's a pity. I can't fix this (but personally I suspect its an error outside of OOo in some other component that affects OOo) but hopefully it'll get fixed through another route.


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