Summary: | KAlarm 19.04 doesn't work at all | ||
---|---|---|---|
Product: | [Applications] kalarm | Reporter: | Bernhard Rosenkränzer <bero> |
Component: | Akonadi | Assignee: | David Jarvie <djarvie> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | anticorporatedemocrat, contact |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | fe40ba8aa6e61beb9e3bf89742df2b66091739ea | Version Fixed In: | 19.04.2 |
Sentry Crash Report: |
Description
Bernhard Rosenkränzer
2019-05-14 23:47:00 UTC
Did you get crash handler dialogs? Without a crash trace, it is unlikely to be possible to fix this. Unfortunately missing a couple of symbols, but doesn't look entirely useless: Application: akonadi_kalarm_resource (akonadi_kalarm_resource), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7faa8652b840 (LWP 1987))] Thread 5 (Thread 0x7faa7aafa700 (LWP 2007)): #0 0x00007faa88d786bf in poll () from /lib64/libc.so.6 #1 0x00007faa876a04fe in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007faa876a061f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x00007faa8938a03b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #4 0x00007faa89318dfe in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #5 0x00007faa890fc0de in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x00007faa890fe008 in ?? () from /usr/lib64/libQt5Core.so.5 #7 0x00007faa87ef1151 in start_thread () from /lib64/libpthread.so.0 #8 0x00007faa88d84d6f in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7faa7b2fb700 (LWP 2000)): #0 0x00007faa88d786bf in poll () from /lib64/libc.so.6 #1 0x00007faa876a04fe in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007faa876a061f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x00007faa8938a03b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #4 0x00007faa89318dfe in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #5 0x00007faa890fc0de in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x00007faa890fe008 in ?? () from /usr/lib64/libQt5Core.so.5 #7 0x00007faa87ef1151 in start_thread () from /lib64/libpthread.so.0 #8 0x00007faa88d84d6f in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7faa7bafc700 (LWP 1998)): #0 0x00007faa88d786bf in poll () from /lib64/libc.so.6 #1 0x00007faa876a04fe in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007faa876a061f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x00007faa8938a03b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #4 0x00007faa89318dfe in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #5 0x00007faa890fc0de in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x00007faa89dd9020 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x00007faa890fe008 in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x00007faa87ef1151 in start_thread () from /lib64/libpthread.so.0 #9 0x00007faa88d84d6f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7faa8158c700 (LWP 1991)): #0 0x00007faa88d786bf in poll () from /lib64/libc.so.6 #1 0x00007faa865b4da2 in ?? () from /usr/lib64/libxcb.so.1 #2 0x00007faa865b7ab9 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x00007faa81753b68 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x00007faa890fe008 in ?? () from /usr/lib64/libQt5Core.so.5 #5 0x00007faa87ef1151 in start_thread () from /lib64/libpthread.so.0 #6 0x00007faa88d84d6f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7faa8652b840 (LWP 1987)): [KCrash Handler] #6 0x000000000040fd5d in KAlarmResource::applyConfigurationChanges() () #7 0x00007faa8a22d8b4 in ?? () from /usr/lib64/libakonadi-singlefileresource.so.5 #8 0x00007faa8935315f in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5 #9 0x00007faa8a2057f3 in ?? () from /usr/lib64/libKF5AkonadiAgentBase.so.5 #10 0x00007faa89de6a5d in ?? () from /usr/lib64/libQt5DBus.so.5 #11 0x00007faa89de52fa in ?? () from /usr/lib64/libQt5DBus.so.5 #12 0x00007faa89de1a67 in ?? () from /usr/lib64/libQt5DBus.so.5 #13 0x00007faa89de26fe in ?? () from /usr/lib64/libQt5DBus.so.5 #14 0x00007faa89351eab in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5 #15 0x00007faa8984bca0 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #16 0x00007faa89848fa8 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #17 0x00007faa89320bdb in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #18 0x00007faa893216d4 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQt5Core.so.5 #19 0x00007faa89389b70 in ?? () from /usr/lib64/libQt5Core.so.5 #20 0x00007faa876a02db in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #21 0x00007faa876a0588 in ?? () from /usr/lib64/libglib-2.0.so.0 #22 0x00007faa876a061f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #23 0x00007faa8938a014 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #24 0x00007faa89318dfe in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #25 0x00007faa8932109f in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5 #26 0x00007faa8a1fab4f in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () from /usr/lib64/libKF5AkonadiAgentBase.so.5 #27 0x0000000000414336 in main () This bug was caused by a mistake in porting the KAlarm resource to the config API (commit fe40ba8aa6e61beb9e3bf89742df2b66091739ea, 18 Aug 2018). Now fixed by kdepim-runtime commit fe40ba8aa6e61beb9e3bf89742df2b66091739ea. This will be in KAlarm version 2.12.3, which will be released as part of KDE Applications version 19.04.2. *** Bug 408006 has been marked as a duplicate of this bug. *** |