Hello. I am the colleague mentioned by user @grafi 
I am having trouble running my project in the OM 6 ROCK environment. Specifically, I am having trouble initializing the frontend in Lua. I also installed the updated packages from the cooker repository mentioned by @uro, namely conky, and checked if I had imlib2.
I even started installing packages at random, because I assumed that the fragmentation in the packages meant that I hadn’t installed something yet, but unfortunately, nothing worked.
The current list of packages with the name lua:
lib64lua5.3-static-devel.x86_64 5.3.6-1 @cooker-x86_64
lib64lua5.3_5.3.x86_64 5.3.6-1 @cooker-x86_64
lib64lua5.4.x86_64 5.4.7-1 @release-x86_64
lib64luajit-5.1.x86_64 2.1.1693350652-1 @release-x86_64
lib64luajit-5.1-common.x86_64 2.1.1693350652-1 @release-x86_64
lib64tree-sitter-lua.x86_64 0.2.0-1 @release-x86_64
lua.x86_64 5.4.8-1 @cooker-x86_64
lua-lgi.x86_64 0.9.2-3 @rock-x86_64
lua5.3.x86_64 5.3.6-1 @cooker-x86_64
luajit.x86_64 2.1.1693350652-1 @release-x86_64
luajit-lpeg.x86_64 1.1.0-1 @release-x86_64
luajit-mpack.x86_64 1.0.12-1 @release-x86_64
and packages for the name cairo:
lib64cairo-devel.x86_64 1.18.4-1 @rock-x86_64
lib64cairo-gir1.0.x86_64 1.84.0-1 @release-x86_64
lib64cairo-gobject2.x86_64 1.18.4-1 @release-x86_64
lib64cairo-script-interpreter2.x86_64 1.18.4-1 @release-x86_64
lib64cairo2.x86_64 1.18.4-1 @release-x86_64
lib64harfbuzz-cairo.x86_64 11.1.0-1 @rock-x86_64
lib64harfbuzz-cairo-devel.x86_64 11.1.0-1 @rock-x86_64
lib64pangocairo-gir1.0.x86_64 1.56.3-1 @release-x86_64
lib64pangocairo1.0_0.x86_64 1.56.3-1 @release-x86_64
libcairo-devel.x86_64 1.18.4-1 @rock-x86_64
libcairo-gobject2.x86_64 1.18.4-1 @rock-x86_64
libcairo-script-interpreter2.x86_64 1.18.4-1 @rock-x86_64
libcairo2.x86_64 1.18.4-1 @rock-x86_64
python-cairo.x86_64 1.28.0-1 @release-x86_64
Conky -v:
conky 1.22.2 compiled for Linux x86_64
Compiled in features:
System config file: /etc/conky/conky.conf
Package library path: lib64/conky
General:
* math
* hddtemp
* IPv6
* Curl
* RSS
* support for IBM/Lenovo notebooks
* old configuration syntax
* Imlib2
* OSS mixer support
* apcupsd
* iostats
* ncurses
* Internationalization support
* PulseAudio
Lua bindings:
* Cairo
* Imlib2
* RSVG
X11:
* Xdamage extension
* Xinerama extension (virtual display)
* Xshape extension (click through)
* XDBE (double buffer extension)
* Xft
* ARGB visual
* Own window
* Mouse events
Wayland:
* ARGB visual
* Mouse events
Music detection:
* CMUS
* MPD
Default values:
* Netdevice: eno1
* Local configfile: $HOME/.conkyrc
* Localedir: /usr/share/locale
* Maximum netdevices: 256
* Maximum text size: 16384
* Size text buffer: 256
The error that appears when I start the project is:
conky: desktop window (0x180001e) is subwindow of root window (0x323)
conky: window type - normal
conky: drawing to created window (0x4400002)
conky: drawing to double buffer
conky: llua_load: ...Pulpit/Zupix-Py2Lua-Mail-conky-v1.0.0_DEV/lua/e-mail.lua:338: module 'cairo' not found:
no field package.preload['cairo']
no file '/usr/share/lua/5.4/cairo.lua'
no file '/usr/share/lua/5.4/cairo/init.lua'
no file '/usr/lib/lua/5.4/cairo.lua'
no file '/usr/lib/lua/5.4/cairo/init.lua'
no file '/usr/lib64/lua/5.4/cairo.lua'
no file '/usr/lib64/lua/5.4/cairo/init.lua'
no file './cairo.lua'
no file './cairo/init.lua'
no file '/home/przemek/Pulpit/Zupix-Py2Lua-Mail-conky-v1.0.0_DEV/lua/cairo.lua'
no file 'lib64/conky/libcairo.so'
no file '/usr/lib64/lua/5.4/cairo.so'
no file '/usr/lib64/lua/5.4/loadall.so'
no file './cairo.so'
no file '/usr/lib/lua/5.4/cairo.so'
no file '/usr/lib/lua/5.4/loadall.so'
no file './cairo.so'
conky: forked to background, pid is 1607
conky: FOUND: wayland
conky: FOUND: x11
conky: FOUND: file
conky: FOUND: ncurses
conky: FOUND: console
conky: llua_do_call: function conky_cairo_init execution failed: attempt to call a nil value
conky: llua_do_call: function conky_draw_mail_indicator execution failed: attempt to call a nil value
conky: 'KDE' x11 session running
conky: llua_do_call: function conky_cairo_init execution failed: attempt to call a nil value
conky: llua_do_call: function conky_draw_mail_indicator execution failed: attempt to call a nil value
conky: llua_do_call: function conky_cairo_init execution failed: attempt to call a nil value
conky: llua_do_call: function conky_draw_mail_indicator execution failed: attempt to call a nil value
conky: llua_do_call: function conky_cairo_init execution failed: attempt to call a nil value
conky: llua_do_call: function conky_draw_mail_indicator execution failed: attempt to call a nil value
conky: llua_do_call: function conky_cairo_init execution failed: attempt to call a nil value
conky: llua_do_call: function conky_draw_mail_indicator execution failed: attempt to call a nil value
conky: llua_do_call: function conky_cairo_init execution failed: attempt to call a nil value
conky: llua_do_call: function conky_draw_mail_indicator execution failed: attempt to call a nil value
conky: llua_do_call: function conky_cairo_init execution failed: attempt to call a nil value
conky: llua_do_call: function conky_draw_mail_indicator execution failed: attempt to call a nil value
conky: llua_do_call: function conky_cairo_init execution failed: attempt to call a nil value
conky: llua_do_call: function conky_draw_mail_indicator execution failed: attempt to call a nil value
I am familiar with this error, but on other distributions, it was enough to install the meta-packages lua and lua-dev and their dependencies + on Arch-based distributions, add the line pcall(require, ‘cairo_xlib’). That’s all.
I can upload the bare code without customization and account tables, but to run the script without a backend (just to check if cairo works), you need to meet a few minimum dependencies, such as the dkjson.lua library and the basic conkyrcfile. I can provide such a minimal package if anyone is interested. The entire project, including scripts that automate installation, is available on GitHub, but at the moment everything is in Polish, so it doesn’t make sense for anyone to struggle with it and use Google Translate on their phone just to check out the whole project.
To try out the solution, all you need is access to the main frontend.