Hi,
I'm new to the list. I tried searching for any references to this type
of error/stack trace, but I didn't get too far in the archives. There
was a mention of a scratchpad issue, but I wasn't sure about the fix.
In anycase, I'm using coLinux with a Debian image 2.6 kernel. I get
the following error messages whenever I start up ion with either ion2
or ion3:
---------------------------------------------
Ion startup error log:
>> KP_Enter: Could not convert keysym to keycode.
>> Stack trace:
0 [C]: in 'do_defbindings'
1 ioncore_bindings.lua:187: in 'defbindings'
2 /home/doobie-do/.ion3/cfg_query.lua:10
[Skipping unnamed C functions.]
5 [C]: in 'dopath'
6 mod_query.lua:954
[Skipping unnamed C functions.]
9 [C]: in 'dopath'
10 /home/doobie-do/.ion3/cfg_ion.lua:42
[Skipping unnamed C functions.]
>> KP_Enter: Could not convert keysym to keycode.
>> Stack trace:
0 [C]: in 'do_defbindings'
1 ioncore_bindings.lua:187: in 'defbindings'
2 /home/doobie-do/.ion3/cfg_menu.lua:10
[Skipping unnamed C functions.]
5 [C]: in 'dopath'
6 mod_menu.lua:395
[Skipping unnamed C functions.]
9 [C]: in 'dopath'
10 /home/doobie-do/.ion3/cfg_ion.lua:43
[Skipping unnamed C functions.]
----------------------------------------------
When I comment out the "dopath("mod_query")" and "dopath("mod_menu")"
line items in cfg_ion.lua, then those errors go away. However,
commenting these out doesn't seem to be right to me (especially as I
lose F12 menu functionality when I comment out the mod_menu portion).
I used apt-get install ion2; apt-get install ion3; apt-get -t testing
ion3. I haven't tried unstable, since I figure that if this problem
persists across two stable releases, it's probably something on my
side.
If anybody can point me in the right direction or has seen this issue
before to see where I can tweak my config files to get rid of these
annoying startup errors, I'd appreciate it.
Thanks.
