You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On my linux machine with my Quest 2 connected, I get the following error:
[24184:0911/193409.171686:ERROR:browser_main_loop.cc(278)] GLib-GObject: ../glib-2.78.6/gobject/gsignal.c:2777: instance '0x2f1401930180' has no handler with id '5139'
Is this documented anywhere? Does anyone have a fix for this?
The text was updated successfully, but these errors were encountered:
JarzaClay
changed the title
[24184:0911/193409.171686:ERROR:browser_main_loop.cc(278)] GLib-GObject: ../glib-2.78.6/gobject/gsignal.c:2777: instance '0x2f1401930180' has no handler with id '5139'
browser_main_loop.cc(278) GLib-GObject: ../glib-2.78.6/gobject/gsignal.c:2777: instance '0x2f1401930180' has no handler with id '5139'
Sep 14, 2024
I have also tried compiling myself, and it says the nodejs usb library does not exist, which checks out, as it is deprecated. It tries pulling an invalid version of the library, and then sidequest always says "an error has occurred" when starting (it does this in the non-usercompiled version too)
I have a similar problem with Quest3. It turns out that I need to allow adb connect in the headset side again. I used to use Windows with the same PC and didn't realize this problem.
On my linux machine with my Quest 2 connected, I get the following error:
Is this documented anywhere? Does anyone have a fix for this?
The text was updated successfully, but these errors were encountered: