Monado issueshttps://gitlab.freedesktop.org/monado/monado/-/issues2024-03-15T17:20:41Zhttps://gitlab.freedesktop.org/monado/monado/-/issues/345xrEndFrame with 0 layers in an overlay app is not throttled2024-03-15T17:20:41ZyshuixrEndFrame with 0 layers in an overlay app is not throttledUnsure if this is expected behavior, but frame loop that ends with an `xrEndFrame` with 0 layers is not throttled. Meaning the application can loop as quickly as it wants. And with each loop, the predicted display time moves forward by o...Unsure if this is expected behavior, but frame loop that ends with an `xrEndFrame` with 0 layers is not throttled. Meaning the application can loop as quickly as it wants. And with each loop, the predicted display time moves forward by one frame. When the application finally submits something, its display time could be in distant future, giving an appearance of application hanging.https://gitlab.freedesktop.org/monado/monado/-/issues/344`xrEndSession` doesn't always stop the session2024-03-15T14:27:00Zyshui`xrEndSession` doesn't always stop the sessionCiting the OpenXR spec (emphasis mine):
> If an error is returned from `xrBeginSession`, the session remains in its current running or not running state. Calling `xrEndSession` **always** transitions a session to the not running state, ...Citing the OpenXR spec (emphasis mine):
> If an error is returned from `xrBeginSession`, the session remains in its current running or not running state. Calling `xrEndSession` **always** transitions a session to the not running state, **regardless of any errors returned**.
Right now if I receive `XR_ERROR_SESSION_NOT_STOPPING` from `xrEndSession`, the next `xrBeginSession` call will return `XR_ERROR_SESSION_RUNNING`, indicating `xrEndSession` did not stop the session.Simon Zenisimon@bl4ckb0ne.caSimon Zenisimon@bl4ckb0ne.cahttps://gitlab.freedesktop.org/monado/monado/-/issues/316Duplicate symbols in OpenHMD and monado2024-02-26T04:28:42ZChristoph HaagDuplicate symbols in OpenHMD and monadoIn particular when OpenHMD is built as a static library, it exposes several symbols that are defined in monado too, leading to compile errors when building monado. In shared library builds, OpenHMD tries to hide these symbols but it's no...In particular when OpenHMD is built as a static library, it exposes several symbols that are defined in monado too, leading to compile errors when building monado. In shared library builds, OpenHMD tries to hide these symbols but it's not possible to hide symbols in static libraries.
This affects the Rift S driver, for example rift_s_parse_imu_calibration, rift_s_controller_parse_imu_calibration, rift_s_controller_free_imu_calibration and I believe the wmr driver.https://gitlab.freedesktop.org/monado/monado/-/issues/300Crash on surface loss on Android2024-02-05T17:34:15ZRylie PavlikCrash on surface loss on AndroidSaw this in logcat when swiping away an app (out of process mode on pixel 3) I suppose this might be two issues actually.
```
11-15 15:35:52.646 1900 7868 W ActivityManager: Process org.freedesktop.monado.openxr_runtime.out_of_process...Saw this in logcat when swiping away an app (out of process mode on pixel 3) I suppose this might be two issues actually.
```
11-15 15:35:52.646 1900 7868 W ActivityManager: Process org.freedesktop.monado.openxr_runtime.out_of_process has crashed too many times, killing! Reason: crashed quickly
11-15 15:35:52.647 1900 7868 W AppStandbyController: Tried to restrict recently used app: org.freedesktop.monado.openxr_runtime.out_of_process due to 1540
11-15 15:35:52.647 1900 7868 I ActivityManager: Killing 7828:org.freedesktop.monado.openxr_runtime.out_of_process/u0a394 (adj 0): crash
```
I symbolized the crashes, and got two. One is familiar: I'm pretty sure this is the same way Monado dies if you close the simulator window on Linux.
<details><summary>Click to expand</summary>
```
Abort message: '/home/ryan/src/monado-android/src/xrt/compositor/main/comp_renderer.c:477: _Bool renderer_ensure_images_and_renderings(struct comp_renderer *, _Bool): assertion "r->buffer_count != 0" failed'
#00 0x000000000004fbcc /apex/com.android.runtime/lib64/bionic/libc.so (abort+164) (BuildId: ba489d4985c0cf173209da67405662f9)
#01 0x000000000004ff70 /apex/com.android.runtime/lib64/bionic/libc.so (__assert2+36) (BuildId: ba489d4985c0cf173209da67405662f9)
#02 0x00000000000b9608 /data/app/~~qXxv0aAYUhSQU9xS9x1uWw==/org.freedesktop.monado.openxr_runtime.out_of_process-OfuVv3zE0IUZG5twCxe0uA==/lib/arm64/libmonado-service.so (BuildId: 79d70f4a017a864bf415398f79157fba242f039e)
renderer_ensure_images_and_renderings
/home/ryan/src/monado-android/src/xrt/compositor/main/comp_renderer.c:477:2
#03 0x00000000000bafdc /data/app/~~qXxv0aAYUhSQU9xS9x1uWw==/org.freedesktop.monado.openxr_runtime.out_of_process-OfuVv3zE0IUZG5twCxe0uA==/lib/arm64/libmonado-service.so (BuildId: 79d70f4a017a864bf415398f79157fba242f039e)
renderer_resize
/home/ryan/src/monado-android/src/xrt/compositor/main/comp_renderer.c:693:2
#04 0x00000000000b8c9c /data/app/~~qXxv0aAYUhSQU9xS9x1uWw==/org.freedesktop.monado.openxr_runtime.out_of_process-OfuVv3zE0IUZG5twCxe0uA==/lib/arm64/libmonado-service.so (BuildId: 79d70f4a017a864bf415398f79157fba242f039e)
renderer_present_swapchain_image
/home/ryan/src/monado-android/src/xrt/compositor/main/comp_renderer.c:716:3
#05 0x00000000000b7ff0 /data/app/~~qXxv0aAYUhSQU9xS9x1uWw==/org.freedesktop.monado.openxr_runtime.out_of_process-OfuVv3zE0IUZG5twCxe0uA==/lib/arm64/libmonado-service.so (comp_renderer_draw+620) (BuildId: 79d70f4a017a864bf415398f79157fba242f039e)
comp_renderer_draw
/home/ryan/src/monado-android/src/xrt/compositor/main/comp_renderer.c:967:2
#06 0x00000000000b5e98 /data/app/~~qXxv0aAYUhSQU9xS9x1uWw==/org.freedesktop.monado.openxr_runtime.out_of_process-OfuVv3zE0IUZG5twCxe0uA==/lib/arm64/libmonado-service.so (BuildId: 79d70f4a017a864bf415398f79157fba242f039e)
compositor_layer_commit
/home/ryan/src/monado-android/src/xrt/compositor/main/comp_compositor.c:299:2
#07 0x00000000001326fc /data/app/~~qXxv0aAYUhSQU9xS9x1uWw==/org.freedesktop.monado.openxr_runtime.out_of_process-OfuVv3zE0IUZG5twCxe0uA==/lib/arm64/libmonado-service.so (BuildId: 79d70f4a017a864bf415398f79157fba242f039e)
xrt_comp_layer_commit
/home/ryan/src/monado-android/src/xrt/include/xrt/xrt_compositor.h:1638:9
#08 0x0000000000131a38 /data/app/~~qXxv0aAYUhSQU9xS9x1uWw==/org.freedesktop.monado.openxr_runtime.out_of_process-OfuVv3zE0IUZG5twCxe0uA==/lib/arm64/libmonado-service.so (BuildId: 79d70f4a017a864bf415398f79157fba242f039e)
multi_main_loop
/home/ryan/src/monado-android/src/xrt/compositor/multi/comp_multi_system.c:512:3
#09 0x00000000001314e0 /data/app/~~qXxv0aAYUhSQU9xS9x1uWw==/org.freedesktop.monado.openxr_runtime.out_of_process-OfuVv3zE0IUZG5twCxe0uA==/lib/arm64/libmonado-service.so (BuildId: 79d70f4a017a864bf415398f79157fba242f039e)
thread_func
/home/ryan/src/monado-android/src/xrt/compositor/multi/comp_multi_system.c:539:27
#10 0x00000000000b1910 /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+264) (BuildId: ba489d4985c0cf173209da67405662f9)
#11 0x00000000000513f0 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: ba489d4985c0cf173209da67405662f9)
```
</details>
The other crash dump (of I guess another thread?) was new and android-specific: bad JNI behavior.
<details><summary>Click to expand</summary>
```
Abort message: 'JNI DETECTED ERROR IN APPLICATION: JNI ERROR (app bug): jobject is an invalid global reference: 0x28a6 (deleted reference at index 325)
#00 0x000000000004fbcc /apex/com.android.runtime/lib64/bionic/libc.so (abort+164) (BuildId: ba489d4985c0cf173209da67405662f9)
#01 0x00000000007716f0 /apex/com.android.art/lib64/libart.so (art::Runtime::Abort(char const*)+904) (BuildId: 4cfdaa9e5146c43e20ae36ee1caf9b7f)
#02 0x00000000000357d0 /apex/com.google.mainline.primary.libs@341050000/lib64/libbase.so/75d3253827fcfd7a8d7b02ad45991611ec4ca424c0278e13e8acfad4d14e597a3ecff6c0caa2b785c73838528ee6e9c2b313240ff895f50ee39b1d7bc10f390a/libbase.so (android::base::SetAborter(std::__1::function<void (char const*)>&&)::$_0::__invoke(char const*)+80) (BuildId: 6f67f69ff36b970d0b831cfdab3b578d)
#03 0x0000000000034d58 /apex/com.google.mainline.primary.libs@341050000/lib64/libbase.so/75d3253827fcfd7a8d7b02ad45991611ec4ca424c0278e13e8acfad4d14e597a3ecff6c0caa2b785c73838528ee6e9c2b313240ff895f50ee39b1d7bc10f390a/libbase.so (android::base::LogMessage::~LogMessage()+352) (BuildId: 6f67f69ff36b970d0b831cfdab3b578d)
#04 0x00000000003f599c /apex/com.android.art/lib64/libart.so (art::JavaVMExt::JniAbort(char const*, char const*)+3540) (BuildId: 4cfdaa9e5146c43e20ae36ee1caf9b7f)
#05 0x00000000002caa64 /apex/com.android.art/lib64/libart.so (art::(anonymous namespace)::ScopedCheck::AbortF(char const*, ...) (.__uniq.99033978352804627313491551960229047428)+188) (BuildId: 4cfdaa9e5146c43e20ae36ee1caf9b7f)
#06 0x0000000000384900 /apex/com.android.art/lib64/libart.so (art::(anonymous namespace)::ScopedCheck::Check(art::ScopedObjectAccess&, bool, char const*, art::(anonymous namespace)::JniValueType*) (.__uniq.99033978352804627313491551960229047428)+1544) (BuildId: 4cfdaa9e5146c43e20ae36ee1caf9b7f)
#07 0x00000000005003f0 /apex/com.android.art/lib64/libart.so (art::(anonymous namespace)::CheckJNI::NewRef(char const*, _JNIEnv*, _jobject*, art::IndirectRefKind) (.__uniq.99033978352804627313491551960229047428)+196) (BuildId: 4cfdaa9e5146c43e20ae36ee1caf9b7f)
#08 0x0000000000124998 /data/app/~~qXxv0aAYUhSQU9xS9x1uWw==/org.freedesktop.monado.openxr_runtime.out_of_process-OfuVv3zE0IUZG5twCxe0uA==/lib/arm64/libmonado-service.so (_JNIEnv::NewGlobalRef(_jobject*)+40) (BuildId: 79d70f4a017a864bf415398f79157fba242f039e)
_JNIEnv::NewGlobalRef(_jobject*)
/home/ryan/Android/Sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/linux-x86_64/sysroot/usr/include/jni.h:549:14
#09 0x0000000000124a98 /data/app/~~qXxv0aAYUhSQU9xS9x1uWw==/org.freedesktop.monado.openxr_runtime.out_of_process-OfuVv3zE0IUZG5twCxe0uA==/lib/arm64/libmonado-service.so (jni::Object::Object(_jobject*, int)+120) (BuildId: 79d70f4a017a864bf415398f79157fba242f039e)
jni::Object::Object(_jobject*, int)
/home/ryan/src/monado-android/src/external/jnipp/jnipp.cpp:301:24
#10 0x00000000001183f0 /data/app/~~qXxv0aAYUhSQU9xS9x1uWw==/org.freedesktop.monado.openxr_runtime.out_of_process-OfuVv3zE0IUZG5twCxe0uA==/lib/arm64/libmonado-service.so (android_custom_surface_get_display_metrics+288) (BuildId: 79d70f4a017a864bf415398f79157fba242f039e)
android_custom_surface_get_display_metrics
/home/ryan/src/monado-android/src/xrt/auxiliary/android/android_custom_surface.cpp:214:70
#11 0x00000000000eccf0 /data/app/~~qXxv0aAYUhSQU9xS9x1uWw==/org.freedesktop.monado.openxr_runtime.out_of_process-OfuVv3zE0IUZG5twCxe0uA==/lib/arm64/libmonado-service.so (android_device_create+436) (BuildId: 79d70f4a017a864bf415398f79157fba242f039e)
android_device_create
/home/ryan/src/monado-android/src/xrt/drivers/android/android_sensors.c:253:7
#12 0x00000000000ecb04 /data/app/~~qXxv0aAYUhSQU9xS9x1uWw==/org.freedesktop.monado.openxr_runtime.out_of_process-OfuVv3zE0IUZG5twCxe0uA==/lib/arm64/libmonado-service.so (BuildId: 79d70f4a017a864bf415398f79157fba242f039e)
android_prober_autoprobe
/home/ryan/src/monado-android/src/xrt/drivers/android/android_prober.c:72:30
#13 0x00000000000b3884 /data/app/~~qXxv0aAYUhSQU9xS9x1uWw==/org.freedesktop.monado.openxr_runtime.out_of_process-OfuVv3zE0IUZG5twCxe0uA==/lib/arm64/libmonado-service.so (BuildId: 79d70f4a017a864bf415398f79157fba242f039e)
add_from_auto_probers
/home/ryan/src/monado-android/src/xrt/state_trackers/prober/p_prober.c:741:7
#14 0x00000000000b1794 /data/app/~~qXxv0aAYUhSQU9xS9x1uWw==/org.freedesktop.monado.openxr_runtime.out_of_process-OfuVv3zE0IUZG5twCxe0uA==/lib/arm64/libmonado-service.so (BuildId: 79d70f4a017a864bf415398f79157fba242f039e)
p_select_device
/home/ryan/src/monado-android/src/xrt/state_trackers/prober/p_prober.c:1106:3
#15 0x00000000000c445c /data/app/~~qXxv0aAYUhSQU9xS9x1uWw==/org.freedesktop.monado.openxr_runtime.out_of_process-OfuVv3zE0IUZG5twCxe0uA==/lib/arm64/libmonado-service.so (BuildId: 79d70f4a017a864bf415398f79157fba242f039e)
xrt_prober_select
/home/ryan/src/monado-android/src/xrt/include/xrt/xrt_prober.h:388:9
#16 0x00000000000c4210 /data/app/~~qXxv0aAYUhSQU9xS9x1uWw==/org.freedesktop.monado.openxr_runtime.out_of_process-OfuVv3zE0IUZG5twCxe0uA==/lib/arm64/libmonado-service.so (BuildId: 79d70f4a017a864bf415398f79157fba242f039e)
legacy_open_system
/home/ryan/src/monado-android/src/xrt/targets/common/target_builder_legacy.c:140:8
#17 0x00000000000b2ec0 /data/app/~~qXxv0aAYUhSQU9xS9x1uWw==/org.freedesktop.monado.openxr_runtime.out_of_process-OfuVv3zE0IUZG5twCxe0uA==/lib/arm64/libmonado-service.so (BuildId: 79d70f4a017a864bf415398f79157fba242f039e)
xrt_builder_open_system
/home/ryan/src/monado-android/src/xrt/include/xrt/xrt_prober.h:634:9
#18 0x00000000000b15f0 /data/app/~~qXxv0aAYUhSQU9xS9x1uWw==/org.freedesktop.monado.openxr_runtime.out_of_process-OfuVv3zE0IUZG5twCxe0uA==/lib/arm64/libmonado-service.so (BuildId: 79d70f4a017a864bf415398f79157fba242f039e)
p_create_system
/home/ryan/src/monado-android/src/xrt/state_trackers/prober/p_prober.c:1073:10
#19 0x000000000014e71c /data/app/~~qXxv0aAYUhSQU9xS9x1uWw==/org.freedesktop.monado.openxr_runtime.out_of_process-OfuVv3zE0IUZG5twCxe0uA==/lib/arm64/libmonado-service.so (BuildId: 79d70f4a017a864bf415398f79157fba242f039e)
xrt_prober_create_system
/home/ryan/src/monado-android/src/xrt/include/xrt/xrt_prober.h:375:9
#20 0x000000000014e650 /data/app/~~qXxv0aAYUhSQU9xS9x1uWw==/org.freedesktop.monado.openxr_runtime.out_of_process-OfuVv3zE0IUZG5twCxe0uA==/lib/arm64/libmonado-service.so (u_system_devices_create_from_prober+232) (BuildId: 79d70f4a017a864bf415398f79157fba242f039e)
u_system_devices_create_from_prober
/home/ryan/src/monado-android/src/xrt/auxiliary/util/u_system_helpers.c:178:9
#21 0x00000000000aedb0 /data/app/~~qXxv0aAYUhSQU9xS9x1uWw==/org.freedesktop.monado.openxr_runtime.out_of_process-OfuVv3zE0IUZG5twCxe0uA==/lib/arm64/libmonado-service.so (BuildId: 79d70f4a017a864bf415398f79157fba242f039e)
t_instance_create_system
/home/ryan/src/monado-android/src/xrt/targets/common/target_instance.c:66:9
#22 0x00000000000a49cc /data/app/~~qXxv0aAYUhSQU9xS9x1uWw==/org.freedesktop.monado.openxr_runtime.out_of_process-OfuVv3zE0IUZG5twCxe0uA==/lib/arm64/libmonado-service.so (BuildId: 79d70f4a017a864bf415398f79157fba242f039e)
xrt_instance_create_system
/home/ryan/src/monado-android/src/xrt/include/xrt/xrt_instance.h:146:9
#23 0x00000000000a3fac /data/app/~~qXxv0aAYUhSQU9xS9x1uWw==/org.freedesktop.monado.openxr_runtime.out_of_process-OfuVv3zE0IUZG5twCxe0uA==/lib/arm64/libmonado-service.so (BuildId: 79d70f4a017a864bf415398f79157fba242f039e)
init_all
/home/ryan/src/monado-android/src/xrt/ipc/server/ipc_server_process.c:487:9
#24 0x00000000000a3d28 /data/app/~~qXxv0aAYUhSQU9xS9x1uWw==/org.freedesktop.monado.openxr_runtime.out_of_process-OfuVv3zE0IUZG5twCxe0uA==/lib/arm64/libmonado-service.so (ipc_server_main_android+104) (BuildId: 79d70f4a017a864bf415398f79157fba242f039e)
ipc_server_main_android
/home/ryan/src/monado-android/src/xrt/ipc/server/ipc_server_process.c:938:12
#25 0x0000000000096450 /data/app/~~qXxv0aAYUhSQU9xS9x1uWw==/org.freedesktop.monado.openxr_runtime.out_of_process-OfuVv3zE0IUZG5twCxe0uA==/lib/arm64/libmonado-service.so (BuildId: 79d70f4a017a864bf415398f79157fba242f039e)
(anonymous namespace)::IpcServerHelper::startServer()::'lambda'()::operator()() const
/home/ryan/src/monado-android/src/xrt/targets/service-lib/service_target.cpp:57:16
#26 0x00000000000963d8 /data/app/~~qXxv0aAYUhSQU9xS9x1uWw==/org.freedesktop.monado.openxr_runtime.out_of_process-OfuVv3zE0IUZG5twCxe0uA==/lib/arm64/libmonado-service.so (BuildId: 79d70f4a017a864bf415398f79157fba242f039e)
decltype(std::__ndk1::forward<(anonymous namespace)::IpcServerHelper::startServer()::'lambda'()>(fp)()) std::__ndk1::__invoke<(anonymous namespace)::IpcServerHelper::startServer()::'lambda'()>((anonymous namespace)::IpcServerHelper::startServer()::'lambda'()&&)
/home/ryan/Android/Sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/linux-x86_64/sysroot/usr/include/c++/v1/type_traits:3501:1
#27 0x0000000000096338 /data/app/~~qXxv0aAYUhSQU9xS9x1uWw==/org.freedesktop.monado.openxr_runtime.out_of_process-OfuVv3zE0IUZG5twCxe0uA==/lib/arm64/libmonado-service.so (BuildId: 79d70f4a017a864bf415398f79157fba242f039e)
void std::__ndk1::__thread_execute<std::__ndk1::unique_ptr<std::__ndk1::__thread_struct, std::__ndk1::default_delete<std::__ndk1::__thread_struct> >, (anonymous namespace)::IpcServerHelper::startServer()::'lambda'()>(std::__ndk1::tuple<std::__ndk1::unique_ptr<std::__ndk1::__thread_struct, std::__ndk1::default_delete<std::__ndk1::__thread_struct> >, (anonymous namespace)::IpcServerHelper::startServer()::'lambda'()>&, std::__ndk1::__tuple_indices<>)
/home/ryan/Android/Sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/linux-x86_64/sysroot/usr/include/c++/v1/thread:273:5
#28 0x0000000000095ca8 /data/app/~~qXxv0aAYUhSQU9xS9x1uWw==/org.freedesktop.monado.openxr_runtime.out_of_process-OfuVv3zE0IUZG5twCxe0uA==/lib/arm64/libmonado-service.so (BuildId: 79d70f4a017a864bf415398f79157fba242f039e)
void* std::__ndk1::__thread_proxy<std::__ndk1::tuple<std::__ndk1::unique_ptr<std::__ndk1::__thread_struct, std::__ndk1::default_delete<std::__ndk1::__thread_struct> >, (anonymous namespace)::IpcServerHelper::startServer()::'lambda'()> >(void*)
/home/ryan/Android/Sdk/ndk/21.4.7075529/toolchains/llvm/prebuilt/linux-x86_64/sysroot/usr/include/c++/v1/thread:283:5
#29 0x00000000000b1910 /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+264) (BuildId: ba489d4985c0cf173209da67405662f9)
#30 0x00000000000513f0 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: ba489d4985c0cf173209da67405662f9)
```
</details>https://gitlab.freedesktop.org/monado/monado/-/issues/310Bad PThreads4W CMake Config2024-02-05T17:00:08ZGabriel PizarroBad PThreads4W CMake ConfigBuilding on Windows fails unless I make edits to the PThreads4W cmake config.
System:
- Windows 11 x64 22635
- CMake 3.24.2 w/ MS Visual Studio 2022 toolchain
Reproduce:
```
vcpkg install
mkdir build
cd build
cmake .. -DCMAKE_PREFIX_P...Building on Windows fails unless I make edits to the PThreads4W cmake config.
System:
- Windows 11 x64 22635
- CMake 3.24.2 w/ MS Visual Studio 2022 toolchain
Reproduce:
```
vcpkg install
mkdir build
cd build
cmake .. -DCMAKE_PREFIX_PATH="../vcpkg_installed"
```
Which fails with message:
```
CMake Error at CMakeLists.txt:139 (find_package):
By not providing "Findpthreads_windows.cmake" in CMAKE_MODULE_PATH this
project has asked CMake to find a package configuration file provided by
"pthreads_windows", but CMake did not find one.
Could not find a package configuration file provided by "pthreads_windows"
with any of the following names:
pthreads_windowsConfig.cmake
pthreads_windows-config.cmake
```
The pthreads_windows cmake config in `vcpkg_installed/x64-windows/share/pthreads_windows` doesn't have either of those names, and renaming the config results in more errors. Instead, I changed [CMakeLists:139](https://gitlab.freedesktop.org/monado/monado/-/blob/main/CMakeLists.txt?ref_type=heads#L139):
```diff
- find_package(pthreads_windows REQUIRED)
+ find_package(PThreads4W REQUIRED)
```
and in `vcpkg_installed/x64-windows/share/PThreads4W/PThreads4WConfig.cmake` replaced all `${_VCPKG_INSTALLED_DIR}/${VCPKG_TARGET_TRIPLET}` to `${PACKAGE_PREFIX_DIR}` (the paths weren't being found).
Then everything builds nicely. Not sure if this is a bug, or if it's just me.https://gitlab.freedesktop.org/monado/monado/-/issues/321CTS-multithreading failure2024-01-29T08:01:22Zhadrian WangCTS-multithreading failureThere was an OpenGL multithreading context issue, and I thought this MR fixed it [Misc fixes from android work (!1377) · Merge requests · Monado / Monado · GitLab](https://gitlab.freedesktop.org/monado/monado/-/merge_requests/1377)
Howe...There was an OpenGL multithreading context issue, and I thought this MR fixed it [Misc fixes from android work (!1377) · Merge requests · Monado / Monado · GitLab](https://gitlab.freedesktop.org/monado/monado/-/merge_requests/1377)
However, I still have the same CTS-multithreading failure using the latest out-of-process Monado runtime on android.
Could anyone help check if this is happening on your platform?https://gitlab.freedesktop.org/monado/monado/-/issues/206Still Android problems with newer SDK version2023-10-26T09:54:02ZRylie PavlikStill Android problems with newer SDK versionTried using my android teapot demo built with a modified 1.0.25 loader (modified to say the stl is "none" so it appeases prefab) for SDK level 33, and the out of process runtime. I'm getting this error, which looks like essentially a sib...Tried using my android teapot demo built with a modified 1.0.25 loader (modified to say the stl is "none" so it appeases prefab) for SDK level 33, and the out of process runtime. I'm getting this error, which looks like essentially a sibling of the issue fixed in !1476, except I have even less idea how to fix this one, short of adding a query element to the app manifest which is a non-starter:
```
09-19 11:22:50.450 21220 21243 I monado-ipc-client: blockingConnect
09-19 11:22:50.450 21220 21243 I monado-ipc-client: bind
09-19 11:22:50.451 21220 21243 W System.err: android.content.pm.PackageManager$NameNotFoundException: Application package org.freedesktop.monado.openxr_runtime.out_of_process not found
09-19 11:22:50.451 21220 21243 W System.err: at android.app.ContextImpl.createPackageContextAsUser(ContextImpl.java:2525)
09-19 11:22:50.451 21220 21243 W System.err: at android.app.ContextImpl.createPackageContext(ContextImpl.java:2490)
09-19 11:22:50.451 21220 21243 W System.err: at android.content.ContextWrapper.createPackageContext(ContextWrapper.java:1000)
09-19 11:22:50.451 21220 21243 W System.err: at org.freedesktop.monado.ipc.Client.bind(Client.java:246)
09-19 11:22:50.451 21220 21243 W System.err: at org.freedesktop.monado.ipc.Client.blockingConnect(Client.java:146)
09-19 11:22:50.451 21220 21243 E monado-ipc-client: bind: Could not find package org.freedesktop.monado.openxr_runtime.out_of_process
09-19 11:22:50.451 21220 21243 E monado-ipc-client: Bind failed immediately
09-19 11:22:50.451 21220 21243 E ipc_connect: Service Connect error!
09-19 11:22:50.451 21220 21243 E ipc_instance_create: Failed to connect to monado service process
09-19 11:22:50.451 21220 21243 E ipc_instance_create:
09-19 11:22:50.451 21220 21243 E ipc_instance_create: ###
09-19 11:22:50.451 21220 21243 E ipc_instance_create: #
09-19 11:22:50.451 21220 21243 E ipc_instance_create: # Please make sure that the service process is running
09-19 11:22:50.451 21220 21243 E ipc_instance_create: #
09-19 11:22:50.451 21220 21243 E ipc_instance_create: # It is called "monado-service"
09-19 11:22:50.451 21220 21243 E ipc_instance_create: # For builds it's located "build-dir/src/xrt/targets/service/monado-service"
09-19 11:22:50.451 21220 21243 E ipc_instance_create: #
09-19 11:22:50.451 21220 21243 E ipc_instance_create: ###
```
cc @quic_jarvhuan
For clarity: Hello XR still works but it's building for SDK 29.https://gitlab.freedesktop.org/monado/monado/-/issues/207Android: App still appears to render after being "switched away", blocking al...2022-09-28T15:19:06ZRylie PavlikAndroid: App still appears to render after being "switched away", blocking all other appsThis has been around for a while, in the "Service" "Draw over other apps", but it makes it pretty challenging to use.
Somehow we need to get the event that the app activity is no longer active, and stop drawing ourselves (and update the...This has been around for a while, in the "Service" "Draw over other apps", but it makes it pretty challenging to use.
Somehow we need to get the event that the app activity is no longer active, and stop drawing ourselves (and update the openxr session state accordingly). Not sure how easy it is to inject some kind of lifecycle observer in.
One thing that did cross my mind, it appears that there's a surfaceDestroyed callback being triggered in the app, we could inject our own view/surface into the app even if we're doing draw-over from the service, just to get that callback, if we needed to, but that's probably less elegant than preferred.
cc @quic_jarvhuanhttps://gitlab.freedesktop.org/monado/monado/-/issues/187Segfault when attempting to run monado without libsurvive2022-09-14T00:22:59ZSupreeemeSegfault when attempting to run monado without libsurviveI want to try to use the vive driver without libsurvive, but monado segfaults. I launch it with `SETUP_VIVE_OVER_SURVIVE=true monado-service`. Here is a backtrace:
```
(gdb) bt
#0 0x00007f49e7886912 in () at /usr/lib/libvulkan_radeon.s...I want to try to use the vive driver without libsurvive, but monado segfaults. I launch it with `SETUP_VIVE_OVER_SURVIVE=true monado-service`. Here is a backtrace:
```
(gdb) bt
#0 0x00007f49e7886912 in () at /usr/lib/libvulkan_radeon.so
#1 0x00007f49e792bd8d in () at /usr/lib/libvulkan_radeon.so
#2 0x000055854fefb9c1 in vk_alloc_and_bind_image_memory
(vk=0x5585506955c8, image=0x558550c41110, max_size=18446744073709551615, pNext_for_allocate=0x0, caller_name=0x5585501e4120 <__func__.10> "vk_create_image_simple", out_mem=0x558550e441d0, out_size=0x0)
at /mnt/xtra/dev/monado/src/xrt/auxiliary/vk/vk_helpers.c:496
#3 0x000055854fefbbbf in vk_create_image_simple (vk=0x5585506955c8, extent=..., format=VK_FORMAT_B8G8R8A8_SRGB, usage=21, out_mem=0x558550e441d0, out_image=0x558550e441c8) at /mnt/xtra/dev/monado/src/xrt/auxiliary/vk/vk_helpers.c:545
#4 0x000055854fee016e in _init_frame_buffer (self=0x558550e441c0, format=VK_FORMAT_B8G8R8A8_SRGB, rp=0x558550d9d0b0, eye=0) at /mnt/xtra/dev/monado/src/xrt/compositor/main/comp_layer_renderer.c:410
#5 0x000055854fee064d in _init (self=0x558550e441c0, s=0x558550697318, vk=0x5585506955c8, extent=..., format=VK_FORMAT_B8G8R8A8_SRGB) at /mnt/xtra/dev/monado/src/xrt/compositor/main/comp_layer_renderer.c:502
#6 0x000055854fee083f in comp_layer_renderer_create (vk=0x5585506955c8, s=0x558550697318, extent=..., format=VK_FORMAT_B8G8R8A8_SRGB) at /mnt/xtra/dev/monado/src/xrt/compositor/main/comp_layer_renderer.c:541
#7 0x000055854fed9d9b in renderer_create_layer_renderer (r=0x558550e58510) at /mnt/xtra/dev/monado/src/xrt/compositor/main/comp_renderer.c:474
#8 0x000055854fed9f7a in renderer_ensure_images_and_renderings (r=0x558550e58510, force_recreate=false) at /mnt/xtra/dev/monado/src/xrt/compositor/main/comp_renderer.c:539
#9 0x000055854feda0aa in renderer_create (r=0x558550e58510, c=0x558550695480) at /mnt/xtra/dev/monado/src/xrt/compositor/main/comp_renderer.c:567
#10 0x000055854fedd1cd in comp_renderer_create (c=0x558550695480) at /mnt/xtra/dev/monado/src/xrt/compositor/main/comp_renderer.c:1589
#11 0x000055854fed7458 in compositor_init_renderer (c=0x558550695480) at /mnt/xtra/dev/monado/src/xrt/compositor/main/comp_compositor.c:1114
#12 0x000055854fed7939 in xrt_gfx_provider_create_system (xdev=0x55855067c7e0, out_xsysc=0x7ffcc4804300) at /mnt/xtra/dev/monado/src/xrt/compositor/main/comp_compositor.c:1181
#13 0x000055854fe7e1cb in t_instance_create_system (xinst=0x5585506642e0, out_xsysd=0x55855064f648, out_xsysc=0x55855064f650) at /mnt/xtra/dev/monado/src/xrt/targets/common/target_instance.c:82
#14 0x000055854fe75c06 in xrt_instance_create_system (xinst=0x5585506642e0, out_xsysd=0x55855064f648, out_xsysc=0x55855064f650) at /mnt/xtra/dev/monado/src/xrt/include/xrt/xrt_instance.h:137
#15 0x000055854fe77125 in init_all (s=0x55855064f630) at /mnt/xtra/dev/monado/src/xrt/ipc/server/ipc_server_process.c:474
#16 0x000055854fe77b9c in ipc_server_main (argc=1, argv=0x7ffcc48044e8) at /mnt/xtra/dev/monado/src/xrt/ipc/server/ipc_server_process.c:794
#17 0x000055854fe75b5e in main (argc=1, argv=0x7ffcc48044e8) at /mnt/xtra/dev/monado/src/xrt/targets/service/main.c:28
```
Monado runs with no issues if I just use libsurvive.https://gitlab.freedesktop.org/monado/monado/-/issues/195Monado Refuses to release the VIVE HMD correctly upon shutdown2022-09-09T14:54:10ZJaryed WoodMonado Refuses to release the VIVE HMD correctly upon shutdownI did an update to monado, and suddenly found that my Vive HMD wouldnt come out of standby when trying to run the service. The light on the side of the HMD doesnt turn green and the display wont wake up. The headset does seem to be detec...I did an update to monado, and suddenly found that my Vive HMD wouldnt come out of standby when trying to run the service. The light on the side of the HMD doesnt turn green and the display wont wake up. The headset does seem to be detected through libsurvive though
After running monado I also found I had to reboot my system before SteamVR - which i also have installed could recognize that my headset even existed and use it.
System Specs
- Linux 5.19.3-269-tkg-cfs (also tried stock linux kernel and TKG 5.18) - makes no difference
- NVIDIA RTX 2070, running proprietary drivers 515.65.01, (also tried an older 5.15, also made no difference)
- Monado via AUR (monado-git 0.9.0.25.git.4f97fe0-1, reports in logs as v21.0.0-2373-g4de631285)
- libsurvive (libsurvive-git 2216.5319743-1, also tried libsurvive 1.0.2, no difference)
Log File (with all debug environment variables enabled)
[monado-service.log](/uploads/ca73e270999f5d3d8fb86bec1a036612/monado-service.log)https://gitlab.freedesktop.org/monado/monado/-/issues/27Make sure to depend on OpenHMD 0.3 in CMake files2022-09-08T22:51:47ZJakob BornecrantzMake sure to depend on OpenHMD 0.3 in CMake filesSee issue #25.See issue #25.Rylie PavlikRylie Pavlikhttps://gitlab.freedesktop.org/monado/monado/-/issues/189Readback window doesn't work on nvidia2022-09-08T16:56:19ZMoses TurnerReadback window doesn't work on nvidiaInstead of any visible content it's just a black window.
This has happened on
* The 3080 assigned to me
* @SafariMonkey's 3090
* @danwillm's 2070 Super
Unsure if this is an upstream nvidia driver issue, or if I setup the barriers wrong ...Instead of any visible content it's just a black window.
This has happened on
* The 3080 assigned to me
* @SafariMonkey's 3090
* @danwillm's 2070 Super
Unsure if this is an upstream nvidia driver issue, or if I setup the barriers wrong when I wrote that code.
![image](/uploads/13f8aecfe53d53b18ae6fa501bbd9391/image.png)https://gitlab.freedesktop.org/monado/monado/-/issues/190Equirect Layer Issues2022-09-08T16:30:38ZBjorn SwensonEquirect Layer IssuesThey are supposed to be rendered as the interior of a sphere, with the ability to be positioned and scaled relative to a space. Currently, equirect layers are always fullscreen in monado and the radius property is ignored.They are supposed to be rendered as the interior of a sphere, with the ability to be positioned and scaled relative to a space. Currently, equirect layers are always fullscreen in monado and the radius property is ignored.https://gitlab.freedesktop.org/monado/monado/-/issues/188VK_ERROR_SURFACE_LOST_KHR when running monado-service on RADV2022-09-08T16:17:29Zkwahoo2VK_ERROR_SURFACE_LOST_KHR when running monado-service on RADVHi,
I am trying to get monado-service running on x86 desktop with Radeon 6600XT and Valve Index.
Unfortunately I am getting:
```
ERROR [renderer_present_swapchain_image] vk_swapchain_present: VK_ERROR_SURFACE_LOST_KHR
ERROR [renderer_a...Hi,
I am trying to get monado-service running on x86 desktop with Radeon 6600XT and Valve Index.
Unfortunately I am getting:
```
ERROR [renderer_present_swapchain_image] vk_swapchain_present: VK_ERROR_SURFACE_LOST_KHR
ERROR [renderer_acquire_swapchain_image] comp_target_acquire: VK_ERROR_SURFACE_LOST_KHR
```
Logs (monado-service, vulkaninfo and hello_xr output) are here https://gist.github.com/kwahoo2/0098b22d2c4c8e8b7b3b4696e5d3d709
Is out of process compositing the indented way to run Monado in HMD or WiP still?
Both
`XRT_COMPOSITOR_FORCE_WAYLAND=1 monado-service`
and
`XRT_COMPOSITOR_FORCE_XCB=1 monado-service`
display VR view (inside a desktop window) correctly.https://gitlab.freedesktop.org/monado/monado/-/issues/184ahardwarebuffer format not support2022-09-08T16:10:07Zcxyahardwarebuffer format not supportwhen i run test_xrCreateSwapchain.cpp
the one test item test format VK_FORMAT_D32_SFLOAT_S8_UINT,
in my service I use AHardwareBuffer,there not have AHardwareBuffer formart correspondence to VK_FORMAT_D32_SFLOAT_S8_UINT.
so this test cra...when i run test_xrCreateSwapchain.cpp
the one test item test format VK_FORMAT_D32_SFLOAT_S8_UINT,
in my service I use AHardwareBuffer,there not have AHardwareBuffer formart correspondence to VK_FORMAT_D32_SFLOAT_S8_UINT.
so this test crash. how can I deal with it,did I not use AHardwareBuffer ? or just not test it and return sucess ? can you help me ,thanks.
```
E AdrenoUtils: <validate_memory_layout_input_parmas:2270>: Unknown Format 0
06-12 03:31:01.258 1769 1810 E AdrenoUtils: <adreno_init_memory_layout:5093>: Memory Layout input parameter validation failed!
06-12 03:31:01.258 1769 1810 E qdgralloc: GetGpuResourceSizeAndDimensions Graphics metadata init failed
06-12 03:31:01.258 1769 1810 E Gralloc3: isSupported(2160, 2160, 52, 1, ...) failed with 1
06-12 03:31:01.258 845 1287 E qdgralloc: GetGpuPixelFormat: No map for format: 0x34
06-12 03:31:01.258 845 1287 E AdrenoUtils: <validate_memory_layout_input_parmas:2270>: Unknown Format 0
06-12 03:31:01.258 845 1287 E AdrenoUtils: <adreno_init_memory_layout:5093>: Memory Layout input parameter validation failed!
06-12 03:31:01.258 845 1287 E qdgralloc: GetGpuResourceSizeAndDimensions Graphics metadata init failed
```https://gitlab.freedesktop.org/monado/monado/-/issues/169Basalt core dumped2022-08-31T18:16:15ZFlorian RicherBasalt core dumpedWhen i check send to basalt slam.
monado-service crash with this error.
```
Setting up filter: t_ns 39645986652796
T_w_i
0.998141 -0.0423707 0.0438201 0
-0.0423707 0.0345201 0.998505 0
-0.0438201 -0.998505 0.03...When i check send to basalt slam.
monado-service crash with this error.
```
Setting up filter: t_ns 39645986652796
T_w_i
0.998141 -0.0423707 0.0438201 0
-0.0423707 0.0345201 0.998505 0
-0.0438201 -0.998505 0.0326606 0
0 0 0 1
vel_w_i 0 0 0
***** Assertion (ba_diff.template segment<3>(3).isApproxToConstant(0)) failed in basalt::IntegratedImuMeasurement<Scalar_>::VecN basalt::IntegratedImuMeasurement<Scalar_>::residual(const basalt::PoseVelState<Scalar_>&, const Vec3&, const basalt::PoseVelState<Scalar_>&, const Vec3&, const Vec3&, basalt::IntegratedImuMeasurement<Scalar_>::MatNN*, basalt::IntegratedImuMeasurement<Scalar_>::MatNN*, basalt::IntegratedImuMeasurement<Scalar_>::MatN3*, basalt::IntegratedImuMeasurement<Scalar_>::MatN3*) const [with Scalar_ = float; basalt::IntegratedImuMeasurement<Scalar_>::VecN = Eigen::Matrix<float, 9, 1, 0, 9, 1>; basalt::IntegratedImuMeasurement<Scalar_>::Vec3 = Eigen::Matrix<float, 3, 1>; basalt::IntegratedImuMeasurement<Scalar_>::MatNN = Eigen::Matrix<float, 9, 9, 0, 9, 9>; basalt::IntegratedImuMeasurement<Scalar_>::MatN3 = Eigen::Matrix<float, 9, 3, 0, 9, 3>]:
/tmp/pamac-build-florian/basalt-monado-git/src/basalt/thirdparty/basalt-headers/include/basalt/imu/preintegration.h:234:
zsh: IOT instruction (core dumped) monado-service
```
and with BASALT_DISABLE_ASSERTS
```
T_w_i
0.998361 -0.0397558 0.0411671 0
-0.0397558 0.0356598 0.998573 0
-0.0411671 -0.998573 0.0340208 0
0 0 0 1
vel_w_i 0 0 0
Sophus ensure failed in function 'static Sophus::SO3<Scalar_> Sophus::SO3<Scalar_, Options>::expAndTheta(const Tangent&, Sophus::SO3<Scalar_, Options>::Scalar*) [with Scalar_ = float; int Options = 0; Sophus::SO3<Scalar_, Options>::Tangent = Eigen::Matrix<float, 3, 1>; Sophus::SO3<Scalar_, Options>::Scalar = float]', file '/home/florian/Téléchargements/basalt-monado-git/src/basalt/thirdparty/basalt-headers/thirdparty/Sophus/sophus/so3.hpp', line 701.
SO3::exp failed! omega: nan nan nan, real: nan, img: nan
zsh: IOT instruction (core dumped) monado-service
```
Env:
```
# Monado
export bsltinstall=/usr
export bsltdeps=/usr/etc
export oxrinstall=/usr
export PATH=$bsltinstall/bin:$PATH
export PKG_CONFIG_PATH=$bsltinstall/lib/pkgconfig:$PKG_CONFIG_PATH # for compile time pkg-config
export LD_LIBRARY_PATH=$bsltinstall/lib/:$LD_LIBRARY_PATH # for runtime ld
export LIBRARY_PATH=$bsltinstall/lib/:$LIBRARY_PATH # for compile time gcc
export PROBER_LOG=debug
export OXR_DEBUG_GUI=1
export XR_RUNTIME_JSON=$oxrinstall/share/openxr/1/openxr_monado.json
export WMR_LOG=debug
export SLAM_LOG=debug
export SLAM_SUBMIT_FROM_START=false
export SLAM_CONFIG=$bsltdeps/basalt/monado/odysseyplus_kb4.toml
# FORCE TO ENABLE RENDERING IN HMD | AllowHMD Nvidia | Gnome can disable all screen because it not a desktop mode
export XRT_COMPOSITOR_FORCE_XCB=1
```https://gitlab.freedesktop.org/monado/monado/-/issues/182Getting Close with New Raspberry-Rift Attempt! Getting swapchain error on mon...2022-07-18T16:27:54ZBlueroom VRGetting Close with New Raspberry-Rift Attempt! Getting swapchain error on monado-service start.Hello! I'm back to trying to get my Rift CV1 to work on my RPi4b but this time I moved to
Raspberry Ubuntu 22.04 64bit - uses Wayland by default.
My goal is to do direct KMSDRM render using Vulkan, ideally straight to HMD without exitin...Hello! I'm back to trying to get my Rift CV1 to work on my RPi4b but this time I moved to
Raspberry Ubuntu 22.04 64bit - uses Wayland by default.
My goal is to do direct KMSDRM render using Vulkan, ideally straight to HMD without exiting to cli tty but exiting to tty is ok too.
Iv'e fiddled a lot and think I managed to create a good edid file that the system accepts.
```
> modetest -c
41 0 connected HDMI-A-2 0x0 1 40
modes:
index name refresh (Hz) hdisp hss hse htot vdisp vss vse vtot
#0 2160x1200 90.00 2160 2168 2200 2240 1200 1250 1252 1472 296750 flags: phsync, nvsync; type: preferred, userdef, driver
```
'non-desktop' is set to 1
But when I in tty run,
XRT_COMPOSITOR_FORCE_VK_DISPLAY=1 monado-service
it starts off promising but then Errors.
See this output https://pastebin.com/P5f56SsX
OpenHMD is installed and 'monado-cli test' finds the Rift.
This is my 'vulkaninfo' output, https://pastebin.com/JnWTiyr0
Is anyone able to help guessing what I might be missing or what's going wrong?
Cheers!
Fredhttps://gitlab.freedesktop.org/monado/monado/-/issues/181"initialized" asserts in os_threading.h cause problems2022-06-29T14:34:27ZJan Schmidt"initialized" asserts in os_threading.h cause problemscommit 14aed90183166851e15437cf128b05534466ee5d introduced assertions to ensure threading primitives are correctly initialized before use, but the ones in the `_destroy()` trigger during some error cleanup paths.
For example, in [init_a...commit 14aed90183166851e15437cf128b05534466ee5d introduced assertions to ensure threading primitives are correctly initialized before use, but the ones in the `_destroy()` trigger during some error cleanup paths.
For example, in [init_all in ipc_server_process.c](https://gitlab.freedesktop.org/monado/monado/-/blob/8729c0485eb3bf6d3b042cdb8ea8626b693511ea/src/xrt/ipc/server/ipc_server_process.c#L449) the `global_state.lock` is initialized last. If the startup fails, `teardown_all` will call `os_mutex_destroy` on a mutex that was never initialized, triggering the assert.
I think there are 3 options:
1) All such cases need to do conditional clean up, not calling destroy on threading primitives in such cases
2) Assume calling `_destroy()` on a zeroed but uninitialized primitive is a no-op as before and remove the asserts
3) Always store and use the `initialized` flag even in release builds inside the threading primitives and skip destroy if they were never initialized.
The last one seems most explicit, and I think should be fine - the extra storage requirement is negligible and initializing and destroying threading primitives is not a performance sensitive path.https://gitlab.freedesktop.org/monado/monado/-/issues/177Monado triggers NVIDIA 515 graphics exception and system hang2022-06-28T16:12:00ZJames HoganMonado triggers NVIDIA 515 graphics exception and system hangAfter a few minutes of use, monado-git 21.0.0.r2124.g604815cb-1 (from AUR on archlinux) appears to trigger a graphics exception that hangs the whole system (blank screen, caps lock LED unresponsive) on nvidia-dkms 515.43.04-1 and linux-h...After a few minutes of use, monado-git 21.0.0.r2124.g604815cb-1 (from AUR on archlinux) appears to trigger a graphics exception that hangs the whole system (blank screen, caps lock LED unresponsive) on nvidia-dkms 515.43.04-1 and linux-hardened 5.17.11.hardened2-1. I'm using a GTX 1060 6GB.
Smells like a bug in their driver, but presumably of value to track here too (?). I hit it just messing around with monado with xrgears the other day, and trying the blender VR scene inspection plugin today.
Here's all thats recorded in the kernel log after a reset:
```
Jun 07 23:10:35 saruman kernel: NVRM: GPU at PCI:0000:01:00: GPU-ae03aa93-2002-dd03-a42f-bf4df2f0ce76
Jun 07 23:10:35 saruman kernel: NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception: Class 0x1 Subchannel 0x0 Mismatch
Jun 07 23:10:35 saruman kernel: NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception: ESR 0x4041b0=0x80001
Jun 07 23:10:35 saruman kernel: NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception: ESR 0x404000=0x80000002
Jun 07 23:10:35 saruman kernel: NVRM: Xid (PCI:0000:01:00): 13, pid=271472, name=monado-service, Graphics Exception: ChID 00d3, Class 0000c197, Offset 00001b0c, Data 10000000
Jun 07 23:10:46 saruman kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000927c:2 2:0:336:328
Jun 07 23:10:51 saruman kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000927c:2 2:0:336:328
Jun 07 23:10:56 saruman kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000927c:2 2:0:336:328
Jun 07 23:11:01 saruman kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000927c:2 2:0:336:328
Jun 07 23:11:06 saruman kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000927c:2 2:0:336:328
Jun 07 23:11:11 saruman kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000927c:2 2:0:336:328
Jun 07 23:11:16 saruman kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000927c:2 2:0:336:328
Jun 07 23:11:21 saruman kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000927c:2 2:0:336:328
Jun 07 23:11:26 saruman kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000927c:2 2:0:336:328
-- Boot c842369f5a0d4ba990c254926aabc81e --
```https://gitlab.freedesktop.org/monado/monado/-/issues/152c/main: Compositor's window isn't fullscreen under wayland2022-02-25T03:15:09ZGhost Userc/main: Compositor's window isn't fullscreen under waylandWhen using extended mode under wayland, the compositor's window isn't sized correctly.
even when made fullscreen (using sway), the lens distortion (inside window) stays the same size.
Not sure if useful, but I've attached some screensho...When using extended mode under wayland, the compositor's window isn't sized correctly.
even when made fullscreen (using sway), the lens distortion (inside window) stays the same size.
Not sure if useful, but I've attached some screenshots for more info.
image 1 is the window's size at startup, it's non resizable and making it fullscreen in sway doesn't do anything either, as seen in image 2.
![1](/uploads/bfc36d3b41adb071f8b2f28d7a8eee5b/1.png)![2](/uploads/88692756faae1d26f0f5a980e1fa5e7a/2.png)