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

"detected broken kqueue" error on OSX Sierra #21

Closed
emead opened this issue Oct 6, 2016 · 7 comments
Closed

"detected broken kqueue" error on OSX Sierra #21

emead opened this issue Oct 6, 2016 · 7 comments

Comments

@emead
Copy link

emead commented Oct 6, 2016

I’m getting an error when trying to run the example:
[warn] kq_init: detected broken kqueue; not using.: Undefined error: 0

Running on OSX Sierra.

Perhaps related to this chromium bug: https://bugs.chromium.org/p/chromium/issues/detail?id=626534

@alexflint
Copy link
Owner

alexflint commented Oct 23, 2016

@emead which example were you running? Or was it the example from the readme? (If from the readme, could you post your entire go source here?)

@emead
Copy link
Author

emead commented Oct 25, 2016

Using the example from the readme:

package main

import (
    "os"
    "runtime"

    "github.com/alexflint/gallium"
)

func main() {
    runtime.LockOSThread()         // must be the first statement in main - see below
    gallium.Loop(os.Args, onReady) // must be called from main function
}

func onReady(app *gallium.App) {
    app.NewWindow("http://example.com/", "Window title!")
}

However, I have since pulled the latest changes to Gallium and now get this error:
app.NewWindow undefined (type *gallium.App has no field or method NewWindow)

Can the readme please be updated with a valid example?

@emead
Copy link
Author

emead commented Oct 25, 2016

I think that the error I had was probably the same as the one raised here: #23

@Virtual-Machine
Copy link

So are these warnings critical?

I am also getting broken kqueue warnings on Mac Sierra but the application still appears to work fine as far as I can tell. I am using the latest version of Gallium and I have tried rebuilding libevent as was recommended on a few other Github projects yet I still see these warnings:

=== gallium.Loop ===
in GalliumLoop
calling content::ContentMain...
MainDelegate::BasicStartupComplete
MainDelegate::PreSandboxStartup
[warn] kq_init: detected broken kqueue; not using.: Undefined error: 0
at GalliumOpenWindow
[warn] kq_init: detected broken kqueue; not using.: Undefined error: 0
[warn] kq_init: detected broken kqueue; not using.: Undefined error: 0
[warn] kq_init: detected broken kqueue; not using.: Undefined error: 0
[warn] kq_init: detected broken kqueue; not using.: Undefined error: 0
at GalliumOpenWindowImpl
[warn] kq_init: detected broken kqueue; not using.: Undefined error: 0
2017/01/01 12:56:24 about clicked

@alexflint
Copy link
Owner

@Virtual-Machine those warnings can be safely ignored. If you figure out how to silence/fix them, please let me know!

@alexflint
Copy link
Owner

@emead readme is fixed now. Closing this issue as I have not been able to reproduce this failure on Sierra. Please reopen if you have further problems.

@alyssaraefox
Copy link

screen shot 2017-02-09 at 6 18 24 pm

I had the same issue. I know I was getting closer to running my full program in a previous development stint. However, even in that session I had lost precious hours over the program passing the incorrect string into the newly opened browsers address bar.

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

4 participants