-
-
Notifications
You must be signed in to change notification settings - Fork 620
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
[Bug]: out_to_wayland not respected anymore (regression) #1898
Comments
with 1.21 there is now no output at all in sway.
in -DD mode, following output get looped:
|
Here on KDE Plasma 6 wayland no output at all. I have downgraded to 1.20 now
|
I'm having the same issue as @magdesign and @olm52 (Hyprland on Arch, for my part, downgrading to 1.20 has been my temporary resolution too) -- but I don't think this is the same issue as the OP. Should be a new issue? |
@simonwiles no need, you'll get a notification when this issue is addressed, so you can just create a new issue if it's not fixed for you then. There's a lot of Wayland support missing so creating a separate issue won't really help. |
Conky got an issue on Wayland since 1.20.2: brndnmtthws/conky#1898
Conky got an issue on Wayland since 1.20.2: brndnmtthws/conky#1898 (cherry picked from commit 8e5597a)
What happened?
In a configuration with
out_to_wayland = true
conky 1.20.2 attempts to use X11 regardless and therefore no output appears at all.A workaround is to set
out_to_x = false
, but this was not needed in earlier versions of conky where this worked fine.Reproduced on sway on Alpine Linux edge and on hyprland 0.39.1 on Arch Linux.
Version
1.20.2
Which OS/distro are you seeing the problem on?
Linux (other)
Conky config
Stack trace
No response
Relevant log output
The text was updated successfully, but these errors were encountered: