Bug 166283 - crash after long idling and connection lost
Summary: crash after long idling and connection lost
Status: RESOLVED DUPLICATE of bug 150667
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-11 10:29 UTC by Juha Tuomala
Modified: 2008-07-11 13:05 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Juha Tuomala 2008-07-11 10:29:44 UTC
Version:            (using KDE 3.5.9)
Installed from:    Fedora RPMs

[Detaching after fork from child process 15349.]
[Detaching after fork from child process 15351.]
[Detaching after fork from child process 15353.]
[Detaching after fork from child process 15355.]
[Detaching after fork from child process 15357.]
[Detaching after fork from child process 15359.]
[Detaching after fork from child process 15361.]
[Detaching after fork from child process 15363.]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 46912496401584 (LWP 25632)]
0x00000034af48f800 in KMail::ImapJob::slotGetNextMessage (this=0x2907030) at imapjob.cpp:277
277       if ( !msgParent || !msg || msg->UID() == 0 )
(gdb) bt
#0  0x00000034af48f800 in KMail::ImapJob::slotGetNextMessage (this=0x2907030) at imapjob.cpp:277
#1  0x00000034af49049d in KMail::ImapJob::init (this=0x2907030, jt=KMail::FolderJob::tGetMessage, sets=@0x7fff10c46e10, folder=0x0, msgList=@0x2907080) at imapjob.cpp:214
#2  0x00000034af4917ba in KMail::ImapJob::execute (this=0x2907030) at imapjob.cpp:675
#3  0x00000034af46cd99 in KMMainWidget::slotMsgActivated (this=0x1b06140, msg=0x2bc9cf0) at kmmainwidget.cpp:2294
#4  0x00000034af47b422 in KMMainWidget::qt_invoke (this=0x1b06140, _id=164, _o=0x7fff10c46fd0) at kmmainwidget.moc:607
#5  0x00000034a7963c29 in QObject::activate_signal (this=0x245f450, clist=<value optimized out>, o=0x7fff10c46fd0) at kernel/qobject.cpp:2359
#6  0x00000034a7964900 in QObject::activate_signal (this=0x2bc9cf0, signal=<value optimized out>) at kernel/qobject.cpp:2328
#7  0x00000034a9ad7181 in KAction::qt_invoke (this=0x245f450, _id=15, _o=0x7fff10c470a0) at kaction.moc:218
#8  0x00000034a7963c29 in QObject::activate_signal (this=0x1b04300, clist=<value optimized out>, o=0x7fff10c470a0) at kernel/qobject.cpp:2359
#9  0x00000034a7964900 in QObject::activate_signal (this=0x2bc9cf0, signal=<value optimized out>) at kernel/qobject.cpp:2328
#10 0x00000034a8f50b85 in KAccelPrivate::emitActivatedSignal (this=0x1b04300, pAction=0x245f980) at kaccel.cpp:400
#11 0x00000034a8fa851a in KAccelPrivate::eventFilter (this=0x1b04300, pEvent=0x7fff10c475a0) at kaccel.cpp:370
#12 0x00000034a79632b2 in QObject::activate_filters (this=0x23630c0, e=0x7fff10c475a0) at kernel/qobject.cpp:906
#13 0x00000034a7963327 in QObject::event (this=0x23630c0, e=0x7fff10c475a0) at kernel/qobject.cpp:738
#14 0x00000034a799a878 in QWidget::event (this=0x2bc9cf0, e=0x34a7cf307b) at kernel/qwidget.cpp:4681
#15 0x00000034a7a59605 in QMainWindow::event (this=0x23630c0, e=0x7fff10c475a0) at widgets/qmainwindow.cpp:1690
#16 0x00000034a7902b75 in QApplication::internalNotify (this=<value optimized out>, receiver=0x23630c0, e=0x7fff10c475a0) at kernel/qapplication.cpp:2638
#17 0x00000034a7904363 in QApplication::notify (this=0x7fff10c47c90, receiver=0x23864c0, e=0x7fff10c475a0) at kernel/qapplication.cpp:2395
#18 0x00000034a8fc7e38 in KApplication::notify (this=0x7fff10c47c90, receiver=0x23864c0, event=0x7fff10c475a0) at kapplication.cpp:550
#19 0x00000034a8f5bf6e in KAccelEventHandler::x11Event (this=<value optimized out>, pEvent=<value optimized out>) at /usr/lib64/qt-3.3/include/qapplication.h:523
#20 0x00000034a8fc6588 in KApplication::x11EventFilter (this=0x7fff10c47c90, _event=0x7fff10c47920) at kapplication.cpp:1659
#21 0x00000034a78906b7 in qt_x11EventFilter (ev=0x7fff10c47920) at kernel/qapplication_x11.cpp:407
#22 0x00000034a78a048e in QApplication::x11ProcessEvent (this=0x7fff10c47c90, event=0x7fff10c47920) at kernel/qapplication_x11.cpp:3382
#23 0x00000034a78b1074 in QEventLoop::processEvents (this=0x6914d0, flags=4) at kernel/qeventloop_x11.cpp:195
#24 0x00000034a791a321 in QEventLoop::enterLoop (this=0x2bc9cf0) at kernel/qeventloop.cpp:201
#25 0x00000034a791a202 in QEventLoop::exec (this=0x2bc9cf0) at kernel/qeventloop.cpp:148
#26 0x0000000000402914 in main (argc=2, argv=<value optimized out>) at main.cpp:110
#27 0x0000003d8721e074 in __libc_start_main (main=0x4027c0 <main>, argc=2, ubp_av=0x7fff10c47f58, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fff10c47f48) at libc-start.c:220
#28 0x0000000000402669 in _start ()
(gdb)                                                                                                  


This had been idling over night, connection
had been lost at some point. Sent one mail
and tried to move message into imap folder.

x86_64 system.
Comment 1 Christophe Marin 2008-07-11 13:05:36 UTC

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