Closed Bug 435070 Opened 17 years ago Closed 17 years ago

This has to do with the u3 version, and the registry on startup

Categories

(Thunderbird :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: jayren, Unassigned)

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727) Build Identifier: thunderbird version 1.5.0.14 (20071210) The app asks if it is the default reader upon startup, and the computer I use has registry editing disabled for normal users. This shouldn't be a problem because the U3 environment should handle all registry concerns. Another application that makes heavy use of the registry has a u3 version that does no such erroring. The u3 version of this application has a "helper application" however, and I am not sure what this helper application is doing. Reproducible: Always Steps to Reproduce: 1. Start thunderbird u3 version 2. error on check for default. Actual Results: The windows machine produced a dialog box saying that registry editing had been disabled and I should contact my system administrator. Expected Results: Like the other u3 application that uses the registry, it should have behaved itself and not tried to poke at the registry on the computer which it might or might not be able to edit.
This is not a support/problem reporting forum for the u3 version of Thunderbird. Only if you can replicate the problem with a standard Thunderbird installation should you report it here. (In reply to comment #0) > Build Identifier: thunderbird version 1.5.0.14 (20071210) I would recommend updating your Thunderbird to the latest available from u3: http://portableapps.com/apps/internet/thunderbird_portable The also see http://portableapps.com/support/thunderbird_portable#modifications it appears the default mail client check has been disabled for that version, therefore this should fix your problem.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.