Your message dated Mon, 19 Mar 2012 23:04:31 +0000
with message-id
<CAPQ4b8mwMLyspS1bd3xnNo0ppPQY=jpu5vpbjjprxldif_p...@mail.gmail.com>
and subject line Re: [aptitude-gtk] aptitude-gtk crashes when reading package
status and build list with glibmm-error **: unhandled exception (type unknown)
in signal handler
has caused the Debian Bug report #575956,
regarding [aptitude-gtk] aptitude-gtk crashes when reading package status and
build list with glibmm-error **: unhandled exception (type unknown) in signal
handler
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
575956: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575956
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: aptitude-gtk
Version: 0.6.1.5-3
Severity: normal
--- Please enter the report below this line. ---
--- System information. ---
Architecture: i386
Kernel: Linux 2.6.32-3-686
Debian Release: Sid
900 unstable www.debian-multimedia.org
900 unstable ftp.debian.org
800 experimental ftp.debian.org
500 stable people.debian.org
101 experimental-snapshots qt-kde.debian.net
--- Package information. ---
Depends (Version) | Installed
================================================-+-====================
aptitude (= 0.6.1.5-3) | 0.6.1.5-3
libapt-pkg-libc6.9-6-4.8 |
libatk1.0-0 (>= 1.20.0) | 1.28.0-1
libboost-iostreams1.40.0 (>= 1.40.0-1) | 1.40.0-6+b1
libc6 (>= 2.3.6-6~) | 2.10.2-6
libcairo2 (>= 1.2.4) | 1.8.10-3
libcairomm-1.0-1 (>= 1.6.4) | 1.8.0-1
libcwidget3 | 0.5.16-3
libept0 (>= 0.5.30) | 0.5.30
libfontconfig1 (>= 2.8.0) | 2.8.0-2
libfreetype6 (>= 2.2.1) | 2.3.11-1
libgcc1 (>= 1:4.1.1) | 1:4.4.3-5
libglade2-0 (>= 1:2.6.1) | 1:2.6.4-1
libglademm-2.4-1c2a (>= 2.6.0) | 2.6.7-2
libglib2.0-0 (>= 2.12.0) | 2.22.4-1
libglibmm-2.4-1c2a (>= 2.22.0) | 2.22.1-2
libgtk2.0-0 (>= 2.8.0) | 2.18.9-2
libgtkmm-2.4-1c2a (>= 1:2.18.0) | 1:2.18.2-1
liblog4cxx10 | 0.10.0-1.1
libncursesw5 (>= 5.6+20071006-3) | 5.7+20100313-1
libpango1.0-0 (>= 1.14.0) | 1.26.2-2
libpangomm-1.4-1 (>= 2.26.0) | 2.26.0-1
libsigc++-2.0-0c2a (>= 2.0.2) | 2.2.4.2-1
libsqlite3-0 (>= 3.6.22) | 3.6.23-1
libstdc++6 (>= 4.4.0) | 4.4.3-5
libvte9 (>= 1:0.20.4) | 1:0.22.5-3
libxapian15 | 1.0.18-1
libxml2 (>= 2.6.27) | 2.7.7.dfsg-1
zlib1g (>= 1:1.1.4) | 1:1.2.3.4.dfsg-3
Recommends (Version) | Installed
===============================-+-===========
aptitude-doc-en | 0.6.1.5-3
OR aptitude-doc |
sensible-utils | 0.0.2
apt-xapian-index | 0.26
Suggests (Version) | Installed
=======================-+-===========
tasksel | 2.81
debtags | 1.7.9+b2
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Hello,
Thank you for your interest in improving Debian, and sorry to keep the
bug unattended for so long. There's now an effort to review the open
bugs related with aptitude and resume development.
The version against which this bug was reported still used log4cxx,
which was replaced since then (0.6.3-1) precisely because it was
causing many random crashes.
However, the subject (there's no other information in the email other
than the back-traces) seems to indicate that it happens always when
reading the package status file and building the list of packages.
There are many bug reports about crashes in aptitude-gtk, but none of
them relate this particular step of execution either.
It seems to me that these crashes are due to memory corruption or
linker problems of some sort (or even because the package status files
are currupted). For example I got this when searching the web (with
the same error message):
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14001
It's unlikely that 2 years later the submitter can reproduce the bug
or still has the package status files available to reproduce the bug,
that's why I am closing the bug report without waiting any longer.
However, if this particular kind of crash can still be experienced or
you can provide any kind of related information, then by all means
please reopen the bug.
Regards.
--- End Message ---
_______________________________________________
Aptitude-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
