Re: antiX Screenshots
Posted: Mon Nov 05, 2018 12:57 pm
Sounds like something we should correct for the next version, thanks for mentioning it.MX17 version didn't have lua5.2 on board
Support for MX and antiX Linux distros
http://www.forum.mxlinux.org/
Sounds like something we should correct for the next version, thanks for mentioning it.MX17 version didn't have lua5.2 on board
wow, a nice selfie
I doubt lua5.2 has anything to do with the problem. Regarding converting conky 1.9 to 1.10, COnky 1.10 does it normally while running, even in MX15/16.male wrote:...No asqwerth, this has nothing to do with other packages bearing the name "cairo" in them ...The only astonishing point was that my (and @eadwiene's) MX17 version didn't have lua5.2 on board, which is necessary to convert syntax1.9 ---> to syntax1.10....
Maybe this is intentional because of the construct: conky-all(1.10) and the CM and its configuration files in 1.9
Code: Select all
conky: llua_do_call: function conky_main execution failed: attempt to call a nil value
conky: llua_do_call: function conky_main execution failed: attempt to call a nil value
conky: llua_do_call: function conky_main execution failed: attempt to call a nil value
conky: llua_do_call: function conky_main execution failed: attempt to call a nil value
That's very thoughtful of you.Jerry3904 wrote:Sounds like something we should correct for the next version, thanks for mentioning it.MX17 version didn't have lua5.2 on board
No one said that either.asqwerth wrote: I doubt lua5.2 has anything to do with the problem. Regarding converting conky 1.9 to 1.10, COnky 1.10 does it normally while running, even in MX15/16.
Why don't you do that in MX17?asqwerth wrote: Anyway, what I did was try to get the manual gears clock conky running in Manjaro, which has conky 1.10, lua (latest 5.3) and lua52 both installed, and also has cairo package (1.16) already installed .
Not for nothing has Sector11 developed the pkill command for this purposeasqwerth wrote:I had to use screenshot because after that first message, another error message kept propagating non-stop (see below) and I couldn't scroll up fast enough to copy the starting error message ("select all" menu option also wouldn't work):
I confess, with 1.9, I didn't even try it.So it didn't work in Manjaro either for me. How did you get it to work??
Because I'm currently booted into Manjaro to install updates.male wrote: Tue Nov 06, 2018 4:29 amWhy don't you do that in MX17?asqwerth wrote: Anyway, what I did was try to get the manual gears clock conky running in Manjaro, which has conky 1.10, lua (latest 5.3) and lua52 both installed, and also has cairo package (1.16) already installed .![]()
I think the terminal error message shows that lua53 is installed but the cairo modules can't be found.First of all, these are the "inconsistencies" of 1.10 ! The gurus have already stumbled over this. 1.10 punishes immediately "errors" of the configuration from 1.9
But the screen says for me, that lua5.3 is not installed ?
How do I use it in a conky?wrote: Not for nothing has Sector11 developed the pkill command for this purpose![]()
To clarify, you successfully ran the original clock conky under conky-legacy (version 1.9) in MX, then you just converted the syntax of the clock config file to 1.10 but you didn't try running the converted file on a system that runs conky 1.10?I confess, with 1.9, I didn't even try it.
I cleaned up the code and adapted it to my MX system and then converted it to 1.10.
I also used the conky packages of the Distri in arch-linux for a long time and had no success.asqwerth wrote: I think the terminal error message shows that lua53 is installed but the cairo modules can't be found.
Also, here is a screenshot from the package manager of manjaro to show it's installed (note that lua52 is also installed):
is ABOVE in many configurations and can also be seen in my screenshots.Not for nothing has Sector11 developed the pkill command for this purpose![]()
How do I use it in a conky?
To clarify, you successfully ran the original clock conky under conky-legacy (version 1.9) in MX, then you just converted the syntax of the clock config file to 1.10 but you didn't try running the converted file on a system that runs conky 1.10?
I cleaned up the code and adapted it to my MX system AND THEN converted it to 1.10.
I was talking about this error:
Question manjaromale wrote:I also used the conky packages of the Distri in arch-linux for a long time and had no success.
Only when I understood to use the packages from AUR instead, the long awaited success was there.