Bug 268477 - Kmail crash when adding account
Summary: Kmail crash when adding account
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: 1.13.5
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 270445 273543 277708 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-03-14 16:18 UTC by Michele Gastaldo
Modified: 2012-08-19 10:55 UTC (History)
4 users (show)

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 Michele Gastaldo 2011-03-14 16:18:52 UTC
Application: kmail (1.13.5)
KDE Platform Version: 4.6.1 (4.6.1)
Qt Version: 4.7.0
Operating System: Linux 2.6.35-27-generic i686
Distribution: Ubuntu 10.10

-- Information about the crash:
I started KMail and followed the wizard to add  a new account (Disconnected IMAP). After hitting the "Finish" button, KMail seemed to crash.
I then opened it again, the SMTP server was configured but not the IMAP. I deleted the former in order to start the wizard again. At some point (can't remember if when hitting "Finish" or right before) KMail crashed.

The crash can be reproduced some of the time.

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

Thread 2 (Thread 0xb252ab70 (LWP 2051)):
#0  0x00d953eb in pthread_mutex_lock () from /lib/libpthread.so.0
#1  0x03668f66 in pthread_mutex_lock () from /lib/libc.so.6
#2  0x092e6b68 in g_main_context_check () from /lib/libglib-2.0.so.0
#3  0x092e745e in ?? () from /lib/libglib-2.0.so.0
#4  0x092e7848 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#5  0x069d659f in QEventDispatcherGlib::processEvents (this=0x98fca48, flags=...) at kernel/qeventdispatcher_glib.cpp:417
#6  0x069a6609 in QEventLoop::processEvents (this=0xb252a220, flags=) at kernel/qeventloop.cpp:149
#7  0x069a6a8a in QEventLoop::exec (this=0xb252a220, flags=...) at kernel/qeventloop.cpp:201
#8  0x068a2b7e in QThread::exec (this=0x9995d60) at thread/qthread.cpp:490
#9  0x0698535b in QInotifyFileSystemWatcherEngine::run (this=0x9995d60) at io/qfilesystemwatcher_inotify.cpp:248
#10 0x068a5df9 in QThreadPrivate::start (arg=0x9995d60) at thread/qthread_unix.cpp:266
#11 0x00d92cc9 in start_thread () from /lib/libpthread.so.0
#12 0x0365b69e in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb7878780 (LWP 2046)):
[KCrash Handler]
#7  QMetaObject::changeGuard (ptr=0x9c7f1b8, o=0x0) at kernel/qobject.cpp:470
#8  0x02bffa77 in operator= (this=0x9c7f018, action=0x9c0a950, action_e=QAction::Trigger, self=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qpointer.h:68
#9  QMenuPrivate::activateAction (this=0x9c7f018, action=0x9c0a950, action_e=QAction::Trigger, self=<value optimized out>) at widgets/qmenu.cpp:1098
#10 0x02c005e0 in QMenu::mouseReleaseEvent (this=0x9c7dc38, e=0xbfeed940) at widgets/qmenu.cpp:2301
#11 0x005f2965 in KMenu::mouseReleaseEvent (this=0x9c7dc38, e=0xbfeed940) at ../../kdeui/widgets/kmenu.cpp:458
#12 0x02791e08 in QWidget::event (this=0x9c7dc38, event=0xbfeed940) at kernel/qwidget.cpp:8187
#13 0x02c0202f in QMenu::event (this=0x9c7dc38, e=0xbfeed940) at widgets/qmenu.cpp:2410
#14 0x02733fdc in QApplicationPrivate::notify_helper (this=0x97d2ab8, receiver=0x9c7dc38, e=0xbfeed940) at kernel/qapplication.cpp:4396
#15 0x0273ac2e in QApplication::notify (this=0xbfeee2a0, receiver=0x9c7dc38, e=0xbfeed940) at kernel/qapplication.cpp:3959
#16 0x005017da in KApplication::notify (this=0xbfeee2a0, receiver=0x9c7dc38, event=0xbfeed940) at ../../kdeui/kernel/kapplication.cpp:311
#17 0x069a7b3b in QCoreApplication::notifyInternal (this=0xbfeee2a0, receiver=0x9c7dc38, event=0xbfeed940) at kernel/qcoreapplication.cpp:732
#18 0x02739094 in sendEvent (receiver=0x9c7dc38, event=0xbfeed940, alienWidget=0x0, nativeWidget=0x9c7dc38, buttonDown=0x30ce3c0, lastMouseReceiver=..., spontaneous=true) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#19 QApplicationPrivate::sendMouseEvent (receiver=0x9c7dc38, event=0xbfeed940, alienWidget=0x0, nativeWidget=0x9c7dc38, buttonDown=0x30ce3c0, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3058
#20 0x027c8261 in QETWidget::translateMouseEvent (this=0x9c7dc38, event=0xbfeede5c) at kernel/qapplication_x11.cpp:4337
#21 0x027c7151 in QApplication::x11ProcessEvent (this=0xbfeee2a0, event=0xbfeede5c) at kernel/qapplication_x11.cpp:3414
#22 0x027f636a in x11EventSourceDispatch (s=0x97d06d0, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#23 0x092e3855 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#24 0x092e7668 in ?? () from /lib/libglib-2.0.so.0
#25 0x092e7848 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#26 0x069d6565 in QEventDispatcherGlib::processEvents (this=0x9791af8, flags=...) at kernel/qeventdispatcher_glib.cpp:415
#27 0x027f5be5 in QGuiEventDispatcherGlib::processEvents (this=0x9791af8, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#28 0x069a6609 in QEventLoop::processEvents (this=0xbfeee154, flags=) at kernel/qeventloop.cpp:149
#29 0x069a6a8a in QEventLoop::exec (this=0xbfeee154, flags=...) at kernel/qeventloop.cpp:201
#30 0x069ab00f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#31 0x02732e07 in QApplication::exec () at kernel/qapplication.cpp:3672
#32 0x0804a88e in main (argc=3, argv=0xbfeee464) at ../../kmail/main.cpp:156

Possible duplicates by query: bug 205625.

Reported using DrKonqi
Comment 1 Christophe Marin 2011-04-08 16:52:28 UTC
from bug 270445

-- Information about the crash:
I opened libre office and saw the stamp button, so I tried it and it brought up
th eunconfigured kmail dialog.  I left it running.

I then started kmail by itself from the desktop, which was unconfigured, and
CRASH.

I had just done a fresh install of SUSE 11.4 in a virtual machine running under
Fedora to test it out.  The disc came from Linux Format issue 144.

I am an experienced user, there was nothing wrong with my virtual machine and
it hadd plenty of resources.
Comment 2 Christophe Marin 2011-04-08 16:52:35 UTC
*** Bug 270445 has been marked as a duplicate of this bug. ***
Comment 3 Christophe Marin 2011-05-18 12:31:25 UTC
*** Bug 273543 has been marked as a duplicate of this bug. ***
Comment 4 Christophe Marin 2011-07-13 17:18:07 UTC
*** Bug 277708 has been marked as a duplicate of this bug. ***
Comment 5 Myriam Schweingruber 2012-08-19 10:55:58 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