Well, I solved my problem, but I don't know why that caused the behavior I saw.

There isn't a ~/.xsession-errors, but there is a /var/log/slim.log. I cleared it out and rebooted. The contents are a bit long, so I put the result at http://sprunge.us/SNiY . In there, you can see an error about a missing icon file. The theme was referencing something outside its directory, so it didn't get copied originally. So, I copied the files from /usr/share/awesome/icons/ into ~/.config/awesome/icons/. When I restarted awesome, things were back to normal.


On 02/02/2011 08:58 AM, Anurag Priyam wrote:
What can be causing this behavior?
Could you check awesome's error log and let us know? If you are using
some desktop manager (gdm, kdm, etc) then the errors should probably
be logged to ~/.xsession-errors, otherwise on the tty you started
awesome from.


--
To unsubscribe, send mail to [email protected].

Reply via email to