Closed
Bug 582936
Opened 15 years ago
Closed 13 years ago
Upgrade from 3.06 to 3.1 causes problems with Login Items
Categories
(Core :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: pgleesonuk, Unassigned)
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; F-6.0SP2-20041109; InfoPath.1; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022; .NET CLR 1.1.4322; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Build Identifier: Snow Leopard 10.6.4
I was running Thunderbird 3.06 with it as one of my Login items with the hidden attribute. On login thunderbird starts, checks for emails, but remains hidden (ie: on window on the screen)
After the upgrade to 3.1 the login item hidden attribute is ignored and at login a thrunderbird window is always openned.
I tried resetting login items, removing thunderbird, re adding it, but the problem remains.
Down-grading to 3.06 restores the correct behaviour.
Down-grading was done by restoring the thunderbird application from a time machine backup. No other changes to profiles etc.
Reproducible: Always
Steps to Reproduce:
1. upgrade to 3.1
2. set thunderbird as login item with hide attribute set
3. restart or log out
Actual Results:
thunderbuird 3.1 ignores the hide attribute of the login item
Expected Results:
thunderbird 3.1 start but remains hidden
Downgradinf to 3.06 fixes the issue
remains hidden at restart / login
Comment 1•15 years ago
|
||
Does Firefox exhibits the same behavior ?
| Reporter | ||
Comment 2•15 years ago
|
||
Yes it does with the latest version
Updated•15 years ago
|
Component: OS Integration → General
Product: Thunderbird → Core
QA Contact: os-integration → general
Comment 3•13 years ago
|
||
Please close the bug WORKSFORME if you no longer see the problem when using a current version.
Or, if you do see the problem, please comment with details.
Whiteboard: [closeme 2012-07-15]
Resolved per whiteboard
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2012-07-15]
You need to log in
before you can comment on or make changes to this bug.
Description
•