[opensuse-kde] Akonadi google and Tumbleweed
Since 10 days, the resource for gmail is constantly crashing. Yes I'm using my complete gmail address for the logging. I've seen in factory-ml that normally a patch should have been forwarded from upstream. Is it normal to still be crashing ? org.kde.pim.akonadiserver: Removed results: 0 Received signal 11 SEGV_MAPERR 000000000004 org.kde.pim.akonadiserver: Subscriber "AgentBaseChangeRecorder - 94635697647456" disconnected org.kde.pim.akonadiserver: Shutting down "akonadi_imap_resource_8" ... org.kde.pim.akonadiserver: Unregistering search instance "akonadi_imap_resource_8" org.kde.pim.akonadiserver: Lost connection to resource "org.freedesktop.Akonadi.Resource.akonadi_imap_resource_8" , discarding cached interface org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/ akonadi_imap_resource" stopped unexpectedly ( "Process crashed" ) org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_imap_resource' crashed! 1 restarts left. org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f9d1017bf80) ) org.kde.pim.akonadiserver: Database "bf_akonadi" opened using driver "QPSQL" org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f9d1017bf80) identified as "AgentBaseChangeRecorder - 94625115979872" org.kde.pim.akonadiserver: SearchManager::registerInstance( "akonadi_imap_resource_8" ) org.kde.pim.akonadiserver: Registering search instance "akonadi_imap_resource_8" [0904/103016.230346:WARNING:stack_trace_posix.cc(699)] Failed to open file: / tmp/.glxMjGxs (deleted) Error: No such file or directory [0904/103016.230434:WARNING:stack_trace_posix.cc(699)] Failed to open file: / ioda/home/bruno/#4668063 (deleted) Error: No such file or directory LOGIN CALLBACK in libCVP11LCB: CK_RV CB_Initialize(CK_CONTEXT_PTR, CK_C_INITIALIZE_ARGS_PTR, CK_ULONG_PTR) My system resumé openSUSE Tumbleweed - 20180831 Linux 4.18.5-1-default x86_64 GNU/Linux, nvidia: 390.87 Qt: 5.11.1, KDE Frameworks: 5.49.0, Plasma: 5.13.4, kmail2 5.9.0 Akonadi using a central postgresql10 database. All mails parts stored inside the db. Would delete (again) of this account and complete recreation would help ? -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe supporter GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Op dinsdag 4 september 2018 10:51:54 CEST schreef Bruno Friedmann:
Since 10 days, the resource for gmail is constantly crashing.
Yes I'm using my complete gmail address for the logging.
I've seen in factory-ml that normally a patch should have been forwarded from upstream. Is it normal to still be crashing ?
org.kde.pim.akonadiserver: Removed results: 0 Received signal 11 SEGV_MAPERR 000000000004 org.kde.pim.akonadiserver: Subscriber "AgentBaseChangeRecorder - 94635697647456" disconnected org.kde.pim.akonadiserver: Shutting down "akonadi_imap_resource_8" ... org.kde.pim.akonadiserver: Unregistering search instance "akonadi_imap_resource_8" org.kde.pim.akonadiserver: Lost connection to resource "org.freedesktop.Akonadi.Resource.akonadi_imap_resource_8" , discarding cached interface org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/ akonadi_imap_resource" stopped unexpectedly ( "Process crashed" ) org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_imap_resource' crashed! 1 restarts left. org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f9d1017bf80) ) org.kde.pim.akonadiserver: Database "bf_akonadi" opened using driver "QPSQL" org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f9d1017bf80) identified as "AgentBaseChangeRecorder - 94625115979872" org.kde.pim.akonadiserver: SearchManager::registerInstance( "akonadi_imap_resource_8" ) org.kde.pim.akonadiserver: Registering search instance "akonadi_imap_resource_8" [0904/103016.230346:WARNING:stack_trace_posix.cc(699)] Failed to open file: / tmp/.glxMjGxs (deleted) Error: No such file or directory [0904/103016.230434:WARNING:stack_trace_posix.cc(699)] Failed to open file: / ioda/home/bruno/#4668063 (deleted) Error: No such file or directory LOGIN CALLBACK in libCVP11LCB: CK_RV CB_Initialize(CK_CONTEXT_PTR, CK_C_INITIALIZE_ARGS_PTR, CK_ULONG_PTR)
My system resumé
openSUSE Tumbleweed - 20180831 Linux 4.18.5-1-default x86_64 GNU/Linux, nvidia: 390.87 Qt: 5.11.1, KDE Frameworks: 5.49.0, Plasma: 5.13.4, kmail2 5.9.0 Akonadi using a central postgresql10 database. All mails parts stored inside the db.
Would delete (again) of this account and complete recreation would help ? I rebuilt mine, and found that one issue is that auth is set to Gmail, where it should be PLAIN. Before rebuilding the account, first do akonadictl fsck akonadictl vacuum. If you keep getting 'unreferenced' messages, check whether ~/.local/share/ akonadi/file_lost+found exists, if not create it
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Hi Gertjan
I rebuilt mine, and found that one issue is that auth is set to Gmail, where it should be PLAIN.
What do you mean be this ? I've seen a token in the password field in the account configuration.
Before rebuilding the account, first do akonadictl fsck akonadictl vacuum. OMG those are done regularly almost once a week for fsck and once a month for vaccum
If you keep getting 'unreferenced' messages, check whether ~/.local/share/ akonadi/file_lost+found exists, if not create it
This folder was not existing but I don't know if it would be used, as every part of mail are directly stored in my database, so I don't have the insane hell's of files in ~/.local/share/akonadi/file_db_data ;-) Why because my db (PostgreSQL) can and love to do that ;-) -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe supporter GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Dienstag, 4. September 2018, 16:55:25 schrieb Bruno Friedmann:
If you keep getting 'unreferenced' messages, check whether ~/.local/share/ akonadi/file_lost+found exists, if not create it
This folder was not existing but I don't know if it would be used, as every part of mail are directly stored in my database, so I don't have the insane hell's of files in ~/.local/share/akonadi/file_db_data ;-)
That shouldn't be necessary anyway. IIANM, lost+found is actually created by "akonadictl fsck" when it finds files (in file_db_data) that are no longer referenced. These files are moved to lost+found then, and you normally can just delete that folder. It should not be used at all by akonadi itself. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Op dinsdag 4 september 2018 17:02:32 CEST schreef Wolfgang Bauer:
Am Dienstag, 4. September 2018, 16:55:25 schrieb Bruno Friedmann:
If you keep getting 'unreferenced' messages, check whether ~/.local/share/ akonadi/file_lost+found exists, if not create it
This folder was not existing but I don't know if it would be used, as every part of mail are directly stored in my database, so I don't have the insane hell's of files in ~/.local/share/akonadi/file_db_data ;-)
That shouldn't be necessary anyway.
IIANM, lost+found is actually created by "akonadictl fsck" when it finds files (in file_db_data) that are no longer referenced. These files are moved to lost+found nope, ~/.local/share/akonadi/file_lost+found was needed. Nothing created by akonadi . After creating the folder the fsck actually worked. I decided to empty the folder instead of removing it. Should I file a bug, or am I seeing some exception caused by older configs?
then, and you normally can just delete that folder. It should not be used at all by akonadi itself.
Kind Regards, Wolfgang
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Dienstag, 4. September 2018, 19:24:45 schrieb Knurpht-openSUSE:
nope, ~/.local/share/akonadi/file_lost+found was needed. Nothing created by akonadi .
It's not needed (or used) by akonadi for its operation. But akonadictl fsck "backups" unreferenced (i.e. stale) cache files there, as mentioned. If "akonadictl fsck" doesn't create the folder automatically and fails therefore, it would be a bug and should be reported at bugs.kde.org (if that's still the case with the latest/current versions). I'm perfectly sure it did create the folder in the past, but it's been a while since I last ran it. (I don't see a need to regularly run it here, or actually at all)
or am I seeing some exception caused by older configs?
I don't think the config can have any influence on this. And it's especially rather not caused by "older configs" , as "akonadictl fsck" already used that folder as sink for stale cache files in 4.x even. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Dienstag, 4. September 2018, 10:51:54 schrieb Bruno Friedmann:
I've seen in factory-ml that normally a patch should have been forwarded from upstream. Is it normal to still be crashing ?
That fix is not in Tumbleweed yet, should be in the next snapshot though: https://build.opensuse.org/request/show/631927 No idea if your crash would be fixed by that though, as you didn't post a backtrace. The output you provided does mention NotificationSubscriber though, so it's probably indeed the same.
Would delete (again) of this account and complete recreation would help ?
If your crash is https://bugs.kde.org/show_bug.cgi?id=397239, removing your search folders may help. Quoting from (the duplicate) https://bugs.kde.org/show_bug.cgi?id=397874:
Oh, looks like the crash is triggered by search updates. You could try removing your search folders temporarily until a fix lands, that should stop the server from crashing.
Your output also does mention SearchManager... Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On mardi, 4 septembre 2018 15.52:29 h CEST Wolfgang Bauer wrote:
Am Dienstag, 4. September 2018, 10:51:54 schrieb Bruno Friedmann:
I've seen in factory-ml that normally a patch should have been forwarded from upstream. Is it normal to still be crashing ?
That fix is not in Tumbleweed yet, should be in the next snapshot though: https://build.opensuse.org/request/show/631927
oh cool let's wait this one.
No idea if your crash would be fixed by that though, as you didn't post a backtrace. The output you provided does mention NotificationSubscriber though, so it's probably indeed the same. Yeah I know I've removed all the akonadi,kmail and related debuginfo package before the 18.08 upgrade to speed up things a bit (I'm also user of 10000's texlive package :-))
Would delete (again) of this account and complete recreation would help ?
If your crash is https://bugs.kde.org/show_bug.cgi?id=397239, removing your search folders may help.
Then it will be the fourth time this year ;-) I've to dig into scripting this things.
Quoting from (the duplicate) https://bugs.kde.org/show_bug.cgi?id=397874:
Oh, looks like the crash is triggered by search updates. You could try removing your search folders temporarily until a fix lands, that should stop the server from crashing.
Your output also does mention SearchManager...
Kind Regards, Wolfgang
I will wait the update, and check if there's a better behavior. If not I will reinstall all debuginfo to grab a nice complete backtrace. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe supporter GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Dienstag, 4. September 2018, 16:50:56 schrieb Bruno Friedmann:
Yeah I know I've removed all the akonadi,kmail and related debuginfo package before the 18.08 upgrade to speed up things a bit (I'm also user of 10000's texlive package :-))
Even without debuginfo packages, a backtrace should at least indicate whether the crash is similar to the one in the mentioned KDE bug report.
If your crash is https://bugs.kde.org/show_bug.cgi?id=397239, removing your search folders may help.
Then it will be the fourth time this year ;-) I've to dig into scripting this things.
Well, it would only be a temporary workaround to (hopefully) avoid the crash for now (it would probably crash again if you create a new search folder though). It should not be necessary after installing the fixed package, if that is your problem.
I will wait the update, and check if there's a better behavior.
If you want to try it right now, you could install the akonadi-server package from KDE:Applications. I wouldn't really recommend to add the repo though, just download and install that one package manually. But unless there's some problem in openQA, the new snapshot might arrive today or tomorrow anyway I suppose. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Would delete (again) of this account and complete recreation would help ?
So as followup, the last upgrade of TW doesn't cure that's damn windows asking google to authorized akonadi resource. I've gone the hard way, delete all google resource related, fsck, vacuum cleanup index folder remove any kwallet entry, and all configuration file that would contain an entry. Recreate the account from akonadiconsole, and for the moment it seems to work again, moving message to folders and so too. Time will say for how long ;-) -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe supporter GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Sonntag, 9. September 2018, 17:26:27 schrieb Bruno Friedmann:
So as followup, the last upgrade of TW doesn't cure that's damn windows asking google to authorized akonadi resource.
Of course not. It only contains a fix for a possible crash, that's actually not specific to gmail/goofle authorization anyway (it's apparently triggered by search folders e.g.). https://bugs.kde.org/show_bug.cgi?id=397239 Regarding the "google auth window popping up again and again" I am aware of two "problems": - https://bugs.kde.org/show_bug.cgi?id=396890 You need to use xxx@gmail.com as username, not just xxx. This should be fixed in 18.08.1 (that's currently in staging), although the last comment suggests it might not. - The authentification method (in the account settings) should be set to "PLAIN", not "GMail". Both problems (and workarounds) were mentioned in the recent discussion on opensuse-factory as well, btw. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On lundi, 10 septembre 2018 10.34:11 h CEST Wolfgang Bauer wrote:
Am Sonntag, 9. September 2018, 17:26:27 schrieb Bruno Friedmann:
So as followup, the last upgrade of TW doesn't cure that's damn windows asking google to authorized akonadi resource.
Of course not. It only contains a fix for a possible crash, that's actually not specific to gmail/goofle authorization anyway (it's apparently triggered by search folders e.g.). https://bugs.kde.org/show_bug.cgi?id=397239
Regarding the "google auth window popping up again and again" I am aware of two "problems":
- https://bugs.kde.org/show_bug.cgi?id=396890 You need to use xxx@gmail.com as username, not just xxx. This should be fixed in 18.08.1 (that's currently in staging), although the last comment suggests it might not.
- The authentification method (in the account settings) should be set to "PLAIN", not "GMail".
Both problems (and workarounds) were mentioned in the recent discussion on opensuse-factory as well, btw.
Kind Regards, Wolfgang
And those 2 were exactly how the account was setup full gmail.com address as user plain and imap with ssl on 993 (smtp on 587 startls) Now after recreating it exactly the same, it works, which is frustrating when you try to understand which detail is wrong :-) -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe supporter GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
participants (3)
-
Bruno Friedmann -
Knurpht-openSUSE -
Wolfgang Bauer