Issue 45513

Summary:	crash report crash on reporting a Base crash
Product:	*Testproduct	Reporter:	leeshipley <leeshipley>
Component:	ui	Assignee:	issues@test <issues>
Status:	CLOSED IRREPRODUCIBLE	QA Contact:	issues@test <issues>
Severity:	Trivial
Priority:	P3	CC:	flibby05, issues
Version:	OOo 2.0	Keywords:	oooqa
Target Milestone:	OOo 2.0
Hardware:	PC
OS:	Windows XP
Issue Type:	DEFECT	Latest Confirmation in:	---
Developer Difficulty:	---

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