Bug 173086 - cntr+l leads occasionally to crashes
Summary: cntr+l leads occasionally to crashes
Status: RESOLVED DUPLICATE of bug 171491
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-18 12:26 UTC by anil
Modified: 2009-03-19 00:34 UTC (History)
2 users (show)

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

Attachments
This is the Crash report generated by KPIM itself. (2.07 KB, application/octet-stream)
2008-10-18 12:28 UTC, anil 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description anil 2008-10-18 12:26:16 UTC 
Version:            (using KDE 3.5.9)
OS:                Linux
Installed from:    Ubuntu Packages

[Thread debugging using libthread_db enabled]
[New Thread 0xb5e89920 (LWP 6023)]
[New Thread 0xb3667b90 (LWP 6051)]
[New Thread 0xb3e68b90 (LWP 6050)]
[New Thread 0xb4669b90 (LWP 6049)]
[New Thread 0xb4e6ab90 (LWP 6048)]
[KCrash handler]
#6  KMHeaders::selectedSernums (this=0x83876e8)
    at /build/buildd/kdepim-3.5.9/./kmail/kmheaders.cpp:3508
#7  0xb52bb740 in KMMainWidget::updateMessageActions (this=0x8386120)
    at /build/buildd/kdepim-3.5.9/./kmail/kmmainwidget.cpp:3294
#8  0xb52cb21e in KMMainWidget::qt_invoke (this=0x8386120, _id=62, 
    _o=0xbffc6f38) at ./kmmainwidget.moc:505
#9  0xb6744704 in QObject::activate_signal (this=0x84546b8, clist=0x8454778, 
    o=0xbffc6f38) at kernel/qobject.cpp:2359
#10 0xb67451e9 in QObject::activate_signal (this=0x84546b8, signal=2)
    at kernel/qobject.cpp:2328
#11 0xb6ad6320 in QTimer::timeout (this=0x84546b8)
    at .moc/debug-shared-mt/moc_qtimer.cpp:82
#12 0xb676bd0e in QTimer::event (this=0x84546b8, e=0xbffc7238)
    at kernel/qtimer.cpp:222
#13 0xb66d8c36 in QApplication::internalNotify (this=0xbffc754c, 
    receiver=0x84546b8, e=0xbffc7238) at kernel/qapplication.cpp:2638
#14 0xb66daa5f in QApplication::notify (this=0xbffc754c, receiver=0x84546b8, 
    e=0xbffc7238) at kernel/qapplication.cpp:2361
#15 0xb6e99672 in KApplication::notify (this=0xbffc754c, receiver=0x84546b8, 
    event=0xbffc7238)
    at /build/buildd/kdelibs-3.5.9/./kdecore/kapplication.cpp:550
#16 0xb666928d in QApplication::sendEvent (receiver=0x84546b8, 
    event=0xbffc7238) at ../include/qapplication.h:523
#17 0xb66cbb19 in QEventLoop::activateTimers (this=0x80af3f0)
    at kernel/qeventloop_unix.cpp:559
#18 0xb667e64b in QEventLoop::processEvents (this=0x80af3f0, flags=4)
    at kernel/qeventloop_x11.cpp:392
#19 0xb66f3f90 in QEventLoop::enterLoop (this=0x80af3f0)
    at kernel/qeventloop.cpp:201
#20 0xb66f3c8e in QEventLoop::exec (this=0x80af3f0)
    at kernel/qeventloop.cpp:148
#21 0xb66da7df in QApplication::exec (this=0xbffc754c)
    at kernel/qapplication.cpp:2761
#22 0x0805c113 in main (argc=)
    at /build/buildd/kdepim-3.5.9/./kontact/src/main.cpp:163
Comment 1 anil 2008-10-18 12:28:42 UTC 
Created attachment 27992 [details]
This is the Crash report generated by KPIM itself.  

This is the Crash report generated by KPIM itself.
Comment 2 George Goldberg 2008-10-18 17:15:20 UTC 
Anil, thanks for filing this report. It would be very helpful if you could answer the following questions to help us try and fix the issue:
 - Approximately how often does this crash happen?
 - Does it happen only in certain circumstances, eg when you are composing a new mail?
 - Can you cause this crash to happen whenever you want by doing certain things? If so, please give us instructions so we can reproduce it too.
Comment 3 Oliver Putz 2008-10-19 20:27:43 UTC 
Same backtrace as in bug #171491. Duplicates?
Comment 4 George Goldberg 2008-10-22 12:00:52 UTC 

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