Hi,
there seem to be encoding problems with the messages of some user. Certains characters like é or ê show up with � instead.
It's probably because those users are not using utf-8 enconding. The issue is likely to be the same as this one, and seems related to this one from slate-irc.
Might be fixed by #167
Can you test current master and see if this issue is fixed?
@ErKaNs Is this on 1.5.0 or master?
version 1.5.0
This issue may be fixed on master, do you mind testing it? https://github.com/thelounge/lounge#development-setup
when i use npm start
0 info it worked if it ends with ok
1 verbose cli [ 'node', '/usr/local/bin/npm', 'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]~prestart: [email protected]
6 silly lifecycle [email protected]~prestart: no script for prestart, continuing
7 info lifecycle [email protected]~start: [email protected]
8 verbose lifecycle [email protected]~start: unsafe-perm in lifecycle true
9 verbose lifecycle [email protected]~start: PATH: /usr/local/lib/node_modules/npm/bin/node-gyp-bin:/home/_/lounge/node_modules/.bin:/usr/local/bin:/usr/local/jdk/bin:/home/_/perl5/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11R6/bin:/home/_/bin
10 verbose lifecycle [email protected]~start: CWD: /home/_/lounge
11 silly lifecycle [email protected]~start: Args: [ '-c', 'node index' ]
12 silly lifecycle [email protected]~start: Returned: code: 8 signal: null
13 info lifecycle [email protected]~start: Failed to exec start script
14 verbose stack Error: [email protected] start:node index
14 verbose stack Exit status 8
14 verbose stack at EventEmitter.(/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:239:16)
14 verbose stack at EventEmitter.emit (events.js:98:17)
14 verbose stack at ChildProcess.(/usr/local/lib/node_modules/npm/lib/utils/spawn.js:24:14)
14 verbose stack at ChildProcess.EventEmitter.emit (events.js:98:17)
14 verbose stack at maybeClose (child_process.js:730:16)
14 verbose stack at Process.ChildProcess._handle.onexit (child_process.js:797:5)
15 verbose pkgid [email protected]
16 verbose cwd /home/*/lounge
17 error Linux 2.6.32-573.7.1.el6.x86_64
18 error argv "node" "/usr/local/bin/npm" "start"
19 error node v0.10.4
20 error npm v3.7.1
21 error code ELIFECYCLE
22 error [email protected] start:node index
22 error Exit status 8
23 error Failed at the [email protected] start script 'node index'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the thelounge package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error node index
23 error You can get information on how to open an issue for this project with:
23 error npm bugs thelounge
23 error Or if that isn't available, you can get their info via:
23 error npm owner ls thelounge
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]
[email protected] is way too old. You should upgrade.
u can look from: http://irc.sevgisohbet.com:9000/
@ErKaNs When you post an image, could you give a little more information. This is like pulling teeth. Is that an image from running master, or are you still running 1.5.0? Have you updated node? etc, etc...
root@224hh8lrz [~]# node -v
v4.4.4
root@224hh8lrz [~]# npm -v
2.15.1
im use this
https://github.com/thelounge/lounge#development-setup
@ErKaNs Is this still an issue on the latest version?
Lacking details, closing this. We can remove if this is an issue, but many things have changed since then.