[Question] I have the default config of awesomewm

[GerardPolloRebozado]

I have the same issue in https://github.com/rxyhn/yoru/issues/68 I dont have a a battery in my computer and i already commented the lines but still same problem

[awohsen]

If it's still not loading yoru after commenting out these lines

https://github.com/rxyhn/yoru/issues/127#issuecomment-1257541558: ~/.config/awesome/ui/panels/top-panel/init.lua : 19

s.battery = require("ui.panels.top-panel.battery")()

~/.config/awesome/ui/panels/top-panel/init.lua : 264

s.battery,

Try these as well

https://github.com/rxyhn/yoru/issues/127#issuecomment-1230963109: I just had this problem of the config not appearing to load completely but I've managed to resolve it.

picom no longer appears to have an argument --experiential-backends. I edited .config/awesome/configuration/autostart.lua accordingly:

line 9 of ~/.config/awesome/configuration/autostart.lua should look like

awful.spawn("picom --config " .. config_dir .. "configuration/picom.conf", false)

If it's not yet solved then post the error logs (you can find them from ~/.xsession-errors)

[GerardPolloRebozado]

If it's still not loading yoru after commenting out these lines

#127 (comment): ~/.config/awesome/ui/panels/top-panel/init.lua : 19

s.battery = require("ui.panels.top-panel.battery")()

~/.config/awesome/ui/panels/top-panel/init.lua : 264

s.battery,

Try these as well

#127 (comment): I just had this problem of the config not appearing to load completely but I've managed to resolve it. picom no longer appears to have an argument --experiential-backends. I edited .config/awesome/configuration/autostart.lua accordingly: line 9 of ~/.config/awesome/configuration/autostart.lua should look like

awful.spawn("picom --config " .. config_dir .. "configuration/picom.conf", false)

If it's not yet solved then post the error logs (you can find them from ~/.xsession-errors)

Still not working xsession-errors.txt

[ViiEx]

I have the same issue as well. Been through the necessary changes in the config, meaning I removed the battery module since I don't use it on a desktop, removed the picoms --experimental-backends flag from the auto start and finally I added a keyboard layout module because I need it.

I my case I'm guessing that it is a module dependency issue tho because I'm on Ubuntu 22.04 and installing on my home Arch desktop the dotfiles was never an issue.

I used the following into my .xinitrc

exec /usr/bin/awesome >>~/.cache/awesome/stdout 2>>~/.cache/awesome/stderr

and the error output I got is the following

#~/.cache/awsome/stderr
WARNING: modelines must use ASCII
playerctl: no process found
error while running function!
stack traceback:
    [C]: in ?
    [C]: in function 'require'
    ...user/.config/awesome/modules/lockscreen/init.lua:9: in function 'modules.lockscreen.init'
    ...e/user/.config/awesome/modules/exit-screen.lua:8: in main chunk
    [C]: in function 'require'
    /home/user/.config/awesome/modules/init.lua:2: in main chunk
    [C]: in function 'require'
    /home/user/.config/awesome/rc.lua:28: in main chunk
error: error loading module 'liblua_pam' from file '/home/user/.config/awesome/modules/lockscreen/lib/liblua_pam.so':
    liblua.so.5.4: cannot open shared object file: No such file or directory
2022-10-11 10:05:41 W: awesome: a_glib_poll:477: Last main loop iteration took 0,196330 seconds! Increasing limit for this warning to that value.
2022-10-11 10:05:41 E: awesome: Error during a protected call: /usr/local/share/awesome/lib/awful/spawn.lua:530: attempt to call a nil value (upvalue 'callback')
stack traceback:
    /usr/local/share/awesome/lib/awful/spawn.lua:530: in function </usr/local/share/awesome/lib/awful/spawn.lua:529>
    (...tail calls...)
    /usr/local/share/awesome/lib/awful/spawn.lua:491: in function </usr/local/share/awesome/lib/awful/spawn.lua:485>
    [C]: in function 'xpcall'
    /usr/local/share/awesome/lib/gears/protected_call.lua:41: in function </usr/local/share/awesome/lib/gears/protected_call.lua:40>
    (...tail calls...)
    /usr/local/share/awesome/lib/awful/spawn.lua:591: in upvalue 'done'
    /usr/local/share/awesome/lib/awful/spawn.lua:606: in function </usr/local/share/awesome/lib/awful/spawn.lua:598>
[ 11/10/2022 10:05:41.903 parse_config_libconfig FATAL ERROR ] Error when reading configuration file "/home/user/.config/awesome/configuration/picom.conf", line 45: syntax error
[ 11/10/2022 10:05:41.903 main FATAL ERROR ] Failed to create new session.

(nm-applet:10640): Gtk-WARNING **: 10:05:41.958: Theme parsing error: gtk.css:14750:20: Not a valid image

(nm-applet:10640): Gtk-WARNING **: 10:05:41.958: Theme parsing error: gtk.css:14756:20: Not a valid image

(nm-applet:10640): Gtk-WARNING **: 10:05:41.958: Theme parsing error: gtk.css:14762:20: Not a valid image

(nm-applet:10640): Gtk-WARNING **: 10:05:41.958: Theme parsing error: gtk.css:14768:20: Not a valid image

(nm-applet:10640): Gtk-WARNING **: 10:05:41.958: Theme parsing error: gtk.css:14774:20: Not a valid image

(nm-applet:10640): Gtk-WARNING **: 10:05:41.958: Theme parsing error: gtk.css:14780:20: Not a valid image

(nm-applet:10640): Gtk-WARNING **: 10:05:41.958: Theme parsing error: gtk.css:14786:20: Not a valid image

(nm-applet:10640): Gtk-WARNING **: 10:05:41.958: Theme parsing error: gtk.css:14792:20: Not a valid image

(nm-applet:10640): Gtk-CRITICAL **: 10:05:42.133: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed

Any idea on what I may be missing?