Wesnoth becomes unresponsive when game starts

[Hamish Downer]

Binary package hint: wesnoth

When I open wesnoth, the menus work fine, I choose a campaign, go through the stories leading up to it, and it all works fine so far. Then the game begins and wesnoth becomes unresponsive. One cpu goes to 100%. Closing the window does nothing, killall wesnoth doesn't work, and I end up having to do kill -9

I have tried this several times, trying different campaigns and the behaviour is consistent. I have tried running it from the command line and the output seems normal.

I am running jaunty 64 bit with intel graphics. The output of lshw is attached if you want to look at the exact graphics stuff.

ProblemType: Bug
Architecture: amd64
Dependencies:

DistroRelease: Ubuntu 9.04
Package: wesnoth None [modified: /var/lib/dpkg/info/wesnoth.list]
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: wesnoth
Uname: Linux 2.6.28-11-generic x86_64
UnreportableReason: This is not a genuine Ubuntu package

[Hamish Downer (mishd)]

> UnreportableReason: This is not a genuine Ubuntu package

Not sure why that is the case, I have just installed it (using aptitude install ...). As far as I know it should be a genuine Ubuntu package.

[Hamish Downer (mishd)]

Fixed with some help from irc.

I had not installed wesnoth-music and this caused the problem. This is a bug that has been fixed in version 1.6.1 of wesnoth.

An alternative work around (if you don't want to install the music package) is to turn off the music in game. (On the first screen, click Preferences -> Sound -> untick the Music box).

The patch is at http://svn.gna.org/viewcvs/wesnoth?view=rev&rev=34257

[Hamish Downer (mishd)]

This is confirmed by talking to upstream on irc, they have a patch in their svn repository. The patch looks pretty small, so can this be included in the jaunty release?

[Rhonda D'Vine (rhonda)]

* mish <email address hidden> [2009-04-09 21:04:18 CEST]:
> This is confirmed by talking to upstream on irc, they have a patch in
> their svn repository. The patch looks pretty small, so can this be
> included in the jaunty release?

 I've prepared a 1:1.6a-3 version which you can find in the SVN
referenced in the source package informations. Given that I'm currently
on vacations and have a very low bandwidth flakey connection I rather
should not overuse (and .. well, I'm on vacations) it might take until
tuesday next week until the fix hits the Debian pool - I haven't managed
to upload it last week's thursday already, sorry.

 So long. :)
Rhonda

[Emmet Hikory (persia)]

Please find attached an update to 1.6a-3 that includes also the one-character fix for bug #360347. I'm uploading this as 1.6a-3ubuntu1 for release team review.

[Launchpad Janitor (janitor)]

This bug was fixed in the package wesnoth - 1:1.6a-3ubuntu1

---------------
wesnoth (1:1.6a-3ubuntu1) jaunty; urgency=low

  * Inclusion of newer Debian revision addresses LP: #358590
  * .ttc -> .ttf for Chinese font link (LP: #360347)

 -- Emmet Hikory <email address hidden> Tue, 14 Apr 2009 23:04:34 +0900

[Rhonda D'Vine (rhonda)]

* Emmet Hikory <email address hidden> [2009-04-14 16:19:11 CEST]:
> Please find attached an update to 1.6a-3 that includes also the one-
> character fix for bug #360347. I'm uploading this as 1.6a-3ubuntu1 for
> release team review.
>
> ** Attachment added: "debdiff for upload"
> http://launchpadlibrarian.net/25454371/wesnoth_1.6a-3ubuntu1.debdiff

 From reading the diff I fear you patched the wrong ttf to ttc. The link
target (being the first part in the ln statement) is wrong, not the link
name itself (being the second part in the ln statement).

 I'm not completely sure where in the ttf-wqy-zenhei package the
filename got changed - I expect it was 0.8.38-1 that got the changed
name as first, so it might also be proper to change the Recommends in
the wesnoth-data package to a versioned one, but as it actually is a
recommends I'm not sure if that will change anything at all anyway.

 Thanks,
Rhonda

[Hamish Downer (mishd)]

OK, got the latest jaunty version and that has fixed the problem. Thank you :)