Bug 247777 - KMail crashes while using the account wizard
Summary: KMail crashes while using the account wizard
Status: RESOLVED FIXED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-13 21:31 UTC by Gregor Petrin
Modified: 2010-12-13 12:21 UTC (History)
1 user (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Gregor Petrin 2010-08-13 21:31:34 UTC 
Application: kmail (1.13.5)
KDE Platform Version: 4.5.00 (KDE 4.5.0)
Qt Version: 4.6.3
Operating System: Linux 2.6.34-12-desktop x86_64
Distribution: "openSUSE 11.3 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:

I started the account wizard and entered my info, credentials and server addresses. Then the wizard said it was checking the capabilities of the server and I got this crash.

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[Current thread is 1 (Thread 0x7fa15727a760 (LWP 9350))]

Thread 3 (Thread 0x7fa138c67710 (LWP 9416)):
#0  0x00007fa152366709 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007fa154736222 in wait (this=<value optimized out>, mutex=0x1204a50, time=30000) at thread/qwaitcondition_unix.cpp:85
#2  QWaitCondition::wait (this=<value optimized out>, mutex=0x1204a50, time=30000) at thread/qwaitcondition_unix.cpp:159
#3  0x00007fa15472c0d0 in QThreadPoolThread::run (this=0x11c3ba0) at concurrent/qthreadpool.cpp:140
#4  0x00007fa154735bf5 in QThreadPrivate::start (arg=0x11c3ba0) at thread/qthread_unix.cpp:248
#5  0x00007fa152361a4f in start_thread () from /lib64/libpthread.so.0
#6  0x00007fa153f0e82d in clone () from /lib64/libc.so.6
#7  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7fa138466710 (LWP 9418)):
#0  0x00007fa152366709 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007fa154736222 in wait (this=<value optimized out>, mutex=0x1204a50, time=30000) at thread/qwaitcondition_unix.cpp:85
#2  QWaitCondition::wait (this=<value optimized out>, mutex=0x1204a50, time=30000) at thread/qwaitcondition_unix.cpp:159
#3  0x00007fa15472c0d0 in QThreadPoolThread::run (this=0xc73170) at concurrent/qthreadpool.cpp:140
#4  0x00007fa154735bf5 in QThreadPrivate::start (arg=0xc73170) at thread/qthread_unix.cpp:248
#5  0x00007fa152361a4f in start_thread () from /lib64/libpthread.so.0
#6  0x00007fa153f0e82d in clone () from /lib64/libc.so.6
#7  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fa15727a760 (LWP 9350)):
[KCrash Handler]
#6  QWidget::ensurePolished (this=0xb46a70) at kernel/qwidget.cpp:9381
#7  0x00007fa154d45181 in QWidget::event (this=0xb46a70, event=0xb5e840) at kernel/qwidget.cpp:8126
#8  0x00007fa155117bcb in QMenu::event (this=0xb46a70, e=0xb5e840) at widgets/qmenu.cpp:2421
#9  0x00007fa154cf44d4 in QApplicationPrivate::notify_helper (this=0x655080, receiver=0xb46a70, e=0xb5e840) at kernel/qapplication.cpp:4302
#10 0x00007fa154cfcaca in QApplication::notify (this=<value optimized out>, receiver=0xb46a70, e=0xb5e840) at kernel/qapplication.cpp:4185
#11 0x00007fa156c170b6 in KApplication::notify (this=0x7fff5260cf60, receiver=0xb46a70, event=0xb5e840) at /usr/src/debug/kdelibs-4.5.0/kdeui/kernel/kapplication.cpp:310
#12 0x00007fa15481ce4c in QCoreApplication::notifyInternal (this=0x7fff5260cf60, receiver=0xb46a70, event=0xb5e840) at kernel/qcoreapplication.cpp:726
#13 0x00007fa1548205ba in sendEvent (receiver=0x0, event_type=0, data=0x60d080) at kernel/qcoreapplication.h:215
#14 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x60d080) at kernel/qcoreapplication.cpp:1367
#15 0x00007fa154845173 in sendPostedEvents (s=<value optimized out>) at kernel/qcoreapplication.h:220
#16 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:276
#17 0x00007fa14bd9ca93 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#18 0x00007fa14bd9d270 in ?? () from /usr/lib64/libglib-2.0.so.0
#19 0x00007fa14bd9d510 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#20 0x00007fa15484567f in QEventDispatcherGlib::processEvents (this=0x612d60, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#21 0x00007fa154d9514e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#22 0x00007fa15481c292 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#23 0x00007fa15481c495 in QEventLoop::exec (this=0x7fff5260cd90, flags=...) at kernel/qeventloop.cpp:201
#24 0x00007fa15482088b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#25 0x00000000004033e8 in _start ()

Possible duplicates by query: bug 234566, bug 230509, bug 225427, bug 217411, bug 216695.

Reported using DrKonqi
Comment 1 Tobias Koenig 2010-12-11 21:34:10 UTC 
Hej Gregor,

is this still reproducable with current SVN version?

Ciao,
Tobias
Comment 2 Gregor Petrin 2010-12-11 22:36:40 UTC 
Hi,

I forgot about this bug report - actually, I think I used the wizard last week when teseting 4.6 beta and it worked. But I will double check it on Monday on my work computer, just to be sure.
Comment 3 Gregor Petrin 2010-12-13 12:21:12 UTC 
Tested, no crash. Seems like the issue was resolved.