brndnmtthws / conky

Light-weight system monitor for X, Wayland (sort of), and other things, too
https://conky.cc
GNU General Public License v3.0
7.25k stars 620 forks source link

[Bug]: out_to_wayland not respected anymore (regression) #1898

Open proycon opened 6 months ago

proycon commented 6 months ago

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

conky.config = {
    out_to_wayland = true,
    alignment = 'middle_middle',
    own_window_argb_value = 0,
    own_window_type = 'desktop',
    default_shade_color = 'grey',
    draw_shades = true,
    font = 'Sxmo:size=13',
    use_xft = true,
    update_interval = 15,
}

conky.text = [[
${alignc}${font Sxmo:size=50:style=Bold}${exec date +"%H"}${font Sxmo:size=50}:${exec date +"%M"}${font}

${font Sxmo:size=20}${exec date +"%a %d %b %Y"}${font}
]]

Stack trace

No response

Relevant log output

$ conky -D -c configs/appcfg/conky.conf
DEBUG(0) [/usr/src/debug/conky/conky/src/conky.cc:1953]: reading contents from config file 'configs/appcfg/conky.conf'
DEBUG(0) [/usr/src/debug/conky/conky/src/x11.cc:312]: enter init_x11()
DEBUG(0) [/usr/src/debug/conky/conky/src/x11.cc:410]: Fixed xinerama area to: 0 0 2160 3840
DEBUG(0) [/usr/src/debug/conky/conky/src/x11.cc:359]: leave init_x11()
DEBUG(0) [/usr/src/debug/conky/conky/src/x11.cc:578]: enter x11_init_window()
DEBUG(0) [/usr/src/debug/conky/conky/src/x11.cc:410]: Fixed xinerama area to: 0 0 2160 3840
conky: desktop window (3db) is root window
conky: drawing to desktop window
DEBUG(0) [/usr/src/debug/conky/conky/src/x11.cc:986]: leave x11_init_window()
DEBUG(0) [/usr/src/debug/conky/conky/src/display-output.cc:138]: Initialized display output 'x11'... 
^Cconky: received SIGHUP, SIGINT, or SIGTERM to terminate. bye!
DEBUG(0) [/usr/src/debug/conky/conky/src/x11.cc:364]: deinit_x11()
magdesign commented 5 months ago

with 1.21 there is now no output at all in sway.

DEBUG(0) [/home/buildozer/aports/main/conky/src/conky-1.21.0/src/conky.cc:1965]: reading contents from config file '/home/me/.config/sxmo/conky.conf'
DEBUG(0) [/home/buildozer/aports/main/conky/src/conky-1.21.0/src/display-output.cc:39]: HTTP display output disabled. Enable by recompiling with 'BUILD_HTTP' flag enabled.
conky: FOUND: console
conky: FOUND: ncurses
conky: FOUND: file
conky: FOUND: x11
conky: FOUND: wayland
DEBUG(0) [/home/buildozer/aports/main/conky/src/conky-1.21.0/src/display-output.cc:109]: Initialized display output 'wayland'... 
conky: '(null)' wayland session running 'sway' destop
DEBUG(0) [/home/buildozer/aports/main/conky/src/conky-1.21.0/src/display-wayland.cc:692]: conky: defining struts

in -DD mode, following output get looped:

DEBUG(1) [/home/buildozer/aports/main/conky/src/conky-1.21.0/src/fonts.cc:84]: loading fonts
olm52 commented 5 months ago

Here on KDE Plasma 6 wayland no output at all. I have downgraded to 1.20 now

conky.config = {
    gap_x = 30,
    gap_y = 1360,
    minimum_width = 410, minimum_height = 105,
    maximum_width = 410,
    alignment = 'top_right',
    update_interval = 5,
    use_xft = true,
    font = 'Noto Sans Mono:size=12',
    own_window = true,
    own_window_type = 'desktop',
    own_window_colour = '#FFFFFF',
    background = true,
    own_window_transparent = false,
    own_window_hints = 'undecorated,below,sticky,skip_taskbar,skip_pager',
    own_window_argb_visual = true,
    own_window_argb_value = 255,
    double_buffer = true,
    draw_shades = false,
    out_to_x = false,
    out_to_wayland = true,
    border_inner_margin = 16,
};
simonwiles commented 5 months ago

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?

Caellian commented 5 months ago

@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.