Wesnoth crashes when installing add-ons

[o_o]

Hello,

I'm experiencing a problem with version 1.6.1.
Whenever I try to install an add-on, just after the download is complete, I get this :



Then Wesnoth crashes.
I use Windows Vista Ultimate, 32 bit.

Any advice ?

[Tiptopdu]

Same problem on my own computer (windows vista). Any solution will be welcomed

[Dragonchampion]

Maybe Wesnoth isn't compatible with Vista?

[Mist]

There's nothing wrong with Wesnoth on Vista. Make sure you've got enough room to extract the add-ons, and nothing (like Data Execution Prevention or AntiVir software) stops it from working properly.

And.

Please do what the Tech Support forum rules ask you. Want our help, play by our rules.

[Tiptopdu]

« Maybe Wesnoth isn't compatible with Vista? »
I confirm what Mist wrote : no problem with Vista. I use the precedent versions with Vista. Or maybe it concerns the new version 1.6.X...

“Make sure you've got enough room to extract the add-ons”
Done and that’s ok.

“...and nothing (like Data Execution Prevention or AntiVir software) stops it from working properly” : It’s not that. My firewall and antivirus prevent me when they stop a prg.

“Please do what the Tech Support forum rules ask you. Want our help, play by our rules.”
Uh! What does it mean...?

Thanks by advance for help!

[Max]

“Please do what the Tech Support forum rules ask you. Want our help, play by our rules.”
Uh! What does it mean...? :-)

see right above the topic ("you must read the following thread")...

Code: Select all

Always attach to the original submission output of stderr, after running the game with --log-debug=all switch, pasted into http://www.pastebin.ca or a similar site that keeps pastes longer than 24 hours.

this file contains more info than a huge screenshot with a meaningless error prompt (this gets worse with every new windows version, i guess in win7 this will be replaced with a box containing just "BANG"^^)

[Tiptopdu]

Hello,

"Always attach to the original submission output of stderr, after running the game with --log-debug=all switch, pasted into http://www.pastebin.ca or a similar site that keeps pastes longer than 24 hours"

Well... I'm sorry... 1) I'm a part of the few and poor peoples on Earth their mother tongue is not English... 2) I'm not a whizz with computers (that means I'm not the author of this "huge screenshot" you wrote about, just because I'm pretty unable to do that!) : 2 handicaps! ...

What is this "output of stderr" it is written about? What's the way to "run the game with --log-debug=all switch"?

Could you please explain me what I have to do? I have understand I have to "capture" something like a file after wesnoth bugging, but what, where and how? that are the questions I know, maybe it's a challendge for you... ...so, if you can't or don't have time to help me, maybe could you indicate me a website where I could find a french technical explanation on this ?

If no... well, I suppose I shall leave Wesnoth after something like 6 years of fun

[Mist]

There's a file called stderr.txt in the main wesnoth folder, "output of stderr" means everything inside that file.
To run wesnoth with the switch rightclick the desktop shortcut, choose proprties, and in the second tab (called "shortcut") in "target element" field, add at the end --log-debug=all. In my case it looks like

Code: Select all

"D:\Battle for Wesnoth 1.6.1\wesnoth.exe" --log-debug=all

You'll probably have a different path, but it doesn't matter, you just need to and the switch at the end.

Postscriptum.
We don't expect everyone to be a native english computer wizards, but we'd really like people to at least read the rules and ask for the bits they don't understand. It significantly cuts the time we spend on getting the useful data and the time people actualy get help. Think of it, we could solve the issue a week ago.

[Tiptopdu]

Hello,
I reinstalled Wesnoth, I tried again to download an extension (and failed again) and I used --log-debug=all as you wrote, and here is the text I've found in the "stderr" file:
------------------------------------------------------------------------------------------
Battle for Wesnoth v1.6.1
Started on Wed Apr 29 19:54:00 2009

Automatically found a possible data directory at C:/Users/Sylvain/AppData/Local/Battle for Wesnoth 1.6.1

