Your message dated Tue, 25 Apr 2006 17:51:59 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#266652: Reproducable?
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: kmail
Version: 4:3.2.92+3.3.0rc1-1
Severity: normal
This crash occured while simply reading mail -- something that has been
just fine at all other times. I got a SIGILL, and the kde crash handler
saved this info:
Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 1110390624 (LWP 22812)]
[KCrash handler]
#3 0x08082028 in ?? ()
#4 0x4022a517 in KMFolder::countUnread () from /usr/lib/libkmailprivate.so.0
#5 0x40261feb in KMSystemTray::updateNewMessages ()
from /usr/lib/libkmailprivate.so.0
#6 0x40262695 in KMSystemTray::qt_invoke ()
from /usr/lib/libkmailprivate.so.0
#7 0x40b7150c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#8 0x40b71334 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#9 0x40eb125b in QTimer::timeout () from /usr/lib/libqt-mt.so.3
#10 0x40b92d22 in QTimer::event () from /usr/lib/libqt-mt.so.3
#11 0x40b14bcf in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#12 0x40b141ce in QApplication::notify () from /usr/lib/libqt-mt.so.3
#13 0x40741f13 in KApplication::notify () from /usr/lib/libkdecore.so.4
#14 0x40b04405 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#15 0x40abdc4b in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#16 0x40b26f28 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#17 0x40b26dd8 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#18 0x40b14e21 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#19 0x0804a0b4 in ?? ()
#20 0xbffff980 in ?? ()
#21 0xbffff890 in ?? ()
#22 0x00000000 in ?? ()
#23 0x00000000 in ?? ()
#24 0x40fb7600 in vtable for QGArray () from /usr/lib/libqt-mt.so.3
#25 0x081a1800 in ?? ()
#26 0x400076fb in _dl_unload_cache () from /lib/ld-linux.so.2
#27 0x405737f8 in __libc_start_main () from /lib/tls/libc.so.6
#28 0x40695edc in ?? () from /lib/tls/libc.so.6
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.7
Locale: LANG=C, LC_CTYPE=en_US
Versions of packages kmail depends on:
ii kdebase-kio-plugins 4:3.3.0-1 KDE I/O Slaves
ii kdelibs4 4:3.3.0-1 KDE core libraries
ii libc6 2.3.2.ds1-16 GNU C Library: Shared libraries an
ii libgcc1 1:3.4.1-5 GCC support library
ii libice6 4.3.0.dfsg.1-6 Inter-Client Exchange library
ii libkcal2 4:3.2.92+3.3.0rc1-1 KDE calendaring library
ii libkdenetwork2 4:3.2.92+3.3.0rc1-1 KDE Network library
ii libkdepim1 4:3.2.92+3.3.0rc1-1 KDE PIM library
ii libkleopatra0 4:3.2.92+3.3.0rc1-1 KDE GnuPG interface libraries
ii libkpimidentities1 4:3.2.92+3.3.0rc1-1 KDE PIM user identity information
ii libksieve0 4:3.2.92+3.3.0rc1-1 KDE mail/news message filtering li
ii libmimelib1 4:3.2.92+3.3.0rc1-1 KDE mime library
ii libpng12-0 1.2.5.0-7 PNG library - runtime
ii libqt3c102-mt 3:3.3.3-3 Qt GUI Library (Threaded runtime v
ii libsm6 4.3.0.dfsg.1-6 X Window System Session Management
ii libstdc++5 1:3.3.4-9 The GNU Standard C++ Library v3
ii libx11-6 4.3.0.dfsg.1-6 X Window System protocol client li
ii libxext6 4.3.0.dfsg.1-6 X Window System miscellaneous exte
ii perl 5.8.4-2 Larry Wall's Practical Extraction
ii xlibs 4.3.0.dfsg.1-6 X Window System client libraries m
ii zlib1g 1:1.2.1.1-5 compression library - runtime
-- no debconf information
--- End Message ---
--- Begin Message ---
John Goerzen a écrit :
On Tue, Apr 25, 2006 at 12:49:23PM -0400, Filipus Klutiero wrote:
OK, thanks. Then, it looks like it would be useful if you could test
kmail again trying to empirically see if this is fixed. Otherwise, as
nobody else mentioned experiencing this bug and it is only reported
against an RC, it seems more optimal to close this than to investigate a
backtrace from old code.
That makes sense to me.
-- John
I understand that you meant that you don't intend to test kmail, and
that it is more optimal to close this bug, so I'm closing as unreproducible.
--- End Message ---
