> Nothing else? Timeout means that mod_statusbar didn't get enough > responses from ion-statusd within 3 seconds of its launch. That > itself is not fatal; the timeout is there merely to calculate a > useful initial statusbar size before workspaces are created etc. > Ion can cope without that, but it can result in annoying extra > resizes after the statusbar has finally managed to start up. > It, however, seems that statusd just quit without doing anything, > not even complaining. That should not happen. > > Try running ion-statusd outside Ion (it's in $PREFIX/lib/ion3/bin/ > normally), with and without parameters (such as -q -m scriptname). > If that works, try figuring out the parameters Ion is running it > with, and check your configuration, including any custom scripts > that might call os.exit() or something. > > -- > Tuomo >
Hm... It seems statusd_amarok was guilty. Don't know how and why it used to work before. But when I disabled this script all returned to normal behavior.
