Announcement

Collapse
No announcement yet.

[plasma5] howto: fix disappearing conky

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

    [plasma5] howto: fix disappearing conky

    Some of us have issues with conky disappearing at times; I've searched for a solution for a couple of weeks and finally found one that appears to work. My own conky installation is now stable and doesn't disappear when I right-click the desktop or any other activity I've tried so far.

    First, credit where credit is due: https://github.com/brndnmtthws/conky/issues/145

    This requires a small change to ~/.conkyrc and a window rule to force conky to behave, but it seems to work -

    First, let's hack up ~/.conkyrc

    Set own_window_type to dock like this

    Code:
    own_window_type dock
    Next, we need a window rule.

    systemsettings --> Window Behavior --> Window Rules and click 'New', then





    Apply and exit. Enjoy
    we see things not as they are, but as we are.
    -- anais nin

    #2
    Thank you for this 'fix'. I've been experiencing this disappearing conky on my laptop for some time now. I knew how to get it back, so it was merely an annoyance, but this 'fix' is nice; just applied it. Now to monitor and see if it in fact fixes the problem.
    Windows no longer obstructs my view.
    Using Kubuntu Linux since March 23, 2007.
    "It is a capital mistake to theorize before one has data." - Sherlock Holmes

    Comment


      #3
      yes ,,,,, I have been away for a wile (no net) and to find this on my first day back is nice

      will test as well .

      applying it in a min

      VINNY
      i7 4core HT 8MB L3 2.9GHz
      16GB RAM
      Nvidia GTX 860M 4GB RAM 1152 cuda cores

      Comment


        #4
        Noticed after applying this fix, that the bottom half of my last line of data output was 'cut off'. I attribute this to the change of own_window_type normal to own_window_type dock, so I changed it back, killed conky, and restarted it. The last line of data output was once again displayed fully. I'm keeping the Window Rule in place. IF conky doesn't start disappearing again, then maybe it is the window rule alone that is needed.
        Last edited by Snowhog; Jun 25, 2016, 04:31 PM.
        Windows no longer obstructs my view.
        Using Kubuntu Linux since March 23, 2007.
        "It is a capital mistake to theorize before one has data." - Sherlock Holmes

        Comment


          #5
          Please let us know, snowhog - if all we need is the window rule that'd be excellent.

          cheers -

          edit: Mine seems to work just fine on normal, setting it to desktop broke it.
          Last edited by wizard10000; Jun 25, 2016, 03:23 PM.
          we see things not as they are, but as we are.
          -- anais nin

          Comment


            #6
            Yes let us know. Also, setting to Dock, does transparency still hold?

            Comment


              #7
              Originally posted by MoonRise View Post
              Yes let us know. Also, setting to Dock, does transparency still hold?
              Yup.

              I had conky disappear once when set to normal so I set it back to dock. Can't explain Snowhog's disappearing half-line, though.
              we see things not as they are, but as we are.
              -- anais nin

              Comment


                #8
                Originally posted by wizard10000 View Post
                Yup.

                I had conky disappear once when set to normal so I set it back to dock. Can't explain Snowhog's disappearing half-line, though.
                it seams as though setting to "dock" makes conky use the hole hight of the screen or @hear it seams so .

                the bottom of my conky has a graphic that did sit right on top of the panel at the bottom ,,,,now it go's behind the panel some ,,,,but the panel is transparent so ,,,,,,,,,,,,,,,,,,,,

                I have had no disappearance of conky since doing this "fix" however.

                VINNY
                i7 4core HT 8MB L3 2.9GHz
                16GB RAM
                Nvidia GTX 860M 4GB RAM 1152 cuda cores

                Comment


                  #9
                  Just made this change. Report back soon.


                  EDIT:

                  Well, no disappearing yet, but I do get the below effect if you click on the CONKY Window instead of the window shown.

                  Click image for larger version

Name:	Selection_007.png
Views:	1
Size:	248.6 KB
ID:	643239
                  Last edited by MoonRise; Jun 26, 2016, 11:26 AM.

                  Comment


                    #10
                    Originally posted by MoonRise View Post
                    ...Well, no disappearing yet, but I do get the below effect if you click on the CONKY Window instead of the window shown.
                    If I have own_window_type set to 'dock' I get some artifacts like you; when set to 'normal' mine quits doing that.

                    I have had conky disappear once when on normal; I just put it back that way and will report back if it's less than stable
                    we see things not as they are, but as we are.
                    -- anais nin

                    Comment


                      #11
                      Reporting back

                      I've seen conky disappear once more when own_window_type was set to normal. Have had some trouble duplicating it but it appears to have disappeared when my display went to sleep - haven't found a way to make it fail consistently, though. Right-clicking the desktop made it come back and so far that's acceptable.
                      we see things not as they are, but as we are.
                      -- anais nin

                      Comment


                        #12
                        Well, I've left the fix in place and can say no disappearing/reappearing act and I haven't yet been bothered by that overlay issue so I'm happy with this at the moment!

                        Comment


                          #13
                          Well, I can say I've had that Disappearing/Reappearing issue for a long time and nothing ever seemed to work. I've even had it in the past few updates where Conky just crashes and exits.

                          So, looking at a command line option to see of I can get any kind of trace I found you can daemonize by starting it with the -d option. Has to be lowercase "d". Since doing that on two machines that I deal with the most, that seems to have stopped all the bad behavior. At least in appearance so far. Again, we shall see and I'll definitely report if otherwise.

                          Comment


                            #14
                            Originally posted by MoonRise View Post
                            Well, I can say I've had that Disappearing/Reappearing issue for a long time and nothing ever seemed to work. I've even had it in the past few updates where Conky just crashes and exits.

                            So, looking at a command line option to see of I can get any kind of trace I found you can daemonize by starting it with the -d option. Has to be lowercase "d". Since doing that on two machines that I deal with the most, that seems to have stopped all the bad behavior. At least in appearance so far. Again, we shall see and I'll definitely report if otherwise.
                            That's the way I've always started conky, sorry for not sharing. I do have issues now with conky failing to autostart about 3/4 of the time and when I filed a bug against Sid for it I was told it was the -d switch causing the issue; it wasn't, but since the DD was able to get conky to autostart consistently the problem is most likely in my config.
                            we see things not as they are, but as we are.
                            -- anais nin

                            Comment


                              #15
                              Really odd though as I haven't seen updates to Conky and those started after other updates. Yeah, conky autostart problematic here too but as stated, only recently after system updates.

                              Comment

                              Working...
                              X