This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Kalarm not installing akonadi

Tags: kalarm, apparmor kalarm, apparmor kalarm, apparmor
(comma "," separated)
rwayland
Registered Member
Posts
13
Karma
0

Kalarm not installing akonadi

Fri May 24, 2019 4:24 pm
Hi All,

This is a new install of KDE Neon.

Installed Kalarm but having issues with akonadi.
Installed Kalarm using Synaptic package manager but it did not install akonadi. (I thought it would be a dependency.) Uninstalled and tried to install using Discover. Still did not install akonadi. Installed akonadi using synaptic package manager but Kalarm says it can't connect. (Don't know for sure I got the correct akonadi install) Installed KDE-PIM but still had issues with akonadi. Finally uninstalled all and came here for help.

If someone can help, I would appreciate step-by-step instructions.

Thanks
djarvie
KDE Developer
Posts
103
Karma
0
OS

Re: Kalarm not installing akonadi

Mon May 27, 2019 10:09 am
The kalarm package automatically installs the akonadi-server package, among other akonadi packages. This should give you all you need as far as Akonadi is concerned. However, Neon doesn't install the mysql database, which is used by default by Akonadi. This may be what is going wrong for you. To fix this:

1) Install the packages mariadb-server and libqt5sql5-mysql.

2) Ensure that apparmor allows mysqld to run. You can google to find out how, either by enabling mysqld in apparmor, or by disabling apparmor if you think that is wise. Note that if you disable apparmor, you need to reboot before it will actually allow mysqld to run.


KAlarm author
User avatar
mrgrimm
Registered Member
Posts
64
Karma
0
OS

Re: Kalarm not installing akonadi

Mon May 27, 2019 11:34 am
no it does not install all that you need. i installed it on the 24th and straight out of the gate got 2 identical error notifications on launching kalarm. bit of advice if you are going to attempt to help actually included a link or links to instructions needed.

hopefully there is something here that will help.

https://www.google.com/search?hl=en&ei= ... VE0IWnHXWI


KDE Neon 64 Bit On Kernel 5.1, 430 nVidia Driver
Asus 970 Gaming/Aura, AMD FX 6300, 16Gig DDR3,
Samsung 120Gig 850 EVO, AOC 29" Ultra Wide 2560x1080, nVidia 750Ti,
USB 3 Card, Drives 2TB, 1.5TB, 1TB / 750Gig, 500Gig
User avatar
Mamarok
Manager
Posts
6071
Karma
16
OS

Re: Kalarm not installing akonadi

Mon May 27, 2019 3:13 pm
How about making a bug report? This is obviously a packaging issue, and should be reported where it belongs.

FWIW: moving this to the KDE Neon subforum.


Running Kubuntu 22.10 with Plasma 5.26.3, Frameworks 5.100.0, Qt 5.15.6, kernel 5.19.0-23 on Ryzen 5 4600H, AMD Renoir, X11
FWIW: it's always useful to state the exact Plasma version (+ distribution) when asking questions, makes it easier to help ...
User avatar
mrgrimm
Registered Member
Posts
64
Karma
0
OS

Re: Kalarm not installing akonadi

Mon May 27, 2019 3:46 pm
Mamarok wrote:How about making a bug report? This is obviously a packaging issue, and should be reported where it belongs.

FWIW: moving this to the KDE Neon subforum.


i'll make a bug report.


KDE Neon 64 Bit On Kernel 5.1, 430 nVidia Driver
Asus 970 Gaming/Aura, AMD FX 6300, 16Gig DDR3,
Samsung 120Gig 850 EVO, AOC 29" Ultra Wide 2560x1080, nVidia 750Ti,
USB 3 Card, Drives 2TB, 1.5TB, 1TB / 750Gig, 500Gig
djarvie
KDE Developer
Posts
103
Karma
0
OS

Re: Kalarm not installing akonadi

Mon May 27, 2019 10:27 pm
mrgrimm wrote:no it does not install all that you need. i installed it on the 24th and straight out of the gate got 2 identical error notifications on launching kalarm. bit of advice if you are going to attempt to help actually included a link or links to instructions needed.


Please give details about the error messages. What do they say?

I didn't include a link to instructions because I am not aware of anywhere where the instructions are written down. I took the trouble to write the instructions myself, from my own experience of getting KAlarm to work in Neon.

Last edited by djarvie on Tue May 28, 2019 9:19 am, edited 1 time in total.


KAlarm author
djarvie
KDE Developer
Posts
103
Karma
0
OS

Re: Kalarm not installing akonadi

