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

force kitty so use xwayland as backend #2648

Closed
salkin-mada opened this issue May 11, 2020 · 9 comments
Closed

force kitty so use xwayland as backend #2648

salkin-mada opened this issue May 11, 2020 · 9 comments

Comments

@salkin-mada
Copy link

System: Arch linux, Sway wm

I am normally not in the need of opening kitty in X under Wayland. But for sharing the kitty window during jitsu meet or other conference platform sessions it is needed.

When unsetting the wayland display unset WAYLAND_DISPLAY apps then try to open with XWayland. This works with some native Wayland terminal emulators and other native Wayland apps.

But with kitty, i guess after the KITTY_ENABLE_WAYLAND env var is longer needed , I cant seem to figure out how to force/make kitty to open with X.
unset WAYLAND_DISPLAY && kitty stills opens a kitty with Wayland. not X.
So i tried exporting it to an empty string. (which also works with other wayland native apps) export WAYLAND_DISPLAY="" && kitty here i found kitty throwing an GLFW error.
It seems kitty still wants to open with wayland.

[132 22:23:07.604940] [glfw error 65544]: Wayland: Failed to connect to display
GLFW initialization failed

Is there an env var like KITTY_DISABLE_WAYLAND or maybe KITTY_FORCE_UNSECURE_X

:=) and thanks for making this wonderful terminal emulator.

@Luflosi
Copy link
Contributor

Luflosi commented May 11, 2020

https://sw.kovidgoyal.net/kitty/conf.html#opt-kitty.linux_display_server might be what you want.

@trygveaa
Copy link
Contributor

Is there an env var like KITTY_DISABLE_WAYLAND

Did you try this? It does exist. From the changelog:

Wayland: Use the kitty Wayland backend by default. Can be switched back to using XWayland by setting the environment variable: KITTY_DISABLE_WAYLAND=1

@salkin-mada
Copy link
Author

Did you try this? It does exist. From the changelog:

Wayland: Use the kitty Wayland backend by default. Can be switched back to using XWayland by setting the environment variable: KITTY_DISABLE_WAYLAND=1

thanks! yeah. this dont seem to work here. xeyes are not moving.
when doing KITTY_DISABLE_WAYLAND=1 && kitty atleast.
Maybe something I am missing?

@Luflosi
Copy link
Contributor

Luflosi commented May 11, 2020

Try KITTY_DISABLE_WAYLAND=1 kitty.

@salkin-mada
Copy link
Author

https://sw.kovidgoyal.net/kitty/conf.html#opt-kitty.linux_display_server might be what you want.

nice. this is new info to me :-)
but as far as I understand, setting this in my kitty.conf will make kitty open with X11 as backend as new default in Wayland. Instead of auto detecting Wayland, kitty just goes for X11.
How could i use this as a command? as a kitty.config like so maybe?:
kitty --config linux_display_server x11

@salkin-mada
Copy link
Author

Try KITTY_DISABLE_WAYLAND=1 kitty.

nope. no cigar. :-)
thanks. really appreciate your help !

@Luflosi
Copy link
Contributor

Luflosi commented May 11, 2020

How could i use this as a command? as a kitty.config like so maybe?

Like so:

kitty -o linux_display_server=x11

@salkin-mada
Copy link
Author

salkin-mada commented May 11, 2020

yes. niice. this works indeed. I will go and check the -o option, seems like a good thing to know about ;-)

@Luflosi
Copy link
Contributor

Luflosi commented May 11, 2020

Glad it works now.
I had a look at the code and unsetting WAYLAND_DISPLAY or setting KITTY_DISABLE_WAYLAND to any value should disable Wayland as long as the linux_display_server config option is set to the default value of auto. Maybe you changed it to wayland in your kitty.conf? You can use kitty --debug-config to see which config options are different from the default.

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