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

Terminal doesn't show up on X11, works fine on Wayland. #36

Open
erenfro opened this issue Jun 11, 2024 · 2 comments
Open

Terminal doesn't show up on X11, works fine on Wayland. #36

erenfro opened this issue Jun 11, 2024 · 2 comments
Labels
investigate Require investigation

Comments

@erenfro
Copy link

erenfro commented Jun 11, 2024

When I use Quake-Terminal extension in X11, for some reason it simply does not work. What happens is very uniquely unusual in what does actually happen though.

With kitty, or alacritty, no configuration or with configuration, does not matter, if kitty or alacritty is used as the Terminal Application starts a terminal, it runs the terminal, but does not properly show the terminal at all. Instead where the terminal should be, there's "dead space" that visually can be seen when it's opening, closing, or there's moving content in the area of which is in that "terminal area". I will get a visual recording of this for demonstration as well.

This seems to only happen on at least these GPU-enhanced terminals like kitty and alacritty, so far in my testing of this, and only in X11 specifically, On wayland, I've seen no apparent issue.

@diegodario88 diegodario88 added the investigate Require investigation label Jun 11, 2024
@erenfro
Copy link
Author

erenfro commented Jun 12, 2024

https://0x0.st/XcZR.mov
There's the effect of the issue I'm seeing.
Now, to note, this problem does not occur if I run kitty or alacritty prior to using the keybinding shortcut. It's basically when the extension itself loads it that it becomes an issue.

@DaWy
Copy link

DaWy commented Jun 20, 2024

Happens to me aswell. Using ubuntu 24.04 on XORG. On Wayland works just fine. Launching it before using the shortcut avoid this issue, so I swear its something on how extension launch the terminal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
investigate Require investigation
Projects
None yet
Development

No branches or pull requests

3 participants