Mon May 27, 2019 10:32 pm
mrgrimm wrote:
Mamarok wrote:How about making a bug report? This is obviously a packaging issue, and should be reported where it belongs.

FWIW: moving this to the KDE Neon subforum.


i'll make a bug report.


The bug report needs to contain all relevant details of what is wrong. Please also give it a descriptive title to sum up what it is about. It isn't practical to use a bug report which simply refers to another thread - how can questions be asked about details contained in the thread without everything getting very confused?


KAlarm author
User avatar
mrgrimm
Registered Member
Posts
64
Karma
0
OS

Re: Kalarm not installing akonadi

Mon May 27, 2019 11:08 pm
i'll reinstall kalarm and post both here and in the bug report what i get.


KDE Neon 64 Bit On Kernel 5.1, 430 nVidia Driver
Asus 970 Gaming/Aura, AMD FX 6300, 16Gig DDR3,
Samsung 120Gig 850 EVO, AOC 29" Ultra Wide 2560x1080, nVidia 750Ti,
USB 3 Card, Drives 2TB, 1.5TB, 1TB / 750Gig, 500Gig
User avatar
mrgrimm
Registered Member
Posts
64
Karma
0
OS

Re: Kalarm not installing akonadi

Mon May 27, 2019 11:35 pm
Code: Select all
Application: akonadi_kalarm_resource (akonadi_kalarm_resource), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f68eaff6e80 (LWP 23782))]

