Closed Bug 248441 Opened 21 years ago Closed 19 years ago

Does not start when installed by admin account and accessed by user account.

Categories

(Thunderbird :: General, defect)

PowerPC
macOS
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: bkerstetter, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/125.2 (KHTML, like Gecko) Safari/125.8 Build Identifier: Thunderbird / 0.7 I installed Mac OS X 10.3.4 on a new drive, then installed TB 0.7 in the Applications folder using the admin account. This is the first install of TB on the system. When running from a user account--not the admin account---TB 0.7 does not start. It bounces twice in the Dock, then quits. Gave my user account ownership of TB 0.7 and nothing changed---same old bounce, bounce, quit. Then dragged it (copied it) on to the desktop of the user account and it started up just fine. Added an IMAP account. Worked okay. This is repeatable. Reproducible: Always Steps to Reproduce: 1. Installs as admin 2. run as user 3. Drag to user desktop 4. Run Actual Results: After step 2, does not run. bounce, bounce, quit. After step 4, does run, but this bad. Expected Results: It should run as a users when installed as an Admin ins Applications folder. Ouch!
Seems to be a problem already described in "Known Issues" section of Release Notes of Thundebird 0.7. (Same description is also written in Release Notes of Firefox 0.9) (Descrition in "Known Issues" section) > If Thunderbird 0.7 is placed in a location with limited access privileges, > it should be run by a user with access to that location first, so that all > initial startup files are generated. There may be issues still where > if a restricted-access user is the first to run the app, these files may not be > generated properly and Thunderbird may enter an infinite restart loop. > This will be fixed in a future release. Haven't you read Release Notes?
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
this is no longer a problem. it's fixed.
I agree, this was fixed somewhere along the line. Since I'm not about to dig up the original bug, I'm marking worksforme.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.