[Bug 322412] Re: Kmail crashes with segfault in KMail::ActionScheduler::fetchTimeOut

Bug Watch Updater 322412 at bugs.launchpad.net
Wed Aug 22 15:31:00 UTC 2012


Launchpad has imported 16 comments from the remote bug at
https://bugs.kde.org/show_bug.cgi?id=155026.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2008-01-03T16:02:08+00:00 Kodefoo wrote:

Version:           1.9.6 (using KDE KDE 3.5.8)
Installed from:    Ubuntu Packages
OS:                Linux

I had set up some new filters to move mail around within Kontact/Kmail.
I selected several larger emails from my inbox and ran the filters
manually.  One of the emails was taking a long time to download so I
cancelled the job.  Nothing seemed to happen for ten or fifteen seconds.
I was able to click on other folders and bring up messages.  Then the
entire app crashed.  I have been able to repeat this multiple times.

Backtrace:
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47399937843856 (LWP 14137)]
[New Thread 1107310928 (LWP 14141)]
[New Thread 1098918224 (LWP 14140)]
[New Thread 1090525520 (LWP 14139)]
[New Thread 1082132816 (LWP 14138)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#5  0x00002b1c242ce599 in QMetaObject::findSignal ()
   from /usr/lib/libqt-mt.so.3
#6  0x00002b1c242de6d5 in QObject::disconnect () from /usr/lib/libqt-mt.so.3
#7  0x00002b1c2e6ed2a1 in KMail::ActionScheduler::fetchTimeOut ()
   from /usr/lib/libkmailprivate.so
#8  0x00002b1c2e6f0a6d in KMail::ActionScheduler::qt_invoke ()
   from /usr/lib/libkmailprivate.so
#9  0x00002b1c242dcd76 in QObject::activate_signal ()
   from /usr/lib/libqt-mt.so.3
#10 0x00002b1c242dd910 in QObject::activate_signal ()
   from /usr/lib/libqt-mt.so.3
#11 0x00002b1c2464c9a2 in QTimer::timeout () from /usr/lib/libqt-mt.so.3
#12 0x00002b1c24303257 in QTimer::event () from /usr/lib/libqt-mt.so.3
#13 0x00002b1c242782a2 in QApplication::internalNotify ()
   from /usr/lib/libqt-mt.so.3
#14 0x00002b1c2427a031 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#15 0x00002b1c22f00248 in KApplication::notify ()
   from /usr/lib/libkdecore.so.4
#16 0x00002b1c2420ad12 in QApplication::sendEvent ()
   from /usr/lib/libqt-mt.so.3
#17 0x00002b1c2426b55c in QEventLoop::activateTimers ()
   from /usr/lib/libqt-mt.so.3
#18 0x00002b1c2421f443 in QEventLoop::processEvents ()
   from /usr/lib/libqt-mt.so.3
#19 0x00002b1c242917e7 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#20 0x00002b1c242915ef in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#21 0x00002b1c24279d68 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#22 0x0000000000419122 in ?? ()
#23 0x00002b1c27bdfb44 in __libc_start_main () from /lib/libc.so.6
#24 0x0000000000418939 in ?? ()
#25 0x00007fff8c1edcc8 in ?? ()
#26 0x0000000000000000 in ?? ()

Reply at: https://bugs.launchpad.net/kdepim/+bug/322412/comments/0

------------------------------------------------------------------------
On 2008-01-05T22:20:10+00:00 Mcguire-c wrote:

Please provide a backtrace, see
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Reply at: https://bugs.launchpad.net/kdepim/+bug/322412/comments/1

------------------------------------------------------------------------
On 2008-02-05T15:04:23+00:00 Mcguire-c wrote:

*** Bug 157091 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/kdepim/+bug/322412/comments/2

------------------------------------------------------------------------
On 2008-11-19T12:37:00+00:00 Cgiboudeaux wrote:

Closing due to lack of feedback (comment #1)

Reply at: https://bugs.launchpad.net/kdepim/+bug/322412/comments/3

------------------------------------------------------------------------
On 2008-11-26T13:01:02+00:00 Jtamate wrote:

Posibly has a dup in bug 175943

Reply at: https://bugs.launchpad.net/kdepim/+bug/322412/comments/4

------------------------------------------------------------------------
On 2008-11-27T17:41:33+00:00 Mcguire-c wrote:

*** Bug 175943 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/kdepim/+bug/322412/comments/5

------------------------------------------------------------------------
On 2008-11-27T17:43:12+00:00 Mcguire-c wrote:

Reopening because of the duplicate.


Reply at: https://bugs.launchpad.net/kdepim/+bug/322412/comments/6

------------------------------------------------------------------------
On 2008-12-04T12:41:48+00:00 Jtamate wrote:

*** Bug 176839 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/kdepim/+bug/322412/comments/7

------------------------------------------------------------------------
On 2008-12-14T19:14:46+00:00 Dario Andres wrote:

*** Bug 177727 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/kdepim/+bug/322412/comments/8

------------------------------------------------------------------------
On 2009-01-21T01:21:34+00:00 Dario Andres wrote:

Isn't this related to bug 136437 ?

Reply at: https://bugs.launchpad.net/kdepim/+bug/322412/comments/9

------------------------------------------------------------------------
On 2009-01-21T01:22:41+00:00 Dario Andres wrote:

*** Bug 181432 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/kdepim/+bug/322412/comments/10

------------------------------------------------------------------------
On 2009-03-15T10:35:33+00:00 Jtamate wrote:

It does not crash for me in kde 4.2.65 >= 20090226 (opensuse factory
builds) filtering >140 spam messages manually (first using a dimap
account and then an imap account).

Reply at: https://bugs.launchpad.net/kdepim/+bug/322412/comments/13

------------------------------------------------------------------------
On 2009-05-29T20:03:18+00:00 Dario Andres wrote:

*** Bug 136437 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/kdepim/+bug/322412/comments/14

------------------------------------------------------------------------
On 2010-01-14T01:58:38+00:00 Björn Ruberg wrote:

Can anybody report about the situation in KDE 4.3?

Reply at: https://bugs.launchpad.net/kdepim/+bug/322412/comments/15

------------------------------------------------------------------------
On 2010-04-25T03:28:36+00:00 Bruce Cran wrote:

I've seen regular crashes when closing KMail as an IMAP operation is
going on with KDE 4.4.1. gdb ends up crashing though so I've not got a
backtrace yet.

Reply at: https://bugs.launchpad.net/kdepim/+bug/322412/comments/16

------------------------------------------------------------------------
On 2012-08-19T11:07:39+00:00 Myriam Schweingruber wrote:

Thank you for your report. Kmail1 is currently unmaintained and the code
has changed sufficiently in Kmail2 so the backtraces are not really
useful anymore. Should you experience the same crash in Kmail 4.8.5 or
later, please open a new report for Kmail2. Thank you for your
understanding

Reply at: https://bugs.launchpad.net/kdepim/+bug/322412/comments/18


** Changed in: kdepim
       Status: New => Unknown

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdepim in Ubuntu.
https://bugs.launchpad.net/bugs/322412

Title:
  Kmail crashes with segfault in KMail::ActionScheduler::fetchTimeOut

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdepim/+bug/322412/+subscriptions




More information about the kubuntu-bugs mailing list