Latest Bugs & Tasks
No response. Multiple users use QEMU/KVM with no issues; assuming fixed.
BeTaskManager works here. A bit slow, but it doesn't hang anything.
I think audio has been fixed, IIRC. The game freezing is a totally separate issue.
Yes, I agree.
We aren't aiming for source compatibility.
gdb is now HaikuPorts' problem. :>
gdb is now HaikuPorts' problem. :>
Probably fixed in hrev48946.
I haven't ever had this happen, on real hardware (really old AMD Athlon XP too) or in VBox. Assuming fixed (we now use FFmpeg for decoding...)
A lot of the other symptoms (e.g. CD not being looked up in CDDB) were probably fixed by me in hrev47476. Assuming fixed.
Fixed already (see ticket history).
Bug supposedly fixed in hrev35434; no response from reporter. Assuming fixed.
netresolv doesn't solve this problem, now that I enabled IPv6 support in it. We will have to implement this ourselves or see if the current code in NetBSD does it.
Fixed in hrev49314
The url the app uses to retrieve the data doesn't work in webpositive but it works in qupzilla.
This worked only a few weeks ago. I'm trying to install the haiku_cross_devel_x86.hpkg and it fails to install. No directory is created.
gcc4/gcc2 hybrid build erroneously builds for gcc4 twice rather than gcc4/gcc2. BuildConfig included.
Creating a few partitions (more than 1) will result in GPT corruption per gdisk.
For example below, create 8 partitions on one disk, then read that disk with gdisk.
$ gdisk test.raw GPT fdisk (gdisk) version 0.8.10 Caution! After loading partitions, the CRC doesn't check out! Warning! Main and backup partition tables differ! Use the 'c' and 'e' options on the recovery & transformation menu to examine the two tables. Warning! One or more CRCs don't match. You should repair the disk! Partition table scan: MBR: not present BSD: not present APM: not present GPT: damaged Found invalid MBR and corrupt GPT. What do you want to do? (Using the GPT MAY permit recovery of GPT data.) 1 - Use current GPT 2 - Create blank GPT Your answer: 1 Command (? for help): p Disk test.raw: 204800 sectors, 100.0 MiB Logical sector size: 512 bytes Disk identifier (GUID): 82009838-FFFF-FFFF-3898-0082FFFFFFFF Partition table holds up to 128 entries First usable sector is 34, last usable sector is 204766 Partitions will be aligned on 8-sector boundaries Total free space is 90045 sectors (44.0 MiB) Number Start (sector) End (sector) Size Code Name 1 49192 65575 8.0 MiB A501 5 49192 65575 8.0 MiB A501 6 65576 81959 8.0 MiB A581 7 81960 98343 8.0 MiB A902 8 98344 114727 8.0 MiB A901 9 40 16423 8.0 MiB EB00 10 16424 32807 8.0 MiB 8300 11 32808 49191 8.0 MiB AB00 12 49192 65575 8.0 MiB A501 Command (? for help): v Problem: The CRC for the main partition table is invalid. This table may be corrupt. Consider loading the backup partition table ('c' on the recovery & transformation menu). This report may be a false alarm if you've already corrected other problems. Caution: The CRC for the backup partition table is invalid. This table may be corrupt. This program will automatically create a new backup partition table when you save your partitions. Problem: partitions 5 and 1 overlap: Partition 5: 49192 to 65575 Partition 1: 49192 to 65575 Problem: partitions 12 and 1 overlap: Partition 12: 49192 to 65575 Partition 1: 49192 to 65575 Problem: partitions 12 and 5 overlap: Partition 12: 49192 to 65575 Partition 5: 49192 to 65575 Identified 5 problems! Command (? for help):
Given the "65575" it looks like there is some overflow somewhere. Our GPT code places partitions on-top of each other :-\