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

Unable open wezterm on hyprland #5299

Closed
huwqchn opened this issue Apr 15, 2024 · 4 comments
Closed

Unable open wezterm on hyprland #5299

huwqchn opened this issue Apr 15, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@huwqchn
Copy link

huwqchn commented Apr 15, 2024

What Operating System(s) are you seeing this problem on?

Linux Wayland

Which Wayland compositor or X11 Window manager(s) are you using?

hyprland

WezTerm version

latest nightly

Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?

Yes, and I updated the version box above to show the version of the nightly that I tried

Describe the bug

ERROR wezterm_term::terminalstate::performer > kitty_img: data should have been materialized in coalesce_kitty_accumulation: base64 decode: Invalid padding

To Reproduce

No response

Configuration

empty config

Expected Behavior

can works on hyprland without error

Logs

20:07:02.920 ERROR wezterm_term::terminalstate::performer > kitty_img: data should have been materialized in coalesce_kitty_accumulation: base64 decode: Invalid padding

Anything else?

No response

@huwqchn huwqchn added the bug Something isn't working label Apr 15, 2024
@ForeverZer0
Copy link

Have the same issue, though it does work for me if I disable Wayland support.

config.enable_wayland = false

It is odd though, as it does work under other Wayland sessions, so it does seem to be something specifically related to Hyprland. I don't seem to get any errors or warning, it simply hangs forever without actually starting.

Here is what I get, not sure if it will help track down the problem:

OS: Arch Linux
Hyprland: 0.39.1-4
wezterm: 20240203.110809.5046fc22-1

Running...

WEZTERM_LOG=debug wezterm start --always-new-process

Resulting Log

It doesn't seem to be dependent on configuration, I can completely remove my configuration for the same result, likewise no difference if using hardware/software rendering, OpenGL, Vulkan, etc.

@woojiq
Copy link

woojiq commented Apr 19, 2024

Duplicate of #5103

@wez
Copy link
Owner

wez commented May 5, 2024

Duplicate of #5103

@wez wez marked this as a duplicate of #5103 May 5, 2024
@wez wez closed this as completed May 5, 2024
Copy link
Contributor

github-actions bot commented Jun 5, 2024

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 5, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants