logkeys: LC_CTYPE locale must be of UTF-8 type
- Dominant language
- C++
- Stars
- 834
- Forks
- 254
- PR merge metrics
- No merged PRs in 30d
Description
```
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.run llk or logkeys --start --output test.log or some other combination (with
sudo)
2.test.log file is created but the program doesnt start
3.
What is the expected output?
the program doesnt start
What do you see instead?
after type
#llk (or some other combination)
#logkeys: LC_CTYPE locale must be of UTF-8 type
and nothing else.
What version of the product are you using (`logkeys --help`)?
logkeys version: 0.1.1a
On what operating system?
Linux userpc 3.2.0-4-amd64 #1 SMP Debian 3.2.35-2 x86_64 GNU/Linux
Please provide any additional information below.
# locale
LANG=es_AR.UTF-8
LANGUAGE=es_AR:es
LC_CTYPE="es_AR.UTF-8"
LC_NUMERIC="es_AR.UTF-8"
LC_TIME="es_AR.UTF-8"
LC_COLLATE="es_AR.UTF-8"
LC_MONETARY="es_AR.UTF-8"
LC_MESSAGES="es_AR.UTF-8"
LC_PAPER="es_AR.UTF-8"
LC_NAME="es_AR.UTF-8"
LC_ADDRESS="es_AR.UTF-8"
LC_TELEPHONE="es_AR.UTF-8"
LC_MEASUREMENT="es_AR.UTF-8"
LC_IDENTIFICATION="es_AR.UTF-8"
LC_ALL=
If applicable, also attach contents of /proc/bus/input/devices, the output
of command `dumpkeys -n > dumpkeys.output`, and any
other relevant files.
```
Original issue reported on code.google.com by `eljuje...@gmail.com` on 24 Feb 2013 at 3:27
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the failure with `llk` or `logkeys --start --output test.log` under the reported Debian/Linux locale, and inspect the `locale` output provided in the issue. Determine why `LC_CTYPE=es_AR.UTF-8` is rejected; done means logkeys starts successfully and creates the expected output instead of stopping with the UTF-8 error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, linux
- Domain
- operating-systems, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100