Bug 286957 - Crash during start up
Summary: Crash during start up
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.13.7
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-18 20:46 UTC by Christopher Heiny
Modified: 2012-08-19 10:55 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 Christopher Heiny 2011-11-18 20:46:29 UTC
Application: kmail (1.13.7)
KDE Platform Version: 4.6.5 (4.6.5)
Qt Version: 4.7.3
Operating System: Linux 2.6.35.13-92.fc14.x86_64 x86_64
Distribution: "Fedora release 14 (Laughlin)"

-- Information about the crash:
Running konsole over X11.  Started did kmail &, then continued typing in another konsole tab.  While typing in that tab, kmail came up with "starting PIM" (or whatever, the usual grey screen thing), stole the focus and some keystrokes, and barfed.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
82	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[KCrash Handler]
#6  0x00000034ba13a313 in KMCommand::slotStart (this=0x2bce080) at /usr/src/debug/kdepim-4.4.11.1/kmail/kmcommands.cpp:266
#7  0x00000034ba145286 in KMCommand::qt_metacall (this=0x2bce080, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x2bed590) at /usr/src/debug/kdepim-4.4.11.1/x86_64-redhat-linux-gnu/kmail/kmcommands.moc:92
#8  0x00000034a55715ca in QObject::event (this=0x2bce080, e=<value optimized out>) at kernel/qobject.cpp:1217
#9  0x00000034a9bb7d24 in QApplicationPrivate::notify_helper (this=0x1e1e3c0, receiver=0x2bce080, e=0x2bc13c0) at kernel/qapplication.cpp:4462
#10 0x00000034a9bbc8da in QApplication::notify (this=<value optimized out>, receiver=0x2bce080, e=0x2bc13c0) at kernel/qapplication.cpp:4341
#11 0x00000034ab640f46 in KApplication::notify (this=0x7fff5f374190, receiver=0x2bce080, event=0x2bc13c0) at /usr/src/debug/kdelibs-4.6.5/kdeui/kernel/kapplication.cpp:311
#12 0x00000034a555d19c in QCoreApplication::notifyInternal (this=0x7fff5f374190, receiver=0x2bce080, event=0x2bc13c0) at kernel/qcoreapplication.cpp:731
#13 0x00000034a5560985 in sendEvent (receiver=0x0, event_type=0, data=0x1dad540) at kernel/qcoreapplication.h:215
#14 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x1dad540) at kernel/qcoreapplication.cpp:1372
#15 0x00000034a55881b3 in sendPostedEvents (s=0x1e08ab0) at kernel/qcoreapplication.h:220
#16 postEventSourceDispatch (s=0x1e08ab0) at kernel/qeventdispatcher_glib.cpp:277
#17 0x0000003271841e33 in g_main_dispatch (context=0x1de5f00) at gmain.c:2149
#18 g_main_context_dispatch (context=0x1de5f00) at gmain.c:2702
#19 0x0000003271842610 in g_main_context_iterate (context=0x1de5f00, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2780
#20 0x00000032718428ad in g_main_context_iteration (context=0x1de5f00, may_block=1) at gmain.c:2843
#21 0x00000034a558834f in QEventDispatcherGlib::processEvents (this=0x1dacd50, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#22 0x00000034a9c5d3ae in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:207
#23 0x00000034a555c532 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#24 0x00000034a555c77c in QEventLoop::exec (this=0x7fff5f373fc0, flags=...) at kernel/qeventloop.cpp:201
#25 0x00000034a5560c3b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008
#26 0x000000000040322b in main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdepim-4.4.11.1/kmail/main.cpp:158

Possible duplicates by query: bug 286508, bug 286471, bug 283645, bug 283069, bug 282087.

Reported using DrKonqi
Comment 1 Myriam Schweingruber 2012-08-19 10:55:14 UTC
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