Hi,
since about December 16th kmail isn't working properly, because akonadi is broken.
Thousands of:
org.kde.pim.akonadicore: Got a stale notification for an item which was already removed. 155786 ""
TW isn't in the state of a rolling release, more of a rolling desaster, given the other issues.
Regards,
Alexander
On Friday, 20 January 2017 09:57:05 CET AW wrote:
Hi,
since about December 16th kmail isn't working properly, because akonadi is broken.
Thousands of:
org.kde.pim.akonadicore: Got a stale notification for an item which was already removed. 155786 ""
TW isn't in the state of a rolling release, more of a rolling desaster, given the other issues.
Regards,
Alexander
whats your setup - imap?
Il giorno Fri, 20 Jan 2017 09:57:05 +0100 AW alexander.willand@t-online.de ha scritto:
since about December 16th kmail isn't working properly, because akonadi is broken.
Can you give more details about the problem? "Broken" isn't particularly informative.
org.kde.pim.akonadicore: Got a stale notification for an item which
was already removed. 155786 ""
These are a red herring, and not particularly related to the issue, whatever it is.
Am Freitag, 20. Januar 2017, 10:51:31 CET schrieb Luca Beltrame:
Il giorno Fri, 20 Jan 2017 09:57:05 +0100
AW alexander.willand@t-online.de ha scritto:
since about December 16th kmail isn't working properly, because akonadi is broken.
Can you give more details about the problem? "Broken" isn't particularly informative.
org.kde.pim.akonadicore: Got a stale notification for an item which
was already removed. 155786 ""
These are a red herring, and not particularly related to the issue, whatever it is.
I gave a full account here:
https://bugzilla.opensuse.org/show_bug.cgi?id=1017147
... and in my various emails to this list during the last five weeks.
My kmail installation here isn't small: Some accounts, partially imap, partially pop3, large mailinglist (orgmode, emacs, tw), some GB weight.
If you walk through the mailinglist of the last five weeks, there are many postings regarding different issues with kmail. I'm not convinced that they have been solved. But if it should be only me, obviously it were an error in my installation -- which worked until the December update of akonadi from v. 16.08 to 16.12.
Regards,
Alexander
In data venerdì 20 gennaio 2017 10:51:31, Luca Beltrame ha scritto:
Il giorno Fri, 20 Jan 2017 09:57:05 +0100
AW alexander.willand@t-online.de ha scritto:
since about December 16th kmail isn't working properly, because akonadi is broken.
Can you give more details about the problem? "Broken" isn't particularly informative.
org.kde.pim.akonadicore: Got a stale notification for an item which
was already removed. 155786 ""
These are a red herring, and not particularly related to the issue, whatever it is.
Do you recall this thread on kde-opensuse.org: [opensuse-kde] A technical inquiry about failures of a new installation of KDE PIM5 in 42.2 fresh install Data: 8/1/2017 20:26 The behavior he describes was also the one another user on the German mailing list was writing about. He solved at the time taking the KDE upgrade from KDE stable repos, saying that (under Leap 42.2) the problem has then ceased.
Am Freitag, 20. Januar 2017, 11:28:44 CET schrieb stakanov:
In data venerdì 20 gennaio 2017 10:51:31, Luca Beltrame ha scritto:
Il giorno Fri, 20 Jan 2017 09:57:05 +0100
AW alexander.willand@t-online.de ha scritto:
since about December 16th kmail isn't working properly, because akonadi is broken.
Can you give more details about the problem? "Broken" isn't particularly informative.
org.kde.pim.akonadicore: Got a stale notification for an item which
was already removed. 155786 ""
These are a red herring, and not particularly related to the issue, whatever it is.
Do you recall this thread on kde-opensuse.org: [opensuse-kde] A technical inquiry about failures of a new installation of KDE PIM5 in 42.2 fresh install Data: 8/1/2017 20:26 The behavior he describes was also the one another user on the German mailing list was writing about. He solved at the time taking the KDE upgrade from KDE stable repos, saying that (under Leap 42.2) the problem has then ceased.
There is also a bug report on the kde bugzilla:
https://bugs.kde.org/show_bug.cgi?id=374734
-
AW -
Luca Beltrame -
nicholas -
stakanov