Conky: Al iniciarse, conky sigue imprimiéndose sobre sí mismo y se convierte en una mancha de texto ilegible.

Creado en 9 jul. 2015  ·  4Comentarios  ·  Fuente: brndnmtthws/conky

Pero si pkill conky y lo reinicio, entonces funciona bien.

Example of unreadable blob on startup

Aquí está mi .conkyrc

conky.config = {
    alignment="top_right";
    background=true;
    border_inner_margin=50;
    default_bar_height=4;
    default_bar_width=0;
    default_color="FFFFFF";
    default_graph_height=24;
    default_graph_width=0;
    double_buffer=true;
    draw_graph_borders=false;
    draw_shades=false;
    font="DejaVu Sans Mono:size=7:Book:antialias:true";
    gap_x=10;
    gap_y=0;
    minimum_height=0;
    minimum_width=0;
    own_window=true;
    own_window_argb_value=0;
    own_window_argb_visual=false;
    own_window_colour="000000";
    own_window_hints="undecorated,below,sticky,skip_taskbar,skip_pager";
    own_window_transparent=true;
    own_window_type="desktop";
    short_units=true;
    update_interval=0.5;
    uppercase=false;
    use_xft=true;
}

conky.text = [[

    ${color}
    ${alignc}${nodename} linux ${machine} ${kernel}
    ${alignc}${exec lscpu | grep -i "model name" | cut -c 24-}

    ${color 2E2EFE}core1 ${execi 5 sensors | grep 'Core 0' | awk '{print $3}'} degrees${alignr}core2 ${execi 5 sensors | grep 'Core 1' | awk '{print $3}'} degrees${color red}
    ${cpugraph cpu1 32, 130}${alignr}${cpugraph cpu2 32, 130}
    ${color 2E2EFE}${cpu cpu1}%${alignc}${color}freq:${color white} ${freq}Mhz ${color white}${alignr}${color 2E2EFE}${cpu cpu2}%

    ${color yellow}${top name 1}${alignr}${top cpu 1}%
    ${top name 2}${alignr}${top cpu 2}%
    ${top name 3}${alignr}${top cpu 3}%
    ${top name 4}${alignr}${top cpu 4}%
    ${top name 5}${alignr}${top cpu 5}%
    ${top name 6}${alignr}${top cpu 6}%
    ${color red}total${alignr} ${cpu}%

    ${color purple}${memgraph}
    ${membar}
    ${color purple}RAM usage${alignr} ${memperc}%
    ${swapbar}
    ${color purple}swap usage${alignr} ${swapperc}%${color yellow}
    ${top_mem name 1}${alignr}${top_mem pid 1}${alignc}${top_mem mem 1}%
    ${top_mem name 2}${alignr}${top_mem pid 2}${alignc}${top_mem mem 2}%
    ${top_mem name 3}${alignr}${top_mem pid 3}${alignc}${top_mem mem 3}%
    ${top_mem name 4}${alignr}${top_mem pid 4}${alignc}${top_mem mem 4}%
    ${top_mem name 5}${alignr}${top_mem pid 5}${alignc}${top_mem mem 5}%
    ${top_mem name 6}${alignr}${top_mem pid 6}${alignc}${top_mem mem 6}%
    ${color purple}total${alignr} ${mem}/${memmax}

    ${color 819FF7}sda6 ${hr 1}
    /${alignr}${fs_size /}
    ${fs_bar /}
    ${fs_used_perc /}%${alignr}${fs_used /}

    sda2 ${hr 1}
    /media/Win8${alignr}${fs_size /media/Win8}
    ${fs_bar /media/Win8}
    ${fs_used_perc /media/Win8}%${alignr}${fs_used /media/Win8}

    ${color yellow}disk read${alignr}disk write
    ${diskiograph_read 32, 130}${alignr}${diskiograph_write 32, 130}
    ${diskio_read}${alignr}${diskio_write}

    ${color green}LAN${hr 1}
    enp7s0${alignr} ${addr enp7s0}
    up ${upspeed enp7s0}${alignr}down ${downspeed enp7s0}
    ${upspeedgraph enp7s0 32, 130}${alignr}${downspeedgraph enp7s0 32, 130}
    total ${totalup enp7s0}${alignr}total ${totaldown enp7s0}

    ${color green}WLAN${hr 1}
    wlp8s0${alignr} ${addr wlp8s0}
    up ${upspeed wlp8s0}${alignr}down ${downspeed wlp8s0}
    ${upspeedgraph wlp8s0 32, 130}${alignr}${downspeedgraph wlp8s0 32, 130}
    total ${totalup wlp8s0}${alignr}total ${totaldown wlp8s0}

    ${color 00FF40}USB${hr 1}
    ${if_existing /dev/sdb1}${exec df -h | grep "sdb1" | cut -c -38} $else $endif
    ${if_existing /dev/sdc1}${exec df -h | grep "sdc1" | cut -c -38} $else $endif
    ${if_existing /dev/sdd1}${exec df -h | grep "sdd1" | cut -c -38} $else $endif
    ${if_existing /dev/sde1}${exec df -h | grep "sde1" | cut -c -38} $else $endif
]]

Comentario más útil

Intente establecer own_window_argb_visual en verdadero. Eso es lo que me solucionó.

Todos 4 comentarios

Intente establecer own_window_argb_visual en verdadero. Eso es lo que me solucionó.

@aereaux Eso soluciona el problema PERO hace que Conky use colores realmente feos.

┌[txtsd@dungeon-of-data]─[~] 
└─▶ conky -d
conky: Invalid value of type 'table' for setting 'background'. Expected value of type 'boolean'.
conky: desktop window (99) is root window
conky: window type - desktop
conky: drawing to created window (0x2200001)
conky: drawing to double buffer
^Cconky: received SIGINT or SIGTERM to terminate. bye!

┌[txtsd@dungeon-of-data]─[~] 
└─▶ conky   
conky: desktop window (99) is root window
conky: window type - desktop
conky: drawing to created window (0x2200001)
conky: drawing to double buffer
conky: forked to background, pid is 8593

Por alguna razón, conky -d lee el campo de fondo de forma incorrecta, pero funciona bien sin el indicador daemonize.

No estoy seguro si algo cambió, pero ya no puedo reproducir este problema.

¿Fue útil esta página
0 / 5 - 0 calificaciones

Temas relacionados

bunder2015 picture bunder2015  ·  4Comentarios

Dimerbone picture Dimerbone  ·  4Comentarios

Microcrap picture Microcrap  ·  4Comentarios

BytEvil picture BytEvil  ·  4Comentarios

Microcrap picture Microcrap  ·  4Comentarios