[Question] Failed to load config

[haridhayal11]

I followed the setup instructions and installed all the dependencies on Fedora 36 but I'm getting this error

I tried the battery status fix mentioned here as well but the issues doesnt seem to be related to that. I'm not familiar with lua. Any help would be appreciated.

[Bendz2012]

Make sure you have the git (development) version of awesome installed

[haridhayal11]

Make sure you have the git (development) version of awesome installed

Yes that seems to have fixed the error but I only see the wallpaper for a split second and it reverts back to the default awesomewm config.

[Ryex]

@haridhayal11 I just had this problem of the config not appearing to load completely but I've managed to resolve it.

First up I set my startx command to output stderr to a log file I got a LOT of errors from

.config/awesome/helpers/ui.lua:12: attempt to concatenate a nil value (local 'color')

it appears that beautiful.accent is nil? these ultimately were not the problem however

second up, picom no longer appears to have an argument --experiential-backends. I edited .config/awesome/configuration/autostart.lua acordingly

Third

.config/awesome/modules/UPower/init.lua:125: attempt to index a nil value (field 'device')

My computer is a desktop and does not have a battery, this makes sense but personally I feel this should be handled better. editing .config/awesome/ui/panels/top-panel/init.lua to comment out references to s.battery allowed the config to load.

[haridhayal11]

@haridhayal11 I just had this problem of the config not appearing to load completely but I've managed to resolve it.

First up I set my startx command to output stderr to a log file I got a LOT of errors from

.config/awesome/helpers/ui.lua:12: attempt to concatenate a nil value (local 'color')

it appears that beautiful.accent is nil? these ultimately were not the problem however

second up, picom no longer appears to have an argument --experiential-backends. I edited .config/awesome/configuration/autostart.lua acordingly

Third

.config/awesome/modules/UPower/init.lua:125: attempt to index a nil value (field 'device')

My computer is a desktop and does not have a battery, this makes sense but personally I feel this should be handled better. editing .config/awesome/ui/panels/top-panel/init.lua to comment out references to s.battery allowed the config to load.

I've tried all this but still has the same issue. looks like it is happening due to an older build of awesome-git on fedora. I will try to build from source.

Any idea how to disable titlebars for all apps?

[Ryex]

if none of these worked best I can suggest is that you follow my first step of getting error logs.

from https://awesomewm.org/apidoc/documentation/90-FAQ.md.html

Where are logs, error messages or something?

When hacking your own configuration, something inevitably would go wrong. Awesome prints error messages to its stderr stream. When run with usual $ startx, it'd be printed right in tty. If you use something more complicated (some kind of DM, like kdm or gdm), stderr is usually redirected somewhere else. To see where, run the following command:

$ ls -l /proc/$(pidof awesome)/fd/2

There's handy way to run Awesome and redirect both its standard output and error streams to files:

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

If you put it into .xinitrc (for startx) or ~/.xsession, you'll be able to watch (with tail -f) everything right from Awesome.

if you can't run down the errors from the logs yourself posting them may help.

[haridhayal11]

if none of these worked best I can suggest is that you follow my first step of getting error logs.

from https://awesomewm.org/apidoc/documentation/90-FAQ.md.html

Where are logs, error messages or something? When hacking your own configuration, something inevitably would go wrong. Awesome prints error messages to its stderr stream. When run with usual $ startx, it'd be printed right in tty. If you use something more complicated (some kind of DM, like kdm or gdm), stderr is usually redirected somewhere else. To see where, run the following command:

$ ls -l /proc/$(pidof awesome)/fd/2

There's handy way to run Awesome and redirect both its standard output and error streams to files:

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

If you put it into .xinitrc (for startx) or ~/.xsession, you'll be able to watch (with tail -f) everything right from Awesome.

if you can't run down the errors from the logs yourself posting them may help.

Removing the picom flag has fixed it. Thanks for helping. Any idea to disable titlebars?

[Ryex]

Removing the picom flag has fixed it. Thanks for helping. Any idea to disable titlebars?

the hotkey Mod+t should toggle them. tracing the lua code from there will likely find a way to default them off.

