Latest Bugs & Tasks

Syndicate content Haiku
Trac Timeline
Updated: 59 min 51 sec ago

Ticket #12921 ([Interface Kit] white progressbar background in FilWip) created

Sun, 2016-08-21 08:31


FilWip now has white progressbar background, looks like another regression.

Categories: Development

Ticket #12920 (Fail safe video mode should be automatically selected when GPU not ...) created

Sun, 2016-08-21 00:04

Currently my Intel GPU is not supported by the Intel Extreme driver, therefore I must use fail-safe video mode on each and every boot by selecting it in safe mode options.
This was not always the case. Haiku Alpha 3 will boot straight into VESA without having to perform this extra step.

Categories: Development

Ticket #12918 (VESA fails to set a valid mode on boot unless selected manually) created

Sat, 2016-08-20 13:01

Around 2 years ago one of my machines (that uses VESA graphics) started requiring me to select a safe video mode on every boot (otherwise it just hangs on the rocket). Knowing that it was between two hrevs 6 months apart I looked for changes relating to VESA between the dates and have found the change [1] that caused it (tested by reverting the change and testing).

The change to vesa accelerant is intended to only set the video mode if it is different to the current one. But at least on my hardware, it causes the system to not set the video mode correctly on boot.

[1] ​

Categories: Development

Ticket #12602 (find_paths does not work inside chroot.) closed

Sat, 2016-08-20 06:01

Fixed in hrev50499.

Categories: Development

Ticket #5289 ([Expander] wrong layout of controls) closed

Sat, 2016-08-20 06:00

Applied in hrev50499. Thanks!

Categories: Development

Ticket #12917 (get_package_dependencies needs to be refactored) created

Thu, 2016-08-18 04:08

It appears the entire reason the url exists in the repo file (BRepositoryInfo blob) is to appease the get_package_dependencies binary. The requirements of get_package_dependencies could be greatly cleaned up.

Current Behaviour

get_package_dependencies takes in the following arguments:

get_package_dependencies then 'solves' the dependencies and links to where the package should be based on the url in the provided binary repo (created from

get_package_dependencies seems to be the only thing that actually uses the url field in the / repo manifest. (this url field makes repo's unportable to other locations)

How it should work

  • A series of remote repo URL's are provided to the tool
    • Tool downloads repo manifest from each remote repo.
    • Tool now knows "where repos exist, and what packages they contain"
  • --
  • Every local hpkg file to be placed into the image.
Categories: Development

Ticket #12916 ([Debugger] Handle retrieving image paths for chrooted teams) created

Wed, 2016-08-17 00:18

Currently, LocalDebuggerInterface uses get_next_image_info() to retrieve the list of images for the targetted team. However, if the team is in a chroot, the path returned in the image information appears to have the path used inside the chroot, rather than the full filesystem path, which consequently leads to us being unable to locate the binary in question.

A few potential solutions present themselves here:

1) get_*_image_info could detect if the caller is in the same team or not, and if not, return the full path rather than the adjusted one. This may or may not be easily done depending on the inner workings of the corresponding kernel data structures (not yet investigated).

2) A new system call could be introduced that, given a team_id and a root-relative path within that team, maps it to its full filesystem path outside the chroot.


3) Additional calls/messages could be added to the debug API that provides similar semantics to get_*_image_info() but always returns the full path, thus leaving the former unmodified.

IMO, the third approach would probably be best, since it minimizes the risk of introducing any regressions in the more widely used standard calls, and makes it clear that the desired behavior is to return the information needed by the debugger. In any case, any such solution also needs to adjust the debug kit's image load/unload events to likewise take chroots into account if they don't already.


Categories: Development

Ticket #3918 (Keymap preferences should save selected keyboard layout.) closed

Tue, 2016-08-16 22:05

Fixed for real this time in hrev50491

It was attempting to save the keyboard layout before, but not correctly.

Categories: Development

Ticket #12912 (undefined reference for _setjmp) closed

Sun, 2016-08-14 07:33

Fixed in hrev50488.

Categories: Development

Ticket #12910 (Haiku x86-64 build won't build itself) closed

Sun, 2016-08-14 06:32

Please don't reopen a ticket for an already existing issue. The problem is still the same as before.

Categories: Development

Ticket #3918 (Keymap preferences should save selected keyboard layout.) reopened

Sun, 2016-08-14 06:30

No, it isn't.

This is not about the keymap, but the layout, which you can select in the second menu. It will always default to "generic 105 key international" when you start the app, which is a bit annoying if that's not the keyboard you use.

Categories: Development

Ticket #12914 (Debugger crashes on Step over) closed

Sun, 2016-08-14 01:27

Fixed in hrev50487.

Categories: Development

Ticket #12913 (Debugger crashes on Step into) closed

Sun, 2016-08-14 01:26
Categories: Development