Joerg van den Hoff wrote:
ion3 was starting and running fine the last weeks since I downloaded it
(including status bar and everything) until today I had to kill (via the
popup menu, actually) an Xterm which was generating lots of output (from
a ls -R) but was not responding to ^C.
I think this triggered the error, which occurs now at each fresh start
or restart and the statusbar only reads something like `[ ? || load:
?]', i.e. date and load information is gone.
the complete error message is:
Stack trace:
0 [C]: in 'warn'
1 mod_statusbar.lua:284: in 'launch_statusd'
2 /Users/vdh/.ion3/cfg_statusbar.lua:46
[Skipping unnamed C functions.]
5 [C]: in 'dopath'
6 mod_statusbar.lua:334
[Skipping unnamed C functions.]
9 [C]: in 'dopath'
10 /Users/vdh/.ion3/cfg_ion.lua:47
[Skipping unnamed C functions.]
>> Failed to start ion-statusd.
>> Stack trace:
0 [C]: in 'warn'
1 mod_statusbar.lua:284: in 'launch_statusd'
2 mod_statusbar.lua:338
[Skipping unnamed C functions.]
5 [C]: in 'dopath'
6 /Users/vdh/.ion3/cfg_ion.lua:47
[Skipping unnamed C functions.]
this was on the list (I found it in the archive) but I did not find the
reason of / solution for the error.
I noted that cfg_statusd.lua in `default-session--0' consists only of:
-- This file has been generated by Ion. Do not edit.
return {
}
which prob. is not right. quitting ion, removing `default-session--0'
manually and starting ion again did not help either.
any help appreciated
joerg
in the meantime I have rebooted the machine (other things under X11 were
no longer working quite correct: rxvt (in contrast to xterm reported:
'cannot connect to tty' or something to that effect) and the reported
problem has 'self-repaired' itself. so probably the X11 server had
hickup'ed causing the error message.
sorry for posting to early (though a hint what might have happened
would nevertheless be appreciated)
joerg
