Attachments (1)
Change History (15)
by , 6 years ago
Attachment: | previous_syslog added |
---|
comment:1 by , 6 years ago
comment:2 by , 6 years ago
Oh, never mind:
package_daemon [50611840: 322] An old packages state ("state_2019-04-04_15:48:42") seems to be active.
You seem to have attached a syslog from the successful boot into the old state. That will not be very helpful in determining what's happening here...
comment:3 by , 6 years ago
comment:4 by , 6 years ago
Well, bad news: hrev53033 boots just fine here. So I don't know what's going on.
comment:5 by , 6 years ago
1650 Launching x-vnd.haiku-app_server failed: Symbol not found
2835 [atheroswifi] (ath) ath_legacy_rx_tasklet: sc_inreset_cnt > 0; skipping
I don't know what make of these 2 lines, the second one is the last in the onscreen debug, the boot process doesn't go farther than that.
comment:6 by , 6 years ago
runtime_loader: /boot/system/lib/libxml2.so.2.9.9: Could not resolve symbol '__builtin_clzll' runtime_loader: /boot/system/lib/libxml2.so.2.9.9: Troubles relocating: Symbol not found
Ah, now that explains why I couldn't reproduce: I only update haiku.hpkg, not the XML library.
comment:7 by , 6 years ago
comment:9 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:11 by , 6 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
comment:12 by , 6 years ago
Please don't post full syslogs inline, it makes reading tickets painful. Please edit your comment to remove it and attach it as a file instead. Besides, if it's the syslog of the working version it's not really useful anyway.
We already confirmed the bug was fixed. Make sure you did update all the packages, and not just the base one, since the bug was in libxml. Make sure you updated libxml2 to 2.9.9-3.
It might not be the same bug. In which case you should open a new ticket instead of reopening this one.
comment:13 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
Yes, this is not the same bug, there is no "app_server" message. It looks like you have intel_extreme; possibly the recent change there broke things.
comment:14 by , 5 years ago
Milestone: | Unscheduled → R1/beta2 |
---|
Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone
It seems strange that there is no activation file after the upgrade, pkgman should have made one. Are you sure there was not some FS corruption?