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 : >> 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: 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 : >> 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
2012/6/22 Rainer M Krug : > 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.
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.