Thread 5 (Thread 0x7f68cdacd700 (LWP 23787)):
#0  0x00007f68e745cbf9 in __GI___poll (fds=0x7f68c4003ce0, nfds=1, timeout=9334) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007f68e1ccc5c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f68e1ccc6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f68e7fc515b in QEventDispatcherGlib::processEvents (this=0x7f68c4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#4  0x00007f68e7f6664a in QEventLoop::exec (this=this@entry=0x7f68cdaccda0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#5  0x00007f68e7d8e41a in QThread::exec (this=<optimized out>) at thread/qthread.cpp:531
#6  0x00007f68e7d8fbc2 in QThreadPrivate::start (arg=0x55cd72950630) at thread/qthread_unix.cpp:361
#7  0x00007f68e6f276db in start_thread (arg=0x7f68cdacd700) at pthread_create.c:463
#8  0x00007f68e746988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7f68ce2ce700 (LWP 23785)):
#0  0x00007f68e745cbf9 in __GI___poll (fds=0x7f68c00049b0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007f68e1ccc5c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f68e1ccc6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f68e7fc515b in QEventDispatcherGlib::processEvents (this=0x7f68c0000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#4  0x00007f68e7f6664a in QEventLoop::exec (this=this@entry=0x7f68ce2cdda0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#5  0x00007f68e7d8e41a in QThread::exec (this=<optimized out>) at thread/qthread.cpp:531
#6  0x00007f68e7d8fbc2 in QThreadPrivate::start (arg=0x55cd728e6bf0) at thread/qthread_unix.cpp:361
#7  0x00007f68e6f276db in start_thread (arg=0x7f68ce2ce700) at pthread_create.c:463
#8  0x00007f68e746988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f68ceacf700 (LWP 23784)):
#0  0x00007fff3a38b635 in ?? ()
#1  0x00007f68e7478ea6 in __GI___clock_gettime (clock_id=clock_id@entry=1, tp=tp@entry=0x7f68ceaceae0) at ../sysdeps/unix/clock_gettime.c:115
#2  0x00007f68e7fc4a41 in qt_clock_gettime (ts=0x7f68ceaceae0, clock=<optimized out>) at kernel/qelapsedtimer_unix.cpp:111
#3  do_gettime (frac=<synthetic pointer>, sec=<synthetic pointer>) at kernel/qelapsedtimer_unix.cpp:166
#4  qt_gettime () at kernel/qelapsedtimer_unix.cpp:175
#5  0x00007f68e7fc3279 in QTimerInfoList::updateCurrentTime (this=this@entry=0x7f68c8004cf0) at kernel/qtimerinfo_unix.cpp:91
#6  0x00007f68e7fc3855 in QTimerInfoList::timerWait (this=0x7f68c8004cf0, tm=...) at kernel/qtimerinfo_unix.cpp:388
#7  0x00007f68e7fc4e9e in timerSourcePrepareHelper (timeout=0x7f68ceaceba4, src=<optimized out>) at kernel/qeventdispatcher_glib.cpp:132
#8  timerSourcePrepare (source=<optimized out>, timeout=0x7f68ceaceba4) at kernel/qeventdispatcher_glib.cpp:165
#9  0x00007f68e1ccbb28 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x00007f68e1ccc4fb in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x00007f68e1ccc6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x00007f68e7fc515b in QEventDispatcherGlib::processEvents (this=0x7f68c8000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#13 0x00007f68e7f6664a in QEventLoop::exec (this=this@entry=0x7f68ceaced70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#14 0x00007f68e7d8e41a in QThread::exec (this=this@entry=0x7f68e93fdd80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:531
#15 0x00007f68e9186015 in QDBusConnectionManager::run (this=0x7f68e93fdd80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178
#16 0x00007f68e7d8fbc2 in QThreadPrivate::start (arg=0x7f68e93fdd80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:361
#17 0x00007f68e6f276db in start_thread (arg=0x7f68ceacf700) at pthread_create.c:463
#18 0x00007f68e746988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f68d784f700 (LWP 23783)):
#0  0x00007f68e745cbf9 in __GI___poll (fds=0x7f68d784ecb8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007f68dabeb747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007f68dabed36a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007f68d8dea32a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x00007f68e7d8fbc2 in QThreadPrivate::start (arg=0x55cd728e5e20) at thread/qthread_unix.cpp:361
#5  0x00007f68e6f276db in start_thread (arg=0x7f68d784f700) at pthread_create.c:463
#6  0x00007f68e746988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f68eaff6e80 (LWP 23782)):
[KCrash Handler]
#6  AlarmTypeRadioWidget::alarmType (this=0x0) at ./resources/kalarm/shared/alarmtyperadiowidget.cpp:59
#7  0x000055cd715cf5c5 in KAlarmResource::applyConfigurationChanges (this=0x55cd7293a780) at ./resources/kalarm/kalarm/kalarmresource.cpp:73
#8  0x00007f68ea4dcb92 in Akonadi::SingleFileResourceBase::<lambda()>::operator() (__closure=0x55cd72952490) at ./resources/shared/singlefileresource/singlefileresourcebase.cpp:51
#9  QtPrivate::FunctorCall<QtPrivate::IndexesList<>, QtPrivate::List<>, void, Akonadi::SingleFileResourceBase::SingleFileResourceBase(const QString&)::<lambda()> >::call (arg=<optimized out>, f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:146
#10 QtPrivate::Functor<Akonadi::SingleFileResourceBase::SingleFileResourceBase(const QString&)::<lambda()>, 0>::call<QtPrivate::List<>, void> (arg=<optimized out>, f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:256
#11 QtPrivate::QFunctorSlotObject<Akonadi::SingleFileResourceBase::SingleFileResourceBase(const QString&)::<lambda()>, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=<optimized out>, this_=0x55cd72952480, r=<optimized out>, a=<optimized out>, ret=<optimized out>) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:439
#12 0x00007f68e7f97f3f in QtPrivate::QSlotObjectBase::call (a=0x7fff3a36b690, r=0x55cd7293a780, this=0x55cd72952480) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394
#13 QMetaObject::activate (sender=0x55cd7293a780, signalOffset=<optimized out>, local_signal_index=<optimized out>, argv=<optimized out>) at kernel/qobject.cpp:3759
#14 0x00007f68ea2b1433 in Akonadi__ControlAdaptor::qt_static_metacall (_a=0x7fff3a36b7e0, _id=6, _c=QMetaObject::InvokeMetaMethod, _o=0x7f68c0005150) at ./obj-x86_64-linux-gnu/src/agentbase/controladaptor.moc:174
#15 Akonadi__ControlAdaptor::qt_metacall (this=0x7f68c0005150, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0x7fff3a36b7e0) at ./obj-x86_64-linux-gnu/src/agentbase/controladaptor.moc:175
#16 0x00007f68e9191128 in QDBusConnectionPrivate::deliverCall (this=this@entry=0x7f68c8003f10, object=object@entry=0x7f68c0005150, msg=..., metaTypes=..., slotIdx=<optimized out>) at qdbusintegrator.cpp:991
#17 0x00007f68e9195f80 in QDBusConnectionPrivate::activateCall (this=this@entry=0x7f68c8003f10, object=0x7f68c0005150, flags=flags@entry=273, msg=...) at qdbusintegrator.cpp:894
#18 0x00007f68e919683c in QDBusConnectionPrivate::activateCall (msg=..., flags=273, object=<optimized out>, this=0x7f68c8003f10) at qdbusintegrator.cpp:843
#19 QDBusConnectionPrivate::activateObject (this=0x7f68c8003f10, node=..., msg=..., pathStartPos=<optimized out>) at qdbusintegrator.cpp:1477
#20 0x00007f68e9198f1e in QDBusActivateObjectEvent::placeMetaCall (this=0x7f68c802aea0) at qdbusintegrator.cpp:1597
#21 0x00007f68e7f98992 in QObject::event (this=0x55cd7293a780, e=<optimized out>) at kernel/qobject.cpp:1249
#22 0x00007f68e8a6b8ac in QApplicationPrivate::notify_helper (this=this@entry=0x55cd728c9dc0, receiver=receiver@entry=0x55cd7293a780, e=e@entry=0x7f68c802aea0) at kernel/qapplication.cpp:3752
#23 0x00007f68e8a72e40 in QApplication::notify (this=0x7fff3a36c040, receiver=0x55cd7293a780, e=0x7f68c802aea0) at kernel/qapplication.cpp:3499
#24 0x00007f68e7f68328 in QCoreApplication::notifyInternal2 (receiver=0x55cd7293a780, event=0x7f68c802aea0) at kernel/qcoreapplication.cpp:1061
#25 0x00007f68e7f684fe in QCoreApplication::sendEvent (receiver=<optimized out>, event=event@entry=0x7f68c802aea0) at kernel/qcoreapplication.cpp:1451
#26 0x00007f68e7f6ae87 in QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x55cd728c7b40) at kernel/qcoreapplication.cpp:1800
#27 0x00007f68e7f6b428 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1654
#28 0x00007f68e7fc5b23 in postEventSourceDispatch (s=0x55cd7291f6d0) at kernel/qeventdispatcher_glib.cpp:276
#29 0x00007f68e1ccc417 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x00007f68e1ccc650 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#31 0x00007f68e1ccc6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#32 0x00007f68e7fc513f in QEventDispatcherGlib::processEvents (this=0x55cd7292f2e0, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#33 0x00007f68e7f6664a in QEventLoop::exec (this=this@entry=0x7fff3a36bfa0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#34 0x00007f68e7f6f800 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1364
#35 0x00007f68ea29777d in Akonadi::ResourceBase::init (r=0x55cd7293a780) at ./src/agentbase/resourcebase.cpp:608
#36 0x000055cd715d5cf3 in Akonadi::ResourceBase::init<KAlarmResource> (argc=<optimized out>, argv=<optimized out>) at /usr/include/KF5/AkonadiAgentBase/resourcebase.h:199
#37 0x00007f68e7369b97 in __libc_start_main (main=0x55cd715c8e50 <main(int, char**)>, argc=3, argv=0x7fff3a36c168, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff3a36c158) at ../csu/libc-start.c:310
#38 0x000055cd715c8e8a in _start ()




