Bug 335871

Summary: Kontact crashes when pressing 'todo list
Product: [Applications] kontact Reporter: NMD <bugsnmd>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: crash CC: a.c.hoerle, kdenis, montel
Priority: NOR Keywords: drkonqi
Version: 4.13   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Bug Report and debug info - another crash pressing 'todo list'
New crash information added by DrKonqi

Description NMD 2014-06-06 09:17:05 UTC
Application: kontact (4.13)
KDE Platform Version: 4.13.0
Qt Version: 4.8.6
Operating System: Linux 3.13.0-24-generic x86_64
Distribution: Ubuntu 14.04 LTS

-- Information about the crash:
Hi,

When I open Kontact and then press the new button (top left hand corner) it crashes immediately. This has happened every time I've tried it.

I also have kmail open in a separate window - this hasn't crashed.

Cheers,
Nick

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fbb29fab800 (LWP 3370))]

Thread 5 (Thread 0x7fbb09b65700 (LWP 3371)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fbb24d4f81d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x00007fbb24d4f859 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x00007fbb21471182 in start_thread (arg=0x7fbb09b65700) at pthread_create.c:312
#4  0x00007fbb2752330d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 4 (Thread 0x7fbac9262700 (LWP 3372)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fbb24a9020d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x00007fbb24d7efd6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x00007fbb21471182 in start_thread (arg=0x7fbac9262700) at pthread_create.c:312
#4  0x00007fbb2752330d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7fbabea67700 (LWP 3376)):
#0  0x00007fbb214747ee in __pthread_mutex_unlock_usercnt (decr=1, mutex=0x7fbab0000a60) at pthread_mutex_unlock.c:57
#1  __GI___pthread_mutex_unlock (mutex=0x7fbab0000a60) at pthread_mutex_unlock.c:310
#2  0x00007fbb20fd39c1 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fbb20f918f9 in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007fbb20f91f52 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007fbb20f920ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007fbb27c9c7be in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7  0x00007fbb27c6e0af in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x00007fbb27c6e3a5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x00007fbb27b6ac5f in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#10 0x00007fbb27b6d32f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#11 0x00007fbb21471182 in start_thread (arg=0x7fbabea67700) at pthread_create.c:312
#12 0x00007fbb2752330d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7fbabd16f700 (LWP 3377)):
#0  __pthread_mutex_unlock_usercnt (decr=1, mutex=0x7fbab4000a60) at pthread_mutex_unlock.c:42
#1  __GI___pthread_mutex_unlock (mutex=0x7fbab4000a60) at pthread_mutex_unlock.c:310
#2  0x00007fbb20fd39c1 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fbb20f91680 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007fbb20f91f03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007fbb20f920ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007fbb27c9c7be in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7  0x00007fbb27c6e0af in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x00007fbb27c6e3a5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x00007fbb27b6ac5f in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#10 0x00007fbb27c4f823 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#11 0x00007fbb27b6d32f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#12 0x00007fbb21471182 in start_thread (arg=0x7fbabd16f700) at pthread_create.c:312
#13 0x00007fbb2752330d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7fbb29fab800 (LWP 3370)):
[KCrash Handler]
#5  0x00007fbb29be8030 in KontactInterface::Plugin::newActions() const () from /usr/lib/libkontactinterface.so.4
#6  0x00007fbb297ad4b1 in Kontact::MainWindow::slotNewClicked() () from /usr/lib/libkontactprivate.so.4
#7  0x00007fbb27c8387a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x00007fbb2865ba62 in QAction::triggered(bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#9  0x00007fbb2865d433 in QAction::activate(QAction::ActionEvent) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#10 0x00007fbb28a14b02 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#11 0x00007fbb28a14c2c in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#12 0x00007fbb28acba4a in QToolButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#13 0x00007fbb286b150a in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#14 0x00007fbb28661e2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#15 0x00007fbb286685dd in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#16 0x00007fbb2936cbaa in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#17 0x00007fbb27c6f4dd in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#18 0x00007fbb28667d93 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#19 0x00007fbb286dc9cb in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#20 0x00007fbb286dc269 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#21 0x00007fbb28703b02 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#22 0x00007fbb20f91e04 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007fbb20f92048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x00007fbb20f920ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x00007fbb27c9c7a1 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#26 0x00007fbb28703bb6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#27 0x00007fbb27c6e0af in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#28 0x00007fbb27c6e3a5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#29 0x00007fbb27c73b79 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#30 0x0000000000403660 in ?? ()
#31 0x00007fbb27449ec5 in __libc_start_main (main=0x402bb0, argc=1, argv=0x7fff4b316918, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff4b316908) at libc-start.c:287
#32 0x0000000000403b28 in _start ()

Possible duplicates by query: bug 328980, bug 300676.

Reported using DrKonqi
Comment 1 Laurent Montel 2014-06-06 10:19:02 UTC
Which "new" element did you try to  create ?
mail ? note ? etc.
see tooltip on this button.
Comment 2 NMD 2014-06-08 16:10:47 UTC
Not sure, it didn't get to the drop down, and in fact just said 'new...'

When I open it now it's looking very different. When I press down to go
to 'Todo lists' it crashes. 'To-do List' doesn't crash (I must have a
couple of programmes or plugins installed that give this
functionality... I don't remember installing them though).


On 06/06/14 11:19, Laurent Montel wrote:
> https://bugs.kde.org/show_bug.cgi?id=335871
>
> Laurent Montel <montel@kde.org> changed:
>
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |montel@kde.org
>
> --- Comment #1 from Laurent Montel <montel@kde.org> ---
> Which "new" element did you try to  create ?
> mail ? note ? etc.
> see tooltip on this button.
>
Comment 3 NMD 2014-07-20 16:53:11 UTC
Created attachment 87837 [details]
Bug Report and debug info - another crash pressing 'todo list'
Comment 4 Alexander C. Hoerle 2016-05-11 22:07:06 UTC
Created attachment 98922 [details]
New crash information added by DrKonqi

kontact (4.14.10) on KDE Platform 4.14.17 using Qt 4.8.7

- What I was doing when the application crashed:

With KMail open separately, I press "new" in the upper-lefthand corner of Kontact, which provokes a crash every single time.

-- Backtrace (Reduced):
#6  0x00007f36816693d1 in KontactInterface::Plugin::newActions() const () at /lib64/libkontactinterface.so.4
#7  0x00007f3681ab3ed1 in Kontact::MainWindow::slotNewClicked() () at /lib64/libkontactprivate.so.4
[...]
#9  0x00007f367f58d9d2 in QAction::triggered(bool) () at /lib64/libQtGui.so.4
#10 0x00007f367f58ed33 in QAction::activate(QAction::ActionEvent) () at /lib64/libQtGui.so.4
#11 0x00007f367f96ab33 in QAbstractButtonPrivate::click() () at /lib64/libQtGui.so.4
Comment 5 Denis Kurz 2017-06-23 22:13:29 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those Framework-based versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 6 Denis Kurz 2018-02-01 09:53:36 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.