-
Notifications
You must be signed in to change notification settings - Fork 131
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
Fails to launch with this configuration on Wayland with an AMD GPU in Plasma6 #20
Comments
wezterm-config/config/appearance.lua Lines 9 to 11 in f330fa3
|
I take back what I said. I'm still not entirely sure what's happening but from what I understand is that it's an issue caused by Wayland and If that is the case and the issue is simply limited to Vulkan and Wayland, there might be 2 solutions:
I don't really have the means to test either of the solutions out, but I'm fairly confident solution 1 will be your best bet. |
Thanks Kevin, I will give this a shot later this week. Thanks |
Hey @Tristor, did you get a chance to try any of the solutions yet? |
Same situation. The second solution works for me. Haven't tried the first, but I suppose it would work too. Thx a lot. |
no worries 😊 |
Hey @Tristor, it's been over a month since the issue was opened and I haven't heard a response in a while. If neither of the solutions doesn't work, feel free to re-open the issue, but at that stage, I do think this is beyond just a config tweak and more an upstream issue potentially with Wezterm, Wayland or AMDVLK |
Description of Issue
I attempted to use this config with a fresh install of WezTerm on my Framework 13 AMD running Arch + Plasma-Desktop. Plasma6 uses the
linux-dmabuf
Wayland interface but the AMDVLK driver useswl_drm
in Wayland, which is a legacy interface. This is, I think, the cause of this interaction. I plan to test with a different compositor outside of Plasma6 to see if I can get this working. I found the following, I think related issue, GPUOpen-Drivers/pal#96Error message logged to terminal:
The text was updated successfully, but these errors were encountered: