fyne-io/terminal

GLX: Failed to create context

avarf opened this issue · 3 comments

avarf commented

I used the go get command that was mentioned in the README to install the terminal but after installation when I want to launch the fyne terminal I face below error:

$ fyneterm 
2021/01/26 15:01:58 Fyne error:  window creation error
2021/01/26 15:01:58   Cause: VersionUnavailable: GLX: Failed to create context: BadValue (integer parameter out of range for operation)
2021/01/26 15:01:58   At: /home/USER/go/src/github.com/fyne-io/terminal/vendor/fyne.io/fyne/v2/internal/driver/glfw/window.go:1306
2021/01/26 15:01:58 Unsupported graphics mode 01
2021/01/26 15:01:58 Unsupported graphics mode 00
2021/01/26 15:01:58 Unsupported graphics mode 01
2021/01/26 15:01:58 Unsupported graphics mode 00
^C

$ fyneterm -h
2021/01/26 15:02:36 Fyne error:  window creation error
2021/01/26 15:02:36   Cause: VersionUnavailable: GLX: Failed to create context: BadValue (integer parameter out of range for operation)
2021/01/26 15:02:36   At: /home/USER/go/src/github.com/fyne-io/terminal/vendor/fyne.io/fyne/v2/internal/driver/glfw/window.go:1306
2021/01/26 15:02:36 Unsupported graphics mode 01
2021/01/26 15:02:36 Unsupported graphics mode 00
2021/01/26 15:02:36 Unsupported graphics mode 01
2021/01/26 15:02:36 Unsupported graphics mode 00

My go and OS version:

$ go version
go version go1.14 linux/amd64

$ cat /etc/os-release 
NAME="Ubuntu"
VERSION="18.04.3 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.3 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
Jacalz commented

Have you updated the system recently without restarting? I have seen this happen after updating and there are changes to the graphics stack that requires a restart before it works.

andydotxyz commented

Also worth asking, was this running inside a virtual machine @avarf

avarf commented

Hi, sorry I forgot about this.
Yes, the problem was the restart and after restarting everything went smoothly.
No I am running Ubuntu bare metal on my laptop.