Bug 253924 - Crash on clicking reply on unresponsive inbox
Summary: Crash on clicking reply on unresponsive inbox
Status: RESOLVED DUPLICATE of bug 248835
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: 1.13.5
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-12 08:44 UTC by Con Kolivas
Modified: 2011-02-14 16:13 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Con Kolivas 2010-10-12 08:44:56 UTC
Application: kmail (1.13.5)
KDE Platform Version: 4.4.5 (KDE 4.4.5)
Qt Version: 4.6.3
Operating System: Linux 2.6.36-rc7-ck1 x86_64
Distribution: Debian GNU/Linux testing (squeeze)

-- Information about the crash:
Starting up kmail with imap settings, the "update throbber" never appeared for checking the inbox. Despite numerous times clicking on "check mail" it never appeared. Then I clicked on "reply" while I had "inbox" selected and it crashed.

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
The current source language is "auto; currently asm".
[Current thread is 1 (Thread 0x7f8a2ef23760 (LWP 3822))]

Thread 2 (Thread 0x7f8a09f57710 (LWP 5064)):
#0  0x00007f8a2b9f4113 in *__GI___poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f8a235f62c9 in ?? () from /lib/libglib-2.0.so.0
#2  0x00007f8a235f671c in g_main_context_iteration () from /lib/libglib-2.0.so.0
#3  0x00007f8a2d03c726 in QEventDispatcherGlib::processEvents (this=0x987b10, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:414
#4  0x00007f8a2d0119e2 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#5  0x00007f8a2d011dbc in QEventLoop::exec (this=0x7f8a09f56de0, flags=) at kernel/qeventloop.cpp:201
#6  0x00007f8a2cf2177b in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:487
#7  0x00007f8a2cff2338 in QInotifyFileSystemWatcherEngine::run (this=0x108b720) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f8a2cf23e15 in QThreadPrivate::start (arg=0x108b720) at thread/qthread_unix.cpp:248
#9  0x00007f8a263108ba in start_thread (arg=<value optimized out>) at pthread_create.c:300
#10 0x00007f8a2b9ff02d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f8a2ef23760 (LWP 3822)):
[KCrash Handler]
#5  0x00007f8a2da78d9f in KMCommand::slotStart (this=0xedf9e0) at ../../kmail/kmcommands.cpp:265
#6  0x00007f8a2da71476 in KMCommand::qt_metacall (this=0xedf9e0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff02779d80) at ./kmcommands.moc:92
#7  0x00007f8a2d026306 in QMetaObject::activate (sender=0x983960, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x1209be8) at kernel/qobject.cpp:3295
#8  0x00007f8a2d02d80f in QSingleShotTimer::timerEvent (this=0x983960) at kernel/qtimer.cpp:308
#9  0x00007f8a2d022b63 in QObject::event (this=0x983960, e=0x7fff0277a4e0) at kernel/qobject.cpp:1212
#10 0x00007f8a2c3b332c in QApplicationPrivate::notify_helper (this=0x661a50, receiver=0x983960, e=0x7fff0277a4e0) at kernel/qapplication.cpp:4302
#11 0x00007f8a2c3b980b in QApplication::notify (this=0x7fff0277a950, receiver=0x983960, e=0x7fff0277a4e0) at kernel/qapplication.cpp:4185
#12 0x00007f8a2e94e836 in KApplication::notify (this=0x7fff0277a950, receiver=0x983960, event=0x7fff0277a4e0) at ../../kdeui/kernel/kapplication.cpp:302
#13 0x00007f8a2d0130bc in QCoreApplication::notifyInternal (this=0x7fff0277a950, receiver=0x983960, event=0x7fff0277a4e0) at kernel/qcoreapplication.cpp:726
#14 0x00007f8a2d03fe92 in QCoreApplication::sendEvent (this=0x6653a0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#15 QTimerInfoList::activateTimers (this=0x6653a0) at kernel/qeventdispatcher_unix.cpp:603
#16 0x00007f8a2d03c9e4 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#17 0x00007f8a235f26f2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#18 0x00007f8a235f6568 in ?? () from /lib/libglib-2.0.so.0
#19 0x00007f8a235f671c in g_main_context_iteration () from /lib/libglib-2.0.so.0
#20 0x00007f8a2d03c6d3 in QEventDispatcherGlib::processEvents (this=0x60c840, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#21 0x00007f8a2c46318e in QGuiEventDispatcherGlib::processEvents (this=0x276f160, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#22 0x00007f8a2d0119e2 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#23 0x00007f8a2d011dbc in QEventLoop::exec (this=0x7fff0277a780, flags=) at kernel/qeventloop.cpp:201
#24 0x00007f8a2d016a4b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#25 0x0000000000403462 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../kmail/main.cpp:156
The current source language is "auto; currently c".
The current source language is "auto; currently asm".

This bug may be a duplicate of or related to bug 248835.

Possible duplicates by query: bug 253243, bug 252678, bug 252408, bug 252022, bug 249381.

Reported using DrKonqi
Comment 1 Christophe Marin 2011-02-14 16:13:29 UTC

*** This bug has been marked as a duplicate of bug 248835 ***