Opened 3 years ago

Closed 3 years ago

#13480 closed bug (fixed)

Updating to hrev51155 causes "no boot" condition

Reported by: vidrep Owned by: nobody
Priority: normal Milestone: Unscheduled
Component: - General Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: yes Platform: All

Description

Updating from hrev51153 to hrev51155 causes a "no boot" condition, where the boot process stops at the rocket icon. I have tried this on two separate systems. Humdinger can also confirm same. Installing to HD partition using the hrev51155 anyboot image proceeds normally, so only updates from earlier hrev appear to be affected. Serial debug log attached

Attachments (2)

x86_gcc5h.txt (117.8 KB ) - added by vidrep 3 years ago.
previous_syslog (219.5 KB ) - added by kim1963 3 years ago.

Download all attachments as: .zip

Change History (11)

by vidrep, 3 years ago

Attachment: x86_gcc5h.txt added

comment:1 by vidrep, 3 years ago

Has a Patch: set

comment:2 by pulkomandy, 3 years ago

From the syslog:

1780	runtime_loader: Cannot open file libfontconfig.so.1: No such file or directory
1781	Launching x-vnd.haiku-app_server failed: Missing library

Probably the Haiku package should depend on the fontconfig one now?

comment:3 by kallisti5, 3 years ago

Confirmed.

Fix:

  1. Reboot, enter boot menu
  2. Select boot volume, choose previous activation state before upgrade
  3. pkgman install fontconfig
  4. boot normally

by kim1963, 3 years ago

Attachment: previous_syslog added

in reply to:  3 comment:4 by kim1963, 3 years ago

Replying to kallisti5:

Confirmed.

Fix:

  1. Reboot, enter boot menu
  2. Select boot volume, choose previous activation state before upgrade
  3. pkgman install fontconfig
  4. boot normally

Not working.

comment:5 by vidrep, 3 years ago

Confirmed working here on x86_gcc2h "pkgman install fontconfig" before running SoftwareUpdater

Can the fontconfig package just be added to the current update to avoid the situation we see above with kim1963?

comment:6 by pulkomandy, 3 years ago

Done in hrev51156. Please confirm if that fixes it.

comment:7 by vidrep, 3 years ago

Confirmed working.

comment:8 by kim1963, 3 years ago

Update 51155 to 51157 - work fine.

comment:9 by pulkomandy, 3 years ago

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.