KDE Neon 64 Bit On Kernel 5.1, 430 nVidia Driver
Asus 970 Gaming/Aura, AMD FX 6300, 16Gig DDR3,
Samsung 120Gig 850 EVO, AOC 29" Ultra Wide 2560x1080, nVidia 750Ti,
USB 3 Card, Drives 2TB, 1.5TB, 1TB / 750Gig, 500Gig
djarvie
KDE Developer
Posts
103
Karma
0
OS

Re: Kalarm not installing akonadi

Tue May 28, 2019 9:17 am
For the record, the bug reported by mrgrimm has already been fixed - see https://bugs.kde.org/show_bug.cgi?id=407544. The fix will be included in KDE Applications 19.04.2 due to be released on 6th June.


KAlarm author
djarvie
KDE Developer
Posts
103
Karma
0
OS

Re: Kalarm not installing akonadi

Tue May 28, 2019 9:30 am
The original Neon issue reported by rwayland should be dealt with if https://bugs.kde.org/show_bug.cgi?id=407827 ("Neon developer live image doesn't contain development packages") gets fixed.


KAlarm author
User avatar
mrgrimm
Registered Member
Posts
64
Karma
0
OS

Re: Kalarm not installing akonadi

Tue May 28, 2019 10:27 am
djarvie wrote:For the record, the bug reported by mrgrimm has already been fixed - see https://bugs.kde.org/show_bug.cgi?id=407544. The fix will be included in KDE Applications 19.04.2 due to be released on 6th June.


thanks for the info. i only reinstalled kalarm to to help you guys out, cause it ended up not being what i need.


KDE Neon 64 Bit On Kernel 5.1, 430 nVidia Driver
Asus 970 Gaming/Aura, AMD FX 6300, 16Gig DDR3,
Samsung 120Gig 850 EVO, AOC 29" Ultra Wide 2560x1080, nVidia 750Ti,
USB 3 Card, Drives 2TB, 1.5TB, 1TB / 750Gig, 500Gig


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], kesang, Yahoo [Bot]