Package: glchess Version: 1:3.4.2-2 Severity: important Dear Maintainer,
* What led up to the situation? A: Playing glchess for some time and quitting the game in between. * What exactly did you do (or not do) that was effective (or ineffective)? A: Quit the game through the 'game' menu * What was the outcome of this action? A: Each game spawned a new process which never got killed. CPU usage went upto 100%. * What outcome did you expect instead? A: Safe exit of process -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (700, 'unstable'), (650, 'testing'), (600, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages glchess depends on: ii dconf-gsettings-backend [gsettings-backend] 0.12.1-2 ii gnome-games-data 1:3.4.2-2 ii gnuchess 6.0.2-1 ii libc6 2.13-33 ii libcairo2 1.12.2-2 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libgl1-mesa-glx [libgl1] 8.0.3-1 ii libglib2.0-0 2.32.3-1 ii libglu1-mesa [libglu1] 8.0.3-1 ii libgtk-3-0 3.4.2-1 ii librsvg2-2 2.36.1-1 ii libsqlite3-0 3.7.13-1 ii libx11-6 2:1.5.0-1 glchess recommends no packages. glchess suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org