Closed Bug 531152 Opened 15 years ago Closed 13 years ago

FastStartup component shouldn't start up when launched with -silent

Categories

(Toolkit :: Startup and Profile System, defect)

defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: Gavin, Unassigned)

References

Details

See bug 530676. The installer was launching fennec.exe -silent and expecting the process to terminate, but FastStartup kicked in so the process never exited. I don't think it's expected that -hidden runs will have faststart, and if that's desired you can already use faststart-hidden, so I think -hidden should imply no faststart.

Since FastStartup is registered to run first ("00-faststartup" vs. "y-default"), I think it can just avoid doing faststartup if findFlag("silent") != -1.
If we do this, we'll need to change the wince installer to use -faststart-hidden to maintain it's current behavior of launching with faststart. Bug 529678 may also make this an option.
I think it should simply not enable itself at all, unless -faststart-hidden is provided.
Hmm, good point. I was kind of assuming that we wanted it to start for "normal" invocations, but maybe limiting it to only starting from installer-created shortcuts would be a good thing?
Right, that was my original intent actually.  I changed it for a couple of reasons I'm now struggling to remember, and I think we should go back.
Blocks: 529678
Depends on: 652445
Faststart was removed in bug 652445, since it only ever worked properly with WinCE, for which support has now been removed.

-> WONTFIX (until/if such point where functional faststart support on relevant platforms is added back in; although likely no longer going to happen, given bug bug 627591 [windows] and bug 632404 [linux])
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.