Ebiten: Ebiten doesn't work with remote desktop protocol

Created on 24 Oct 2020  路  16Comments  路  Source: hajimehoshi/ebiten

When I run go build, it generates an executable file called main. When I run main, however, I get an error.

No protocol specified
2020/10/23 19:27:01 PlatformError: X11: Failed to open display :10.0
panic: NotInitialized: The GLFW library is not initialized

goroutine 1 [running]:
github.com/go-gl/glfw/v3.3/glfw.acceptError(0x0, 0x0, 0x0, 0x0, 0x10006)
    /home/pi/go/src/github.com/go-gl/glfw/v3.3/glfw/error.go:174 +0x1a4
github.com/go-gl/glfw/v3.3/glfw.panicError(...)
    /home/pi/go/src/github.com/go-gl/glfw/v3.3/glfw/error.go:185
github.com/go-gl/glfw/v3.3/glfw.WindowHint(0x20004, 0x0)
    /home/pi/go/src/github.com/go-gl/glfw/v3.3/glfw/window.go:275 +0x40
github.com/hajimehoshi/ebiten/internal/glfw.WindowHint(...)
    /home/pi/go/src/github.com/hajimehoshi/ebiten/internal/glfw/glfw_notwindows.go:329
github.com/hajimehoshi/ebiten/internal/uidriver/glfw.initialize(0x87e500, 0x5582c)
    /home/pi/go/src/github.com/hajimehoshi/ebiten/internal/uidriver/glfw/ui.go:133 +0x3c
github.com/hajimehoshi/ebiten/internal/uidriver/glfw.init.1()
    /home/pi/go/src/github.com/hajimehoshi/ebiten/internal/uidriver/glfw/ui.go:120 +0x14

Perhaps it fails to initialize because of (a) Failed to open display :10.0 or (b) No protocol specified?

bug linux
Source
picture 01556

Most helpful comment

@hajimehoshi i'm no expert, the most I do with DISPLAY is prefix commands with DISPLAY=:0.

@goisgreat what happens if you do DISPLAY=:0 ./main, whre main is your output exe ?

EDIT: I am going to take a guess that @goisgreat is connecting to his rpi via ssh. if this is the case, he would need to edit his sshd config (on the rpi) to allow x11 forwarding. After that is done, when he ssh's into the rpi he needs to add the -X arg to forward the x session stuff. This would run the app on the rpi, but forward the window to wherever he's connecting from. The performance is gonna be terribad, though. I would advise against this.

The better option is to connect the rpi to an hdmi monitor and prefix his commands that launch gui applications with DISPLAY=:0. This way, he can still drive it via ssh, and it should launch the app with the local hdmi output for the rpi.

picture gravestench on 26 Oct 2020
👍2

All 16 comments

BTW, I'm using a raspberry pi, so please consider this issue unique from other operating systems.

01556 picture 01556 on 24 Oct 2020

