Bug 347785 - Kontact (contacts) crash when editing contact group
Summary: Kontact (contacts) crash when editing contact group
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2015-05-16 09:55 UTC by domhans
Modified: 2018-02-01 09:54 UTC (History)
0 users

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 domhans 2015-05-16 09:55:52 UTC
Application: kontact (4.14.7)
KDE Platform Version: 4.14.7
Qt Version: 4.8.6
Operating System: Linux 3.19.0-16-generic x86_64
Distribution: Ubuntu 15.04

-- Information about the crash:
- What I was doing when the application crashed:
as sooa as I click (right) on contact group and try to edit the group Kontact crashes.

The crash can be reproduced every time.

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

Thread 5 (Thread 0x7fe46da3c700 (LWP 2465)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fe48890881d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x00007fe488908859 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x00007fe4850006aa in start_thread (arg=0x7fe46da3c700) at pthread_create.c:333
#4  0x00007fe48b145eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7fe42d139700 (LWP 2466)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fe48864920d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x00007fe488937fd6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x00007fe4850006aa in start_thread (arg=0x7fe42d139700) at pthread_create.c:333
#4  0x00007fe48b145eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7fe41d27c700 (LWP 2469)):
#0  0x00007fe48b13a8dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fe484b1aebc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fe484b1afcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fe48b8ce82e in QEventDispatcherGlib::processEvents (this=0x7fe4180008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0x00007fe48b89dcd1 in QEventLoop::processEvents (this=this@entry=0x7fe41d27bdd0, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007fe48b89e035 in QEventLoop::exec (this=this@entry=0x7fe41d27bdd0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007fe48b791e89 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:538
#7  0x00007fe48b7946ff in QThreadPrivate::start (arg=0x2533720) at thread/qthread_unix.cpp:349
#8  0x00007fe4850006aa in start_thread (arg=0x7fe41d27c700) at pthread_create.c:333
#9  0x00007fe48b145eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fe41762f700 (LWP 2471)):
#0  0x00007fe48b13649d in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fe484b5e2f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fe484b1a96c in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fe484b1ae60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007fe484b1afcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007fe48b8ce82e in QEventDispatcherGlib::processEvents (this=0x7fe4100008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#6  0x00007fe48b89dcd1 in QEventLoop::processEvents (this=this@entry=0x7fe41762ed80, flags=...) at kernel/qeventloop.cpp:149
#7  0x00007fe48b89e035 in QEventLoop::exec (this=this@entry=0x7fe41762ed80, flags=...) at kernel/qeventloop.cpp:204
#8  0x00007fe48b791e89 in QThread::exec (this=this@entry=0x2e6efa0) at thread/qthread.cpp:538
#9  0x00007fe48b87e443 in QInotifyFileSystemWatcherEngine::run (this=0x2e6efa0) at io/qfilesystemwatcher_inotify.cpp:265
#10 0x00007fe48b7946ff in QThreadPrivate::start (arg=0x2e6efa0) at thread/qthread_unix.cpp:349
#11 0x00007fe4850006aa in start_thread (arg=0x7fe41762f700) at pthread_create.c:333
#12 0x00007fe48b145eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fe48dc66800 (LWP 2464)):
[KCrash Handler]
#6  0x00007fe48b074267 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55
#7  0x00007fe48b075eca in __GI_abort () at abort.c:89
#8  0x00007fe48b46a06d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x00007fe48b467ee6 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x00007fe48b467f31 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#11 0x00007fe48b468199 in __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#12 0x00007fe48b89e23b in QEventLoop::exec (this=this@entry=0x7ffc6ac0e6a0, flags=...) at kernel/qeventloop.cpp:218
#13 0x00007fe48b8a3ab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1227
#14 0x00007fe48c2aac1c in QApplication::exec () at kernel/qapplication.cpp:3828
#15 0x0000000000403509 in main (argc=1, argv=0x7ffc6ac0e8e8) at ../../../kontact/src/main.cpp:219

Possible duplicates by query: bug 347734, bug 347595, bug 347580, bug 347472, bug 347430.

Reported using DrKonqi
Comment 1 Denis Kurz 2017-06-23 19:36:13 UTC
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks (5.x). Those 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 oportunity 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 2 Denis Kurz 2018-02-01 09:54:19 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.