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.03k stars 611 forks source link

[Bug]: blank window #1960

Open kleshas opened 1 month ago

kleshas commented 1 month ago

What happened?

Running sway, updated arch (new install). AMD 6750XT

Not sure when it started but recently my previously-working config only shows a blank window. I saw a link on google saying this can be caused by an external IP lookup happening too often, but removing that from my config didn't help.

When out_to_x=true, out_to_wayland=false I get a blank conky window. When out_to_x=false, out_to_wayland=true I don't get a window at all (though there is a conky running in htop).

Actually, it seems that the window DOES eventually populate, but after a few mins, and it seems to not be doing any further updates (I have a time entry in the config, it hasn't changed for 5 mins).

With out_to_wayland=true there is no change using own_window_type override, desktop or normal. Running from command line: conky -c ~/.conkyrc conky: drawing to single buffer conky: FOUND: console conky: FOUND: ncurses conky: FOUND: file conky: FOUND: x11 conky: FOUND: wayland

and nothing after.

conky-cairo (1.21.2) has the error: "unknown setting out_to_wayland, and Unable to find a usable display output when using out_to_wayland=true

Version

all from 1.18

Which OS/distro are you seeing the problem on?

Arch Linux

Conky config

conky.config = {

out_to_x=false,
out_to_wayland=true,
font = 'Liberation Mono Regular:size=10',
background = false,
cpu_avg_samples = 2,
diskio_avg_samples = 10,
double_buffer = true,
if_up_strictness = 'address',
net_avg_samples = 2,
no_buffers = true,
temperature_unit = 'celsius',
text_buffer_size = 2048,
update_interval = 1,
imlib_cache_size = 0,
alignment = 'top_left',
gap_x = 0,
gap_y = 0,
minimum_height = 600,
minimum_width = 350,
maximum_width = 350,
border_outer_margin = 1,
border_width = 1,
default_bar_width = 250,
default_bar_height = 10,
default_gauge_height = 25,
default_gauge_width = 40,
default_graph_height = 40,
default_graph_width = 153,
default_shade_color = '#000000',
default_outline_color = '#000000',
draw_borders = false,
draw_graph_borders = true,
draw_shades = false,
draw_outline = false,
stippled_borders = 0,
extra_newline = false,
format_human_readable = true,
max_text_width = 0,
max_user_text = 16384,
short_units = true,
top_name_width = 21,
top_name_verbose = false,
uppercase = false,
use_spacer = 'none',
use_xft = true,
xftalpha = 1,
own_window = true,
own_window_argb_value =255,
own_window_argb_visual = true,
own_window_class = 'Conky',
own_window_transparent = false,
own_window_title = 'system_conky',
own_window_type = 'normal',
format_human_readable = true,

default_color = '1A4770', -- Window border
}

conky.text = [[
Memory Usage
 ]]

Stack trace

No response

Relevant log output

No response

kleshas commented 1 month ago

looks like AirVPN was causing the blank screen. Mullvad VPN doesn't have this issue. I do still have the issue with out_to_wayland=true not working.