Announcement

Collapse
No announcement yet.

Conky and the plasma desktop

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Conky and the plasma desktop

    I have a conky script running on the plasma desktop (KDE) however, whenever I click on the plasma desktop the conky display disappears. I think what it's doing is bringing the plasma desktop to the front and the conky display is "hiding" behind the desktop as when close down the conky display appears (briefly) once the desktop has closed down.

    How do I display conky on the desktop without it "hiding" behind the desktop when I click on the desktop?

    #2
    I had that problem some time ago but can't remember what I did to fix it. Here is the settings part of my .conkyrc script that currently works OK.

    Code:
    alignment top_left
    use_xft yes
    xftfont DejaVu Sans Mono:size=12
    own_window yes
    own_window_type normal
    own_window_argb_visual yes
    own_window_argb_value 120
    own_window_transparent no
    own_window_colour 36a
    own_window_hints undecorated,skip_taskbar,sticky
    double_buffer yes
    border_width 1
    default_color 3f6
    default_outline_color f36
    default_shade_color 36f
    draw_outline yes
    gap_x 0
    gap_y 0
    minimum_size 100 100
    cpu_avg_samples 2
    update_interval 1.0
    Ken.
    Opinions are like rear-ends, everybody has one. Here's mine. (|)

    Comment


      #3
      Conky needs the two lines you see in lcorken's .conkyrc:

      Code:
      own_window yes
      own_window_type normal
      Without these kwin sees Conky as a background process and actually raises the wallpaper over it when you click on the desktop.
      Computers don't make mistakes. They only execute them.

      Comment


        #4
        Thanks Dutchman. I have those two lines in my .conkyrc file already. Contents of my .conkyrc file is below:
        Code:
        background no
        own_window yes
        own_window_type normal
        own_window_argb_visual true
        own_window_transparent yes
        own_window_hints undecorated,below,sticky,skip_taskbar,skip_pager
        double_buffer yes

        Comment


          #5
          What happens when you set background to yes?

          Code:
          background yes
          sigpic

          Comment


            #6
            I've never run across that before Nick, but then I'm far from a Conky expert. Here's my entire setup, maybe there's something you'll see in it that will help.

            Code:
            background no
            font Sans:size=8
            update_interval 3.0
            total_run_times 0
            own_window yes
            own_window_type normal
            own_window_argb_visual true
            own_window_transparent yes
            own_window_hints undecorated,below,sticky,skip_taskbar,skip_pager
            double_buffer yes
            minimum_size 220 5
            maximum_width 220
            draw_shades no
            draw_outline no
            draw_borders no
            draw_graph_borders yes
            default_color gray
            #default_shade_color black
            alignment top_right
            gap_x 12
            gap_y 35
            cpu_avg_samples 2
            override_utf8_locale yes
            uppercase yes # set to yes if you want all text to be in uppercase
            
            TEXT
            ${color gray}SYSTEM ${hr 1}${color}
            
            Hostname: $alignr$nodename
            Kernel: $alignr$kernel
            Uptime: $alignr$uptime
            Temperatures: ${alignr}GPU ${nvidia temp}°C
            ${alignr}Core0 ${execi 5 sensors | grep "Core 0" | awk '{print $3}' | cut -c2-3}°C
            ${alignr}Core1 ${execi 5 sensors | grep "Core 1" | awk '{print $3}' | cut -c2-3}°C
            
            CPU: ${alignr}${freq} MHz
            Processes: ${alignr}$processes ($running_processes running)
            Load: ${alignr}$loadavg
            
            CPU1 ${alignr}${cpu cpu1}%
            ${cpubar 4 cpu1}
            CPU2 ${alignr}${cpu cpu2}%
            ${cpubar 4 cpu2}
            
            Ram ${alignr}$mem / $memmax ($memperc%)
            ${membar 4}
            swap ${alignr}$swap / $swapmax ($swapperc%)
            ${swapbar 4}
            
            Highest CPU $alignr CPU% MEM%
            ${top name 1}$alignr${top cpu 1}${top mem 1}
            ${top name 2}$alignr${top cpu 2}${top mem 2}
            ${top name 3}$alignr${top cpu 3}${top mem 3}
            
            Highest MEM $alignr CPU% MEM%
            ${top_mem name 1}$alignr${top_mem cpu 1}${top_mem mem 1}
            ${top_mem name 2}$alignr${top_mem cpu 2}${top_mem mem 2}
            ${top_mem name 3}$alignr${top_mem cpu 3}${top_mem mem 3}
            
            ${color gray}Filesystem ${hr 1}${color}
            
            Root: ${alignr}${fs_free /} / ${fs_size /}
            ${fs_bar 4 /}
            Home: ${alignr}${fs_free /home} / ${fs_size /home}
            ${fs_bar 4 /home}
            
            ${color gray}NETWORK ${hr 1}${color}
            
            Down ${downspeed eth0} k/s ${alignr}Up ${upspeed eth0} k/s
            ${downspeedgraph eth0 25,107} ${alignr}${upspeedgraph eth0 25,107}
            Total ${totaldown eth0} ${alignr}Total ${totalup eth0}
            life0riley, I tried the "background yes" just to see what happened, but it seemed to make no difference. Nothing changed. According to the documentation that comes with Conky, it just changes Conky to a background process if set to yes. I checked both ways in "top", and nothing changes there either, same memory, nice level, shared, just stays the same. Perhaps there's some difference when using Lua to customize it?
            Computers don't make mistakes. They only execute them.

            Comment

            Working...
            X