aMule Forum
English => aMule Help => Topic started by: sick boy on October 02, 2005, 02:38:44 AM
-
hi all,
When i open aMule i'm getting this error: "cannot set locale 'es_AR' "
any idea what is this? i have no probs with ID or dl bu is still strange! can that be because i have an national ip filter on?
thanx in advance
-
sick boy,
If you live in Lisbon, why is your locale setting to es_AR, which is the argentinian variation of the spanish language (castellano)? It should be pt_PT. Just curiosity :)
Anyway, to your problem: wxWidgets 2.6.2 has a problem with locale setting. Either downgrade to wx-2.6.1 or use wx-CVS. This is not an aMule bug.
And to answer your question, no, this is not related to IP filtering.
Cheers!
-
hi phoenix,
this is understanable because i used to live in spain, just moved to portugal!
My system is in english, keyboard in spanish and it's set to filter portuguese IPs only + internet prefs set to search for portuguese pages first!! LoL that might be why it doesn't warn me for the pt_PT.
Anyway, to your problem: wxWidgets 2.6.2 has a problem with locale setting. Either downgrade to wx-2.6.1 or use wx-CVS. This is not an aMule bug.
i am using wx-CVS no?? well at lest what i installed was the last mac binary...
for what i understood this is not a problem to ID stuff so, i was just curious about what it was?
thanx to clear my doubts...
PS- adoro a tua terra cara! ;) abraço...
-
Hi sick boy!
Originally posted by sick boy
this is understanable because i used to live in spain, just moved to portugal!
My system is in english, keyboard in spanish and it's set to filter portuguese IPs only + internet prefs set to search for portuguese pages first!! LoL that might be why it doesn't warn me for the pt_PT.
Ok, that explains :) But once you get aMule running, it will be in castellano with that locale. But I guess this is not a problem to you :)
Originally posted by sick boy
Anyway, to your problem: wxWidgets 2.6.2 has a problem with locale setting. Either downgrade to wx-2.6.1 or use wx-CVS. This is not an aMule bug.
i am using wx-CVS no?? well at lest what i installed was the last mac binary...
Hum, sorry, I am affraid I don't understand how Mac's OS work in detail, maybe our "Mac knows it all" staff can help you here. There should be a way for you to know which libraries you are using. This bug I mentioned has been recently reported in the forums, so that is why I could answer you so fast.
Originally posted by sick boy
for what i understood this is not a problem to ID stuff so, i was just curious about what it was?
thanx to clear my doubts...
You're wellcome!
Originally posted by sick boy
PS- adoro a tua terra cara! ;) abraço...
Obrigado! :) Um abraço!
-
Originally posted by phoenix
Ok, that explains :) But once you get aMule running, it will be in castellano with that locale. But I guess this is not a problem to you :)
?( it's running in english!!
my sys is in english, it's the keyboard that is set to spanish(as i bought it in barcelona).
Originally posted by phoenix
..., maybe our "Mac knows it all" staff can help you here. There should be a way for you to know which libraries you are using. This bug I mentioned has been recently reported in the forums, so that is why I could answer you so fast.
this is what i downloaded:
aMule-Mac.cvs2005-09-12.zip » 6177 Downloads
CVS Snapshot build for Mac OS X. See forum for more details.
Date: 18/09/2005 Filesize: 4MB » View Full Info
i haven't notest any bug here... except for that error :P
mais uma vez obrigado e abraço ;)
-
The Mac binary you are using was probably built with a version of wxMac which had the bug that phoenix is talking about. The wxWidgets folks have fixed the bug recently, but that fix won't help you until a new Mac binary incorporating it is built and released by lionell77.
-
That's weird, the aMule-Mac.cvs2005-09-12.zip binary I posted was built with wxWidgets cvs 2005-09-09. I thought the wx fix was much earlier than that.
I'll post a new binary soon and then we can see whether the issue is resolved or not.
-
Well, it was only a guess on my part. I don't actually know the specifics of the bug or when it was fixed (except "after 2.6.2" ;)).