Closed Bug 246789 Opened 21 years ago Closed 20 years ago

infinite loop when launching from disk image

Categories

(Toolkit :: Startup and Profile System, defect)

Product:
Toolkit
Component:
Startup and Profile System
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
RESOLVED WORKSFORME
Milestone:
mozilla1.8final

People

(Reporter: bugzilla, Assigned: bugs)

References

Details

(Keywords: qawanted)

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040614 Firefox/0.9 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040614 Firefox/0.9 When the newly downloaded firefox 0.9 disk image is opened, if the application is launched straight from the mounted image it goes into an infinite loop of launching (dock icon bouncing), then failing after 3 seconds then retrying. Force Quit has no effect and since the system cancells logout if an application is launching, you have to do a hard reset. Reproducible: Always Steps to Reproduce: 1. launch fron the mounted disk image Actual Results: infinite loop Expected Results: fail with a warning? You could also stop people launching from the mounted image by putting a background image on the folder, telling people to copy the application to the Applications folder.
This is *probably* a duplicate of bug 246806. Disk images are read-only, so code that tries to write to the "application directory" is going to fail.
Status: UNCONFIRMED → NEW
Depends on: 246806
Ever confirmed: true
WFM using using... tested with http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/0.9/firefox-0.9-mac.dmg.gz On 10.3.4 (fresh install) but also running a day old trunk branch as well... Bernard, I assume Firefox started just fine after you moved it off the disc image? Have you been using an older version of firefox?
Ah looks like I was wrong... I stoped when the profile manager appeared... if I go past the profile manger... then yes I get this...
*** Bug 246929 has been marked as a duplicate of this bug. ***
> Bernard, I assume Firefox started just fine after you moved it off the disc > image? Have you been using an older version of firefox? Yes it did. I had an older version (0.8 release) installed at the time.
Blocks: 246456
*** Bug 246456 has been marked as a duplicate of this bug. ***
This is a larger problem (for me) than expected. After dragging the application out of the dmg, I immediately chown the entire package to some other user/group, and effectively strip any normal users of any write privilege on the application. This is good security practice, and SOP for me. Unfortunately, Firefox will not run unless "blessed" by first being run when writable. After the first successful launch, it appears that write privilege can then be revoked by chowning it away. With Firefox 0.9, it seemed that I was able to circumvent this problem by doing "cd Firefox.app/Contents/MacOS ; sudo ./redo-prebinding.sh" manually. This does not work with Firefox 0.9.1; it must be launched with write permission. ***Applications that need to write to themselves are very not good from a security perspective, and will flat-out fail under circumstances where appropriate security precautions have been taken. This bug also prevents Firefox from being run from a "live" boot CD, for example.***
*** Bug 250673 has been marked as a duplicate of this bug. ***
*** Bug 246127 has been marked as a duplicate of this bug. ***
*** Bug 251858 has been marked as a duplicate of this bug. ***
Flags: blocking-aviary1.0RC1?
clearing blocking flags... this is a dup of a bug I have already about not being able to run properly the first time when there isn't write access
Flags: blocking-aviary1.0RC1?
*** Bug 252704 has been marked as a duplicate of this bug. ***
I don't see other blocking bugs on this.
Assignee: bsmedberg → bugs
Flags: blocking-aviary1.0+
Flags: blocking-aviary1.0+ → blocking-aviary1.0mac+
If I make it writable, in my console log, 2004-08-31 01:23:23.319 firefox-bin[6395] Not prebound, launching update script 2004-08-31 01:23:24.818 update_prebinding[6400] Start of update_prebinding 2004-08-31 01:23:25.494 update_prebinding[6400] Start of search for binaries in packages... 2004-08-31 01:23:25.494 update_prebinding[6400] Discover library dependencies (0/1 complete) 2004-08-31 01:23:27.795 update_prebinding[6400] Discover library dependencies (1/66 complete) etc... This should never happen. The OS is responsible for prebinding. Making the app do it is questionable at best, and show-stopping for me, since I don't like it world-writable. There's also no guarantee that the app will be writable (e.g. so I can bring a CD around so I don't have to use IE). Relying on the OS to dynamically bind and then prebind should work fine in 99% of cases.
*** Bug 255841 has been marked as a duplicate of this bug. ***
wfm now in: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.3) Gecko/20040903 Firefox/1.0 PR (NOT FINAL)
Keywords: fixed-aviary1.0
*** Bug 247455 has been marked as a duplicate of this bug. ***
*** Bug 256750 has been marked as a duplicate of this bug. ***
*** Bug 260222 has been marked as a duplicate of this bug. ***
*** Bug 260151 has been marked as a duplicate of this bug. ***
I use Mac Os X 10.3.5 (Build 7M34). Since is began to use irefox version 0.8 i had Problems launsching the application. As i have tried out firefox launching will end in an infinte loop when launching form the disk image. This will end up an an competely consumption of RAM for firefox which will force the user to make a complete hard reset (force quit) doesn´t work since firefox is in a launching infinite loop) When i copied firefox to the desktop fiefox will first try to boot up fail then reboot and start which worked (this happend at the first launch of firefox). After a second launch of firefox firefox will start up much quicker and without need to reboot. Then i tried to copy firefox to my application folder. Than i launched firefox from the application folder and everything seemed to work smoothly. Please fix the launching infinte loop to use firefox out of the application folder. thanx
*** Bug 261590 has been marked as a duplicate of this bug. ***
*** Bug 261687 has been marked as a duplicate of this bug. ***
Actually, I'm not sure it is fixed I'm removing fixed-aviary1.0 so we'll get some QA. Can someone test with latest aviary-branch build?
Keywords: fixed-aviary1.0 → qawanted
*** Bug 260164 has been marked as a duplicate of this bug. ***
*** Bug 261808 has been marked as a duplicate of this bug. ***
Seems fixed to me... will need to do more testing... different systems... Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.3) Gecko/20041002 Firefox/0.10
It seems that for this bug, there are two cases: 1) launching from the disk image, and 2) launching when you've done a chmod a-w. Now, whilst we could fix this bug and allow users to do 1), it could be a better idea to detect the launch from the disk image, and pop up a dialog saying "Firefox is designed to be run from your hard drive. Please choose a place to install Firefox. [Quit] [Choose]". Then it copies itself over and re-launches. What do people think? Makes Firefox less pure? Unnecessary bloat? Would be OK if someone else coded it?
Other applications don't prompt the user that way, so Firefox doing so would be weird. You're correct that chmod a-w causes the same results; burning Firefox to a CD-ROM would behave the same way. This bug should be fixed so that the application doesn't need to be writable (comment 27 says it's fixed now; I haven't verified it myself), so Firefox works as expected in all these cases. Mac OS X users are used to copying applications out of disk images to install them, but they're also used to the application working from the disk image, which is handy if they just want to try it to see how well it works (which will be the case for a lot of people considering switching from Safari). I've just submitted bug 268794 which should make this issue obsolete on Mac OS X 10.2.3 and later.
*** Bug 262559 has been marked as a duplicate of this bug. ***
moving blocking1.0mac bugs to Firefox1.1 Target Milestone.
Target Milestone: --- → Firefox1.1
*** Bug 273031 has been marked as a duplicate of this bug. ***
*** Bug 260236 has been marked as a duplicate of this bug. ***
at least a readme would be nice. This infinite loop is terrible, and preventable! (Using Sunbird 0.2)
OK, how about this: "Firefox is designed to be run from your hard drive. Please copy Firefox to your Applications folder before running it. [Quit]" Simple, and preferable to an infinite loop...
Depends on: 286421
See also bug 286421.
Flags: blocking-aviary1.1?
Status: NEW → RESOLVED
Closed: 20 years ago
Flags: blocking-aviary1.1?
Flags: blocking-aviary1.0mac+
Resolution: --- → WORKSFORME
Some Mac programs come as a disk image which, when mounted, copies its contents to a folder on the desktop (and then usually puts the disk image in the trash). Should firefox do this?
That's bug 268794.
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.