logkeys
logkeys copied to clipboard
kernc
error parsing map file at boot
If reporting a bug, please ensure the bug is present in the latest
developmental source (checkout from SVN). Some major bugs have been fixed
already.
What steps will reproduce the problem?
1.execute a simple script that execute logkeys program with the comand :
>$ logkeys -s -m /path/it.map during the boot
2.
3.
What is the expected output?
nothing, logkeys should start correctly
What do you see instead?
error message on boot consolle
What version of the product are you using (`logkeys --help`)?
0.1.0
On what operating system?
debian
i wrote a script that simply run logkeys program with my preferit options.
that's the script:
#! /bin/bash
### BEGIN INIT INFO
# Provides: logkeys my way start
# Required-Start: $remote_fs
# Required-Stop: $remote_fs
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start the logkeys keylogger with my preferit options
### END INIT INFO
logkeys -s -m /home/user/.../it.map
exit 0
and i put it in /etc/init.d/ and executed the comand
>#update-rc script-name update
the script is executed at the boot time but he fails writing on consol error
while parsing it.map file at line n
the charactars that meke it fails are '£' 'ì' so i think maybe it fails couse
he can't recognize non ascii character at boot time, infact if i run the same
script after kde start it works fine.
Original issue reported on code.google.com by [email protected] on 11 Dec 2012 at 6:28
that's the line where it fails i think:
if (sscanf(line, "%lc %lc %lc\n", &char_keytable[index],
&shift_keytable[index], &altgr_keytable[index]) < 2) {
fprintf(stderr, "%s: Error parsing keymap '%s' on line %d: %s\n", argv[0], keymap_filename, line_number, line);
return EXIT_FAILURE;
Original comment by [email protected] on 11 Dec 2012 at 6:29
I have no idea.
Have you tried executing the script by setting the line in /etc/rc.local ?
Original comment by [email protected] on 12 Dec 2012 at 7:21
no i didn't i'll try and tell u if it works
Original comment by [email protected] on 12 Dec 2012 at 9:07
i tried, but it doesnt' work! same error. i give up!! :(
Original comment by [email protected] on 18 Dec 2012 at 8:54