error message on startup from awsetbg
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Whenever I log in and awesome starts, I get the following error message: awsetbg: Something went wrong while setting the wallpaper. Run 'feh --bg-scale /usr/share/awesome/themes/default/background.png' from an xterm to find out what. But when I execute the command from xterm, it works (and I have the default background even after that message). My .xsession-errors also does not give me any indication: ## $ cat .xsession-errors openConnection: connect: No such file or directory cannot connect to brltty at :0 /usr/sbin/lightdm-session: 45: /etc/X11/Xsession.d/98vboxadd-xclient: /usr/bin/VBoxClient: not found /usr/sbin/lightdm-session: 46: /etc/X11/Xsession.d/98vboxadd-xclient: /usr/bin/VBoxClient: not found /usr/sbin/lightdm-session: 48: /etc/X11/Xsession.d/98vboxadd-xclient: /usr/bin/VBoxClient: not found /usr/sbin/lightdm-session: 50: /etc/X11/Xsession.d/98vboxadd-xclient: /usr/bin/VBoxClient: not found pgrep: invalid option -- '-' WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-YvNZ7W/pkcs11: No such file or directory pgrep: invalid option -- '-' WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-YvNZ7W/pkcs11: No such file or directory Can't become exclusive indexer: flock failed. Return (other pid?): 15569 Conky: forked to background, pid is 15708 Conky: forked to background, pid is 15710 Conky: desktop window (167) is root window Conky: window type - override Conky: drawing to created window (0x241) Conky: drawing to double buffer X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 113 (X_KillClient) Value in failed request: 0x1c1 Serial number of failed request: 16 Current serial number in output stream: 23 Conky: desktop window (167) is root window Conky: window type - override Conky: drawing to created window (0x161) Conky: drawing to double buffer ** Message: applet now removed from the notification area ** Message: applet now embedded in the notification area ** Message: applet now removed from the notification area ** Message: using fallback from indicator to GtkStatusIcon ** Message: applet now embedded in the notification area QSystemTrayIcon::setVisible: No Icon set $ ## This is no big deal, but annoying. Any suggestions what is going on? Rainer -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/kGWsACgkQoYgNqgF2egr3EQCdERQ772F0mJf5ZgYbHUEGDjea mAsAnjr9r3CEzbwRi9mlSGFfwxQGV7mv =3a1X -END PGP SIGNATURE- -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
How to specify config file in .desktop file?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi I added a new desktop file (below) to the xsessions directory to start with a non-default awesone config file, and everything is working now, but I am not happy that I have to specify the complete path in the -c : I tried Exec=awesome -c ~/.config/awesome/rc.shifty.lua Exec=awesome -c $HOME/.config/awesome/rc.shifty.lua in the assumption that this would be evaluated after the variables are set, but this is not the case - in both cases, the file rc.shifty.lua was not found. Only when using, as below, Exec=awesome -c /home/rkrug/.config/awesome/rc.shifty.lua it worked. This is not a problem as I am the only user, but I would like to know what the best way is to specify the awesome config file. Cheers, Rainer $ cat /usr/share/xs xscreensaver/ xserver-xorg/ xsessions/ rkrug@ecolmod:~$ cat /usr/share/xse xserver-xorg/ xsessions/ rkrug@ecolmod:~$ cat /usr/share/xsessions/awesome awesome.desktop awesome_shifty.desktop rkrug@ecolmod:~$ cat /usr/share/xsessions/awesome_shifty.desktop [Desktop Entry] Encoding=UTF-8 Name=awesome shifty Comment=Highly configurable framework window manager TryExec=awesome Exec=awesome -c /home/rkrug/.config/awesome/rc.shifty.lua -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/kITEACgkQoYgNqgF2egotXACfUvNW2f/PSYLr1NcOt1iWNqzX ENwAn3FsHeAIY6THtmGGK6BxTABN06Ul =IuKg -END PGP SIGNATURE- -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: error message on startup from awsetbg
2012/6/22 Rainer M Krug r.m.k...@gmail.com: This is no big deal, but annoying. Any suggestions what is going on? I was facing the same problem and my suspection is that there is some kind of race condition with the default command 'awsetbg'. In my case it was happening when using 2 or 3 display configuration - maybe setting wallpaper with a big resolution took too much time or something... Anyway, my workaround was to change the theme setting command in theme.lua from 'awsetbg' to that 'feh --bg-scale'. Not a perfect solution, but it was so uninmportant that I've decided not to investigate further. HTH, Paweł -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
bug in lib/gears/surface.lua
/usr/share/awesome/lib/gears/surface.lua my lgi.version = 0.6.2 = that will let the following code failed if tonumber(require(lgi.version)) = 0.5 then error(lgi too old, need at least version 0.7 (not yet released?) or rece nt git) end
Re: error message on startup from awsetbg
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 22/06/12 10:46, Paweł Rumian wrote: 2012/6/22 Rainer M Krug r.m.k...@gmail.com: This is no big deal, but annoying. Any suggestions what is going on? I was facing the same problem and my suspection is that there is some kind of race condition with the default command 'awsetbg'. In my case it was happening when using 2 or 3 display configuration - maybe setting wallpaper with a big resolution took too much time or something... Anyway, my workaround was to change the theme setting command in theme.lua from 'awsetbg' to that 'feh --bg-scale'. Not a perfect solution, but it was so uninmportant that I've decided not to investigate further. Thanks - I'll do the same and see. Cheers, Rainer HTH, Paweł -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/kNWwACgkQoYgNqgF2egrRjgCfZXHTbXH3kSqPedWfC3bz2sza HNAAoIWoCHhh/6POYpdK5eF01LrDfgrn =Adke -END PGP SIGNATURE- -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: error message on startup from awsetbg
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 22/06/12 10:46, Paweł Rumian wrote: 2012/6/22 Rainer M Krug r.m.k...@gmail.com: This is no big deal, but annoying. Any suggestions what is going on? I was facing the same problem and my suspection is that there is some kind of race condition with the default command 'awsetbg'. In my case it was happening when using 2 or 3 display configuration - maybe setting wallpaper with a big resolution took too much time or something... Anyway, my workaround was to change the theme setting command in theme.lua from 'awsetbg' to that 'feh --bg-scale'. Not a perfect solution, but it was so uninmportant that I've decided not to investigate further. Thanks - I'll do the same and see. Cheers, Rainer HTH, Paweł -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/kNXgACgkQoYgNqgF2egqN1gCdFUAOmWtWjskcwhfzPKO7dkVa VawAn1IbSJ3yGv+/NX9I9lTYtOU18jtb =J3kz -END PGP SIGNATURE- -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: Viewing Multiple Tags
On Mon, 18 Jun 2012, Hong Shick Pak wrote:
What do you mean strange layouts?
I ment strange keyboard layouts, not tiling layouts :)
The least you can do is add some debug print() statements to those
bindings to see if it's being executed at all maybe it thinks there is
no tag 2 on that screen. Start like this
awful.key({ modkey, Control }, # .. i + 9, function ()
local screen = mouse.screen
if tags[screen][i] then
print(Found tag .. tags[screen][i])
awful.tag.viewtoggle(tags[screen][i])
else
print(Did not find tag .. tags[screen][i])
end
end),
--
Adrian C. (anrxc) | anrxc..sysphere.org | PGP ID: D20A0618
PGP FP: 02A5 628A D8EE 2A93 996E 929F D5CB 31B7 D20A 0618
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: Viewing Multiple Tags
Just found out what was wrong. I remapped my Caps Lock to Ctrl with
xmodmap and this:
remove Lock = Caps_Lock
remove Control = Control_L
keysym Caps_Lock = Control_L
add Lock = Caps_Lock
add Control = Control_L
If I use the actual Ctrl key, everything works fine. I popped up xev
and I guess it's a problem with
XKeysymToKeycode returns keycode: 37
because the actual keycode for the Caps Lock is 66.
Why would this only bug that one special case with viewing tags?
On Fri, Jun 22, 2012 at 7:27 PM, Adrian C. an...@sysphere.org wrote:
On Mon, 18 Jun 2012, Hong Shick Pak wrote:
What do you mean strange layouts?
I ment strange keyboard layouts, not tiling layouts :)
The least you can do is add some debug print() statements to those
bindings to see if it's being executed at all maybe it thinks there is
no tag 2 on that screen. Start like this
awful.key({ modkey, Control }, # .. i + 9, function ()
local screen = mouse.screen
if tags[screen][i] then
print(Found tag .. tags[screen][i])
awful.tag.viewtoggle(tags[screen][i])
else
print(Did not find tag .. tags[screen][i])
end
end),
--
Adrian C. (anrxc) | anrxc..sysphere.org | PGP ID: D20A0618
PGP FP: 02A5 628A D8EE 2A93 996E 929F D5CB 31B7 D20A 0618
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: [PATCH] Broken lgi version checking
On Fri, 22 Jun 2012 01:22:01 +0200, asido4 wrote:
-if tonumber(require(lgi.version)) = 0.5 then +if
tonumber(string.match(require('lgi.version'), '(%d%.%d)')) = 0.5 then
error(lgi too old, need at least version 0.7 (not yet released?)
or recent git)
end
Maybe it would be good to also rephrase the error message, since already
released 0.6.1 should be OK. Maybe something like this:
error(lgi %s too old, need at least version 0.6.1, require
(lgi.version))
(sorry for not preparing proper patch, I still don't have cloned awesome
repo :-( )
--
Pavel
--
To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
[awesome bugs] #1010 - awesome does not start when lgi version has 3 numbers
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Abdó Roig (abdo) Attached to Project - awesome Summary - awesome does not start when lgi version has 3 numbers Task Type - Bug Report Category - Core Status - Unconfirmed Assigned To - Operating System - All Severity - Medium Priority - Normal Reported Version - git/master Due in Version - Undecided Due Date - Undecided Details - The version check for lgi in gears.surface fails, due to the fact that on my system lgi version is 0.6.2, which obviously does not convert to a number. One possible solution would be keeping only the first two numbers in the lgi version string for the comparison: if tonumber(require(lgi.version):match(%d+.%d+)) = 0.5 then error(lgi too old, need at least version 0.7 (not yet released?) or recent git) end git version: v3.4-728-g77b5dad More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1010 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
[awesome bugs] #1010 - awesome does not start when lgi version has 3 numbers
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1010 - awesome does not start when lgi version has 3 numbers User who did this - Arvydas Sidorenko (Asido) -- I sent a patch yesterday about it already, nobody reacted yet though. -- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1010#comment3055 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
0001-Do-not-attempt-to-call-global-destroy.patch
Hello list, I got attempt to call global destroy from two locations in naughty.lua, which should be fixed with this patch. The first one can be triggered by spamming notifications, the second one appeared to me on evolution's mail notification, which is supposed to be closed when opening the mail. From 47b5bec7c1e8234028a16d894e564194891a6003 Mon Sep 17 00:00:00 2001 From: Felix Bier flx.b...@googlemail.com Date: Fri, 22 Jun 2012 19:46:41 +0200 Subject: [PATCH] Do not attempt to call global destroy Signed-off-by: Felix Bier flx.b...@googlemail.com --- lib/naughty.lua.in | 4 ++-- 1 Datei geändert, 2 Zeilen hinzugefügt(+), 2 Zeilen entfernt(-) diff --git a/lib/naughty.lua.in b/lib/naughty.lua.in index 9e0fcee..27949e2 100644 --- a/lib/naughty.lua.in +++ b/lib/naughty.lua.in @@ -193,7 +193,7 @@ local function get_offset(screen, position, idx, width, height) -- if positioned outside workarea, destroy oldest popup and recalculate if v.y + height ws.y + ws.height or v.y ws.y then idx = idx - 1 -destroy(notifications[screen][position][1]) +naughty.destroy(notifications[screen][position][1]) v = get_offset(screen, position, idx, width, height) end if not v.idx then v.idx = idx end @@ -568,7 +568,7 @@ if capi.dbus then elseif data.member == CloseNotification then local obj = getById(appname) if obj then - destroy(obj) + naughty.destroy(obj) end elseif data.member == GetServerInfo or data.member == GetServerInformation then -- name of notification app, name of vender, version -- 1.7.11 signature.asc Description: This is a digitally signed message part
Re: 0001-Do-not-attempt-to-call-global-destroy.patch
On 22.06.2012 20:02, Felix Bier wrote: Hello list, I got attempt to call global destroy from two locations in naughty.lua, which should be fixed with this patch. The first one can be triggered by spamming notifications, the second one appeared to me on evolution's mail notification, which is supposed to be closed when opening the mail. Pushed, thanks. Seems like lua 5.2 caused more breakage than I had hoped for. :-( Uli -- For saving the Earth.. and eating cheesecake! -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
[awesome bugs] #1010 - awesome does not start when lgi version has 3 numbers
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#1010 - awesome does not start when lgi version has 3 numbers
User who did this - Uli Schlachter (psychon)
Reason for closing: Fixed
Additional comments about closing: commit
65de8a7ab5bac633b28a4deb4e2ccc1a6817aafb
Author: Arvydas Sidorenko asi...@gmail.com
Date: Fri Jun 22 01:22:01 2012 +0200
Broken lgi version checking
Currently it takes `require('lgi.version')`, converts it blindly to
number and compares with another value.
I am using lgi v0.6.1 and that is not convertable to number value,
thus tonumber() returns nil and crashes Awesome.
The fix is to take major and minor numbers only ignoring the rest.
Signed-off-by: Arvydas Sidorenko asi...@gmail.com
Signed-off-by: Uli Schlachter psyc...@znc.in
More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1010
You are receiving this message because you have requested it from the Flyspray
bugtracking system. If you did not expect this message or don't want to
receive mails in future, you can change your notification settings at the URL
shown above.
--
To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
Re: 0001-Do-not-attempt-to-call-global-destroy.patch
On 22.06.2012 23:58, Arvydas Sidorenko wrote: On 06/22/2012 11:19 PM, Uli Schlachter wrote: On 22.06.2012 20:02, Felix Bier wrote: Hello list, I got attempt to call global destroy from two locations in naughty.lua, which should be fixed with this patch. The first one can be triggered by spamming notifications, the second one appeared to me on evolution's mail notification, which is supposed to be closed when opening the mail. Pushed, thanks. Seems like lua 5.2 caused more breakage than I had hoped for. :-( The result of my lousy job :P I don't think that I would have done better. Finding all of these hiding module accesses is pretty much impossible. One could grep for all defined functions and variables in a module, but that would take forever... Also, in half a year or so, all the broken places that are left can be used as a marker on code that no one uses. ;-) Uli -- In the beginning the Universe was created. This has made a lot of people very angry and has been widely regarded as a bad move. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
[awesome bugs] #1009 - Awesome with Lua 5.2 leaks memory
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1009 - Awesome with Lua 5.2 leaks memory User who did this - Arvydas Sidorenko (Asido) -- That was issue in Lua 5.2 itself. Updating to v5.2.1 fixed the problem. -- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1009#comment3056 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
