Package: aptitude Version: 0.4.1-1.1 Severity: normal I start up aptitude as root and hit u. During the update (possibly at the end of the file retrievals) it crashes. The terminal shows Ouch! Got SIGSEGV, dying.. Segmentation fault
I did just do an apt-get dist-upgrade, though nothing obviously related changed (there were python changes). I suspect this has to do with aptitude trying to work out dependency conflicts. I've been using aptitude update (from the command line) but apt-get for my dist-upgrades and upgrades. So aptitudes notion of how things should be is pretty far from the current system state (e.g., the system went through the X 7 upgrade awhile ago). When aptitude starts it shows there are conflicts, and when I go to examine them the display of open/closed/etc keeps updating counts. I presume this was going on during the update, and suspect the crash has something to do with that. It might be relevant that when I started aptitude before the X transition (but when the new X was available) it would ask if I wanted to examine alternatives. It would show 1/1, but then when I selected next alternative it would show 2/2, and so on, seemingly without limit. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (50, 'unstable'), (40, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-k7-smp Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages aptitude depends on: ii apt [libapt-pkg-libc6.3-6-3.1 0.6.44.2 Advanced front-end for dpkg ii libc6 2.3.6-15 GNU C Library: Shared libraries ii libgcc1 1:4.1.1-5 GCC support library ii libncursesw5 5.5-2 Shared libraries for terminal hand ii libsigc++-2.0-0c2a 2.0.16-3 type-safe Signal Framework for C++ ii libstdc++6 4.1.1-5 The GNU Standard C++ Library v3 Versions of packages aptitude recommends: pn aptitude-doc-en | aptitude-do <none> (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
