-
Notifications
You must be signed in to change notification settings - Fork 79
Conky-manger doesn't work #15
Comments
That does look like normal output when you start conky from terminal. But maybe nobody really runs conky with a root context, but I don't care, but in many cases the user desktop is not a root context so it seems like a weird effort. The terminal command If you want to use a specific config then you can use a command such as: If you want to use the Gotam config then you can use a command such as: The better way to run that same command would be:
If you run the conky-manager and select Gotam, then you should immediately see the Gotam conky config show up on your screen(and it might be behind another window). If you do not see this, then you need to run a terminal command as above so you can find out the exact error message that the conky program is encountering, -this is not related to the conky-manager. If you fix the error, then conky-manager will probably act correctly. |
home/julio # cd ~/.conky/Gotham ; conky -c conky.config /home/julio # conky-manager |
This is ~/.conky/Gotham/Gotham: I changed the configuration for transparency in archlinux, this configuration has always worked for me without problems. use_xft yes own_window_colour black double_buffer yes minimum_size 0 0 |
The problem is not conky-manager. You have to find the error. Above, it does say there is a problem on line 159. Find it with this: For you, ~ means /root, I do not know why you are using the root user, so you have to make sure you do the correct thing. But, the problem is not conky-manager. |
I thank you for your support, however, I still can't find a way to get conky and conky manager to work, it must be some archlinux bug, there is no other explanation, because before reinstalling it on the new hard drive it was working perfectly. |
Today I faced the same issue too, I've been using Conky for a long time, I guess it requires more recent updates. Here's the output to your command and I get the same or similar to every clock widget in conky
|
conky is showing the error, not conky-manager. Maybe you can check the version of I don't use Arch so I can't see where to offer a suggestion for this. I do know that most distros do not run default as a root user, but as a user account, so running as root but using a user account setup of these packages might be related but I have no idea. Also, for conky-manager, after you get the conky problem worked out, not conky-manager, maybe you should be using conky-manager2 instead. good luck, if you find where the problem is, or if this is "some Arch bug" then you should post the solution here so others can get the benefit too. zcot |
Just chiming in to confirm that the error is shown by conky-manager due to mismatching LUA versions. Digging in for a fix. |
Hey all just to confirm with @thatjohn conky-manager has not been worked on since 2017 and naturally conky's configuration files changed. Here is my configuration: conky.config = { ${voffset 8}$color$hr ${voffset 20}${goto 40}${color}${font3}Temperatures ${voffset 20}${goto 40}${font3}${color}RAM${font Bitstream Vera Sans:bold:size=8}$alignr$mem$font ${voffset 20}${goto 40}${font3}${color}Swap${font Bitstream Vera Sans:bold:size=8}$alignr${swap}/ ${swapfree} ${voffset 15}$font$alignr${execi 10000 awk -F= '/TION/ {print $2}' /etc/lsb-release |sed 's/"//g'} ]] as you can see it is way different than the old conky-manager files |
This is the exit when you throw conky from the terminal
/home/julio # conky manager
conky: desktop window (600010) is subwindow of root window (139)
conky: window type - desktop
conky: drawing to created window (0x2200001)
conky: drawing to double buffer
When I open Cponky-manager and select the Gotam box, and I configure everything and close, the conky Gotam doesn't open, and when I open the conky-manager application again the box is unchecked, I did it several times and it always answers the same.
I have a Thinkpad lenovo T430, with archlinux 86x64 installed.
I thank you for your support
Julio Cesar campos
The text was updated successfully, but these errors were encountered: