-
Notifications
You must be signed in to change notification settings - Fork 17
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
Error starting wterm in velox #3
Comments
I think the wayland protocols I am using are dated, that's also something to check.
…On Sun, Mar 11, 2018 at 02:03:37AM +0000, MichaelMackus wrote:
Latest Wayland slackbuilds under Slackware.
Getting this error:
```
***@***.***: error 0: use_unstable_version must be called first
```
I've verified the earlier call to xdg_shell_use_unstable_version is being called. So, I don't know why this error occurs? It seems to occur somewhere in the "draw" function based on quick debugging.
Any pointers on where to look to fix this? Im assuming xdg shell has updated , is there any way to use/lock to an older version? I'm unfamiliar with Wayland otherwise I would have those answers.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#3
|
majestrate
added a commit
that referenced
this issue
Mar 11, 2018
try latest commit. |
Thanks! On gentoo now, I'll try to build for this platform & try again. |
Merged
TornadoCookie
added a commit
to TornadoCookie/wterm
that referenced
this issue
Feb 11, 2024
… when i got here
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Latest Wayland slackbuilds under Slackware.
Getting this error:
I've verified the earlier call to xdg_shell_use_unstable_version is being called. So, I don't know why this error occurs? It seems to occur somewhere in the "draw" function based on quick debugging.
Any pointers on where to look to fix this? Im assuming xdg shell has updated , is there any way to use/lock to an older version? I'm unfamiliar with Wayland otherwise I would have those answers.
The text was updated successfully, but these errors were encountered: