Package: aptitude Version: 0.4.9-2 Severity: normal
I normally run aptitude from a konsole session, su'ing to a root prompt before running aptitude. On one recent occasion I failed to quit aptitude before quitting a kde session and aptitude remained running, consuming excessive amounts of CPU time. Should the closure of the konsole session stop aptitude, even if it is being run from a root prompt within that konsole session? If aptitude "loses" its controlling terminal, shouldn't it quit anyway, unless something special was done to run it without a controlling terminal? -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.23 (SMP w/1 CPU core; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages aptitude depends on: ii apt [libapt-pkg-libc6.6-6 0.7.9 Advanced front-end for dpkg ii libc6 2.7-3 GNU C Library: Shared libraries ii libcwidget0 0.5.5-4 high-level terminal interface libr ii libgcc1 1:4.2.2-4 GCC support library ii libncursesw5 5.6+20071124-1 Shared libraries for terminal hand ii libsigc++-2.0-0c2a 2.0.17-2 type-safe Signal Framework for C++ ii libstdc++6 4.2.2-4 The GNU Standard C++ Library v3 Versions of packages aptitude recommends: ii aptitude-doc-en [aptitude-doc 0.4.9-2 English manual for aptitude, a ter ii libparse-debianchangelog-perl 1.1.1-1 parse Debian changelogs and output -- debconf-show failed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
