Bug 343951 - Akonadi Crashes creating resource
Summary: Akonadi Crashes creating resource
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Google Resource (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash (vote)
Target Milestone: ---
Assignee: Daniel Vrátil
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2015-02-09 00:09 UTC by René Serral
Modified: 2018-02-01 09:55 UTC (History)
2 users (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 René Serral 2015-02-09 00:09:24 UTC
Application: akonadi_googlecalendar_resource (4.81.0)
 (Compiled from sources)
Qt Version: 5.4.0
Operating System: Linux 3.18.6 x86_64
Distribution: Debian GNU/Linux 8.0 (jessie)

-- Information about the crash:
- What I was doing when the application crashed:
I just installed KDE5 from sources, everytime I try to add a Google calendar, or I try to add my google contacts from akonadi configuration I get a crash

The crash can be reproduced every time.

-- Backtrace:
Application: Akonadi Resource (akonadi_googlecalendar_resource), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1b98c52800 (LWP 7033))]

Thread 2 (Thread 0x7f1b96f28700 (LWP 7034)):
#0  0x00007f1ba8e39d8d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f1ba169d252 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007f1ba169eddf in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007f1b98a379b9 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
#4  0x00007f1ba99caa5e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f1ba74930a4 in start_thread (arg=0x7f1b96f28700) at pthread_create.c:309
#6  0x00007f1ba8e428cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f1b98c52800 (LWP 7033)):
[KCrash Handler]
#6  0x00007f1baa51b790 in QBoxLayout::insertWidget(int, QWidget*, int, QFlags<Qt::AlignmentFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#7  0x0000000000455edf in SettingsDialog::SettingsDialog (this=0x2190510, accountManager=0x21929a0, windowId=16777221, parent=0x21c3950) at /usr/src/kde5/src/kde/kdepim-runtime/resources/google/calendar/settingsdialog.cpp:49
#8  0x000000000043d1c8 in CalendarResource::runConfigurationDialog (this=0x21c3950, windowId=16777221) at /usr/src/kde5/src/kde/kdepim-runtime/resources/google/calendar/calendarresource.cpp:95
#9  0x0000000000459541 in GoogleResource::configure (this=0x21c3950, windowId=16777221) at /usr/src/kde5/src/kde/kdepim-runtime/resources/google/common/googleresource.cpp:111
#10 0x00007f1bb26519e0 in Akonadi__ControlAdaptor::configure (this=0x219ed70, windowId=16777221) at /usr/src/kde5/build/kde/kdepimlibs/akonadi/src/agentbase/controladaptor.cpp:51
#11 0x00007f1bb2651ad1 in Akonadi__ControlAdaptor::qt_static_metacall (_o=0x219ed70, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0x7fff462c7b70) at /usr/src/kde5/build/kde/kdepimlibs/akonadi/src/agentbase/controladaptor.moc:118
#12 0x00007f1bb2651c78 in Akonadi__ControlAdaptor::qt_metacall (this=0x219ed70, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0x7fff462c7b70) at /usr/src/kde5/build/kde/kdepimlibs/akonadi/src/agentbase/controladaptor.moc:167
#13 0x00007f1bb3d02507 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#14 0x00007f1bb3d06ca5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#15 0x00007f1bb3d077ab in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#16 0x00007f1bb3d0944e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#17 0x00007f1ba9c3895a in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007f1baa508f0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x00007f1baa50e590 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#20 0x00007f1ba9c0792b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007f1ba9c0999b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007f1ba9c5f533 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x00007f1ba5913c5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x00007f1ba5913f48 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x00007f1ba5913ffc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x00007f1ba9c5f947 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x00007f1ba9c050e2 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#28 0x00007f1ba9c0cd2c in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#29 0x00007f1bb263c222 in Akonadi::ResourceBase::init (r=0x21c3950) at /usr/src/kde5/src/kde/kdepimlibs/akonadi/src/agentbase/resourcebase.cpp:581
#30 0x0000000000448c88 in Akonadi::ResourceBase::init<CalendarResource> (argc=3, argv=0x7fff462c84e8) at /usr/local/kde5/include/KF5/AkonadiAgentBase/resourcebase.h:192
#31 0x0000000000444b28 in main (argc=3, argv=0x7fff462c84e8) at /usr/src/kde5/src/kde/kdepim-runtime/resources/google/calendar/calendarresource.cpp:747

Reported using DrKonqi
Comment 1 Tajidin Abd 2015-02-14 21:12:05 UTC
with my Arch linux source build i get all the way to the point where i can enter my 6 digit code during the 2 step authentication. The window just freezes and I can not do anything. The window freezes.
Comment 2 Denis Kurz 2017-06-23 20:00:01 UTC
This bug has never been confirmed for a KDE PIM 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 3 Denis Kurz 2018-02-01 09:55:22 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.