Mageia forum

Hello,

My system: Mageia 8 Plasma. I use Kmail to download my email from POP3 accounts. My email is locally stored in folders (inbox, sent, drafts, trash + a set of other folders) on a separate (permanently mounted) data partition with a symlink in the default location ~/.local/share/local-mail.

This set-up worked fine for many years. But this morning I couldn't read my email in the Local Folders. Only the headers (subject, date, sender) were visible, not de content of the message.
Also, KMail wasn't able to store new email from my POP3 accounts. And I couldn't delete any message in Local Folders, nor move any message to another folder.

All email messages are still present in the directory where they were stored. I think that this is an Akonadi database issue.

I tried to fix this by deleting everything in ~/.local ~/.kde ~/.cache and ~/.config (after logout, as root) and let the system after a reboot recreate these directories, but without succes.
Akonadictl status tells that Akonadi is running, but Akonadi doesn't "import" the email in Local Folders into its database.

Then I created a new user account, and configured KMail there, but that wasn't succesful either.

Access to my email is very important. Please, can you help me to fix this problem?

seems a bug report has already been filed and a fix proposed

https://bugs.mageia.org/show_bug.cgi?id=29359.

you are welcome to assist in the test of this proposed fix.

i have problem with kaddrss book and knotes, after upgrade.
i suppose the same akonady problem

I dont know if it is needed, but did you reboot, or at least log out and in?

More exactly how is the problem expressed?

Is there a way to let the database do a consistency check / repair of some kind?

i Morgano, i have try to restart akonady many time, restart x interface and restart computer.

Knote have lose the information, nb inside the directory ./local/share/note, the files are present.
Don't permit crating new note,

kaddress dont permit to add new contact , by importing file vcf, or creating by kaddress, or kcontact

have try to start by console for look about log, but no log about

Enrico

What is the output from in terminal running
rpm -qa | grep 5.15.2-4

morgano wrote:Is there a way to let the database do a consistency check / repair of some kind?

Yes via

Code: Select all

akonadictl fsck

but that won't help until the Qt update is installed because akonadi will still have issues with mariadb version detection.

doktor5000 wrote:

morgano wrote:Is there a way to let the database do a consistency check / repair of some kind?

Yes via

Code: Select all

akonadictl fsck

Done,
....... a lots or row and :
Making sure virtual search resource and collections exist
Consistency check done.

Nothing is change, can''t add new note or new contact

Enrico

bitit wrote:

morgano wrote:What is the output from in terminal running

Code: Select all

rpm -qa |  grep 5.15.2-4
a lot of    -5.15.2-4.5.mga8

Ah. You should have -4.6.
But wait a bit more because -4.7 and also -4.8 are building.
http://pkgsubmit.mageia.org/
and then your mirror need to sync https://mirrors.mageia.org/status

Then install from updates testing repo.
See https://wiki.mageia.org/en/Enabling_the_Testing_media

from MCC i have removed all repository and reload new, after i have upgrade the new repository but, i haven't upgrade to install;
i have selected tainted and back port also .

Enrico

As morgano already told you, you need to wait a little bit as the packages where still building. The build finished only some time ago and now it also needs some time until all mirrors populate as the tier 1 mirrors got the package less then 1 hour ago...
If you can't wait, then you need to chose a tier 1 mirror. https://mirrors.mageia.org/ and https://mirrors.mageia.org/status

And why did you enable backports? That is not what morgano advised. Testing is something completely different than backports...

benmc wrote:seems a bug report has already been filed and a fix proposed

https://bugs.mageia.org/show_bug.cgi?id=29359.

you are welcome to assist in the test of this proposed fix.

Thanks benmc, for your quick response and the link to the bug report!
It's great that a fix is already available in testing.