[haridhayal11]

Removing the picom flag has fixed it. Thanks for helping. Any idea to disable titlebars?

the hotkey Mod+t should toggle them. tracing the lua code from there will likely find a way to default them off.

Thanks

[jordhanlucaso]

if none of these worked best I can suggest is that you follow my first step of getting error logs. from https://awesomewm.org/apidoc/documentation/90-FAQ.md.html

Where are logs, error messages or something? When hacking your own configuration, something inevitably would go wrong. Awesome prints error messages to its stderr stream. When run with usual $ startx, it'd be printed right in tty. If you use something more complicated (some kind of DM, like kdm or gdm), stderr is usually redirected somewhere else. To see where, run the following command:

$ ls -l /proc/$(pidof awesome)/fd/2

There's handy way to run Awesome and redirect both its standard output and error streams to files:

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

If you put it into .xinitrc (for startx) or ~/.xsession, you'll be able to watch (with tail -f) everything right from Awesome.

if you can't run down the errors from the logs yourself posting them may help.

Removing the picom flag has fixed it. Thanks for helping. Any idea to disable titlebars?

How you did that? Im having the same issue, and dont know how to solve it.

[Ryex]

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

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

[awohsen]

Very same issue, when restarting awesome it shows yoru background and some stuff for milliseconds and then it reset back to original config, i followed the manual and I'm using awesome-git.

This is '.xcession-errors' file (keeps repeating!):

...
2022-09-25 20:19:46 E: awesome: Error during a protected call: /home/awohsen/.config/awesome/helpers/ui.lua:12: attempt to concatenate a nil value (local 'color')
stack traceback:
    /home/awohsen/.config/awesome/helpers/ui.lua:12: in function 'helpers.ui.colorize_text'
    ...wohsen/.config/awesome/modules/lockscreen/lockscreen.lua:172: in upvalue 'activate_word'
    ...wohsen/.config/awesome/modules/lockscreen/lockscreen.lua:188: in upvalue 'reset_time'
    ...wohsen/.config/awesome/modules/lockscreen/lockscreen.lua:202: in local 'func'
    /usr/share/awesome/lib/gears/object.lua:164: in function 'signal.playerctl.emit_signal'
    [C]: in function 'xpcall'
    /usr/share/awesome/lib/gears/protected_call.lua:41: in function </usr/share/awesome/lib/gears/protected_call.lua:40>
    (...tail calls...)
    /usr/share/awesome/lib/gears/timer.lua:103: in function </usr/share/awesome/lib/gears/timer.lua:102>
2022-09-25 20:19:46 E: awesome: Error during a protected call: /home/awohsen/.config/awesome/helpers/ui.lua:12: attempt to concatenate a nil value (local 'color')
stack traceback:
    /home/awohsen/.config/awesome/helpers/ui.lua:12: in function 'helpers.ui.colorize_text'
    /home/awohsen/.config/awesome/ui/decorations/music.lua:244: in local 'func'
    /usr/share/awesome/lib/gears/object.lua:164: in function 'signal.playerctl.emit_signal'
    ...awesome/modules/bling/signal/playerctl/playerctl_lib.lua:263: in upvalue 'position_cb'
    ...awesome/modules/bling/signal/playerctl/playerctl_lib.lua:458: in local 'func'
    /usr/share/awesome/lib/gears/object.lua:164: in function 'signal.playerctl.emit_signal'
    [C]: in function 'xpcall'
    /usr/share/awesome/lib/gears/protected_call.lua:41: in function </usr/share/awesome/lib/gears/protected_call.lua:40>
    (...tail calls...)
    /usr/share/awesome/lib/gears/timer.lua:103: in function </usr/share/awesome/lib/gears/timer.lua:102>
