** Summary changed: - Running bzflag results in xorg lockup/Xid + [nvidia-glx-legacy] Running bzflag results in xorg lockup/Xid
** Description changed: Binary package hint: nvidia-glx-legacy Description of the problem: The act of running BZflag seems to be able to trigger a bug in the nvidia-glx-legacy driver for me. This problem seems to have gotten worse over the years and is something that only nvidia can fix. This is just a place holder for other people to find. Steps to reproduce: 1. Install nvidia-glx-legacy and ensure that composite is turned off so 3D acceleration works. 2. Install bzflag . 3. Run bzflag then go to: Join Game -> Start Server -> Start . Expected result: Server to fail to start because bzflag-server is not installed. "Failed (exit = 2)." to be displayed. Actual result: Server fails to start because bzflag-server is not installed. "Failed (exit = 2)." is displayed. Keyboard stops responding and bzflag will chew up 98% of the CPU until killed off at a virtual terminal. The following is printed in syslog: NVRM: Xid: 6, PE0002 0404 00120000 00000000 80000000 00120000 (or) NVRM: Xid: 6, PE0002 0404 00120000 00210000 80000000 00120000 + How reproducible is this problem? + It is reproducible every time. + Version information: nvidia-glx-legacy 1.0.7184+2.6.17.5-5 linux-image-2.6.17-10-386 2.6.17-10.24 linux-restricted-modules-2.6.17-10-386 2.6.17.5-5 nVidia Corporation NV10DDR [GeForce 256 DDR] (rev 10) -- [nvidia-glx-legacy] Running bzflag results in xorg lockup/Xid https://bugs.launchpad.net/bugs/63427 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
