zserge / lorca

Build cross-platform modern desktop apps in Go + HTML5
MIT License
8.04k stars 535 forks source link

Updated chrome - now ui.New fails to start #184

Closed karlredgate closed 10 months ago

karlredgate commented 1 year ago

Chrome version: Version 110.0.5481.177 (Official Build) (64-bit)

These are the errors from ui.New()

2023/03/08 13:25:26 websocket.Dial ws://127.0.0.1:45031/devtools/browser/396a03af-3f1b-400b-8294-9c0f2f25cd29: bad status
exit status 1

Running chrome on its own - like lorca calls it generates:

[0308/095229.172548:WARNING:bluez_dbus_manager.cc(247)] Floss manager not present, cannot set Floss enable/disable.
[0308/095229.190683:WARNING:sandbox_linux.cc(393)] InitializeSandbox() called with multiple threads in process gpu-process.
karlredgate commented 1 year ago

From another project - it looks like adding this argument resolves the issue:

--remote-allow-origins=\*
karlredgate commented 1 year ago

Also seems related to - https://github.com/zserge/lorca/issues/183

LazyForNaming commented 1 year ago

But doing it like https://github.com/zserge/lorca/issues/183 only wakes up Chrome, not the GUI as it originally did

justinmichaelvieira commented 1 year ago

https://github.com/zserge/lorca/pull/185 fixes this. Hopefully it is accepted upstream.