Development

In the Time preflet, the 'Set time zone' button is greyed out. Changing from local time to GMT (actually called UTC since forever) also does nothing.

hrev 49058 installed.

invalid

invalid:

I seems that you're using A4.1 which had CPUfrequency preflet. It was deleted more that a year ago, see ​http://cgit.haiku-os.org/haiku/log/src/preferences/cpufrequency
So please use a recent nightly image to report bugs ​http://download.haiku-os.org/nightly-images/x86_gcc2_hybrid/

* Fix jpeg, jpeg2000. * Partialy fixes #11999. * Fix jpeg, jpeg2000. * Partialy fixes #11999.

On my Lenovo T60 laptop the CPU speed is detected correctly as Core Duo 1.83GHz but the menu bar shows it as ??GHz.

Also, the manufacturer isn't detected which is kind of curious given that these things are pretty old and common.

no change required

This avoids having to call it from the BoardSetup files. This avoids having to call it from the BoardSetup files.

Adding a message to a message does not transfer ownership. Adding a message to a message does not transfer ownership.

Stop watching nodes before quitting and therefore deleting the looper that was subscribed. Stop watching nodes before quitting and therefore deleting the looper that was subscribed.

It can be used to dump the current heap allocations with their details and stack traces if enabled. It can be used to dump the current heap allocations with their details and stack traces if enabled.

If it was already determined that the memory is within the kernel stack, a simple memcpy is enough. This allows capturing kernel stack traces in situations where a fault handler cannot be installed (i.e. where one is already installed). If it was already determined that the memory is within the kernel stack, a simple memcpy is enough. This allows capturing kernel stack traces in situations where a fault handler cannot be installed (i.e. where one is already installed).

When extracting/inserting report items there might not be a full uint32 available in the report anymore. Only copy as many bytes as are actually needed by the report item and guaranteed to be present in the report. When extracting/inserting report items there might not be a full uint32 available in the report anymore. Only copy as many bytes as are actually needed by the report item and guaranteed to be present in the report.

Twice the size was copied due to a missed adjustment in hrev31839, reading past the key state array. This didn't cause any corruption because the overwritten state wasn't used anymore later on and the write didn't overrun. It could cause a crash however if the read went past the allocated area. Twice the size was copied due to a missed adjustment in hrev31839, reading past the key state array. This didn't cause any corruption because the overwritten state wasn't used anymore later on and the write didn't overrun. It could cause a crash however if the read went past the allocated area.