Unfortunately, it appears that we do eed to sleep some more when started
from KUAL, because the framework schedules a refresh that risks popin up
over us if we start too early/fast... :/.
I tried to be tricky (by stopping awesome, and s cheduling a resume
later) to avoid sleeping, but that didn't work :'(.
We just end up with the scheduled refresh as soon as awesome resumes...
First: sleep less. Looks okay on the slowest device I could find
(an indexing Touch in a hottish weather). Tweak if things are still racy
somewhere.
Second: Switch to a gentler approach to get rid of the title bar.
Seems to do the trick, and we don't get a slew of warnings in the logs
on exit ;).
Besides a few sanity fixes, this adds logging, doesn't flood
KUAL's log anymore, and handles KUAL-only code-paths properly.
There's a bunch of maybe-no-terribly-necessary sleeps in there,
but in general they help avoid weird crap happening.
