You are not logged in.
The problem doesn't arise in Gnome, so I assume something has to be up in Awesome. The bug(?) is non-existant in the first few minutes of the Awesome session. Then all timeout/expire arguments for notifications are ignored - the notification window stays up until I kill it with a click. This happens no matter if I fire the notification from a shell with "notify-send asdf -t 3000" or through Awesome with "naughty.notify({text='asdf', timeout=3})".
"grep notif *" in /var/log revealed nothing useful.
I have an ugly workaround through bash (can post it if someone needs it and we can't find a better solution), but I'd prefer something more elegant. I'm out of ideas - what should I be looking for?
Last edited by abesto (2009-03-07 20:53:22)
Linux user #476135 || Dotfiles hosted by GitHub
Offline
mhhm, my timeouts work just fine.
i'm using v3.2-rc4 (Faith) and did set some values in rc.lua
...
naughty.config.presets.normal.timeout = 5
naughty.config.presets.critical.timeout = 10
...
and any notification disappears just like it's supposed to.
Offline
Thanks for the answer, I didn't know about this feature. Actually, the timeouts do work. The error was unrelated.
There was a text update for a non-existent textbox in the 60-second timer hook (error was reported in ~/.xsession-errors). This fried Awesome more or less. D'oh.
Linux user #476135 || Dotfiles hosted by GitHub
Offline