Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Morse]

this is the same problem that was described here:http://forum.amule.org/index.php?topic=15328.0

i decided to create new topic because the name of previous doesn't fully describe the problem. amuled doesn't work with unicode at all:  it doesn't share unicode files, it doesn't make searches on unicode requests, and even if request is fully english it doesn't show files with unicode symbols in results. the last is the worst, because many "innocent" files have some chinese prefixes for some reason, and thus can't be found. the only way to find and download such files is to stop amuled, launch amule, find and add files and stop-launch all back. the files would be in queue in amuled, and after completion they will be named "unknown".

amule 2.2.2

[lfroen]

Mine works fine. However, I start it from regular shell, and not from init script.
I hope you do understand that there's almost zero chance someone will figure out how your init script(s) work or doesn't work. Your problem may be in script or locale or compilation flags or in all of them.

BTW, you did not specified what distro are you running and what WX version is installed. This is relevant.

[Morse]

that's odd - the problem indeed is in init-script. starting from the shell, amuled is fine.

it's not an amule problem, but if anyone have some clues about this, please send me a message.

[lfroen]

that's odd - the problem indeed is in init-script. starting from the shell, amuled is fine.

it's not an amule problem, but if anyone have some clues about this, please send me a message.

There's nothing odd. By the time amuled is started, environment is (apparently) not set - most chances it's about locale.

[Morse]

that was odd. i relaunched amuled many times after the boot with no result.

anyway, the problem is solved now: script "status_rc" that is the part of any init-script in suse had in the very begin this
LC_ALL=POSIX
export LC_ALL
i don't know what for it is, but it was the source of the problem.

[Kry]

You may want to add a note to the wiki about it. It seems to be a common problem.

[dissociative]

well I have this problem as well (I run ever amuled from the text terminal) and I havent find a way to resolve it yet, here's all the info anyway:

Operative System: Slackware 12.1
aMule 2.2.2
wxGTK 2.8.8

here is the output of locale

Code: [Select]

bash-3.1$ locale
LANG=en_US.utf8
LC_CTYPE="en_US.utf8"
LC_NUMERIC="en_US.utf8"
LC_TIME="en_US.utf8"
LC_COLLATE="en_US.utf8"
LC_MONETARY="en_US.utf8"
LC_MESSAGES="en_US.utf8"
LC_PAPER="en_US.utf8"
LC_NAME="en_US.utf8"
LC_ADDRESS="en_US.utf8"
LC_TELEPHONE="en_US.utf8"
LC_MEASUREMENT="en_US.utf8"
LC_IDENTIFICATION="en_US.utf8"
LC_ALL=
I even tried this: export LC_ALL=en_US.utf8 and then running amuled from the terminal and it didn't solve the problem.

and I'm attaching the amule.conf and config.log files of aMule and wxGTK sources compilation

I was thinking about additionally filling a bug report in the bug tracker

[dissociative]

looks like I have fixed the problem in my case, in part the fault was mine, I compiled my amule both monolithic and the daemon with the --disable-nls switch and that made amuled not to support unicode searches/results and shares, though the monolithic build didnt had that problem with nls disabled.