Issue 45513 - crash report crash on reporting a Base crash
Summary: crash report crash on reporting a Base crash
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: *Testproduct
Classification: Test
Component: ui (show other issues)
Version: OOo 2.0
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: OOo 2.0
Assignee: issues@test
QA Contact: issues@test
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2005-03-19 22:17 UTC by leeshipley
Modified: 2005-07-25 22:07 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description leeshipley 2005-03-19 22:17:59 UTC 
I am not even sure if I am in the right place to do this so bear with me.

I am simply trying to report a bug using the automatic bug reporter.  I tried
twice and twice it collapsed into a Microsoft Bug Report.

Initially though, I was trying to send through a crash report that surfaced
because I used "Base"  thinking that this was the base introduction, got
frightened by what I saw and bailed out hitting the finish button leaving the
system trying to recover from a database error.  It had not occured to me that I
was in a database wizard because I was in new user tunnel vision mode.  Yes,
even someone with 30 years IT experience goes dumb when facing a new and complex
program like OOO.  
Suggest a simple kiss-off splash on completion of the installation dialog that
tells what components are available and where--it would prevent a great deal of
aggrevation.

Best wishes,
Comment 1 flibby05 2005-04-21 14:15:41 UTC 
crash reporter was significantly improved since beta2.0,
the described behvaiour should not happen anymore.
closing for now,
please reopen if needed
Comment 2 flibby05 2005-04-21 14:15:53 UTC 
.