#7595 closed bug (fixed)
Can't start BootManager
Reported by: | idefix | Owned by: | axeld |
---|---|---|---|
Priority: | normal | Milestone: | R1/alpha3 |
Component: | Applications/Installer | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
Installer
won't start BootManager
when the mime-info database isn't updated.
Steps to reproduce:
- Download an R1 Alpha3 RC cd-image (eg. haiku-r1a3-rc-r41789-cd.tar.xz)
- Boot from the cd
- Choose
Run Installer
inReadOnlyBootPrompt
- Select
Tools
-Set up boot menu
- You get a warning stating "Bootman, the application to configure the Haiku boot menu, could not be launched."
To fix this, the code in InstallerWindow.cpp should be changed to search for BootManager
in the apps
folder.
Also, the warning should read "BootManager, the application to configure the Haiku boot menu, could not be launched."
Attachments (1)
Change History (8)
by , 13 years ago
Attachment: | installer.patch added |
---|
Fix launching of BootManager when mime database is incomplete
comment:2 by , 13 years ago
patch: | 0 → 1 |
---|
comment:3 by , 13 years ago
Would updating the warning text from "Bootman" to "BootManager" partially break Installer's catalog files?
comment:4 by , 13 years ago
"Break" is too hard a word. It'll invalidate the string and add a new one that needs to be translated again. Which is more or less a copy&paste thing. As it looks like alpha3 is delayed a while longer, that's no problem whatsoever, I think.
comment:5 by , 13 years ago
Owner: | changed from | to
---|---|
Status: | new → in-progress |
comment:6 by , 13 years ago
Milestone: | R1 → R1/alpha3 |
---|---|
Resolution: | → fixed |
Status: | in-progress → closed |
Applied in hrev41837, thanks a lot!
comment:7 by , 13 years ago
Version: | R1/alpha3 → R1/Development |
---|
R1 Alpha 3 has not yet been released. This was with an R1 Alpha 3 Release Candidate image.
The attached patch should fix it. (
Not tested yet.Tested with R1/alpha3 hrev41789.)