Issue 44930 - Crash Reports crash program when sending to OOo
Summary: Crash Reports crash program when sending to OOo
Status: CLOSED DUPLICATE of issue 39622
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 2.0 Beta
Hardware: PC Windows 98
: P3 Trivial (vote)
Target Milestone: ---
Assignee: hennes.rohling
QA Contact: issues@framework
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2005-03-13 13:11 UTC by swissmac
Modified: 2005-05-12 11:58 UTC (History)
3 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 swissmac 2005-03-13 13:11:50 UTC 
On restart after a crash has occurred, the Crash Report tool opens up and
requests to be sent to OOo. Selecting the topmost of the three options (use
system settings) for sending the crash report caused program to crash. This made
it almost impossible to notify OOo of defects in the program, especially as for
normal non-technical users like me the bug reporting mechanism is non-trivial to
learn and use.

I would suggest crash reports are sent via the users default email program, and
that the bug report search system is simplified considerably. All those
categories are only useful if the correct information is entered, and currently
it is not clear what information this should be. Most users will just ignore
anything complex and you will never learn what went wrong and they will revert
to using their existing software.
Comment 1 atr 2005-03-14 09:02:20 UTC 
atr: Hi Joost, please have a look.
Comment 2 flibby05 2005-04-21 13:43:10 UTC 
summarizing reporters comment:

"I would suggest crash reports are sent via the users default email program, and
that the bug report search system is simplified considerably."


defect -> enhancement

reassign
Comment 3 Joost Andrae 2005-04-21 14:26:39 UTC 
ja->swissmac: sending crash reports via email has been tested but the current
solution has been proven to be far more user friendly. If you use email then
there has to be an email program configured and this email program needs to have
an application programming interface which doesn't change. As there are zillions
of different email clients available it's not manageable to use this way. A
solution by using a SOAP request sent via http is better.

ja: changing issue type back to defect.
ja->hro: please take a look at this issue. There seems to be a problem with
internet settings on system level on Win98. I think we should have a deeper look
into this area. Reassigned to you.
Comment 4 peschtra 2005-04-22 02:05:48 UTC 
You need to only include one issue per issue. You have both a defect and an RFE
in the same issue, as others have mentioned.

This is a duplicate of 39622.

*** This issue has been marked as a duplicate of 39622 ***
Comment 5 hennes.rohling 2005-05-12 11:58:02 UTC 
closed.