2022-09-25 20:19:47 E: awesome: Error during a protected call: /home/awohsen/.config/awesome/helpers/ui.lua:12: attempt to concatenate a nil value (local 'color')
stack traceback:
    /home/awohsen/.config/awesome/helpers/ui.lua:12: in function 'helpers.ui.colorize_text'
    ...wohsen/.config/awesome/modules/lockscreen/lockscreen.lua:172: in upvalue 'activate_word'
    ...wohsen/.config/awesome/modules/lockscreen/lockscreen.lua:188: in upvalue 'reset_time'
    ...wohsen/.config/awesome/modules/lockscreen/lockscreen.lua:202: in local 'func'
    /usr/share/awesome/lib/gears/object.lua:164: in function 'signal.playerctl.emit_signal'
    [C]: in function 'xpcall'
    /usr/share/awesome/lib/gears/protected_call.lua:41: in function </usr/share/awesome/lib/gears/protected_call.lua:40>
    (...tail calls...)
    /usr/share/awesome/lib/gears/timer.lua:103: in function </usr/share/awesome/lib/gears/timer.lua:102>
...

The code:

...
local capi = { mouse = mouse }

local _ui = {}

function _ui.colorize_text(text, color)
    return "<span foreground='" .. color .. "'>" .. text .. "</span>"
end

function _ui.add_hover_cursor(w, hover_cursor)
    local original_cursor = "left_ptr"
...

➜  awesome --version
awesome v4.3-1538-g4a140ea5e (Too long)
 • Compiled against Lua 5.4.4 (running with 0.9.2)
 • API level: 4
 • D-Bus support: yes
 • xcb-errors support: no
 • execinfo support: yes
 • xcb-randr version: 1.6
 • LGI version: /usr/share/lua/5.4/lgi/version.lua
 • Transparency enabled: yes
 • Custom search paths: no

[awohsen]

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

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

I've done this too, it helped so much things get loaded but still i get the old background and titlebars and the default awesome title

[Ryex]

There are a number of significant errors in the config. I have some open PRs for the ones I remember explicitly fixing. but I know there is at least one I'm forgetting. form your logs above I know those errors start popping up AFTER the main config has errored and awesome tries to fallback to the config in /etc/xdg/awesome/rc.lua

Please try to find that very first error in the log or post the full thing and I'll try to help.

[awohsen]

Please try to find that very first error in the log or post the full thing and I'll try to help.

Here there are the first ones before color thing keeps repeating:

WARNING: modelines must use ASCII
playerctl: no process found
error while running function!
stack traceback:
    /home/awohsen/.config/awesome/modules/UPower/init.lua:125: in function 'modules.UPower.new'
    (...tail calls...)
    /home/awohsen/.config/awesome/signal/battery.lua:7: in main chunk
    [C]: in function 'require'
    .../awohsen/.config/awesome/ui/panels/top-panel/battery.lua:4: in main chunk
    [C]: in function 'require'
    /home/awohsen/.config/awesome/ui/panels/top-panel/init.lua:19: in function 'ui.panels.top-panel'
    /home/awohsen/.config/awesome/ui/init.lua:15: in local 'func'
    /usr/share/awesome/lib/awful/screen.lua:583: in function 'awful.screen.connect_for_each_screen'
    /home/awohsen/.config/awesome/ui/init.lua:13: in main chunk
    [C]: in function 'require'
    /home/awohsen/.config/awesome/rc.lua:34: in main chunk
error: /home/awohsen/.config/awesome/modules/UPower/init.lua:125: attempt to index a nil value (field 'device')
2022-09-26 09:25:08 E: awesome: Error during a protected call: /home/awohsen/.config/awesome/helpers/ui.lua:12: attempt to concatenate a nil value (local 'color')
stack traceback:
    /home/awohsen/.config/awesome/helpers/ui.lua:12: in function 'helpers.ui.colorize_text'
    /home/awohsen/.config/awesome/ui/decorations/music.lua:235: in local 'func'
    /usr/share/awesome/lib/gears/object.lua:164: in function 'gears.object.emit_signal'
    ...awesome/modules/bling/signal/playerctl/playerctl_lib.lua:200: in upvalue 'emit_metadata_signal'
    ...awesome/modules/bling/signal/playerctl/playerctl_lib.lua:438: in upvalue 'get_current_player_info'
    ...awesome/modules/bling/signal/playerctl/playerctl_lib.lua:468: in upvalue 'start_manager'
    ...awesome/modules/bling/signal/playerctl/playerctl_lib.lua:550: in function <...awesome/modules/bling/signal/playerctl/playerctl_lib.lua:549>
    [C]: in function 'xpcall'
    /usr/share/awesome/lib/gears/protected_call.lua:41: in function </usr/share/awesome/lib/gears/protected_call.lua:40>
    (...tail calls...)
    /usr/share/awesome/lib/gears/timer.lua:280: in function 'gears.timer.run_delayed_calls_now'
