Conky text outline acts like a shadow

freyr · 2016-10-11 16:00:06

So I've just updated my system completely and after reboot conky looked strange.
The outline of the text is like a shadow. Now, before, with version 1.10.4 it was a normal outline but now with version 1.10.5 it looks more like a shadow.

Here's the relevant part of my config file (I know it's the old format, converting it to the new format doesn't change a thing):

#  Basic Settings

background yes
use_xft yes
xftfont inconsolata:size=11
xftalpha 0
update_interval 1
total_run_times 0
own_window 1
own_window_transparent yes
own_window_type desktop
own_window_hints undecorated,below,sticky,skip_taskbar,skip_pager
double_buffer yes
minimum_size 450 1
maximum_width 600
draw_shades no
draw_outline yes
draw_borders no
draw_graph_borders no
default_color Black
default_shade_color fff
default_outline_color 000
alignment tr
gap_x 10
gap_y 20
no_buffers yes
uppercase no
cpu_avg_samples 2
override_utf8_locale yes

and here's a screenshot (sadly I don't have a "before screenshot" but the text certainly didn't look like this):

It is the outline, if I set the value of draw_outline to no, it disappears.

seth · 2016-10-11 18:54:40

So, do you have a chance to bisect conky?
What happens if you set "default_color f00"? (The picture looks like there's an outline PLUS the actual text and while the outline might be the trigger of the "shadow", the shadow might still be the actual text)

coruun · 2016-10-12 05:03:13

I guess, my problem is related: In my setup, the outlines are disabled but shades are used. However, besides a bug with the goto function, which reenables shades, neither an outline nor a shade is visible. I bisected *this* bug (not the goto-bug) to commit 178015a.

I could reproduce the "falling shadows" of the OP by removing a workaround in my script: Shades seem to be defined with respect to the default font (specified with "font = ..."). If the default font and the actual font don't match, there is a strange offset between text and shade.

My script (slightly shortened):

conky.config = {
    -- work in background
    background = true,

    -- better fonts
    use_xft = true,
    --xftalpha = 1,

    -- update interval
    update_interval = 1.0,
    total_run_times = 0,

    -- window settings
    own_window = true,
    own_window_transparent = true,
    own_window_type = 'normal',
    own_window_hints = 'undecorated, below, sticky, skip_taskbar, skip_pager',
    own_window_argb_visual = true,
    --own_window_argb_value = 0,

    -- anti-flickering
    double_buffer = true,

    -- size
    minimum_width = 200, 
    maximum_width = 200,
    minimum_height = 1000,

    -- shadows
    draw_shades = true,
    default_shade_color = 'black',

    -- borders
    draw_outline = false,
    default_outline_color = 'red',
    draw_graph_borders = true,

    -- frame
    draw_borders = false,

    -- color
    default_color = 'white',

    -- position
    alignment = 'top_left',
    gap_x = 1715,
    gap_y = 32,

    -- misc
    no_buffers = true,
    uppercase = false,
    cpu_avg_samples = 2,
    if_up_strictness = 'address',

    show_graph_range = false,
    show_graph_scale = false,
    --default_bar_height = 6,
    --default_bar_width = 200,
    text_buffer_size = 1000,
    override_utf8_locale = true,

    font = 'Liberation Sans:bold:size=9', --important for shades
    template0 = 'Liberation Sans:bold:size=9',
    template1 = 'Liberation Mono:bold:size=7',
}


conky.text = [[
${font $template0}SYSTEM ${hr 2}
${font $template1}$sysname $kernel $alignr $machine
Host:$alignr$nodename
Uptime:$alignr$uptime
Updates: ${execi 300 cat "/var/log/pending_updates.log" | wc -l}$alignr Stand: ${execi 300 date -r /var/log/pending_updates.log +%R}

${font $template0}PROZESSOR ${hr 2}
${font $template1}${cpugraph cpu0}
${voffset -6}${loadgraph 13,200 FFFFFF FFFFFF 8}
Last:$alignr${loadavg 1} / ${loadavg 2} / ${loadavg 3}
CPU1: ${alignr 15}${cpu cpu1}% ${alignr 8}${execi 5 sensors coretemp-isa-0000 | grep "Core 0" | cut -b16-17}°C$alignr${cpubar cpu1 6,110}
CPU2: ${alignr 15}${cpu cpu2}% ${alignr 8}${execi 5 sensors coretemp-isa-0000 | grep "Core 1" | cut -b16-17}°C$alignr${cpubar cpu2 6,110}
CPU3: ${alignr 15}${cpu cpu3}% ${alignr 8}${execi 5 sensors coretemp-isa-0000 | grep "Core 2" | cut -b16-17}°C$alignr${cpubar cpu3 6,110}
CPU4: ${alignr 15}${cpu cpu4}% ${alignr 8}${execi 5 sensors coretemp-isa-0000 | grep "Core 3" | cut -b16-17}°C$alignr${cpubar cpu4 6,110}
Lüfter: $alignr${execi 5 sensors f71858fg-isa-0a00 | grep "fan1:" | cut -b14-17} / ${execi 5 sensors f71858fg-isa-0a00 | grep "fan2:" | cut -b14-17}
#
#${font $template0}GRAFIKKARTE ${hr 2}
#${font $template1}Lüfter: $alignr${execi 5 cat /sys/class/hwmon/hwmon0/pwm1}
#Temperatur: $alignr${execi 5 cat /sys/class/hwmon/hwmon0/temp1_input | cut -b1-2}°C

${font $template0}GRAFIKKARTE ${hr 2}
${font $template1}#
Temperatur: $alignr${execi 5 nvidia-smi --query-gpu=temperature.gpu --format=csv,nounits,noheader}°C
Lüfter: $alignr${execi 5 nvidia-smi --query-gpu=fan.speed --format=csv,nounits,noheader}%
Speicher: $alignr${execi 5 nvidia-smi --query-gpu=memory.used --format=csv,nounits,noheader} / ${execi 300 nvidia-smi --query-gpu=memory.total --format=csv,nounits,noheader}

${font $template0}FESTPLATTE ${hr 2}
${font $template1}${diskiograph 12,200 FFFFFF FFFFFF sda}
#${voffset -11}${diskiograph 12,200 FFFFFF FFFFFF sdb}
Lesen: ${diskio_read sda} ${goto 100}Schreiben: ${diskio_write sda}
]]

seth · 2016-10-12 07:01:02

There's an *obvious* bug in commit 178015a.
Two local statics were defined overriding global statics, so there's no communication between draw_stuff() and the outside.

The local statics should be wrapped:
#ifndef BUILD_X11
static int text_offset_x, text_offset_y; /* offset for start position *
#endif

(given the patch ain't bonkers anyway and text_offset_* should be avaialable on non-X11 as well)

Did you file a bug against conky?

coruun · 2016-10-12 11:09:40

I filed both bugs as #331 and #332.

Last edited by coruun (2016-10-12 11:11:35)

freyr · 2016-10-12 13:54:13

seth wrote:

So, do you have a chance to bisect conky?
What happens if you set "default_color f00"? (The picture looks like there's an outline PLUS the actual text and while the outline might be the trigger of the "shadow", the shadow might still be the actual text)

Honestly I don't know what "bisect" means in this case.
Changing the default_color has no noticeable effect.

seth · 2016-10-12 14:00:28

"git bisect", you approach the problem via a binary tree from a known good and a known bad commit.
Nevermind, I'd say coruun has identified your bug, bisected the commits (of one is clearly wonky) and filed bugs to conky.
So you owe him a beer and just watch the filed conky bugs ;-)

freyr · 2016-10-12 14:02:35

seth wrote:

"git bisect", you approach the problem via a binary tree from a known good and a known bad commit.
Nevermind, I'd say coruun has identified your bug, bisected the commits (of one is clearly wonky) and filed bugs to conky.
So you owe him a beer and just watch the filed conky bugs ;-)

Indeed.

Thanks, both of you!

drcouzelis · 2017-01-11 06:57:07

For anyone interested... I posted a quick fix for the "outline" bug on the bug report given above.

Last edited by drcouzelis (2017-05-29 15:54:12)

Arch Linux

#1 2016-10-11 16:00:06

Conky text outline acts like a shadow

#2 2016-10-11 18:54:40

Re: Conky text outline acts like a shadow

#3 2016-10-12 05:03:13

Re: Conky text outline acts like a shadow

#4 2016-10-12 07:01:02

Re: Conky text outline acts like a shadow

#5 2016-10-12 11:09:40

Re: Conky text outline acts like a shadow

#6 2016-10-12 13:54:13

Re: Conky text outline acts like a shadow

#7 2016-10-12 14:00:28

Re: Conky text outline acts like a shadow

#8 2016-10-12 14:02:35

Re: Conky text outline acts like a shadow

#9 2017-01-11 06:57:07

Re: Conky text outline acts like a shadow

Board footer