Opened 12 years ago
Closed 12 years ago
#9427 closed bug (fixed)
FirstBootPrompt appears after installation when you first start.
Reported by: | Premislaus | Owned by: | mmadia |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Applications/FirstBootPrompt | Version: | R1/Development |
Keywords: | Cc: | stippi | |
Blocked By: | Blocking: | ||
Platform: | x86 |
Description (last modified by )
FirstBootPrompt appears after installation when you first start. This happening in the nightly builds. Just click on the Boot to Desktop. After that this no longer occurs.
I run Haiku from the CD. Because I do not have installed BootManager.
Change History (7)
comment:1 by , 12 years ago
Component: | Applications/ReadOnlyBootPrompt → Applications/FirstBootPrompt |
---|---|
Description: | modified (diff) |
Summary: | ReadOnlyBootPrompt appears after installation when you first start. → FirstBootPrompt appears after installation when you first start. |
comment:2 by , 12 years ago
Owner: | changed from | to
---|---|
Status: | new → in-progress |
comment:3 by , 12 years ago
comment:4 by , 12 years ago
Cc: | added |
---|
comment:5 by , 12 years ago
The idea was always that FirstBootPrompt *writes* the settings, even on read-only media, and actually relies on the presence of the write overlay so that the virtually written settings are then copied by the Installer as a real file in the target installation, thereby carrying over the choice that the user made for language and keyboard layout. It's been too long and I cannot really comment on the patch.
comment:6 by , 12 years ago
Currently FirstBootPrompt will only write the settings if the default values are changed. If a user simply clicks the 'Installer' or 'desktop' buttons, the Locale settings will not be written.
comment:7 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | in-progress → closed |
A tweaked version of my diff in comment:3 was applied in hrev45286. Now, FirstBootPrompt will write the settings upon launch (in addition to whenever they're changed by the user). FirstBootPrompt will always launch on read-only mediums. For non-read-only medium, FirstBootPrompt will launch only if "Locale settings" does not exist.
stippi, would having FirstBootPrompt write the settings immediately upon launch be proper? The following "works", but i'm not sure if the Locale settings file should be written prior to running PopulateLanguages() and _PopulateKeymaps().
If so, then Bootscript could be changed to launch FirstBootPrompt always on read-only mediums and whenever the Locale settings file does not exist.