2022-09-26 09:25:08 W: awesome: a_glib_poll:477: Last main loop iteration took 0.332107 seconds! Increasing limit for this warning to that value.
2022-09-26 09:25:08 E: awesome: Error during a protected call: /usr/share/awesome/lib/awful/spawn.lua:530: attempt to call a nil value (upvalue 'callback')
stack traceback:
    /usr/share/awesome/lib/awful/spawn.lua:530: in function </usr/share/awesome/lib/awful/spawn.lua:529>
    (...tail calls...)
    /usr/share/awesome/lib/awful/spawn.lua:491: in function </usr/share/awesome/lib/awful/spawn.lua:485>
    [C]: in function 'xpcall'
    /usr/share/awesome/lib/gears/protected_call.lua:41: in function </usr/share/awesome/lib/gears/protected_call.lua:40>
    (...tail calls...)
    /usr/share/awesome/lib/awful/spawn.lua:591: in upvalue 'done'
    /usr/share/awesome/lib/awful/spawn.lua:606: in function </usr/share/awesome/lib/awful/spawn.lua:598>
blueman-applet 09.25.08 WARNING  PluginManager:151 __load_plugin: Not loading DhcpClient because its conflict has higher priority
blueman-applet 09.25.08 WARNING  PluginManager:151 __load_plugin: Not loading PPPSupport because its conflict has higher priority
blueman-applet 09.25.08 WARNING  TransferService:213 _make_share_path: Failed to get Download dir from XDG
blueman-applet 09.25.08 WARNING  DiscvManager:119 update_menuitems: warning: Adapter is None
2022-09-26 09:25:08 E: awesome: Error during a protected call: /home/awohsen/.config/awesome/helpers/ui.lua:12: attempt to concatenate a nil value (local 'color')
stack traceback:
    /home/awohsen/.config/awesome/helpers/ui.lua:12: in function 'helpers.ui.colorize_text'
    ...wohsen/.config/awesome/modules/lockscreen/lockscreen.lua:172: in upvalue 'activate_word'
    ...wohsen/.config/awesome/modules/lockscreen/lockscreen.lua:188: in upvalue 'reset_time'
    ...wohsen/.config/awesome/modules/lockscreen/lockscreen.lua:202: in local 'func'
    /usr/share/awesome/lib/gears/object.lua:164: in function 'gears.object.emit_signal'
    [C]: in function 'xpcall'
    /usr/share/awesome/lib/gears/protected_call.lua:41: in function </usr/share/awesome/lib/gears/protected_call.lua:40>
    (...tail calls...)
    /usr/share/awesome/lib/gears/timer.lua:103: in function </usr/share/awesome/lib/gears/timer.lua:102>
2022-09-26 09:25:09 E: awesome: Error during a protected call: /home/awohsen/.config/awesome/helpers/ui.lua:12: attempt to concatenate a nil value (local 'color')
...

[Ryex]

Here there are the first ones before color thing keeps repeating:

error: /home/awohsen/.config/awesome/modules/UPower/init.lua:125: attempt to index a nil value (field 'device')

your computer does not have a battery and thus the config crashes.

comment out the following two lines

/home/awohsen/.config/awesome/ui/panels/top-panel/init.lua : 19

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

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

s.battery,

[awohsen]

comment out the following two lines

/home/awohsen/.config/awesome/ui/panels/top-panel/init.lua : 19

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

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

s.battery,

Thanks a lot, It's working now :partying_face:

btw, why there's no info about this issue in manual or anywhere else?!