Data directory: C:/Users/Sylvain/AppData/Local/Battle for Wesnoth 1.6.1
User configuration directory: C:/Users/Sylvain/Documents/My Games/Wesnoth1.6

Checking video mode: 1024x768x32...
setting mode to 1024x768x32
20090429 19:55:14 error display: could not open image '../images/items/football.png'
20090429 19:55:24 error display: Problem handling utf8 in message 'L'extension « » a été installée avec succès.'
-----------------------------------------------------------------------------------------
'L'extension « » a été installée avec succès.' : it is "l'extension a été installé avec succès" and it means more or less "the extension was successfully installed". Also my computer is french speaker...and maybe that's the matter

"Think of it, we could solve the issue a week ago."
If "forum rules" was written bigger or/and if beside it was written "Merci de lire les règles du forum avant de poster quoi que ce soit", I would have certainly seen and read it and we would have certainly earn few messages, that's sure...

[Mist]

20090429 19:55:24 error display: Problem handling utf8 in message 'L'extension « » a été installée avec succès.'

I've got a feeling it's a very stupid translation releated issue. Can you try switching the language to english and see what happens? I'm 100% sure it'll fix the problems. French translation team should be rather red faced now :]

[Tiptopdu]

"I've got a feeling it's a very stupid translation releated issue."

you're right, it is! I used english version and it works perfectly.

To thank you, here is a french translation of the forum rules
------------------------------------------------------------------------------------------

Merci de lire ces quelques lignes. Le forum étant de plus en plus difficile à contrôler, nous avons besoin d’édicter quelques règles :

Premièrement et avant toute chose :
Ne pas réévoquer inutilement un problème déjà soulevé dans un post précédent.

Deuxièmement :
Cette partie du forum ne concerne que le jeu tel qu’il a été téléchargé sur le site officiel (http://www.wesnoth.org) via la page de téléchargement. Elle ne vous sera donc d’aucune utilité pour résoudre des problèmes concernant des extensions créées par des tiers et téléchargées par la suite. Si vous rencontrez un problème avec une ère ou une campagne allez vous renseigner sur Faction and Era Contributions Forum ou Scenario and Campaign Development Forum

Les posts ne respectant pas la première et la seconde de ces règles seront supprimés.

Et finalement :
Afin que nous puissions vous répondre rapidement, merci de joindre dans votre post le contenu de votre fichier stderr. Pour cela, suivez la procédure ci-dessous :
- Clic droit sur le raccourci de Wesnoth ;
- dans la fenêtre qui apparaît, allez sur l’onglet « Raccourci » ;
- dans le champs intitulé « cible » placez --log-debug=all juste après "C:\Users\XXX\AppData\Local\Battle for Wesnoth X.X.X\wesnoth.exe"
- appuyez sur « OK » : la fenêtre se ferme.
- De nouveau clic droit sur le raccourci Wesnoth et retournez sous l’onglet raccourci ;
- à présent, appuyez sur « ouvrir l’emplacement du fichier ;
- dans la fenêtre qui s’ouvre, double-cliquez sur le fichier « stderr.text » et copiez le contenu.

Quelques amendements...
*Cette partie du forum n’est pas un “atelier WML » (« Wesnoth Markup Language » le langage qui est utilisé pour créer de nouvelles unité, scénarii, campagne, ères… à peu près tout le contenu de ce jeu !).
*Les spécificités de votre PC importent vraiment : signalez-les dans votre message !
------------------------------------------------------------------------------------------

Thanks again,
Ciao

[silene]

I've got a feeling it's a very stupid translation releated issue. Can you try switching the language to english and see what happens? I'm 100% sure it'll fix the problems. French translation team should be rather red faced now :]

The issue can indeed be avoided by modifying the French translation and it will be. But note that the translation is not "corrupt", as wrongly reported in the bug-report. The bug (or feature?) is somewhere else: the variable substitution engine of Wesnoth is not UTF8-aware and can therefore create invalid UTF8 strings. So this crash will also occur for other languages that use (for instance) non-breaking spaces after variable names.