Closed Bug 428254 Opened 16 years ago Closed 16 years ago

File manager crashes when using "Send to" on right mouse click

Categories

(Thunderbird :: General, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: djolence, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.13) Gecko/20080311 Firefox/2.0.0.13
Build Identifier: 2.0.0.12

When I try to send file(s) to Thunderbird (default email client) from file manager (Total Commander, Windows Expolorer,...) using right mouse click and "Send to/Mail Recipient", my file manager crashes

Reproducible: Always

Steps to Reproduce:
1.set Thunderbird as default email client
2.select file(s) in file manager (Total Commander, Windows Explorer,...)
3.right mouse click and select "Send to/Mail Recipient"
Actual Results:  
1. selected files are sent to the Thunderbird
2. few seconds after that the file manager crashes

Expected Results:  
1. All settings in MS Registry, related to default email client should be rechecked
2. Command line for Thunderbird should be rechecked

This problem happens on my office computer, on my home computer as well as on my notebook computer.
I am using Windows XP SP2.
Before Thunderbird I was using Netscape 7.2 as default email client. On my office and home computers I've migrated all email from Netscape 7.2 to the Thunderbird.
On my notebook computer I've defined new (empty) profile, just to check is the problem related to previous email in the Netscape.
When I was using Netscape 7.2 as default email client everything worked perfectly.
Version: unspecified → 2.0
->INVALID. I don't see how thunderbird could fix this. If another program crash, that is a bug in the other program. 

Resetting thunderbird as default email client could possibly help fix the registry problems.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
you can use regmon from sysinternals.com (microsoft.com)  to compare the settings on working and broken computers. if you can show logs and explain what's different that causes the problem, perhaps someone might do something. but yes, in general, unless our library is in their process, it isn't our fault.
You need to log in before you can comment on or make changes to this bug.