I cannot reproduce the crash at will. After playing around for a long time, I got an identical crash, but I couldn’t exactly describe when it hit. I did have a search filter going and clicked from one entry to the next…
I was not able to reproduce the issue of packages seemingly missing, even after re-installing the test image. It’s entirely possible it was a user error, it was pretty early then and I didn’t have a coffee yet…
Alas, HDS admin users are hard to find these days…
First checks with 32bit and 64bit boot at 2 laptops went without a hitch, no supprises there regarding hardware, one glich found on 32bit after installing it to an existing install (so not sure if that could be the cause or not), drop-down menu for “Find” doesn’t show correctly.
Just checked the clean iso boot, looks fine there.
Are the translations already frozen or can them still be fixed or completed?
Hey cafeina, You can check the timeline here: https://dev.haiku-os.org/wiki/R1/Beta5/Timeline
The dates are a bit delayed though, but there should be a final string sync after these testing weeks atleast, so it should still be possible to update translations (If I understand correctly)
regards
Well the games crashes on my haiku system. But i think the problem maybe IS on the radeon_hd driver which doesn’t like full screen.
It’s possible; what’s in the menu? Are there very long items? May need a ticket.
I tested this again and the bug/crash is only happening on VMware and not on real hardware so it may be possible to release without this being fixed, we’ll just have to make the caveat that this is a known bug unless somebody can fix this one soon.
I’ll check again later/tomorrow, closed that install earlier.
Couple small notes:
No, please open a ticket.
It is supposed to show up on it‘s own now (in deskbar), but only when you have a battery connected.
https://cgit.haiku-os.org/haiku/commit/?id=ef1427bb586c45998898fa36aaefc6f3572b725b
VMware may be reporting battery status which is why it gets added. I just checked in my VMware and indeed there are two batteries reported, both are “unused” with apparently invalid data. The ACPI battery driver should probably ignore them.
Just a thought: if your survey asks if the sound works, then just put a standard sound file on the desktop, or at least give a link to one in the survey. Yes, it’s not difficult to find something on the net to play, but now people will be reporting on different files with different formats. It is hard to generalize from that.
Sorta related: #12082 (Default sound theme needed) – Haiku
Wonderbrush is installed by default in 32-bit but not in 64-bit.
libQtWebEngineCore has a libvpx.so.7 missing error, which can be resolved by installed the older version of libvpx(libvpx1.11).
That version of libvpx is not installed as a dependency for QtWebEngine
I like to do my bit, but am not really that interested about running the backward compatible gcc2 version. Is it important that we do both on any given machine?
I don’t have a clue how to find sounds to play. It should be easy but never really had to do it before. BBC requires sign in, most radio in-app players don’t work anyway. I looked for sound effects and when I find a site that does not require sign in I cannot download - is that a problem with WebPositive? I am neurodiverse and realise that when asked to go off piste I can flap around a bit without a clue.
I think I will skip sound feedback this time round, sound is not super important to my own workload, perhaps the later release candidates will have a jingle we can play?
I tried booting the 64bit system on the Asus Prime B450M-K motherboard, Ryzen 3 3200g CPU, 16 GB RAM, system stuck after rocket (starting desktop):
The debugger accepts input from the keyboard (the system is not frozen).
Photo from booting with debugger:
What else can I try?
Tried 64bit system on old laptop Acer Aspire 5349 with intel i7 2620M, 8 GB ram.
System boots from USB flash, sound works, LAN works, Toutchpad works, WiFi (intel Centrino Advanced N 6200) seems to work, but cannot connect to network after input of the password. The computer was left unattended for some time, when I returned to it I found on it’s screen:
Should be fixed in revision 5
No, you are not obligated to test this, if you only want to test one that is okay. (though humdinger already identified errors in the 64bit version by comparing both)
regards
