awesome wm menubar not working [SOLVED]

_govind · 2015-01-13 04:09:14

I have recently upgraded awesome (3.5.5-1 -> 3.5.6-1)

After that I get the following error on modkey + p

/usr/share/awesome/lib/menubar/utils/lua:17: bad argument #2 to 'gsub' (string/function/table expected)
/usr/share/awesome/lib/menubar/init.lua:152: bar argument #1 to 'ipars' (table expected, got nil)

Here is my config.
This is also happening with default config at /etc/xdg/awesome/rc.lua

https://github.com/awesomeWM/awesome/pull/83 solved the issue

Last edited by _govind (2015-02-23 10:09:08)

Kinokoio · 2015-01-14 00:04:26

Can you access the menu? I use xdg_menu to create the menu to display and it works well.

_govind · 2015-01-15 04:49:21

I am not talking about the awesome menu (the one at top left). This works. I am talking about the modkey + p, which does not work any more.

awful.key({ modkey }, "p", function() menubar.show() end)

This is similar to modkey + r, where you can type commands.

nullified · 2015-01-15 05:32:09

Since the error persists using the default rc.lua, perhaps it's due to something in your theme? I can't imagine what it would be, but what theme are you using? Post the .lua here

Edit: apologies, I missed the theme.lua config up there. I'll see if I can replicate.

Last edited by nullified (2015-01-15 05:40:39)

_govind · 2015-01-15 17:52:25

I do not know if this is a config issue. I tried
#mv ~/.config/awesome ~/.config/awesome.backup
May be this is a recent change in awesome that caused this?

I will try awesome-git and try to git bisect this over the weekend.

Thanks

Demonix_Fox · 2015-01-21 07:44:25

I just ran into this same problem. The true error is the first error in the utils.lua. For some reason on that line in the gsub command, the program.Name is not being set correctly. Even stranger about this issue is that it happened on my desktop after I updated, but not my laptop.

I temporarily replace the program.Name call with just a static string to see what would happen, and the problem seems to have disappeared, now we just need to find out why program.Name is not being set.

Both of them are using identical rc.lua and it still happens with the default rc.lua.

I also diffed each file in the /usr/share/awesome/lib/menubar directory between my laptop and desktop.

EDIT: Sorry, utils.lua not init.lua

Last edited by Demonix_Fox (2015-01-21 15:54:50)

krypsin · 2015-01-22 21:43:43

Just thought I'd jump into this thread as I am experiencing the exact same issue.

Installed awesome for the first time last week and only tried using a theme yesterday and every theme I've tried gives me a gsub bad argument error.

Here's my stderr for awesome on startup:

/bin/bash: unclutter: command not found
error while running function
stack traceback:
	[C]: in function 'gsub'
	/usr/share/awesome/lib/menubar/utils.lua:178: in function 'parse'
	/usr/share/awesome/lib/menubar/utils.lua:203: in function 'parse_dir'
	/usr/share/awesome/lib/menubar/menu_gen.lua:92: in function 'generate'
	/home/krypsin/.config/awesome/menugen/init.lua:28: in function 'build_menu'
	/home/krypsin/.config/awesome/rc.lua:107: in main chunk
error: /usr/share/awesome/lib/menubar/utils.lua:178: bad argument #2 to 'gsub' (string/function/table expected)
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[8919:8919:0122/213804:ERROR:sandbox_linux.cc(319)] InitializeSandbox() called with multiple threads in process gpu-process
[8881:8940:0122/213804:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates
[WARNING:flash/platform/pepper/pep_module.cpp(63)] SANDBOXED
Fontconfig error: Cannot load default config file

From what I can see (and I don't know any lua), program.Name isn't a registered variable or something, pretty much what Demonix_Fox was saying.
No idea how I'd debug this...

Am running awesome v3.5.6 if that helps anyone

lucke · 2015-01-22 22:23:41

Works here.

Judging by its behaviour, without looking at any code, I'd say that it is whatever you have installed that makes the difference. Some desktop file breaks it or somesuch.

nullified · 2015-01-23 16:06:25

lucke wrote:

Some desktop file breaks it or somesuch.

That seems to be the case according to this pull request: https://github.com/awesomeWM/awesome/pull/83

See if the fix there works.

daasdingo · 2015-01-25 17:26:46

Had the same issue, the fix from the pull request worked!

krypsin · 2015-01-25 22:25:43

nullified wrote:

lucke wrote:
Some desktop file breaks it or somesuch.
That seems to be the case according to this pull request: https://github.com/awesomeWM/awesome/pull/83
See if the fix there works.

Brilliant! Thanks so much for posting that, worked a charm.

So if I understand correctly, it's just a problem to do with menu building. When looking for .desktop files, if there's ones that aren't written correctly then it throws the error.

Arch Linux

#1 2015-01-13 04:09:14

awesome wm menubar not working [SOLVED]

#2 2015-01-14 00:04:26

Re: awesome wm menubar not working [SOLVED]

#3 2015-01-15 04:49:21

Re: awesome wm menubar not working [SOLVED]

#4 2015-01-15 05:32:09

Re: awesome wm menubar not working [SOLVED]

#5 2015-01-15 17:52:25

Re: awesome wm menubar not working [SOLVED]

#6 2015-01-21 07:44:25

Re: awesome wm menubar not working [SOLVED]

#7 2015-01-22 21:43:43

Re: awesome wm menubar not working [SOLVED]

#8 2015-01-22 22:23:41

Re: awesome wm menubar not working [SOLVED]

#9 2015-01-23 16:06:25

Re: awesome wm menubar not working [SOLVED]

#10 2015-01-25 17:26:46

Re: awesome wm menubar not working [SOLVED]

#11 2015-01-25 22:25:43

Re: awesome wm menubar not working [SOLVED]

Board footer