[RESOLVED] Conky shines through

Stonegrip · 2023-10-21 17:01:35

I'm facing the following peculiarity: Conky shines through my opaque/non-transparent apps, if I keep my transparent Xterm open on another workspace.

I'm using I3 desktop environment, and I use Xcompmanager to keep my terminal (Xterm) transparent by adding the following command to my .bashrc:

 xcompmgr &
[ -n "$XTERM_VERSION" ] && transset-df --id "$WINDOWID" >/dev/null

Everything works perfectly when I keep only opaque apps open on various workspaces, meaning Conky stays invisible, however if I open Xterm on any workplace, Conky becomes visible across all the other workspaces.

What settings should I adjust to fix it? Thanks a lot for the help. Please let me know if you want to see my Conky config, Xresources dot-file or anything else.

Last edited by Stonegrip (2023-10-22 03:42:16)

seth · 2023-10-21 19:29:34

Conky config and "xprop" output would probably be useful.
Also, do you get the same effect w/ picom?
(which you btw. can configure to set random windows transparent and if you don't mind, urxvt can actually run in argb mode, ie. you get opaque text on a transparent background and for a tiled window, you could even use pseudo-transparency that uses the root pixmap as background)

Stonegrip · 2023-10-22 00:06:27

I've switched to Picom, and now I can't see Conky at all, even though I know it is running, since I see the corresponding process in "ps aux" list.

Here is my Picom config:

inactive-opacity = 0.90;
active-opacity = 0.95;
frame-opacity = 0.80;
inactive-opacity-override = false;

#blur: {
#  method = "dual_kawase";
#  strength = 9;
#  background = false;
#  background-frame = false;
#  background-fixed = false;
#};


shadow=true;

shadow-radius: 7;

shadow-exclude = [
  
  "class_g = 'conky'"

];

fade-exclude = [
  
  "class_g = 'conky'"

];




 opacity-rule = [ 
   "100:class_g = 'firefox'",
   
   "100:class_g = 'conky'"
   
];

 blur-background-exclude = [ 
   "window_type = 'dock'",
   "window_type = 'desktop'",
   "class_g = 'firefox'",
   "class_g = 'conky'"
   
];

And here is my Conky config:

conky.config = {
    alignment = 'top_right',
    background = true,
    border_width = 1,
    cpu_avg_samples = 2,
    default_color = 'aquamarine',
    default_outline_color = 'white',
    default_shade_color = 'white',
    double_buffer = false,
    draw_borders = false,
    draw_graph_borders = true,
    draw_outline = false,
    draw_shades = false,
    extra_newline = false,
    font = 'DejaVu Sans Mono:size=12',
    gap_x = 60,
    gap_y = 60,
    minimum_height = 5,
    minimum_width = 5,
    net_avg_samples = 2,
    no_buffers = true,
    out_to_console = false,
    out_to_ncurses = false,
    out_to_stderr = false,
    out_to_x = true,
    own_window = false,
    own_window_class = 'conky',
    own_window_type = 'desktop',
    -- own_window_transparent = false,
    show_graph_range = false,
    show_graph_scale = false,
    stippled_borders = 0,
    update_interval = 1.0,
    uppercase = false,
    use_spacer = 'none',
    use_xft = true,
    xftalpha = 0.9
}

conky.text = [[
${color grey}Info:$color ${scroll 32 Conky $conky_version - $sysname $nodename $kernel $machine}
$hr
${color grey}Uptime:$color $uptime
${color grey}Frequency (in MHz):$color $freq
${color grey}Frequency (in GHz):$color $freq_g
${color grey}RAM Usage:$color $mem/$memmax - $memperc% ${membar 4}
${color grey}Swap Usage:$color $swap/$swapmax - $swapperc% ${swapbar 4}
${color grey}CPU Usage:$color $cpu% ${cpubar 4}
${color grey}Processes:$color $processes  ${color grey}Running:$color $running_processes
$hr
${color grey}File systems:
 / $color${fs_used /}/${fs_size /} ${fs_bar 6 /}
${color grey}Networking:
Up:$color ${upspeed} ${color grey} - Down:$color ${downspeed}
$hr
${color grey}Name              PID     CPU%   MEM%
${color lightgrey} ${top name 1} ${top pid 1} ${top cpu 1} ${top mem 1}
${color lightgrey} ${top name 2} ${top pid 2} ${top cpu 2} ${top mem 2}
${color lightgrey} ${top name 3} ${top pid 3} ${top cpu 3} ${top mem 3}
${color lightgrey} ${top name 4} ${top pid 4} ${top cpu 4} ${top mem 4}
]]

So, in summary, after I turned off xcompmanager and switched to Picom, Conky is not visible at all, even on an empty workspace. Since I did not change Conky config, I suppose the root cause lies in the Picom config (see above). Any ideas on why Conky stays behind the wallpaper?

Stonegrip · 2023-10-22 03:40:36

My bad. I somehow used a wrong version of Conky config. I've changed a couple of settings, and Conky started working like a charm.

Here are the changes, in case somebody is interested:

    own_window = true,
    own_window_argb_visual = true,
    own_window_class = 'conky',
    own_window_type = 'override',
    own_window_transparent = true

So, now there is no shining through, and the issue is resolved. I'm closing the thread.

The moral: use Picom instead of Xcompmanager And watch what the config says to avoid silly issues.

Last edited by Stonegrip (2023-10-22 04:10:53)

seth · 2023-10-22 07:07:09

The critical value was "own_window = false" as that wll make conky paint on the root window - which conflicts which pretty much every compositor.

Arch Linux

#1 2023-10-21 17:01:35

[RESOLVED] Conky shines through

#2 2023-10-21 19:29:34

Re: [RESOLVED] Conky shines through

#3 2023-10-22 00:06:27

Re: [RESOLVED] Conky shines through

#4 2023-10-22 03:40:36

Re: [RESOLVED] Conky shines through

#5 2023-10-22 07:07:09

Re: [RESOLVED] Conky shines through

Board footer