Bug#354379: wesnoth: Wesnoth crash Xorg

2006-02-26 Thread Emmanuel Fleury
Hi,

Isaac Clerencia wrote:
 
 I'm reducing the severity of this bug report as I can't reproduce it. Please, 
 do further investigation about it and try to provide more info.

Might be related to the architecture (AMD64), I didn't tried yet on
another processor.

 On the other hand, Wesnoth uses SDL library to do all the graphics stuff, so 
 in any case, SDL (or the X server) should be guilty and not Wesnoth itself.

Right.

Actually, this might be the combination of a lot of things. I have to
investigate this much further (especially if I want to finish the
campaign I just started ! :)).

 If you want to play Wesnoth in the meanwhile may be you can try the -w 
 option to run it in windowed mode.

It works ok like this, it means that this is really the full-screen mode
that makes it crash.

I'll try to track the bug down and I'll report to whom it may concern
(probably SDL and maybe Xorg).

Thanks for your mail
-- 
Emmanuel Fleury

Rules of Optimization:
- Rule 1: Don't do it.
- Rule 2 (for experts only): Don't do it yet.
  -- M. A. Jackson


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#354379: wesnoth: Wesnoth crash Xorg

2006-02-25 Thread Emmanuel Fleury
Package: wesnoth
Version: 1.1.1-3
Severity: critical
Justification: breaks unrelated software

When starting wesnoth, the display becomes all black and the monitor
display a label No signal. I cannot do anything but kill the Xserver
(Ctrl+Alt+Backspace).

I managed to run wesnoth from a console
(Ctrl+Alt+F1 and 'export DISPLAY=:0) and I got the following error message:

Battle for Wesnoth v1.1.1
Started on Sat Feb 25 20:16:36 2006

started game: 2728662934
Checking video mode: 1024x768x16...
16
setting mode to 1024x768x16
X Error of failed request:  BadValue (integer parameter out of range for
operation)
  Major opcode of failed request:  135 (XFree86-VidModeExtension)
  Minor opcode of failed request:  10 (XF86VidModeSwitchToMode)
  Value in failed request:  0x44
  Serial number of failed request:  107
  Current serial number in output stream:  109



So, it seems that Wesnoth is asking for a refresh rate which is out of
bound and makes the monitor to block the out-of-range signal.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages wesnoth depends on:
ii  libc6 2.3.6-1GNU C Library: Shared
libraries an
ii  libfreetype6  2.1.10-1   FreeType 2 font engine,
shared lib
ii  libfribidi0   0.10.7-1   Free Implementation of the
Unicode
ii  libgcc1   1:4.1-0exp6GCC support library
ii  libsdl-image1.2   1.2.4-1image loading library for
Simple D
ii  libsdl-mixer1.2   1.2.6-1.1+b1   mixer library for Simple
DirectMed
ii  libsdl-net1.2 1.2.5-6network library for Simple
DirectM
ii  libsdl1.2debian   1.2.9-0.1  Simple DirectMedia Layer
ii  libstdc++64.1-0exp6  The GNU Standard C++ Library v3
ii  libx11-6  6.9.0.dfsg.1-4 X Window System protocol
client li
ii  python2.3 2.3.5-9An interactive high-level
object-o
ii  ttf-dejavu2.1-2  Bitstream Vera fonts with
addition
ii  wesnoth-data  1.1.1-3data files for Wesnoth
ii  zlib1g1:1.2.3-9  compression library - runtime

wesnoth recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#354379: wesnoth: Wesnoth crash Xorg

2006-02-25 Thread Isaac Clerencia
On Saturday, 25 February 2006 20:27, Emmanuel Fleury wrote:
 Package: wesnoth
 Version: 1.1.1-3
 Severity: critical
 Justification: breaks unrelated software

 When starting wesnoth, the display becomes all black and the monitor
 display a label No signal. I cannot do anything but kill the Xserver
 (Ctrl+Alt+Backspace).

Hi, Emmanuel.

I'm reducing the severity of this bug report as I can't reproduce it. Please, 
do further investigation about it and try to provide more info.

On the other hand, Wesnoth uses SDL library to do all the graphics stuff, so 
in any case, SDL (or the X server) should be guilty and not Wesnoth itself.

If you want to play Wesnoth in the meanwhile may be you can try the -w 
option to run it in windowed mode.

Best regards

-- 
Isaac Clerencia at Warp Networks, http://www.warp.es
Work: [EMAIL PROTECTED]   | Debian: [EMAIL PROTECTED]


pgpuLZpXcAX7s.pgp
Description: PGP signature