Bug 330891 - Crash when adding international phone number to Google Contacts
Summary: Crash when adding international phone number to Google Contacts
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Google Resource (show other bugs)
Version: 4.12
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Daniel Vrátil
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2014-02-07 14:46 UTC by David Pyke
Modified: 2017-01-07 22:04 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 David Pyke 2014-02-07 14:46:28 UTC
Application: akonadi_googlecontacts_resource (4.12)
KDE Platform Version: 4.12.1
Qt Version: 4.8.6
Operating System: Linux 3.13.1 x86_64
Distribution: Ubuntu 13.10

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

I had just added a new contact (French) to my (North American) contact list including the 011 prefix and saved.  When the sync began, the conduit crashed.

-- Backtrace:
Application: Google Contacts (loftwyr@gmail.com) of type Google Contacts (akonadi_googlecontacts_resource), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x00007f2b7fd53798 in main_arena () from /lib/x86_64-linux-gnu/libc.so.6
#7  0x00007f2b82107e74 in QMetaObject::invokeMethod (obj=obj@entry=0xd46390, member=<optimized out>, type=type@entry=Qt::QueuedConnection, ret=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1166
#8  0x00007f2b8211add5 in invokeMethod (val9=..., val8=..., val7=..., val6=..., val5=..., val4=..., val3=..., val2=..., val1=..., val0=..., type=Qt::QueuedConnection, member=<optimized out>, obj=0xd46390) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs.h:418
#9  QTimer::singleShot (msec=msec@entry=0, receiver=receiver@entry=0xd46390, member=member@entry=0x7f2b81616373 "1_k_doStart()") at kernel/qtimer.cpp:360
#10 0x00007f2b815a6ad1 in KGAPI2::Job::restart (this=this@entry=0xd46390) at /build/buildd/libkgapi-2.0.1/libkgapi2/job.cpp:374
#11 0x000000000041a2ed in GoogleResource::slotAuthJobFinished (this=0xc121f0, job=0xbe4420) at ../../../../resources/google/common/googleresource.cpp:239
#12 0x00007f2b82111ae8 in QMetaObject::activate (sender=0xbe4420, m=m@entry=0x7f2b8183eb40 <KGAPI2::Job::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff9acce9e0) at kernel/qobject.cpp:3539
#13 0x00007f2b815a55ff in KGAPI2::Job::finished (this=<optimized out>, _t1=0xbe4420) at /build/buildd/libkgapi-2.0.1/obj-x86_64-linux-gnu/libkgapi2/job.moc:151
#14 0x00007f2b82115e9e in QObject::event (this=0xbe4420, e=<optimized out>) at kernel/qobject.cpp:1194
#15 0x00007f2b8043de7c in QApplicationPrivate::notify_helper (this=this@entry=0xaac140, receiver=receiver@entry=0xbe4420, e=e@entry=0xcdb860) at kernel/qapplication.cpp:4567
#16 0x00007f2b804444f0 in QApplication::notify (this=this@entry=0x7fff9accf0a0, receiver=receiver@entry=0xbe4420, e=e@entry=0xcdb860) at kernel/qapplication.cpp:4353
#17 0x00007f2b81148c6a in KApplication::notify (this=0x7fff9accf0a0, receiver=0xbe4420, event=0xcdb860) at ../../kdeui/kernel/kapplication.cpp:311
#18 0x00007f2b820fd73d in QCoreApplication::notifyInternal (this=0x7fff9accf0a0, receiver=receiver@entry=0xbe4420, event=event@entry=0xcdb860) at kernel/qcoreapplication.cpp:953
#19 0x00007f2b82100daf in sendEvent (event=0xcdb860, receiver=0xbe4420) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#20 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0xa701f0) at kernel/qcoreapplication.cpp:1577
#21 0x00007f2b82101253 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1470
#22 0x00007f2b8212b213 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#23 postEventSourceDispatch (s=0xaa9760) at kernel/qeventdispatcher_glib.cpp:280
#24 0x00007f2b7df233b6 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x00007f2b7df23708 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x00007f2b7df237ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x00007f2b8212aad5 in QEventDispatcherGlib::processEvents (this=0xa71af0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#28 0x00007f2b804dfcb6 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#29 0x00007f2b820fc30f in QEventLoop::processEvents (this=this@entry=0x7fff9accf010, flags=...) at kernel/qeventloop.cpp:149
#30 0x00007f2b820fc605 in QEventLoop::exec (this=this@entry=0x7fff9accf010, flags=...) at kernel/qeventloop.cpp:204
#31 0x00007f2b82101deb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225
#32 0x00007f2b8043c3cc in QApplication::exec () at kernel/qapplication.cpp:3828
#33 0x00007f2b82852e33 in Akonadi::ResourceBase::init (r=r@entry=0xc121f0) at ../../akonadi/resourcebase.cpp:504
#34 0x0000000000417bb3 in Akonadi::ResourceBase::init<ContactsResource> (argc=<optimized out>, argv=<optimized out>) at /usr/include/KDE/Akonadi/../../akonadi/resourcebase.h:192
#35 0x00007f2b7f9b3de5 in __libc_start_main (main=0x40ad40 <main(int, char**)>, argc=3, ubp_av=0x7fff9accf1b8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff9accf1a8) at libc-start.c:260
#36 0x000000000040ad6e in _start ()

Reported using DrKonqi
Comment 1 Denis Kurz 2016-09-24 20:42:36 UTC
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:04:32 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.