osy

Results 28 issues of osy

Currently because OSX does not know if a non-PCI device triggered the GPE, it will assume that every non-PCI and non-PCI power management enabled device triggered the GPE. Then it...

help wanted

`getEventImage()` in Camera.ts only queries `CameraEventImage`. However, on the Nest Doorbell (battery), `CameraClipPreview` is used instead. https://developers.google.com/nest/device-access/traits/device/camera-clip-preview describes the preview as > A clip preview is a 10 frame video...

enhancement
help wanted
good first issue
missing-hardware

This addresses two issues with HWCursor support: 1. Sometimes stale cursor data will be presented to the host due to a race condition. 2. Cursor hiding by guest was not...

Currently, the buttons in the accessory view do not respect the safe area. This means that when an external keyboard is connected, the home indicator bar would overlap some of...

Thank you very much for resolving the resolution issue on UTM for iOS devices; my testing on version 4.5.0 beta has shown that the resolution issues on Windows systems have...

One time warning when custom QEMU arguments are used because they may contain unsafe arguments.

enhancement

This way if the host is under severe load, it would not timeout.

Cross referencing with https://github.com/hashicorp/vagrant/issues/12518 This has been requested by quite a bit of users and this issue should track it.

enhancement

This is a warning in both libgettext and qemu strchrnul is defined as: ```c __OSX_AVAILABLE(15.4) __IOS_AVAILABLE(18.4) __TVOS_AVAILABLE(18.4) __WATCHOS_AVAILABLE(11.4) char *_LIBC_CSTR strchrnul(const char *__s, int __c); ```