beq-osleap@linux-91w7:~> akonadictl start
org.kde.pim.akonadictl: Starting Akonadi Server...
org.kde.pim.akonadicontrol: Service org.freedesktop.Akonadi.Control.lock already registered, terminating now.
Error: akonadi_control was started but didn't register at D-Bus session bus.
Make sure your system is set up correctly!
beq-osleap@linux-91w7:~>
As I needed my mail, calendar, etc, I set the system back with # snapper rollback.
It looks like openSUSE-SLE-15.4-2022-2017 (1) - security update for MariaDB - is the culprit. I started a new upgrade and ticked it off. Kontact/KMail/Akonadi is still working.
The patch you’ve mentioned (openSUSE-SLE-15.4-2022-2017) is addressed at IceWM …
I suspect that, you mean the patch “openSUSE-SLE-15.4-2022-2107” …
What you can do is, to forcibly re-install the patch –
First, “zypper verify
” the ensure that everything is more or less OK. - And, check the Repositories you’re using – should be the Leap 15.4 Respository set.
Also “rpm --verify --all
”. - Then, “zypper install --type patch openSUSE-SLE-15.4-2022-2107
”. - And, for good measure: “zypper install --type patch openSUSE-SLE-15.4-2022-731
”
But, before you do that, you’ll need to check the D-Bus service –
> systemctl status --user dbus.service
You may have to restart the systemd User dbus.service.
Also, take a look in ‘~/.local/share/akonadi/’ for any lock files.
Also, check that, a link exists pointing to ‘/run/user/1000/akonadi/’ – assuming that, your user has the UID 1000.
In other words, the Akonadi Control D-Bus services are restarted with another offset within the list of D-Bus services.
[HR][/HR]Looking at the error message being presented on your system when attempting to (re)start Akonadi, it seems that, the RPM packages related to Akonadi and KDE Plasma in general are missing some components or, some of the components have been corrupted or, you’ve picked up some components from a repository which is not compatible with Leap 15.4.
Please, recheck your Leap 15.4 repositories – a minimal list of URLs is –
@ dcurtisfra:
Thanks or your detailed response, which certainly is valid for others. As I said before, akonadi was working again after a # snapper rollback. Now I updated everything including MariaDB, and everything is working well. Unfortunately data from the journal is already excluded, as its size is constrained to 100M. It might have been a lock as you already guessed.
The repolist is ok. I used plasma-pk-updates as well, but did not see any error messages.
The history: I had serious problems with KMail during Leap 15.3. My 2 Imap accounts constantly went offline. $ akonadictl fsck or akonadictl vacuum did not help. Before trying a fresh install, I created another test user, and when everything was well, I switched over. No other intervention since then.