Bug#326592: marked as done (crash when cancelling GPG query after selecting different folder)
Your message dated Thu, 18 Jan 2018 16:01:58 +0100
with message-id
and subject line Re: crash when cancelling GPG query after selecting different folder
has caused the Debian Bug report #326592,
regarding crash when cancelling GPG query after selecting different folder
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 owner@bugs.debian.org
immediately.)
--
326592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=326592
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: kmail
Version: 3.3.2-3
When I click on an encrypted message, I get a popup asking for my passphrase.
If I don't answer this popup but instead click a different folder, the popup
window (ok, this part probably depends on the windowmanager) is put behind
the main kmail window, but still open. First problem here: either the popup
is modal, i.e. blocking access to the main window or it automatically closes
when a different folder is selected (and therefore it loses its context) - at
least that's what I'd expect. Anyhow, apart from being confusing/annoying,
nothing really bad happens because of this popup.
The really bad thing happens when you now close this window, either by
providing the passphrase or pressing cancel - kmail simply crashes, see
attached backtrace. This behaviour is reproducable and I'm not aware of any
other workaround.
cheers and thanks
Uli
(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
...
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1244895552 (LWP 860)]
(no debugging symbols found)
...
(no debugging symbols found)
[KCrash handler]
#3 0xb7ea24a3 in KMail::ObjectTreeParser::parseObjectTree ()
from /usr/lib/libkmailprivate.so.0
#4 0xb7db2c39 in KMReaderWin::parseMsg () from /usr/lib/libkmailprivate.so.0
#5 0xb7db25b3 in KMReaderWin::displayMessage ()
from /usr/lib/libkmailprivate.so.0
#6 0xb7db2169 in KMReaderWin::updateReaderWin ()
from /usr/lib/libkmailprivate.so.0
#7 0xb7db92da in KMReaderWin::qt_invoke () from /usr/lib/libkmailprivate.so.0
#8 0xb72b771c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#9 0xb72b7544 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#10 0xb75f881b in QTimer::timeout () from /usr/lib/libqt-mt.so.3
#11 0xb72d8f72 in QTimer::event () from /usr/lib/libqt-mt.so.3
#12 0xb725ae1f in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#13 0xb725a41e in QApplication::notify () from /usr/lib/libqt-mt.so.3
#14 0xb7809ec3 in KApplication::notify () from /usr/lib/libkdecore.so.4
#15 0xb724a645 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#16 0xb7203cfb in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#17 0xb726d1d8 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#18 0xb726d088 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#19 0xb725b071 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#20 0x0804a0b4 in ?? ()
#21 0xbffff8d0 in ?? ()
#22 0xbffff7e0 in ?? ()
#23 0x00000000 in ?? ()
#24 0x00000000 in ?? ()
#25 0xb76fec40 in vtable for QGArray () from /usr/lib/libqt-mt.so.3
#26 0x080ea398 in ?? ()
#27 0xb7ac2618 in __malloc_initialize_hook () from /lib/tls/libc.so.6
#28 0xb7ac2218 in __malloc_initialize_hook () from /lib/tls/libc.so.6
#29 0xb7fc2770 in vtable for KMKernel () from /usr/lib/libkmailprivate.so.0
#30 0xb79f40a0 in free () from /lib/tls/libc.so.6
#31 0xb79a1ec0 in __libc_start_main () from /lib/tls/libc.so.6
#32 0x08049e11 in ?? ()
--- End Message ---
--- Begin Message ---
Dear bug submitter,
Thank you for reporthing this issue. The bug has been determined not to be
Debian specific, and therefore was reported in the KDE bugtracker; see
https://bugs.kde.org/show_bug.cgi?id=180741.
We are sorry it has not been resolved. However, the version in which the
issue was reported is now obsolete and the upstream tracker has closed the
issue. Thus we are also closing the issue in Debian bug tracker.
If you think the bug is still relevant to a KDE Pim version in Debian stable
(aka Stretch) or newer -- i.e. part of KDE Applications 15.08.0 or newer --
then please open a new bugreport upstream and add your new information in the
upstream bugreport.
Again, thank you for reporting the issue. If there are any questions feel free
to ask.
KDE upstream bug tracker closed their bug with following statement:
"This bug has only been reported for versions before 15.08.0, which have been
unsupported for at least two years now. Can anyone tell if this bug still
present?
If noone confirms this bug for a Framework-based version of kontact
(version 5.0 or later, as part of KDE Applications 15.08 or later),
it gets closed in about three months.
Just as announced in my last comment, I close this bug.
If you encounter it again in a recent version (at least 5.0 aka 15.08),
please open a new one unless it already exists. Thank you for all your input."
--- End Message ---
Reply to: