Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

browser_main_loop.cc(278) GLib-GObject: ../glib-2.78.6/gobject/gsignal.c:2777: instance '0x2f1401930180' has no handler with id '5139' #230

Open
JarzaClay opened this issue Sep 11, 2024 · 2 comments

Comments

@JarzaClay
Copy link

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?

@JarzaClay 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
@JarzaClay
Copy link
Author

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)

@joezhouchenye
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants