I have the Gnome version of OpenSuse 13.1 and additionally I installed kalarm. The problem is that when I try to run it it starts but shows the following error message:
“The Akonadi personal information management service is not operational.”
Looking at the details of the error the concrete warnings/failures are:
MySQL server custom configuration not available
Nepomuk search service not registered at D-Bus
Protocol version check not possible
No resource agents found
Current Akonadi server error log found
Previous Akonadi server error log found
I am not very familiar with KDE, but it looks like the nepomuk service is the cause.
kdepim4-runtime was missing, after installing it kalarm starts correctly.
The problem now is that if I try to add a new alarm or import a backup of my previously saved alarms it crashes:
Application: KAlarm (kalarm), signal: Aborted
Using host libthread_db library “/lib64/libthread_db.so.1”.
[Current thread is 1 (Thread 0x7fa4e31b2880 (LWP 7003))]
Thread 5 (Thread 0x7fa4c7b3b700 (LWP 7004)): #0 0x00007fa4dd91eb3d in poll () from /lib64/libc.so.6 #1 0x00007fa4d7698604 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007fa4d7698a6a in g_main_loop_run () from /usr/lib64/libglib-2.0.so.0 #3 0x00007fa4cffe7c16 in ?? () from /usr/lib64/libgio-2.0.so.0 #4 0x00007fa4d76bd035 in ?? () from /usr/lib64/libglib-2.0.so.0 #5 0x00007fa4dcf890db in start_thread () from /lib64/libpthread.so.0 #6 0x00007fa4dd92790d in clone () from /lib64/libc.so.6
Thread 4 (Thread 0x7fa4c733a700 (LWP 7005)): #0 0x00007fa4dd91a99d in read () from /lib64/libc.so.6 #1 0x00007fa4d76d75c0 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007fa4d769812c in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x00007fa4d769859b in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x00007fa4d769870c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x00007fa4d7698759 in ?? () from /usr/lib64/libglib-2.0.so.0 #6 0x00007fa4d76bd035 in ?? () from /usr/lib64/libglib-2.0.so.0 #7 0x00007fa4dcf890db in start_thread () from /lib64/libpthread.so.0 #8 0x00007fa4dd92790d in clone () from /lib64/libc.so.6
Thread 3 (Thread 0x7fa4c6338700 (LWP 7007)): #0 0x00007fa4dcf8d458 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007fa4d76d85f5 in g_cond_wait_until () from /usr/lib64/libglib-2.0.so.0 #2 0x00007fa4d766ea71 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x00007fa4d766effb in g_async_queue_timeout_pop () from /usr/lib64/libglib-2.0.so.0 #4 0x00007fa4d76bdac6 in ?? () from /usr/lib64/libglib-2.0.so.0 #5 0x00007fa4d76bd035 in ?? () from /usr/lib64/libglib-2.0.so.0 #6 0x00007fa4dcf890db in start_thread () from /lib64/libpthread.so.0 #7 0x00007fa4dd92790d in clone () from /lib64/libc.so.6
Thread 2 (Thread 0x7fa4af505700 (LWP 7010)): #0 0x00007fa4dd91eb3d in poll () from /lib64/libc.so.6 #1 0x00007fa4d7698604 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007fa4d769870c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x00007fa4def7bd76 in QEventDispatcherGlib::processEvents (this=0x7fa4a80008c0, flags=…) at kernel/qeventdispatcher_glib.cpp:427 #4 0x00007fa4def4dd0f in QEventLoop::processEvents (this=this@entry=0x7fa4af504d20, flags=…) at kernel/qeventloop.cpp:149 #5 0x00007fa4def4e005 in QEventLoop::exec (this=this@entry=0x7fa4af504d20, flags=…) at kernel/qeventloop.cpp:204 #6 0x00007fa4dee4cfef in QThread::exec (this=this@entry=0x2346760) at thread/qthread.cpp:536 #7 0x00007fa4def2f513 in QInotifyFileSystemWatcherEngine::run (this=0x2346760) at io/qfilesystemwatcher_inotify.cpp:256 #8 0x00007fa4dee4f68f in QThreadPrivate::start (arg=0x2346760) at thread/qthread_unix.cpp:338 #9 0x00007fa4dcf890db in start_thread () from /lib64/libpthread.so.0 #10 0x00007fa4dd92790d in clone () from /lib64/libc.so.6
Thread 1 (Thread 0x7fa4e31b2880 (LWP 7003)):
[KCrash Handler] #5 0x00007fa4dd875849 in raise () from /lib64/libc.so.6 #6 0x00007fa4dd876cd8 in abort () from /lib64/libc.so.6 #7 0x00007fa4dde6b655 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib64/libstdc++.so.6 #8 0x00007fa4dde697c6 in ?? () from /usr/lib64/libstdc++.so.6 #9 0x00007fa4dde697f3 in std::terminate() () from /usr/lib64/libstdc++.so.6 #10 0x00007fa4dde69a66 in __cxa_rethrow () from /usr/lib64/libstdc++.so.6 #11 0x00007fa4def4e1f6 in QEventLoop::exec (this=this@entry=0x7fffbe8e9850, flags=…) at kernel/qeventloop.cpp:218 #12 0x00007fa4def5313b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1221 #13 0x0000000000452124 in ?? () #14 0x00007fa4dd861be5 in __libc_start_main () from /lib64/libc.so.6 #15 0x0000000000453895 in _start ()
Running kalarm interactively from the console the error seems to be related with akonadi:
Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt. You must
reimplement QApplication::notify() and catch all exceptions there.
terminate called after throwing an instance of ‘Akonadi::PayloadException’
what(): Akonadi::PayloadException: Wrong payload type (requested: sp(0)<QByteArray>; present: sp(0)<KAlarmCal::KAEvent>
KCrash: Application ‘kalarm’ crashing…
KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit
sock_file=/home/jlopez/.kde4/socket-pcsistemas3/kdeinit4__0
QSocketNotifier: Invalid socket 21 and type ‘Read’, disabling…
I have tried deleting the configuration and starting again from scratch but kalarm still crashes any time it has to write to disk.
Actually I have no idea why akonadi is failing:
*what(): Akonadi::PayloadException: Wrong payload type (requested: sp(0)<QByteArray>; present: sp(0)<KAlarmCal::KAEvent>*
Looking at the error log it only complains about Nepomuk Query Server not available but it gives no clue about the PayloadException.
cat ~/.local/share/akonadi/akonadiserver.error
Nepomuk Query Server not available
It seems something related to the fact I am unsing kalarm from gnome because from a KDE only installation it works.
I do not know if it is a general issue or just some specific configuration on my side that is interfering. Anyone is able to use kalarm from gnome in 13.1?
alcachi wrote:
>
> Hi,
>
> I have the Gnome version of OpenSuse 13.1 and additionally I installed
> kalarm. The problem is that when I try to run it it starts but shows the
> following error message:
> “The Akonadi personal information management service is not
> operational.”
>
> Looking at the details of the error the concrete warnings/failures are:
> - MySQL server custom configuration not available
> - Nepomuk search service not registered at D-Bus
> - Protocol version check not possible
> - No resource agents found
> - Current Akonadi server error log found
> - Previous Akonadi server error log found
>
> I am not very familiar with KDE, but it looks like the nepomuk service
> is the cause.
>
> Thanks!
>
>
Why use kalarm when you can use alarm in clocks application in GNOME 3.10
–
GNOME 3.10.1
openSUSE 13.1 (Bottle) (x86_64) 64-bit
Kernel Linux 3.11.6-4-desktop
Where are my penguins :- https://features.opensuse.org/316767
Thanks vazhavandan, I was not aware of the new alarm in clocks in 3.10. I have been testing it and the main feature I miss is the option to schedule the alarm for a given date, I have also tried the gnome alarm clock applet but at the end the only suitable alternative I have found is using evolution or the Lightbird extension of Thunderbird to show pop ups for calendar/task events.
The issue with kalarm is solved after installing the complete KDE desktop. Now I can run kalarm from Gnome and it does not crash when adding a new alarm. I guess it is due to some dependency not resolved automatically by the package.