Closed Bug 384641 Opened 18 years ago Closed 6 years ago

thunderbird installer launches thunderbird when exit by killing/closing window

Categories

(Thunderbird :: Installer, defect)

x86
Windows XP
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: emoore, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4 Build Identifier: Thunderbird version 2.0.0.4 (20070604) If I install Thunderbird 2.0.0.4 under XP Pro SP2 the last window in the setup program asks if I want to launch Thunderbird. If I don't press any of the buttons and attempt to exit the program by pressing the 'X' control to close the window it launches Thundebird. I assume it does that because it just checks whether the checkbox was still checked, rather than explicitly checking both the checkbox is checked and that the user pressed the okay button. While this is easy for a user to workaround the install program should not behave unexpectedly. The user is given the impression that Thunderbird has finished installing and its a common idiom to abort a program by pressing the 'X' control to close the main window. I assume this behavior occurs with earlier versions but I haven't bothered testing them. Reproducible: Always
still reproducible with trunk version 3.0a1pre (2008040204)
Status: UNCONFIRMED → NEW
Ever confirmed: true
Thanks Nikolay. This is similar to bug 380862, which involves bug 345067. a good exercise is for someone to check if profile manager has similar issue(s) ;-) sev=minor is correct since there is a workaround
Depends on: 345067
Summary: thunderbird installer launches thunderbird when exit by killing window → thunderbird installer launches thunderbird when exit by killing/closing window
Version: unspecified → Trunk
why mark this bug ver=trunk? the fix might be delivered via trunk, but the problem is not trunk-only, no?
apply to current build of TB 2.0.0.12 also
(In reply to comment #3) > why mark this bug ver=trunk? > the fix might be delivered via trunk, but the problem is not trunk-only, no? If a bug is happening on trunk the version field should be upgraded. Fixes for branches are shown by the appropriate fixed keywords.
I don't think your definition is SOP. And I've never seen version= as being reflective of where a *patch* lands. It's supposed to define where bug behavior is seen. Further, patches are frequently coded first to trunk, so by your definition almost all bugs should be marked version=trunk. but that clearly doesn't make much sense.
(In reply to comment #2) > a good exercise is for someone to check if profile manager has similar issue(s) Profile manager doesn't affect by this issue in trunk.
(In reply to comment #6) > And I've never seen version= as being reflective of where a *patch* lands. It's > supposed to define where bug behavior is seen. There was already a long debate about this a long time ago. I don't want to start again... Because I can also see this with an installer of a current trunk build I set the version to trunk. It makes it easier to understand. Even this wont be fixed for Thunderbird2 because its not a security bug.
On my win7 system, thunderbird nightly build custom install, the X is disabled/not clickble
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.