Bug 325384 - kmail crashes during changing settings
Summary: kmail crashes during changing settings
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.11.2
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2013-09-28 09:47 UTC by arthur
Modified: 2017-01-07 22:17 UTC (History)
1 user (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 arthur 2013-09-28 09:47:18 UTC
Application: kmail (4.11.2)
KDE Platform Version: 4.11.2
Qt Version: 4.8.4
Operating System: Linux 3.11.0-8-generic x86_64
Distribution: Ubuntu Saucy Salamander (development branch)

-- Information about the crash:
Kcontact crashed during changing settings.
It was mentioned that a file was missing.
(did not update today yet)

The crash can be reproduced sometimes.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7d92ae1800 (LWP 2134))]

Thread 6 (Thread 0x7f7d6cfd0700 (LWP 2274)):
#0  0x00007f7d8fe49bbd in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f7d87fb7660 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f7d87f781bc in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f7d87f7862b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f7d87f7879c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f7d91498a76 in QEventDispatcherGlib::processEvents (this=0x7f7d680008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0x00007f7d9146a5ef in QEventLoop::processEvents (this=this@entry=0x7f7d6cfcfd30, flags=...) at kernel/qeventloop.cpp:149
#7  0x00007f7d9146a8e5 in QEventLoop::exec (this=this@entry=0x7f7d6cfcfd30, flags=...) at kernel/qeventloop.cpp:204
#8  0x00007f7d9136988f in QThread::exec (this=this@entry=0x117ebc0) at thread/qthread.cpp:542
#9  0x00007f7d9144bd13 in QInotifyFileSystemWatcherEngine::run (this=0x117ebc0) at io/qfilesystemwatcher_inotify.cpp:265
#10 0x00007f7d9136bf2f in QThreadPrivate::start (arg=0x117ebc0) at thread/qthread_unix.cpp:338
#11 0x00007f7d8d71af6e in start_thread (arg=0x7f7d6cfd0700) at pthread_create.c:311
#12 0x00007f7d8fe57ecd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 5 (Thread 0x7f7d667cd700 (LWP 2295)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007f7d847b183d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x00007f7d847b1879 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x00007f7d8d71af6e in start_thread (arg=0x7f7d667cd700) at pthread_create.c:311
#4  0x00007f7d8fe57ecd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 4 (Thread 0x7f7d2573b700 (LWP 2299)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007f7d844f35ad in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x00007f7d847e1096 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x00007f7d8d71af6e in start_thread (arg=0x7f7d2573b700) at pthread_create.c:311
#4  0x00007f7d8fe57ecd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 3 (Thread 0x7f7d24ae8700 (LWP 2311)):
#0  0x00007f7d87fb80da in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007f7d87fb83b9 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f7d87f77d30 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f7d87f785b3 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f7d87f7879c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f7d91498a76 in QEventDispatcherGlib::processEvents (this=0x7f7d180008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0x00007f7d9146a5ef in QEventLoop::processEvents (this=this@entry=0x7f7d24ae7d70, flags=...) at kernel/qeventloop.cpp:149
#7  0x00007f7d9146a8e5 in QEventLoop::exec (this=this@entry=0x7f7d24ae7d70, flags=...) at kernel/qeventloop.cpp:204
#8  0x00007f7d9136988f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:542
#9  0x00007f7d9136bf2f in QThreadPrivate::start (arg=0x169cd20) at thread/qthread_unix.cpp:338
#10 0x00007f7d8d71af6e in start_thread (arg=0x7f7d24ae8700) at pthread_create.c:311
#11 0x00007f7d8fe57ecd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 2 (Thread 0x7f7d1d532700 (LWP 2398)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007f7d7ba1906b in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x00007f7d7ba190a9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x00007f7d8d71af6e in start_thread (arg=0x7f7d1d532700) at pthread_create.c:311
#4  0x00007f7d8fe57ecd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 1 (Thread 0x7f7d92ae1800 (LWP 2134)):
[KCrash Handler]
#6  0x00007f7d8bcc858f in MessageList::Core::Manager::defaultAggregation (this=0x0) at ../../messagelist/core/manager.cpp:217
#7  0x00007f7d8bd09663 in MessageList::Utils::AggregationComboBox::selectDefault (this=0x226f2a0) at ../../messagelist/utils/aggregationcombobox.cpp:102
#8  0x00007f7d9187a054 in slotSelectDefaultAggregation (this=0x226d860) at ../../kmail/configuredialog/configuredialog.cpp:1447
#9  AppearancePageHeadersTab::doLoadFromGlobalSettings (this=0x226d860) at ../../kmail/configuredialog/configuredialog.cpp:1491
#10 0x00007f7d9189cfb1 in load (this=0x226d860) at ../../kmail/configuredialog/configuredialog_p.cpp:95
#11 ConfigModuleWithTabs::load (this=0x20e6500) at ../../kmail/configuredialog/configuredialog_p.cpp:66
#12 0x00007f7d9258e9c9 in KCModule::qt_static_metacall (_o=<optimized out>, _id=<optimized out>, _a=<optimized out>, _c=<optimized out>) at ./kcmodule.moc:66
#13 0x00007f7d91483dce in QObject::event (this=this@entry=0x20e6500, e=e@entry=0x15cea40) at kernel/qobject.cpp:1194
#14 0x00007f7d9085836b in QWidget::event (this=0x20e6500, event=0x15cea40) at kernel/qwidget.cpp:8845
#15 0x00007f7d90808dfc in QApplicationPrivate::notify_helper (this=this@entry=0xc8d060, receiver=receiver@entry=0x20e6500, e=e@entry=0x15cea40) at kernel/qapplication.cpp:4567
#16 0x00007f7d9080f470 in QApplication::notify (this=this@entry=0x7fff4e5c9300, receiver=receiver@entry=0x20e6500, e=e@entry=0x15cea40) at kernel/qapplication.cpp:4353
#17 0x00007f7d92501a9a in KApplication::notify (this=0x7fff4e5c9300, receiver=0x20e6500, event=0x15cea40) at ../../kdeui/kernel/kapplication.cpp:311
#18 0x00007f7d9146b8bd in QCoreApplication::notifyInternal (this=0x7fff4e5c9300, receiver=receiver@entry=0x20e6500, event=event@entry=0x15cea40) at kernel/qcoreapplication.cpp:946
#19 0x00007f7d9146ee1f in sendEvent (event=0x15cea40, receiver=0x20e6500) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#20 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0xc23220) at kernel/qcoreapplication.cpp:1570
#21 0x00007f7d9146f2c3 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1463
#22 0x00007f7d91499073 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#23 postEventSourceDispatch (s=0xc9b320) at kernel/qeventdispatcher_glib.cpp:279
#24 0x00007f7d87f783a6 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x00007f7d87f786f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x00007f7d87f7879c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x00007f7d91498a55 in QEventDispatcherGlib::processEvents (this=0xc24b00, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#28 0x00007f7d908aa9d6 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#29 0x00007f7d9146a5ef in QEventLoop::processEvents (this=this@entry=0x7fff4e5c8f50, flags=...) at kernel/qeventloop.cpp:149
#30 0x00007f7d9146a8e5 in QEventLoop::exec (this=this@entry=0x7fff4e5c8f50, flags=...) at kernel/qeventloop.cpp:204
#31 0x00007f7d9146fe5b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1218
#32 0x00007f7d9080734c in QApplication::exec () at kernel/qapplication.cpp:3828
#33 0x0000000000402d3a in main (argc=<optimized out>, argv=<optimized out>) at ../../kmail/main.cpp:146

