awesome

Welcome to awesome bug tracking system.
Tasklist

FS#320 - Error setting wallpaper on startup

Attached to Project: awesome
Opened by Andrey A. Ugolnik (andreyu) - Thursday, 18 September 2008, 20:55 GMT
Last edited by Uli Schlachter (psychon) - Monday, 14 June 2010, 12:20 GMT
Task Type Bug Report
Category Core
Status Closed
Assigned To No-one
Operating System Linux
Severity Low
Priority Normal
Reported Version 3.0-rc6
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Each time i run awesome (affected version 3.0-rc6 and 3.0) i get message about imposible to set wallpaper. But wallpaper already set at startup.

Executing this command from terminal works fine, without errors.

I use Gentoo Linux, clean awesome install (only default scripts).
This task depends upon

Closed by  Uli Schlachter (psychon)
Monday, 14 June 2010, 12:20 GMT
Reason for closing:  Fixed
Additional comments about closing:  Seems to be fixed by now
Comment by Julien Danjou (jd) - Friday, 19 September 2008, 06:16 GMT
And… what message?
Comment by Andrey A. Ugolnik (andreyu) - Friday, 19 September 2008, 10:47 GMT
Message appear in window:

awsetbg: Something went wrong while setting the wallpaper.
Run 'display -window root /usr/share/awesome/themes/default-background.png' from an xterm to find out what.
Comment by Andrey A. Ugolnik (andreyu) - Friday, 19 September 2008, 10:48 GMT
Currently i just create my own theme with "wallpaper_cmd = awsetbg /usr/share/awesome/themes/default-background.png" comented.
Comment by Julien Danjou (jd) - Friday, 19 September 2008, 10:52 GMT
And so if you do what it tells, what happens?…
Comment by Andrey A. Ugolnik (andreyu) - Friday, 19 September 2008, 12:19 GMT
Wolpaper set, but this error message appear every time i start awesome or reload config.
Comment by Julien Danjou (jd) - Friday, 19 September 2008, 12:27 GMT
I think you misunderstand me. If you run that:

display -window root /usr/share/awesome/themes/default-background.png

what happens?
Comment by Andrey A. Ugolnik (andreyu) - Friday, 19 September 2008, 13:36 GMT
As i say in may first message it works fine, without any errors.
Comment by Konstantin Mukhamediev (Polir) - Saturday, 27 September 2008, 09:56 GMT
I've got the same issue. Execute 'awsetbg -i' in xterm and see the result.
In my case it was: "display doesn't set the wallpaper properly. ..." and so on.
I installed 'feh' and that fixed the problem.
The output from 'awsetbg -i' after that: "feh is a nice wallpapersetter. You won't have any problems."
Comment by Christophe-Marie Duquesne (christophe-marie) - Sunday, 11 January 2009, 21:30 GMT
installing feh also solved the problem for me
Comment by Niro (niro) - Thursday, 15 January 2009, 19:53 GMT
awsetbg used a range of wallpapersetters (from left to right):
Esetroot habak wmsetbg feh hsetroot chbg display qiv xv xsri xli xsetbg xsetroot
So, display is used after feh. And problem will not appear at all.

For all wpsetters awsetbg waits not 0, if something went wrong.
But display returns 1 even wallpaper exist. Maybe there's bug in it...

You may set wpsetters variable to which exists in your system (i.e. in .bashrc) but not display

wpsetters=feh xsetroot
Comment by shean massey (japon) - Monday, 19 January 2009, 12:32 GMT
I had the exact same problem with gentoo but figured it out after I wanted to light up Fluxbox, the "problem" is that awesome3 required a newer version of imlib2 in the ebuild. If you like me only installed imlib2 without saving the flags (png, jpeg, ...) in /etc/portage/package.use or /etc/make.conf imlib2 will be built without any support.

To fix it:
echo "media-libs/imlib2 X bzip2 gif jpeg mp3 nls png tiff zlib" >> /etc/portage/package.use; emerge -v imlib2

Hope that helps :)
Comment by Evgenii Terechkov (evg) - Saturday, 24 January 2009, 08:51 GMT
I had this problem too, but error dialog on startup/restart says:
====================================================================================
awsetbg: Something went wrong while setting the wallpaper.
Run 'display -sample -window root /usr/share/awesome/themes/default/background.png' from an xterm to find out what.
====================================================================================

AFAIK, problem not in "display" itself, but in awset's dependency on xwinfo:

evg@evg ~ $ grep -A1 'display)' /usr/bin/awsetbg
display)
full="-sample `xwininfo -root 2> /dev/null|awk '/geom/{print $2}'` -window root"

My system lack on "xwinfo", so display exit with code 1 and warning about invalid arg to -sample keyword. I think that istalling xwinfo may workaround this bug, but IMHO right way is to set wpsetters to right preference order. Personally I in my build for ALT Linux set primary settler to xsetroot (I can't remove xsetroot without removing awesome too by dependencies): 'http://git.altlinux.org/people/evg/packages/awesome.git?p=awesome.git;a=commitdiff;h=0b7eafcd4e6faa55043cda1095a615ce5afb2062#patch4'
Comment by Nikos Ntarmos (ntarmos) - Monday, 26 January 2009, 06:32 GMT
FWIW there is also the -u flag in awsetbg that stores the preferred setter in 'lastwallpaper'.
Comment by Evgenii Terechkov (evg) - Monday, 26 January 2009, 12:29 GMT
'-u' is not out-of-box solution :-)
Comment by Uli Schlachter (psychon) - Saturday, 12 June 2010, 19:43 GMT
Not knowing about this, I recently received a report about this xwininfo dependency on IRC and fixed it.
Can anyone confirm that this is really fixed?
Comment by Alex-P Natsios (Drakevr) - Sunday, 13 June 2010, 19:38 GMT
this should be fixed by now.

i can @ least guarantee that it fully works with feh.
unless someone can reproduce it with other setters i think this bug should be closed.

Loading...