Bug 260824 - Crash of Kontact/Kadressbook when opening vCard
Summary: Crash of Kontact/Kadressbook when opening vCard
Status: RESOLVED WORKSFORME
Alias: None
Product: kaddressbook
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-20 21:28 UTC by Bernhard Jungk
Modified: 2012-03-04 21:25 UTC (History)
1 user (show)

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 Bernhard Jungk 2010-12-20 21:28:51 UTC
Application: kontact (4.4.8)
KDE Platform Version: 4.5.85 (4.6 Beta2)
Qt Version: 4.7.1
Operating System: Linux 2.6.37-10-server x86_64
Distribution: Ubuntu natty (development branch)

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

Opening a vCard file. The crash always happens. The backtrace seems to be different to the other bug report, maybe this is related?

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Aborted
[Current thread is 1 (Thread 0x7fd3aa54f780 (LWP 6807))]

Thread 4 (Thread 0x7fd382997700 (LWP 6829)):
#0  0x00007fd3a0cd275e in g_main_context_check () from /lib/libglib-2.0.so.0
#1  0x00007fd3a0cd3052 in ?? () from /lib/libglib-2.0.so.0
#2  0x00007fd3a0cd3559 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#3  0x00007fd3a7c98f26 in QEventDispatcherGlib::processEvents (this=0x200d030, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:417
#4  0x00007fd3a7c6d362 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007fd3a7c6d59c in QEventLoop::exec (this=0x7fd382996da0, flags=...) at kernel/qeventloop.cpp:201
#6  0x00007fd3a7b84274 in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:490
#7  0x00007fd3a7c4f82f in QInotifyFileSystemWatcherEngine::run (this=0x21824e0) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007fd3a7b86a2e in QThreadPrivate::start (arg=0x21824e0) at thread/qthread_unix.cpp:285
#9  0x00007fd3a119b971 in start_thread (arg=<value optimized out>) at pthread_create.c:304
#10 0x00007fd3a757192d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7fd385a6f700 (LWP 6831)):
#0  0x00007fd3a7565203 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007fd3a0cd3030 in ?? () from /lib/libglib-2.0.so.0
#2  0x00007fd3a0cd3559 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#3  0x00007fd3a7c98f26 in QEventDispatcherGlib::processEvents (this=0x1ebdc60, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:417
#4  0x00007fd3a7c6d362 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007fd3a7c6d59c in QEventLoop::exec (this=0x7fd385a6eda0, flags=...) at kernel/qeventloop.cpp:201
#6  0x00007fd3a7b84274 in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:490
#7  0x00007fd3a7c4f82f in QInotifyFileSystemWatcherEngine::run (this=0x1d6d970) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007fd3a7b86a2e in QThreadPrivate::start (arg=0x1d6d970) at thread/qthread_unix.cpp:285
#9  0x00007fd3a119b971 in start_thread (arg=<value optimized out>) at pthread_create.c:304
#10 0x00007fd3a757192d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7fd38674f700 (LWP 6832)):
#0  0x00007fd3a0cd300d in ?? () from /lib/libglib-2.0.so.0
#1  0x00007fd3a0cd3559 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#2  0x00007fd3a7c98f26 in QEventDispatcherGlib::processEvents (this=0x2048110, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:417
#3  0x00007fd3a7c6d362 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#4  0x00007fd3a7c6d59c in QEventLoop::exec (this=0x7fd38674edb0, flags=...) at kernel/qeventloop.cpp:201
#5  0x00007fd3a7b84274 in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:490
#6  0x00007fd39c4c213c in Herqq::Upnp::HControlPointThread::run() () from /usr/lib/libHUpnp.so.0
#7  0x00007fd3a7b86a2e in QThreadPrivate::start (arg=0x1fddb00) at thread/qthread_unix.cpp:285
#8  0x00007fd3a119b971 in start_thread (arg=<value optimized out>) at pthread_create.c:304
#9  0x00007fd3a757192d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#10 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fd3aa54f780 (LWP 6807)):
[KCrash Handler]
#6  0x00007fd3a74beba5 in raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00007fd3a74c26b0 in abort () at abort.c:92
#8  0x00007fd3a78c97ed in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6
#9  0x00007fd3a78c7a36 in ?? () from /usr/lib/libstdc++.so.6
#10 0x00007fd3a78c7a63 in std::terminate() () from /usr/lib/libstdc++.so.6
#11 0x00007fd3a78c7bb6 in __cxa_rethrow () from /usr/lib/libstdc++.so.6
#12 0x00007fd3a7c6d692 in QEventLoop::exec (this=0x7fffed750070, flags=...) at kernel/qeventloop.cpp:214
#13 0x00007fd3a7c719bb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#14 0x0000000000403ff7 in main (argc=1, argv=<value optimized out>) at ../../../kontact/src/main.cpp:224

This bug may be a duplicate of or related to bug 259777.

Possible duplicates by query: bug 260821, bug 260819, bug 260817, bug 260811, bug 260793.

Reported using DrKonqi
Comment 1 Christophe Marin 2012-02-07 14:43:20 UTC
Unfortunately, the backtrace is not helpful. As you're able to reproduce it,
please follow the steps mentioned on this page to get a better one (with a recent kaddressbook version):

http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_when_an_uncaught_exception_is_causing_a_crash
Comment 2 Bernhard Jungk 2012-03-04 21:25:42 UTC
I finally had the time to try to reproduce the bug. Happily I'm unable to do so. The bug seems to be fixed in 4.8.