Your message dated Tue, 24 Jul 2007 12:23:49 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#375361: Still happening?
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: wesnoth-utbs
Version: 1.1.5-1
Severity: important
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14-2-k7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
In the first scenario, Seela is immediately affected.
The other archer that enters at the top is also paralysed.
If I save the
game and then load the saved game, many other units are also affect.
They can't attack or move. If I try to attack with such a unit, i
get the attack dialogue, but no options for weapons are available.
I can see the profile, which has the weapons listed. The units always
seem to remain in this state. There was one exception, when a paralysed
unit levelled. After that i could move with it.
I played through the first scenario without loading a saved game,
but in the second scenario, with recalled units, things got much worse.
There other units became paralysed even without saving a game.
Please let me know if you need any configuration files or further information.
Astrid
--- End Message ---
--- Begin Message ---
Hi!
On Sat, Aug 26, 2006 at 10:49:13AM +0200, Isaac Clerencia wrote:
> have you tried UTBS in 1.1.8 or in 1.1.9 (which I'm uploading just now)?
> does it still happens?
As this bug wasn't really reproducible and no response were given to
the answer I guess this is a non-bug and/or has been fixed in the
meantime.
If it still happens to you feel free to reopen the bug.
Rhonda
--- End Message ---
