Bug 355112 - Google_contact crashed after deleting contact and every restart system
Summary: Google_contact crashed after deleting contact and every restart system
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Google Resource (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Daniel Vrátil
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2015-11-09 22:46 UTC by Sergey
Modified: 2018-02-01 09:44 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 Sergey 2015-11-09 22:46:59 UTC
Application: akonadi_googlecontacts_resource (4.89.0)

Qt Version: 5.4.2
Operating System: Linux 4.2.0-17-generic x86_64
Distribution: Ubuntu 15.10

-- Information about the crash:
- What I was doing when the application crashed:
delete contact in google adressbook
power off system or restart
power on system

The crash can be reproduced every time.

-- Backtrace:
Application: Источник данных Akonadi (akonadi_googlecontacts_resource), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc453a96840 (LWP 3374))]

Thread 3 (Thread 0x7fc4518ed700 (LWP 3375)):
#0  0x00007fc466fed8dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fc4603acbd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007fc4603ae74f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007fc45360aa39 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
#4  0x00007fc4678f72be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007fc4608176aa in start_thread (arg=0x7fc4518ed700) at pthread_create.c:333
#6  0x00007fc466ff8eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fc44981f700 (LWP 3380)):
#0  0x00007fc45fccc884 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007fc45fc87a59 in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fc45fc88167 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fc45fc882fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007fc467b2e29b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007fc467ad475a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007fc4678f23d4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007fc4678f72be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007fc4608176aa in start_thread (arg=0x7fc44981f700) at pthread_create.c:333
#9  0x00007fc466ff8eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fc453a96840 (LWP 3374)):
[KCrash Handler]
#6  0x000000000041d768 in QList<QSharedPointer<KGAPI2::Object> >::Node::t (this=<optimized out>) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:108
#7  QList<QSharedPointer<KGAPI2::Object> >::at (i=<optimized out>, this=<optimized out>) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:479
#8  ContactsResource::slotCreateJobFinished (this=0x895910, job=0x8d6170) at ../../../../resources/google/contacts/contactsresource.cpp:532
#9  0x00007fc467b07617 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007fc46a48e9af in KGAPI2::Job::finished(KGAPI2::Job*) () from /usr/lib/x86_64-linux-gnu/libKF5GAPICore.so.5
#11 0x00007fc46a492949 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5GAPICore.so.5
#12 0x00007fc467b08651 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007fc4683a4b8c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x00007fc4683aa230 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x00007fc467ad6f1b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007fc467ad9057 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007fc467b2de73 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007fc45fc87ff7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007fc45fc88250 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007fc45fc882fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007fc467b2e27f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007fc467ad475a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x00007fc467adc2cc in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x00007fc46ab6321a in Akonadi::ResourceBase::init (r=r@entry=0x895910) at ../../../../akonadi/src/agentbase/resourcebase.cpp:602
#25 0x0000000000423d88 in Akonadi::ResourceBase::init<ContactsResource> (argc=<optimized out>, argv=<optimized out>) at /usr/include/KF5/AkonadiAgentBase/resourcebase.h:193
#26 0x00007fc466f12a40 in __libc_start_main (main=0x4178a0 <main(int, char**)>, argc=3, argv=0x7ffd49773f78, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffd49773f68) at libc-start.c:289
#27 0x00000000004178d9 in _start ()

Possible duplicates by query: bug 332347, bug 331524, bug 330255.

Reported using DrKonqi
Comment 1 Denis Kurz 2017-06-23 20:17:53 UTC
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.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 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 2 Denis Kurz 2018-02-01 09:44: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.