v1.21.3

[github-actions[bot]]

What's Changed

🐞 Bug fixes

• Replace strncat with strcat by @Caellian in Replace strncat with strcat #1950
• Fix minimum height not being applied by @Suyooo in Fix minimum height not being applied #1952
• Revert removal of dpi scaling by @Caellian in Revert removal of dpi scaling #1949
• Fix for the graph scale text colour changing depending on graph position by @randomcoder67 in Fix for the graph scale text colour changing depending on graph position #1957
• Restore previous strut behavior by @m42a in Restore previous strut behavior #1963

🎛️ Miscellaneous

• Bump version by @brndnmtthws in Bump version #1946
• Docker: make sure image has sensible default name by @brndnmtthws in Docker: make sure image has sensible default name #1953
• Docker: only write to cache if creds available by @brndnmtthws in Docker: only write to cache if creds available #1958
• Docker cache extern pr by @brndnmtthws in Docker cache extern pr #1959
• build(deps): bump the actions group with 2 updates by @dependabot in build(deps): bump the actions group with 2 updates #1955

New Contributors

• @randomcoder67 made their first contribution in Fix for the graph scale text colour changing depending on graph position #1957
• @m42a made their first contribution in Restore previous strut behavior #1963

Full Changelog: v1.21.2...v1.21.3

---

This discussion was created from the release v1.21.3.

[BayouGuru67]

For some time now, I have been having issues with my compiled versions of conky not operating smoothly, especially as more time passes. At this point, with the latest update compiled and installed, and my system having been up for 13 days now, BOTH of my conkys are now having update frequency issues, one to the point of utter uselessness, in that it will not update at the specified frequency of 1 second, updating VERY irregularly instead. It might update on the second once, maybe 2x, or may skip up to 5+ seconds before updating. Tried killing all conky processes and restarted it, but it is behaving the same way, regardless. There are no errors in the logs, or terminal, so I am not sure what to look for next. The problem is lessened after a reboot, but creeps back upwards in severity as time goes on. I am so frustrated with this issue at this point because I am out of ideas on what to search for and what to do to make conky work smoothly again over any significant period of time. I am guessing the lack of search results probably means it is something stupid-simple having to do with KDE Plasma or Kubuntu 22.04.

UPDATE: Some of the problem seems to be some sort of incompatibility between Konversation irc client and conky, for when I closed Konversation, my network conky suddenly started updating regularly again on the second as-programmed. Thought I would mention that important info in here ASAP to help in figuring out the issue.

[brndnmtthws]

If you can report a separate issue with the details, that would be wonderful, thanks! 🙏

I do my best, but it's tricky to handle all the myriad of configurations and use cases. And I am just a lowly peasant trying to survive in this world.

All the best!

[BayouGuru67]

UPDATE! So I was doing some housekeeping on the SSD and came across the source and build directories for the past 2 versions of conky that I have built. I could not remove those directories, however, because it seems my system has linked to the lua-related .so files in the build directory. Until I can figure out how to correct that issue, I cannot proceed with the troubleshooting of conky, and I strongly suspect that this might be a part or even all of the problem. The specific files that seem to be linked and defined as system files not to be deleted are the .so files in the build/lua/ directory in BOTH of the conky build folders. Advice?

[BayouGuru67]

Sure, no problem.

…

On Wed, Jun 19, 2024, 9:11 AM Brenden Matthews ***@***.***> wrote: If you can report a separate issue with the details, that would be wonderful, thanks! 🙏 I do my best, but it's tricky to handle all the myriad of configurations and use cases. And I am just a lowly peasant trying to survive in this world. All the best! — Reply to this email directly, view it on GitHub <#1966 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADQ3OSOJ3IAJYU7GFZU6KODZIGNSLAVCNFSM6AAAAABJC6AYXWVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TQMJZGA2TS> . You are receiving this because you commented.Message ID: ***@***.***>

[BayouGuru67]

Okay, after an adventure in computing that doesn't bear elaboration, I think I can somewhat identify my issues: Firstly, I had force_redraw set to true, which I suspect was causing some sort of timing issues with my video playback once the system had run a few days. Secondly, I am uncertain as to whether Cairo and/or Lua and/or rsvg were all correctly installed previously. I have since replaced my main drive with a new SSD, RAM and Main board, & installed Kubuntu 22.0.4.7 LTS on the fresh hardware. Also used the GUI cmake option when compiling it this time. Glitchy playback still happened with force_redraw set to true. I haven't rebooted since changing the setting to false, and the video playback is smooth and the conkys are also behaving. I have also previously split my 2 larger conkys into 2 medium and 2 small ones in an effort to get to the root of my issue. That was work! :)

…

On Wed, Jun 19, 2024, 1:18 PM Glen Kelly ***@***.***> wrote: Sure, no problem. On Wed, Jun 19, 2024, 9:11 AM Brenden Matthews ***@***.***> wrote: > If you can report a separate issue with the details, that would be > wonderful, thanks! 🙏 > > I do my best, but it's tricky to handle all the myriad of configurations > and use cases. And I am just a lowly peasant trying to survive in this > world. > > All the best! > > — > Reply to this email directly, view it on GitHub > <#1966 (reply in thread)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ADQ3OSOJ3IAJYU7GFZU6KODZIGNSLAVCNFSM6AAAAABJC6AYXWVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TQMJZGA2TS> > . > You are receiving this because you commented.Message ID: > ***@***.***> >