Hi, I think you have solved the issue (https://github.com/hajimehoshi/ebiten/issues/1401#issuecomment-714800216), but now you run into the same issue?

hajimehoshi picture hajimehoshi on 24 Oct 2020

2020/10/23 19:27:01 PlatformError: X11: Failed to open display :10.0

I guess this is an issue in X. I'm not so familiar with it, but is the DISPLAY environment set correctly?

hajimehoshi picture hajimehoshi on 24 Oct 2020

I decided to open this in a new issue.... It broke again for some reason. Also, here is the results of env | grep DISPLAY:

DISPLAY=:10.0
01556 picture 01556 on 24 Oct 2020

I can't tell this is the correct value or not. Do the other X applications work?

hajimehoshi picture hajimehoshi on 24 Oct 2020

What is an "X application"? If you mean applications that spawn windows on the raspberry pi's graphical desktop, then yes. There is an RDP server running on the raspberry pi, so from my laptop I can view the graphical desktop. From the RDP client (remmina), I can start up a terminal window fine, but whenever I run my golang desktop application, it dies!

01556 picture 01556 on 24 Oct 2020

Maybe I could compile to WASM and then run it in a browser.... Lemme try that now.

01556 picture 01556 on 24 Oct 2020

Ebiten should work on Raspberry Pi, but unfortunately I'm not an expert about X.

If you mean applications that spawn windows on the raspberry pi's graphical desktop

Yes, I meant that.

@gravestench do you have any insights in this issue? Thanks.

hajimehoshi picture hajimehoshi on 24 Oct 2020

@hajimehoshi i'm no expert, the most I do with DISPLAY is prefix commands with DISPLAY=:0.

@goisgreat what happens if you do DISPLAY=:0 ./main, whre main is your output exe ?

EDIT: I am going to take a guess that @goisgreat is connecting to his rpi via ssh. if this is the case, he would need to edit his sshd config (on the rpi) to allow x11 forwarding. After that is done, when he ssh's into the rpi he needs to add the -X arg to forward the x session stuff. This would run the app on the rpi, but forward the window to wherever he's connecting from. The performance is gonna be terribad, though. I would advise against this.

The better option is to connect the rpi to an hdmi monitor and prefix his commands that launch gui applications with DISPLAY=:0. This way, he can still drive it via ssh, and it should launch the app with the local hdmi output for the rpi.

gravestench picture gravestench on 26 Oct 2020
👍2

@gravestench I'm using a RDP (remote desktop protocol) client to connect to my raspberry pi because I need to access the graphical desktop. I switched to WASM, but I got this output.

01556 picture 01556 on 28 Oct 2020

As WebGL (or probably any libraries using GPU) doesn't work, I guess it is impossible to use Ebiten via RDP, unfortunately.

hajimehoshi picture hajimehoshi on 28 Oct 2020

Oof. Can I maybe use a cpu instead? Is there a way to let GPU-leveraging code just use the CPU?

01556 picture 01556 on 28 Oct 2020

@hajimehoshi i'm no expert, the most I do with DISPLAY is prefix commands with DISPLAY=:0.

@goisgreat what happens if you do DISPLAY=:0 ./main, whre main is your output exe ?

EDIT: I am going to take a guess that @goisgreat is connecting to his rpi via ssh. if this is the case, he would need to edit his sshd config (on the rpi) to allow x11 forwarding. After that is done, when he ssh's into the rpi he needs to add the -X arg to forward the x session stuff. This would run the app on the rpi, but forward the window to wherever he's connecting from. The performance is gonna be terribad, though. I would advise against this.

The better option is to connect the rpi to an hdmi monitor and prefix his commands that launch gui applications with DISPLAY=:0. This way, he can still drive it via ssh, and it should launch the app with the local hdmi output for the rpi.

By the way, this is the output for DISPLAY=:0 ./main:

No protocol specified
2020/10/28 13:44:45 PlatformError: X11: Failed to open display :0
panic: NotInitialized: The GLFW library is not initialized

goroutine 1 [running]:
github.com/go-gl/glfw/v3.3/glfw.acceptError(0x0, 0x0, 0x0, 0x0, 0x10006)
    /home/pi/go/src/github.com/go-gl/glfw/v3.3/glfw/error.go:174 +0x1a4
github.com/go-gl/glfw/v3.3/glfw.panicError(...)
    /home/pi/go/src/github.com/go-gl/glfw/v3.3/glfw/error.go:185
github.com/go-gl/glfw/v3.3/glfw.WindowHint(0x20004, 0x0)
    /home/pi/go/src/github.com/go-gl/glfw/v3.3/glfw/window.go:275 +0x40
github.com/hajimehoshi/ebiten/internal/glfw.WindowHint(...)
    /home/pi/go/src/github.com/hajimehoshi/ebiten/internal/glfw/glfw_notwindows.go:329
github.com/hajimehoshi/ebiten/internal/uidriver/glfw.initialize(0x1476500, 0x5583c)
    /home/pi/go/src/github.com/hajimehoshi/ebiten/internal/uidriver/glfw/ui.go:133 +0x3c
github.com/hajimehoshi/ebiten/internal/uidriver/glfw.init.1()
    /home/pi/go/src/github.com/hajimehoshi/ebiten/internal/uidriver/glfw/ui.go:120 +0x14
01556 picture 01556 on 28 Oct 2020
👀1

It's not easy to have software rendering as a fallback, but this sounds nice to have. Let me keep this issue open.

hajimehoshi picture hajimehoshi on 29 Oct 2020

Okay, thanks! I'm going to use my local machine....

01556 picture 01556 on 29 Oct 2020

Oh, please keep this open.

hajimehoshi picture hajimehoshi on 29 Oct 2020
Was this page helpful?
0 / 5 - 0 ratings

Related issues

hajimehoshi picture hajimehoshi  路  6Comments
hajimehoshi picture hajimehoshi  路  6Comments
hajimehoshi picture hajimehoshi  路  6Comments
hajimehoshi picture hajimehoshi  路  3Comments
joaowiciuk picture joaowiciuk  路  5Comments