Latest Bugs & Tasks

Syndicate content Haiku
Trac Timeline
Updated: 1 hour 40 min ago

Ticket #12550 (Improved Find Panel) created

Thu, 2015-12-31 14:29

This is an idea, I posted in a ​forum article a few years back. The full-size versions of the thumbnails in it appear to be lost on the website. I re-create the article here, in the hope it'll endure the next couple of years unharmed...
Check out the comments to the forum post and the short ​mailing list discussion, if you're interested.

Haiku's queries, while lightning fast, are a bit too complicated to use with the Find panel. You have to navigate through too many drop-down menus when all you want to do is quickly find a file of a specific type.
Here is a suggestion how this could be improved. Excuse the imperfect mockups, I'm sure the real thing would be much more pleasing to the eye... :)

Instead of tuning all search parameters in the Find panel and be surprised what turns up in the result window, then go back to refine/rinse/repeat, I'd like to see instant results while typing the search strings. So, it's more like narrowing down a search by more and more filtering.

Quick Icon Bar

To speed up everyday searches, there's an icon bar at the top where a user can drag&drop his most often used query templates. These templates only consist of the filetype and the layout of the attribute columns which will determine which attributes can be searched.

Query Filetype

If you don't already have it in your quick icon bar, you choose the filetype and the partition to search. There are also the expandable options from the current Find panel for temporary queries and in/exclunding the trash.
It should be possible to search through a whole supertype, like audio/*, video/* or image/*, because a user normally doesn't know/care what exact type the music/video/image is.
You can drag the icon into the quick bar. If it gets too crowded up there, they can gradually shrink from 64px.
If a dragged filetype already exists up there, its setting (attribute layout) is updated.

Query Strings

When your filetype is set, you have an empty file list below with the attribute layout typical (or saved with the quick icon bar) for that filetype. You can add/remove columns via right-click etc. as usual.
Now you begin typing in the textbox above the attribute-column you'd like to search. After, say, 3 letters the query gets updated live and the file list fills with results. You can change the criteria with a drop-down menu above every textbox according to the type of attribute: contains/contains not, is/is not, begins/ends, larger/smaller, before/after... etc.

The different attributes are always AND linked, as this to me makes sense in real life: You search for an artist AND an album, but I can't think of a real use for looking for one OR the other.

More Query Strings

However, if you need to search for more than one string within an attribute, you can click on the "+" button and add another search box for the column. Here you can choose between an AND/OR link with another drop-down menu. Removing a search box is done with its "-".

Here's the whole panel:

Next Generation Find Panel

So, a quick query would now go like this, for example:

  • ALT+F
  • Click music-icon
  • Click into artist search box
  • Enter "Breeders" (which I promplty forgot in all the mockup images...)
Categories: Development

Ticket #12549 (KDL booting hrev49947 x86_gcc2) created

Wed, 2015-12-30 08:55
Welcome to Kernel Debugging Land...
Thread 18 "main2" running on CPU 2
stack trace for thread 18 "main2"
    kernel stack: 0x81c2f000 to 0x81c33000
frame               caller     <image>:function + offset
 0 81c326d4 (+  32) 80148712   <kernel_x86> arch_debug_stack_trace() + 0x12
 1 81c326f4 (+  16) 800a7ef7   <kernel_x86> stack_trace_trampoline__FPv() + 0x0b
 2 81c32704 (+  12) 8013a49e   <kernel_x86> arch_debug_call_with_fault_handler() + 0x1b
 3 81c32710 (+  48) 800a9a1a   <kernel_x86> debug_call_with_fault_handler() + 0x5a
 4 81c32740 (+  64) 800a8113   <kernel_x86> kernel_debugger_loop__FPCcT0Pcl() + 0x217
 5 81c32780 (+  48) 800a848f   <kernel_x86> kernel_debugger_internal__FPCcT0Pcl() + 0x53
 6 81c327b0 (+  48) 800a9da6   <kernel_x86> panic() + 0x3a
 7 81c327e0 (+ 144) 8011ef7d   <kernel_x86> vm_page_fault() + 0x145
 8 81c32870 (+  80) 80149f43   <kernel_x86> x86_page_fault_exception() + 0x177
 9 81c328c0 (+  12) 8013ce5c   <kernel_x86> int_bottom() + 0x3c
kernel iframe at 0x81c328cc (end = 0x81c3291c)
 eax 0x8189b720    ebx 0x81899f6c     ecx 0x82a9a500  edx 0x73
 esi 0x656d5f6c    edi 0xa            ebp 0x81c32944  esp 0x81c32900
 eip 0x8186d9ad eflags 0x10206
 vector: 0xe, error code: 0x0
10 81c328cc (+ 120) 8186d9ad   <acpi> AcpiNsBuildNormalizedPath() + 0x51
11 81c32944 (+  64) 8186d908   <acpi> AcpiNsHandleToPathname() + 0x44
12 81c32984 (+  48) 81870445   <acpi> AcpiGetName() + 0x65
13 81c329b4 (+  64) 81867033   <acpi> get_next_entry() + 0x9b
14 81c329f4 (+ 544) 818679f7   <acpi> acpi_enumerate_child_devices__FP11device_nodePCc() + 0x237
15 81c32c14 (+ 144) 81867b17   <acpi> acpi_module_register_child_devices__FPv() + 0x103
16 81c32ca4 (+  48) 800bc14d   <kernel_x86> Register__11device_nodeP11device_node() + 0x8d
17 81c32cd4 (+  64) 800baa62   <kernel_x86> register_node__FP11device_nodePCcPC11device_attrPC11io_resourcePP11device_node() + 0xfe
18 81c32d14 (+ 112) 818677b5   <acpi> acpi_module_register_device__FP11device_node() + 0x49
19 81c32d84 (+  64) 800bc8a9   <kernel_x86> _RegisterPath__11device_nodePCc() + 0x4d
20 81c32dc4 (+  96) 800bca9f   <kernel_x86> _RegisterDynamic__11device_nodeP11device_node() + 0x147
21 81c32e24 (+  48) 800bc177   <kernel_x86> Register__11device_nodeP11device_node() + 0xb7
22 81c32e54 (+  64) 800baa62   <kernel_x86> register_node__FP11device_nodePCcPC11device_attrPC11io_resourcePP11device_node() + 0xfe
23 81c32e94 (+ 192) 800bd519   <kernel_x86> init_node_tree__Fv() + 0x41
24 81c32f54 (+  16) 800bd6f1   <kernel_x86> device_manager_init() + 0xfd
25 81c32f64 (+  80) 80066942   <kernel_x86> main2__FPv() + 0x76
26 81c32fb4 (+  48) 80087563   <kernel_x86> common_thread_entry__FPv() + 0x3b
Categories: Development

Ticket #12548 (Debugger: implement architectural unwinding of frameless functions) created

Tue, 2015-12-29 00:02

Currently compiling the ffmpeg add-on with debug symbols enabled, but in the stack trace, the second to last stack frame seems to be missing unless one uses the step into function.

E.g. I have added a memcpy that's triggering a segfault exception, where the calling function is _MoveAudioFramesToRawDecodedAudioFormatAndUpdateStartTimes(), but this stack frame is not present. Only the function calling _MoveAudio..., _DecodeNextAudioFrame(), is in the call stack.

When I have a breakpoint configured in _DecodeNextAudioFrame, then use Step Into to enter into the _MoveAudioFrames... function, does it then show up in the stack trace. If I use the Run button instead, it doesn't show up in the stack trace either.

Categories: Development

Ticket #12547 (MediaPlayer aborts with assertion a->planar failed at ...) created

Sun, 2015-12-27 14:19

MediaPlayer aborts with assertion a->planar failed at libswresample/swresample.c:284 when playing some files.
A test file where this occurs can be found at ​

This worked fine previously, though I don't know exactly which revision it stopped working.
I am not getting a debug report, so I have not attached one. Is there another way to create it?

Created as a new ticket on the suggestion of pulkomandy instead of as part of #12509.

Categories: Development

Ticket #12509 (FFmpeg media plugin broken since using libresample) closed

Sun, 2015-12-27 11:18

@markh: so, it does not crash with "resampling failed" as with all reports submitted here. This means it is not the same problem. Please open a new ticket and attach a debugger report.

I think this one can be closed now.

Categories: Development

Ticket #11266 (BLayoutBuilder doesn't include BCardLayout) closed

Sun, 2015-12-27 01:37

Applied in hrev49943. Thanks!

Categories: Development

Ticket #12546 (Webpositive cannot connect to Haiku Mailing Lists Archives) created

Fri, 2015-12-25 22:15

Go to:
Haiku Home page
Mailing Lists
Select any "Message archive"
Webpositive never loads the page
hrev49941 x86_gcc2

Categories: Development

Ticket #12545 (Webpositive page rendering) created

Thu, 2015-12-24 21:20

hrev49939 x86_gcc2
Go to ​
The login dialog is barely visible
Any text enetered in the area for name and password cannot be seen
(attached screenshot1)

Categories: Development

Ticket #12544 (Shortcuts broken) created

Wed, 2015-12-23 19:25

The keuboard shortcuts set in the Shortcuts preference seem to be broken in hrev49939. A existing shortcut using right-ALT-/ does not work. I created another shortcut to bring up a terminal, and it did not work either.

Categories: Development

Ticket #11299 (Webpositive slow to close) closed

Wed, 2015-12-23 06:11
Categories: Development

Ticket #12543 (weed out parallel build bugs) created

Tue, 2015-12-22 19:20

Parallel build bugs are generally caused by incorrect dependencies within our Jam build system.

These bugs can be hard to track down and generally are random in nature.

This ticket is a central spot to begin reporting suspected subsystem dependency issues.

Categories: Development

Ticket #12542 (libroot: unistd.h defines constants for unsupported POSIX features) closed

Mon, 2015-12-21 16:13

Applied in hrev49935. Thanks!

On a side node, you're welcome to join us in the #haiku channel on Freenode.

Categories: Development

Ticket #12542 (libroot: unistd.h defines constants for unsupported POSIX features) created

Mon, 2015-12-21 15:59

Haiku does not yet support certain features related to POSIX threads. For this reason, unistd.h defines the _POSIX_THREAD_ATTR_STACKADDR and _POSIX_THREAD_PRIORITY_SCHEDULING constants to -1, meant to signal the absence of these features.

However, a careful reading of ​the POSIX spec suggests these constants should actually be left undefined. Referring to _POSIX_THREAD_ATTR_STACKADDR:

The following symbolic constants are always defined to unspecified values to indicate that this functionality from the POSIX Threads Extension is always present on XSI-conformant systems:


If _XOPEN_REALTIME_THREADS is defined to have a value other than -1, then the following symbolic constants will be defined to an unspecified value to indicate that the features are supported:

Emphasis mine. The implication is that if the features are not available the constants should not be defined to any value; that is, they should be left undefined.

This seems to match ​how these constants are actually used in the wild.

The attached patch corrects the implementation by modifying

  • unistd.h to undefine the two constants (they are left in the file to indicate they have not simply been forgotten) and
  • conf.cpp so sysconf returns -1 when the presence of these features is tested (which matches the existing behaviour; POSIX says simply "​the results are unspecified" in this case).

These changes are needed to build ​Apache Thrift on Haiku.

Categories: Development

Ticket #12541 ("PANIC: unable to find irq routing for PCI 4:4:0" from nightly builds) created

Mon, 2015-12-21 13:03

i tried booting via usb hrev49933, hrev49928 and hrev49917, and all these 3 shown: "PANIC: unable to find irq routing for PCI 4:4:0"

it seems to continue boot when typing "continue" on debugging land, but there is no usb mice or network available

from gnu/linux (ubuntu 15.10) i get from lspci:

guest@1v5tf:~$ lspci
00:00.0 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge
00:00.1 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge
00:00.2 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge
00:00.3 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge
00:00.4 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge
00:00.5 PIC: VIA Technologies, Inc. CN896/VN896/P4M900 I/O APIC Interrupt Controller
00:00.6 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Security Device
00:00.7 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237/VX700 PCI Bridge
00:02.0 PCI bridge: VIA Technologies, Inc. CN896/VN896/P4M900 PCI to PCI Bridge Controller (rev 80)
00:0f.0 IDE interface: VIA Technologies, Inc. VT8237A SATA 2-Port Controller (rev 80)
00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 07)
00:10.0 USB controller: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller (rev a0)
00:10.1 USB controller: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller (rev a0)
00:10.2 USB controller: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller (rev a0)
00:10.3 USB controller: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller (rev a0)
00:10.4 USB controller: VIA Technologies, Inc. USB 2.0 (rev 86)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8237A PCI to ISA Bridge
00:11.7 Host bridge: VIA Technologies, Inc. VT8237/8251 Ultra VLINK Controller
00:13.0 Host bridge: VIA Technologies, Inc. VT8237A Host Bridge
00:13.1 PCI bridge: VIA Technologies, Inc. VT8237A PCI to PCI Bridge
02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Device 71c3 (rev 9e)
02:00.1 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Device 71e3 (rev 9e)
04:04.0 Multimedia controller: Philips Semiconductors SAA7131/SAA7133/SAA7135 Video Broadcast Decoder (rev d1)
04:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8110SC/8169SC Gigabit Ethernet (rev 10)
80:01.0 Audio device: VIA Technologies, Inc. VT8237A/VT8251 HDA Controller (rev 10)


Categories: Development

Ticket #12540 (Can't set new target for TextSearch) created

Mon, 2015-12-21 09:50

This is hrev49934.

The menu item "File | Set new target..." doesn't open a file dialog to set the new location. I tried to debug it a little, but I'm rubbish at it. It always returns after this test:

So it looks like fFilePanelPath doesn't hold the right path, as it should...

Categories: Development

Ticket #12539 (TextSearch won't grep XHTML files) created

Mon, 2015-12-21 09:17

This is hrev49934.

XHTML has unfortunately a MIME type of application/xhtml+xml. You'd have to uncheck TextSearch's setting "Text files only" (which is what you usually want) to make it work.

TextSearch examines files, if they have a "text" supertype for this.
Would introducing this exception in code be acceptable:

// Make an exception for XHTML files
if (strcmp("application/xhtml+xml", mimeTypeString) == 0)
	return true;

(inserted here: ​

Categories: Development

Ticket #12538 (HaikuDepot missing a repository column) created

Mon, 2015-12-21 06:57

I always want to know from wich repository the packages i install are coming from. The only way to determin it atm. is to switch between repositorys and take a look if the given packages are showing up.
If one colum would be available, wich shows the repository it comes from, would be really helpfull.

Categories: Development

Ticket #11294 ([PATCH] Nuke SetSubDirSupportedPlatformsBeOSCompatible) closed

Sat, 2015-12-19 01:55

This is more complicated than it seems, and probably isn't possible anyway.

Categories: Development