Bug 407544 - KAlarm 19.04 doesn't work at all
Summary: KAlarm 19.04 doesn't work at all
Status: RESOLVED FIXED
Alias: None
Product: kalarm
Classification: Applications
Component: Akonadi (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: David Jarvie
URL:
Keywords:
: 408006 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-05-14 23:47 UTC by Bernhard Rosenkränzer
Modified: 2019-05-28 08:59 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 19.04.2


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bernhard Rosenkränzer 2019-05-14 23:47:00 UTC
On a fresh install (or live image), start kalarm for the first time.

It pops up 3 dialogs (all at the same time) and 3 crash notifications ("akonadi_kalarm_resource Closed Unexpectedly"):

Failed to create default calendar "Alarm Templates"
Location: file:///home/live/.local/share/kalarm/template.ics (New configuration timed out)

Failed to create default calendar "Active Alarms"
Location: file:///home/live/.local/share/kalarm/calendar.ics (New configuration timed out)

Failed to create default calendar "Archived Alarms"
Location: file:///home/live/.local/share/kalarm/expired.ics (New configuration timed out)

and the Konsole KAlarm was started from says:
org.kde.pim.kidentitymanagement: IdentityManager: There was no default identity. Marking first one as default.
org.kde.pim.kalarm: Error writing autostart file: "/home/neon/.config/autostart/kalarm.autostart.desktop"
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7ff8dc1a7a50) )
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7ff8dc1a7a50) identified as "kalarm-182605794 - 94578821812896"
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7ff8dc17ca40) )
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7ff8dc16af70) )
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7ff8dc159c40) )
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7ff8dc17ca40) identified as "AgentBaseChangeRecorder - 94416152789328"
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7ff8dc16af70) identified as "akonadi_birthdays_resource - 94416152897040"
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7ff8dc1e4ff0) )
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7ff8dc1edd20) )
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7ff8dc159c40) identified as "AgentBaseChangeRecorder - 94501010757296"
"No file selected."
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = akonadi_kalarm_resource path = /usr/bin pid = 12459
KCrash: Arguments: /usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_0 
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit
sock_file=/run/user/999/kdeinit5__0
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7ff8dc1e4ff0) identified as "AgentBaseChangeRecorder - 94252596204928"
org.kde.pim.akonadicore: Failed to place D-Bus call.
org.kde.pim.kalarm: ResourceSynchronizationJob error:  "Unable to obtain D-Bus interface for resource 'akonadi_kalarm_resource_0'"
QSocketNotifier: Invalid socket 7 and type 'Read', disabling...
QSocketNotifier: Invalid socket 13 and type 'Read', disabling...
QSocketNotifier: Invalid socket 9 and type 'Read', disabling...
QSocketNotifier: Invalid socket 15 and type 'Read', disabling...
"No file selected."
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = akonadi_kalarm_resource path = /usr/bin pid = 12460
KCrash: Arguments: /usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_1 
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit
sock_file=/run/user/999/kdeinit5__0
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7ff8dc207d80) )
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7ff8dc1edd20) identified as "AgentBaseChangeRecorder - 93900593768336"
org.kde.pim.akonadicore: Failed to place D-Bus call.
org.kde.pim.kalarm: ResourceSynchronizationJob error:  "Unable to obtain D-Bus interface for resource 'akonadi_kalarm_resource_1'"
QSocketNotifier: Invalid socket 7 and type 'Read', disabling...
QSocketNotifier: Invalid socket 13 and type 'Read', disabling...
QSocketNotifier: Invalid socket 9 and type 'Read', disabling...
QSocketNotifier: Invalid socket 15 and type 'Read', disabling...
"No file selected."
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = akonadi_kalarm_resource path = /usr/bin pid = 12461
KCrash: Arguments: /usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_2 
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit
sock_file=/run/user/999/kdeinit5__0
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7ff8dc207d80) identified as "AgentBaseChangeRecorder - 94505301737152"
org.kde.pim.akonadicore: Failed to place D-Bus call.
org.kde.pim.kalarm: ResourceSynchronizationJob error:  "Unable to obtain D-Bus interface for resource 'akonadi_kalarm_resource_2'"
QSocketNotifier: Invalid socket 7 and type 'Read', disabling...
QSocketNotifier: Invalid socket 13 and type 'Read', disabling...
QSocketNotifier: Invalid socket 9 and type 'Read', disabling...
QSocketNotifier: Invalid socket 15 and type 'Read', disabling...
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7ff8dc221fb0) )
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7ff8dc221fb0) identified as "AgentBaseChangeRecorder - 94654863352992"
"No file selected."
org.kde.pim.akonadiserver: Handler exception when handling command FetchCollections on connection akonadi_ical_resource_0 (0x55879bbc4b70) : Hierarchical RID does not specify an existing collection
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7ff8dc258340) )
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7ff8dc258340) identified as "AgentBaseChangeRecorder - 94885781934928"
org.kde.pim.akonadiserver: Subscriber "AgentBaseChangeRecorder - 94501010757296" disconnected
org.kde.pim.maildirresource: the resource is not properly configured: there is no config file for the resource. We create a new one.
QObject::killTimer: Timers cannot be stopped from another thread
org.kde.pim.kalarm: Timeout fetching collection for resource
org.kde.pim.akonadiserver: Subscriber "AgentBaseChangeRecorder - 94252596204928" disconnected
org.kde.pim.akonadiserver: Subscriber "AgentBaseChangeRecorder - 93900593768336" disconnected
org.kde.pim.kalarm: Timeout fetching collection for resource
org.kde.pim.kalarm: Timeout fetching collection for resource
QProcess: Destroyed while process ("/usr/bin/akonadi_kalarm_resource") is still running.
org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadi_kalarm_resource" stopped unexpectedly ( "Process crashed" )
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_kalarm_resource' crashed. No restart!
QProcess: Destroyed while process ("/usr/bin/akonadi_kalarm_resource") is still running.
org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadi_kalarm_resource" stopped unexpectedly ( "Process crashed" )
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_kalarm_resource' crashed. No restart!
QProcess: Destroyed while process ("/usr/bin/akonadi_kalarm_resource") is still running.
org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadi_kalarm_resource" stopped unexpectedly ( "Process crashed" )
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_kalarm_resource' crashed. No restart!



Kalarm remains open, but all functionality is grayed out.


The problem remains even if I create the *.ics files it's complaining about manually (making them say:
BEGIN:VCALENDAR
PRODID:-//K Desktop Environment//NONSGML KAlarm 2.12.2//EN
VERSION:2.0
X-KDE-ICAL-IMPLEMENTATION-VERSION:1.0
END:VCALENDAR
)


To rule out an OpenMandriva packaging problem, I've reproduced this with the Neon live image (neon-user-20190502-1122.iso). I get the exact same error there (after installing kalarm and hunting down the dependencies it needs to do something useful)
Comment 1 David Jarvie 2019-05-17 20:15:37 UTC
Did you get crash handler dialogs? Without a crash trace, it is unlikely to be possible to fix this.
Comment 2 Bernhard Rosenkränzer 2019-05-18 19:51:34 UTC
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 ()
Comment 3 David Jarvie 2019-05-23 22:00:45 UTC
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.
Comment 4 David Jarvie 2019-05-28 08:59:02 UTC
*** Bug 408006 has been marked as a duplicate of this bug. ***