Reported using DrKonqi
Comment 1 Laurent Montel 2013-09-28 10:17:28 UTC
Do you have kmail plugins activate or not in your kontact ?
I need to know why it crashs.
Comment 2 arthur 2013-09-28 11:33:39 UTC
Laurent,

As far as I know, only Agenda has plugins. None is used.

If you considder email, adresses, agenda, feeds, notes, pop-up notes, special 
dates, to do, journal as ... plugins.... then all of them are marked.

>settings>configurekmail>pencil>sjablone>   I have changed chablones already 
twice... does not seem to stick (executed update/upgrade)

>settings>configure>various>Proxy		it is mentioned: could not find plugin 
"proxy" for programme "Kontact". Library "kcm_kio" not found.

I hope this helps.

Arthur


Op zaterdag 28 september 2013 10:17:28 schreef u:
> https://bugs.kde.org/show_bug.cgi?id=325384
> 
> Laurent Montel <montel@kde.org> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
> CC|                            |montel@kde.org
> 
> --- Comment #1 from Laurent Montel <montel@kde.org> ---
> Do you have kmail plugins activate or not in your kontact ?
> I need to know why it crashs.
Comment 3 Laurent Montel 2013-09-28 13:36:32 UTC
Ok will investigate it soon.
Comment 4 Denis Kurz 2016-09-24 17:57:56 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 5 Denis Kurz 2017-01-07 22:17:40 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.