[opensuse-factory] Kontact/kmail crashing often
Hi Is anyone else getting this problem? Kmail or Kontact crash at will and sometimes crashes out using the crash handler and sometimes just dies without it. It seems to happen when you access an email, read or unread, i've not had it crash for any other action so far. I will log a bug if it seems to be happening to others as well. I was going to delete the akonadi database to see if it makes any difference on a fresh database as there are loads of duplicates in it but i'm fed up with recreating the kmail settings etc, is there anyway i can remove the data without removing the settings? Regards Ian -- opensuse:tumbleweed:20171028 Qt: 5.9.2 KDE Frameworks: 5.39.0 KDE Plasma: 5.11.2 kwin 5.11.2 kmail2 5.6.2 akonadiserver 5.6.2 Kernel: 4.13.9-1-default Nouveau: 1.0.15_1.2 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Dienstag, 31. Oktober 2017, 10:25:43 CET schrieb ianseeks:
Is anyone else getting this problem? Kmail or Kontact crash at will and sometimes crashes out using the crash handler and sometimes just dies without it. It seems to happen when you access an email, read or unread, i've not had it crash for any other action so far.
Yes, I'm struggeling with Kmail and crashes as well.
I will log a bug if it seems to be happening to others as well.
Sorry to say, but unfortunately this gives not much response (see below)
I was going to delete the akonadi database to see if it makes any difference on a fresh database as there are loads of duplicates in it but i'm fed up with recreating the kmail settings etc, is there anyway i can remove the data without removing the settings?
Rename ~/.local/share/akonadi , that should force a rebuild. Having done the same, Kmail crashes on start. I opened a bug report with severity critical [1] 3 weeks ago, but did not even get a 'Hello' response. I first thought the problem is related to the switch from mysql to postgres, but I found that the error is independent from the database backend used Good luck Axel [1] https://bugs.kde.org/show_bug.cgi?id=385532 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday, 31 October 2017 09:32:34 GMT Axel Braun wrote:
Am Dienstag, 31. Oktober 2017, 10:25:43 CET schrieb ianseeks:
Is anyone else getting this problem? Kmail or Kontact crash at will and sometimes crashes out using the crash handler and sometimes just dies without it. It seems to happen when you access an email, read or unread, i've not had it crash for any other action so far.
Yes, I'm struggeling with Kmail and crashes as well. Thanks for the reply, i'm glad its not just me.
I will log a bug if it seems to be happening to others as well.
Sorry to say, but unfortunately this gives not much response (see below) This is my second email about it too.
I was going to delete the akonadi database to see if it makes any difference on a fresh database as there are loads of duplicates in it but i'm fed up with recreating the kmail settings etc, is there anyway i can remove the data without removing the settings?
Rename ~/.local/share/akonadi , that should force a rebuild. That also seems to destroy the current kmail/contact settings as well, i want to be able to do it without having to recreate them.
Having done the same, Kmail crashes on start. I opened a bug report with severity critical [1] 3 weeks ago, but did not even get a 'Hello' response. I first thought the problem is related to the switch from mysql to postgres, but I found that the error is independent from the database backend used
Good luck Axel [1] https://bugs.kde.org/show_bug.cgi?id=385532 I'll add to your bug when it crashes again, i've started in the cli to hopefully get something useful
-- opensuse:tumbleweed:20171028 Qt: 5.9.2 KDE Frameworks: 5.39.0 KDE Plasma: 5.11.2 kwin 5.11.2 kmail2 5.6.2 akonadiserver 5.6.2 Kernel: 4.13.9-1-default Nouveau: 1.0.15_1.2 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Il giorno Tue, 31 Oct 2017 10:32:34 +0100 Axel Braun <axel.braun@gmx.de> ha scritto:
'Hello' response. I first thought the problem is related to the switch from mysql to postgres, but I found that the error is independent from the database backend used
This is what I got from the developer: [13:01] <dvratil> einar77_work: looks like he did not wipe his setup properly - it's trying to setup the same resource twice due to the resource existing in configuration but not in the db [13:02] <dvratil> I'd suggest wiping ~/.local/share/akonadi as well as ~/.config/akonadi to make sure he starts with a clean setup If that's not the case, please update the upstream report.
Am Dienstag, 31. Oktober 2017, 13:21:33 CET schrieb Luca Beltrame:
Il giorno Tue, 31 Oct 2017 10:32:34 +0100
Axel Braun <axel.braun@gmx.de> ha scritto:
'Hello' response. I first thought the problem is related to the switch from mysql to postgres, but I found that the error is independent from the database backend used
This is what I got from the developer:
[13:01] <dvratil> einar77_work: looks like he did not wipe his setup properly - it's trying to setup the same resource twice due to the resource existing in configuration but not in the db [13:02] <dvratil> I'd suggest wiping ~/.local/share/akonadi as well as ~/.config/akonadi to make sure he starts with a clean setup
Thats from scratch scratch :-( with losing all settings. I will try this in a new account and let you know the result Cheers Axel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Gesendet: Dienstag, 31. Oktober 2017 um 13:21 Uhr Von: "Luca Beltrame" <lbeltrame@kde.org> An: opensuse-factory@opensuse.org Betreff: [opensuse-factory] Re: Kontact/kmail crashing often
Il giorno Tue, 31 Oct 2017 10:32:34 +0100 Axel Braun <axel.braun@gmx.de> ha scritto:
'Hello' response. I first thought the problem is related to the switch from mysql to postgres, but I found that the error is independent from the database backend used
This is what I got from the developer:
[13:01] <dvratil> einar77_work: looks like he did not wipe his setup properly - it's trying to setup the same resource twice due to the resource existing in configuration but not in the db [13:02] <dvratil> I'd suggest wiping ~/.local/share/akonadi as well as ~/.config/akonadi to make sure he starts with a clean setup
If that's not the case, please update the upstream report.
So, I've done as propsed and wiped the above directories. started akonadi and created resources. Very nice - KMail proposes on each new IMAP connection one of the former IMAP mailboxes - as well those ones I had deleted in beween. After some hours I went back to the PC to see how things are going. All mail was replicated. All Personas/Identities needed rework as folders for send mail /drafts etc were pointing to nonsense directories. HD light was heavily flickering (as in the problem 'runs into infinite loop - https://bugs.kde.org/show_bug.cgi?id=385532 ) so I shut down akonadi (Postgres DB did not shut down - https://bugs.kde.org/show_bug.cgi?id=386173 ) and restartet the PC. Now KMail crasehs immediately at start - Could not create collection outbox, resourceId: 2 This is similar to https://bugs.kde.org/show_bug.cgi?id=386175 Except that I dont find a resource 2: docb@T520:~/.config/akonadi> dir insgesamt 128 -rw-r--r-- 1 docb users 16 1. Nov 14:41 agent_config_akonadi_archivemail_agent_changes.dat -rw-r--r-- 1 docb users 37 1. Nov 10:04 agent_config_akonadi_contacts_resource_0 -rw-r--r-- 1 docb users 16 1. Nov 14:41 agent_config_akonadi_contacts_resource_0_changes.dat -rw-r--r-- 1 docb users 16 1. Nov 09:57 agent_config_akonadi_followupreminder_agent_changes.dat -rw-r--r-- 1 docb users 50 1. Nov 10:08 agent_config_akonadi_googlecontacts_resource_0 -rw-r--r-- 1 docb users 16 1. Nov 14:41 agent_config_akonadi_googlecontacts_resource_0_changes.dat -rw-r--r-- 1 docb users 41 1. Nov 14:42 agent_config_akonadi_imap_resource_0 -rw-r--r-- 1 docb users 16 1. Nov 14:41 agent_config_akonadi_imap_resource_0_changes.dat -rw-r--r-- 1 docb users 44 1. Nov 14:42 agent_config_akonadi_imap_resource_3 -rw-r--r-- 1 docb users 16 1. Nov 14:41 agent_config_akonadi_imap_resource_3_changes.dat -rw-r--r-- 1 docb users 43 1. Nov 14:42 agent_config_akonadi_imap_resource_4 -rw-r--r-- 1 docb users 16 1. Nov 14:41 agent_config_akonadi_imap_resource_4_changes.dat -rw-r--r-- 1 docb users 41 1. Nov 14:42 agent_config_akonadi_imap_resource_5 -rw-r--r-- 1 docb users 16 1. Nov 14:41 agent_config_akonadi_imap_resource_5_changes.dat -rw-r--r-- 1 docb users 47 1. Nov 14:42 agent_config_akonadi_imap_resource_7 -rw-r--r-- 1 docb users 16 1. Nov 14:41 agent_config_akonadi_imap_resource_7_changes.dat -rw-r--r-- 1 docb users 51 1. Nov 14:42 agent_config_akonadi_imap_resource_9 -rw-r--r-- 1 docb users 16 1. Nov 14:41 agent_config_akonadi_imap_resource_9_changes.dat -rw-r--r-- 1 docb users 32 1. Nov 14:42 agent_config_akonadi_indexing_agent -rw-r--r-- 1 docb users 16 1. Nov 09:57 agent_config_akonadi_indexing_agent_changes.dat -rw-r--r-- 1 docb users 51 1. Nov 09:57 agent_config_akonadi_maildir_resource_0 -rw-r--r-- 1 docb users 16 1. Nov 14:41 agent_config_akonadi_maildir_resource_0_changes.dat -rw-r--r-- 1 docb users 32 1. Nov 14:42 agent_config_akonadi_maildispatcher_agent -rw-r--r-- 1 docb users 16 1. Nov 14:41 agent_config_akonadi_maildispatcher_agent_changes.dat -rw-r--r-- 1 docb users 16 1. Nov 09:57 agent_config_akonadi_mailfilter_agent_changes.dat -rw-r--r-- 1 docb users 16 1. Nov 14:41 agent_config_akonadi_migration_agent_changes.dat -rw-r--r-- 1 docb users 16 1. Nov 09:57 agent_config_akonadi_newmailnotifier_agent_changes.dat -rw-r--r-- 1 docb users 16 1. Nov 14:41 agent_config_akonadi_notes_agent_changes.dat -rw-r--r-- 1 docb users 16 1. Nov 09:57 agent_config_akonadi_sendlater_agent_changes.dat -rw-r--r-- 1 docb users 2088 1. Nov 14:27 agentsrc -rw-r--r-- 1 docb users 221 1. Nov 14:42 akonadiconnectionrc -rw------- 1 docb users 177 1. Nov 14:42 akonadiserverrc any idea? Thanks Axel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 31 October 2017 at 10:25, ianseeks <bingmybong@btinternet.com> wrote:
Is anyone else getting this problem? Kmail or Kontact crash at will and sometimes crashes out using the crash handler and sometimes just dies without it. It >seems to happen when you access an email, read or unread, i've not had it crash for any other action so far.
Kontack crashes a lot for me too. Haven't I read here that it was related to the nouveau driver? I actually use this driver. But whatever the reason Kmail/Kontact crashes now, it feels to me as the continuation of a very long series of issues. I'm getting tired of if. Cheers, JFL -- Jean-François Lemaire -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday, 31 October 2017 09:53:55 GMT J. F. Lemaire wrote:
On 31 October 2017 at 10:25, ianseeks <bingmybong@btinternet.com> wrote:
Is anyone else getting this problem? Kmail or Kontact crash at will and sometimes crashes out using the crash handler and sometimes just dies without it. It >seems to happen when you access an email, read or unread, i've not had it crash for any other action so far.
Kontack crashes a lot for me too. Haven't I read here that it was related to the nouveau driver? I actually use this driver. But whatever the reason Kmail/Kontact crashes now, it feels to me as the continuation of a very long series of issues. I'm getting tired of if. That could be the connection, i'm using nouveau too. Maybe someone with more knowledge than us will give an answer.
Cheers, JFL
-- opensuse:tumbleweed:20171028 Qt: 5.9.2 KDE Frameworks: 5.39.0 KDE Plasma: 5.11.2 kwin 5.11.2 kmail2 5.6.2 akonadiserver 5.6.2 Kernel: 4.13.9-1-default Nouveau: 1.0.15_1.2 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Il giorno Tue, 31 Oct 2017 10:28:26 +0000 ianseeks <bingmybong@btinternet.com> ha scritto:
That could be the connection, i'm using nouveau too. Maybe someone with more knowledge than us will give an answer.
If you use Noveau, yes, it *will* crash.
On Tuesday, 31 October 2017 10:39:50 GMT Luca Beltrame wrote:
Il giorno Tue, 31 Oct 2017 10:28:26 +0000 ianseeks <bingmybong@btinternet.com> ha scritto:
That could be the connection, i'm using nouveau too. Maybe someone with more knowledge than us will give an answer.
If you use Noveau, yes, it *will* crash.
So i see. Is it worth logging or just something we have to suffer until nouveau works? I've run kmail from cli and just got these messages after selecting a folder just prior to a crash.. org.kde.akonadi.ETM: collection: "kdepim-users" org.kde.akonadi.ETM: Fetch job took 1055 msec org.kde.akonadi.ETM: was item fetch job: items: 2107 kmail: pushbuf.c:727: nouveau_pushbuf_data: Assertion `kref' failed. *** KMail got signal 6 (Exiting) *** Dead letters dumped. [1556:1617:1031/105336.056736:ERROR:gles2_cmd_decoder.cc(2439)] [.RenderWorker-0x55c1d94397a0]GL ERROR :GL_OUT_OF_MEMORY : ScopedTextureBinder::dtor: <- error from previous GL command [1556:1617:1031/105336.059730:ERROR:gles2_cmd_decoder.cc(5202)] Error: 5 for Command kCopySubTextureCHROMIUM [1556:1617:1031/105336.061174:ERROR:gles2_cmd_decoder.cc(4169)] GLES2DecoderImpl: Trying to make lost context current. [1556:1617:1031/105336.061238:ERROR:gles2_cmd_decoder.cc(4169)] GLES2DecoderImpl: Trying to make lost context current. [1556:1617:1031/105336.061292:ERROR:gles2_cmd_decoder.cc(4169)] GLES2DecoderImpl: Trying to make lost context current. [1556:1617:1031/105336.061377:ERROR:gles2_cmd_decoder.cc(4169)] GLES2DecoderImpl: Trying to make lost context current. [1556:1617:1031/105336.061431:ERROR:gles2_cmd_decoder.cc(4169)] GLES2DecoderImpl: Trying to make lost context current. [1556:1617:1031/105336.061483:ERROR:gles2_cmd_decoder.cc(4169)] GLES2DecoderImpl: Trying to make lost context current. [1556:1617:1031/105336.061534:ERROR:gles2_cmd_decoder.cc(4169)] GLES2DecoderImpl: Trying to make lost context current. KCrash: Application 'kmail' crashing... KCrash: Attempting to start /usr/lib64/libexec/drkonqi from kdeinit sock_file=/run/user/1002/kdeinit5__0 [1556:1611:1031/105336.065142:FATAL:rand_util_posix.cc(54)] Check failed: success. #0 0x7f8e3bc24efe <unknown> #1 0x7f8e3bc37592 <unknown> #2 0x7f8e3bc5b831 <unknown> #3 0x7f8e3b9b82b6 <unknown> #4 0x7f8e3b9b8372 <unknown> #5 0x7f8e3c8581ab <unknown> #6 0x7f8e3c45f409 <unknown> #7 0x7f8e3c46013d <unknown> #8 0x7f8e3c463000 <unknown> #9 0x7f8e3c45af49 <unknown> #10 0x7f8e3c468685 <unknown> #11 0x7f8e3c468853 <unknown> #12 0x7f8e3c86e36a <unknown> #13 0x7f8e3c86a2b9 <unknown> #14 0x7f8e3c87dd5a <unknown> #15 0x7f8e3c872ed3 <unknown> #16 0x7f8e3bc431df <unknown> #17 0x7f8e33c6dfc8 <unknown> #18 0x7f8e33c6ea0f event_base_loop #19 0x7f8e3bc430c3 <unknown> #20 0x7f8e3bc3f258 <unknown> #21 0x7f8e3bc5bc9b <unknown> #22 0x7f8e3b4f8e48 <unknown> #23 0x7f8e3b4f93fb <unknown> #24 0x7f8e3bc738d8 <unknown> #25 0x7f8e3bc6f92b <unknown> #26 0x7f8e46f45558 start_thread #27 0x7f8e5143643f __GI___clone Unable to start Dr. Konqi Re-raising signal for core dump handling. Aborted (core dumped) This list is the cli display before the crash ->kmail org.kde.pim.akonadicore: "QLocalSocket::connectToServer: Connection refused" "/tmp/akonadi-is.QCMZb3/akonadiserver-cmd.socket" org.kde.pim.akonadicore: "QLocalSocket::connectToServer: Connection refused" "/tmp/akonadi-is.QCMZb3/akonadiserver-cmd.socket" Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) Pass a valid window to KWallet::Wallet::openWallet(). The kwalletd service has been registered org.kde.akonadi.ETM: GEN true false false org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: org.kde.pim.akonadicore: Socket error occurred: "QLocalSocket::connectToServer: Connection refused" org.kde.pim.akonadicore: Socket error occurred: "QLocalSocket::connectToServer: Connection refused" QDBusConnection: name 'org.kde.kwalletd5' had owner '' but we thought it was ':1.46' akonadi.collectionattributetable OK akonadi.collectionmimetyperelation OK akonadi.collectionpimitemrelation OK akonadi.collectiontable OK akonadi.flagtable OK akonadi.mimetypetable OK akonadi.parttable OK akonadi.parttypetable OK akonadi.pimitemflagrelation OK akonadi.pimitemtable OK akonadi.pimitemtagrelation OK akonadi.relationtable OK akonadi.relationtypetable OK akonadi.resourcetable OK akonadi.schemaversiontable OK akonadi.tagattributetable OK akonadi.tagremoteidresourcerelationtable OK akonadi.tagtable OK akonadi.tagtypetable OK Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) QDBusConnection: name 'org.freedesktop.Akonadi.Control' had owner '' but we thought it was ':1.42' org.kde.pim.akonadicontrol: Agent instance ( "setAgentInstanceOnline" ) "akonadi_pop3_resource_1" has no agent interface. org.kde.pim.akonadicontrol: "AgentManager::agentInstanceSynchronize" Agent instance "akonadi_pop3_resource_1" has no resource interface! org.kde.pim.akonadicontrol: Agent instance ( "setAgentInstanceOnline" ) "akonadi_pop3_resource_2" has no agent interface. org.kde.pim.akonadicontrol: "AgentManager::agentInstanceSynchronize" Agent instance "akonadi_pop3_resource_2" has no resource interface! org.kde.pim.akonadicontrol: Agent instance ( "setAgentInstanceOnline" ) "akonadi_maildir_resource_0" has no agent interface. org.kde.pim.akonadicontrol: "AgentManager::agentInstanceSynchronize" Agent instance "akonadi_maildir_resource_0" has no resource interface! org.kde.pim.akonadicontrol: Agent instance ( "setAgentInstanceOnline" ) "akonadi_pop3_resource_0" has no agent interface. org.kde.pim.akonadicontrol: "AgentManager::agentInstanceSynchronize" Agent instance "akonadi_pop3_resource_0" has no resource interface! org.kde.akonadi.ETM: GEN true false false org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: org.kde.akonadi.ETM: Subtree: 3 QSet(12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 17, 16, 15, 14, 13) org.kde.akonadi.ETM: collection: "inbox" org.kde.akonadi.ETM: Fetch job took 365 msec org.kde.akonadi.ETM: was collection fetch job: collections: 15 org.kde.akonadi.ETM: first fetched collection: "Local Folders" org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: Fetch job took 489 msec org.kde.akonadi.ETM: was collection fetch job: collections: 3 org.kde.akonadi.ETM: first fetched collection: "Search" org.kde.akonadi.ETM: GEN true false false org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: org.kde.akonadi.ETM: Subtree: 3 QSet(14, 9, 8, 11, 10, 5, 4, 7, 6, 17, 3, 16, 13, 12, 15) org.kde.akonadi.ETM: Fetch job took 31 msec org.kde.akonadi.ETM: was collection fetch job: collections: 15 org.kde.akonadi.ETM: first fetched collection: "Local Folders" org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: Fetch job took 33 msec org.kde.akonadi.ETM: was collection fetch job: collections: 3 org.kde.akonadi.ETM: first fetched collection: "Search" org.kde.akonadi.ETM: Fetch job took 1 msec org.kde.akonadi.ETM: was collection fetch job: collections: 0 org.kde.akonadi.ETM: GEN true false false org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: org.kde.akonadi.ETM: Subtree: 3 QSet(11, 12, 13, 14, 15, 16, 17, 3, 4, 5, 6, 7, 8, 9, 10) org.kde.akonadi.ETM: Fetch job took 39 msec org.kde.akonadi.ETM: was collection fetch job: collections: 15 org.kde.akonadi.ETM: first fetched collection: "Local Folders" org.kde.akonadi.ETM: collection: QVector() org.kde.akonadi.ETM: Fetch job took 45 msec org.kde.akonadi.ETM: was collection fetch job: collections: 3 org.kde.akonadi.ETM: first fetched collection: "Search" org.kde.akonadi.ETM: Fetch job took 2 msec org.kde.akonadi.ETM: was collection fetch job: collections: 0 org.kde.akonadi.ETM: Fetch job took 1010 msec org.kde.akonadi.ETM: was item fetch job: items: 43 org.kde.akonadi.ETM: Fetch job took 870 msec org.kde.akonadi.ETM: was collection fetch job: collections: 0 QXcbConnection: XCB error: 8 (BadMatch), sequence: 2867, resource id: 52428862, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 2870, resource id: 52428862, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 2873, resource id: 52428862, major code: 130 (Unknown), minor code: 3 -- opensuse:tumbleweed:20171028 Qt: 5.9.2 KDE Frameworks: 5.39.0 KDE Plasma: 5.11.2 kwin 5.11.2 kmail2 5.6.2 akonadiserver 5.6.2 Kernel: 4.13.9-1-default Nouveau: 1.0.15_1.2 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Dienstag, 31. Oktober 2017, 10:59:33 schrieb ianseeks:
I've run kmail from cli and just got these messages after selecting a folder just prior to a crash..
org.kde.akonadi.ETM: collection: "kdepim-users" org.kde.akonadi.ETM: Fetch job took 1055 msec org.kde.akonadi.ETM: was item fetch job: items: 2107 kmail: pushbuf.c:727: nouveau_pushbuf_data: Assertion `kref' failed. ^^^ Yes, that's indeed the well-known and long-standing nouveau crash.
Uninstalling Mesa-nouveau-dri should help, or installing the proprietary nvidia driver. There are (a lot of) bug reports about that upstream at KDE, Qt, and Mesa/nouveau (where the actual problem lies). Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday, 31 October 2017 15:48:32 GMT Wolfgang Bauer wrote:
Am Dienstag, 31. Oktober 2017, 10:59:33 schrieb ianseeks:
I've run kmail from cli and just got these messages after selecting a folder just prior to a crash..
org.kde.akonadi.ETM: collection: "kdepim-users" org.kde.akonadi.ETM: Fetch job took 1055 msec org.kde.akonadi.ETM: was item fetch job: items: 2107 kmail: pushbuf.c:727: nouveau_pushbuf_data: Assertion `kref' failed. ^^^ Yes, that's indeed the well-known and long-standing nouveau crash.
Uninstalling Mesa-nouveau-dri should help, or installing the proprietary nvidia driver.
Thanks Wolfgang. I thought i had done this a long time ago, not sure how it got back there.
There are (a lot of) bug reports about that upstream at KDE, Qt, and Mesa/nouveau (where the actual problem lies).
Kind Regards, Wolfgang
-- opensuse:tumbleweed:20171029 Qt: 5.9.2 KDE Frameworks: 5.39.0 KDE Plasma: 5.11.2 kwin 5.11.2 kmail2 5.6.2 akonadiserver 5.6.2 Kernel: 4.13.9-1-default Nouveau: 1.0.15_1.2 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Dienstag, 31. Oktober 2017, 16:33:58 schrieb Ianseeks:
On Tuesday, 31 October 2017 15:48:32 GMT Wolfgang Bauer wrote:
Am Dienstag, 31. Oktober 2017, 10:59:33 schrieb ianseeks:
I've run kmail from cli and just got these messages after selecting a folder just prior to a crash..
org.kde.akonadi.ETM: collection: "kdepim-users" org.kde.akonadi.ETM: Fetch job took 1055 msec org.kde.akonadi.ETM: was item fetch job: items: 2107 kmail: pushbuf.c:727: nouveau_pushbuf_data: Assertion `kref' failed.
^^^ Yes, that's indeed the well-known and long-standing nouveau crash.
Uninstalling Mesa-nouveau-dri should help, or installing the proprietary nvidia driver.
Thanks Wolfgang. I thought i had done this a long time ago, not sure how it got back there.
Well, as discussed in another subthread, we had/have a patch in QtWebEngine (used by kmail to display mails) to prevent those crashes since over a year. That patch didn't work any more since the update to Qt 5.9.2 though, so that's why you had this problem (again) now. A fix has been submitted to Tumbleweed already meanwhile, so you should be able to reinstall Mesa-dri-nouveau after the next libqt5-qtwebengine update. Not having it installed will disable hardware accelerated OpenGL in general. This also means that the desktop will be slower. So probably a good idea to install it again then, if it doesn't cause you other problems. ;-) Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday, 31 October 2017 17:06:52 GMT Wolfgang Bauer wrote:
Am Dienstag, 31. Oktober 2017, 16:33:58 schrieb Ianseeks:
On Tuesday, 31 October 2017 15:48:32 GMT Wolfgang Bauer wrote:
Am Dienstag, 31. Oktober 2017, 10:59:33 schrieb ianseeks:
I've run kmail from cli and just got these messages after selecting a folder just prior to a crash..
org.kde.akonadi.ETM: collection: "kdepim-users" org.kde.akonadi.ETM: Fetch job took 1055 msec org.kde.akonadi.ETM: was item fetch job: items: 2107 kmail: pushbuf.c:727: nouveau_pushbuf_data: Assertion `kref' failed.
^^^ Yes, that's indeed the well-known and long-standing nouveau crash.
Uninstalling Mesa-nouveau-dri should help, or installing the proprietary nvidia driver.
Thanks Wolfgang. I thought i had done this a long time ago, not sure how it got back there.
Well, as discussed in another subthread, we had/have a patch in QtWebEngine (used by kmail to display mails) to prevent those crashes since over a year. That patch didn't work any more since the update to Qt 5.9.2 though, so that's why you had this problem (again) now.
A fix has been submitted to Tumbleweed already meanwhile, so you should be able to reinstall Mesa-dri-nouveau after the next libqt5-qtwebengine update.
Not having it installed will disable hardware accelerated OpenGL in general. This also means that the desktop will be slower. So probably a good idea to install it again then, if it doesn't cause you other problems. ;-)
Thanks for the update.
Kind Regards, Wolfgang
-- opensuse:tumbleweed:20171030 Qt: 5.9.2 KDE Frameworks: 5.39.0 KDE Plasma: 5.11.2 kwin 5.11.2 kmail2 5.6.2 akonadiserver 5.6.2 Kernel: 4.13.10-1-default Nouveau: 1.0.15_1.2 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Just for the records: I'm not using Nouveau Schöne Grüße Axel -- Written from cell phone - excuses for typos Am 31. Oktober 2017 11:39:50 MEZ schrieb Luca Beltrame <lbeltrame@kde.org>:
Il giorno Tue, 31 Oct 2017 10:28:26 +0000 ianseeks <bingmybong@btinternet.com> ha scritto:
That could be the connection, i'm using nouveau too. Maybe someone with more knowledge than us will give an answer.
If you use Noveau, yes, it *will* crash. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op dinsdag 31 oktober 2017 12:01:09 CET schreef Axel Braun:
Just for the records: I'm not using Nouveau Schöne Grüße Axel
No nouveau here either.
Il giorno Tue, 31 Oct 2017 10:28:26 +0000
ianseeks <bingmybong@btinternet.com> ha scritto:
That could be the connection, i'm using nouveau too. Maybe someone with more knowledge than us will give an answer.
If you use Noveau, yes, it *will* crash.
-- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi everybody, I did some testing, TW Systems I tested, all with newest updates (as of today, 8pm-9pm): 1) Dell Desktop (with NVIDIA) * Nouveau -> Kontact crashes on start * NVIDIA drivers (TW repo): Kontact works fine -> Exception: In an X2go session it crashes at start, like with Nouveau. SSH+X works, though it's no fun :-) 2) Lenovo laptop with Intel grafics: No problem, KDE and Kontact work fine, worked fine with any update throughout the last weeks, no problem. Compiz runs, three monitors, just like it should - at least if you're not stuck with NVIDIA. 3) Acer Laptop with Intel graphics: One of the updates last week broke it. Kontact crashes on start. None of the updates until now fixed it. 4) Dell laptop with intel graphics: Just updated 2879 packages (after a week or two?), rebooted and works fine. If this problem is really NVIDIA/Nouveau related, then I can't explain why we are having similar issues on non-NV-hardware... :-) Well, we'll see. Am Dienstag, 31. Oktober 2017, 12:05:10 CET schrieb Knurpht - Gertjan Lettink:
Op dinsdag 31 oktober 2017 12:01:09 CET schreef Axel Braun:
Just for the records: I'm not using Nouveau Schöne Grüße
Axel
No nouveau here either.
Il giorno Tue, 31 Oct 2017 10:28:26 +0000
ianseeks <bingmybong@btinternet.com> ha scritto:
That could be the connection, i'm using nouveau too. Maybe someone with more knowledge than us will give an answer.
If you use Noveau, yes, it *will* crash.
-- Markus Feilner Team Lead Documentation P.S.: I moved - new home address: Wöhrdstraße 10, 93059 Regensburg SUSE Linux GmbH GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) - - - "Well, MY part of the Titanic is rising." - - - +49 173 5876 838 (also via Signal), privat: +49 170 302 7092 mfeilner@suse.[com|de] http://www.suse.com G+: https://plus.google.com/+MarkusFeilner Xing: http://www.xing.com/profile/Markus_Feilner LinkedIn: https://www.linkedin.com/in/markusfeilner #mfeilner: Jabber, Skype, Twitter openSUSE: http://www.opensuse.org -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
31.10.2017 23:05, Markus Feilner пишет:
Hi everybody, I did some testing,
TW Systems I tested, all with newest updates (as of today, 8pm-9pm):
1) Dell Desktop (with NVIDIA) * Nouveau -> Kontact crashes on start * NVIDIA drivers (TW repo): Kontact works fine -> Exception: In an X2go session it crashes at start, like with Nouveau. SSH+X works, though it's no fun :-)
2) Lenovo laptop with Intel grafics: No problem, KDE and Kontact work fine, worked fine with any update throughout the last weeks, no problem. Compiz runs, three monitors, just like it should - at least if you're not stuck with NVIDIA.
3) Acer Laptop with Intel graphics: One of the updates last week broke it. Kontact crashes on start. None of the updates until now fixed it.
4) Dell laptop with intel graphics: Just updated 2879 packages (after a week or two?), rebooted and works fine.
If this problem is really NVIDIA/Nouveau related, then I can't explain why we are having similar issues on non-NV-hardware... :-)
What Xorg driver are you using in each case?
Well, we'll see.
Am Dienstag, 31. Oktober 2017, 12:05:10 CET schrieb Knurpht - Gertjan Lettink:
Op dinsdag 31 oktober 2017 12:01:09 CET schreef Axel Braun:
Just for the records: I'm not using Nouveau Schöne Grüße
Axel
No nouveau here either.
Il giorno Tue, 31 Oct 2017 10:28:26 +0000
ianseeks <bingmybong@btinternet.com> ha scritto:
That could be the connection, i'm using nouveau too. Maybe someone with more knowledge than us will give an answer.
If you use Noveau, yes, it *will* crash.
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday, 31 October 2017 10:39:50 GMT Luca Beltrame wrote:
Il giorno Tue, 31 Oct 2017 10:28:26 +0000 ianseeks <bingmybong@btinternet.com> ha scritto:
That could be the connection, i'm using nouveau too. Maybe someone with more knowledge than us will give an answer.
If you use Noveau, yes, it *will* crash.
Another thing i forgot to mention, this particular crashing problem only started happening after one of last weeks snapshots. It running really well up until then apart from a few duplicates. -- opensuse:tumbleweed:20171028 Qt: 5.9.2 KDE Frameworks: 5.39.0 KDE Plasma: 5.11.2 kwin 5.11.2 kmail2 5.6.2 akonadiserver 5.6.2 Kernel: 4.13.9-1-default Nouveau: 1.0.15_1.2 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op dinsdag 31 oktober 2017 12:20:00 CET schreef Ianseeks:
On Tuesday, 31 October 2017 10:39:50 GMT Luca Beltrame wrote:
Il giorno Tue, 31 Oct 2017 10:28:26 +0000
ianseeks <bingmybong@btinternet.com> ha scritto:
That could be the connection, i'm using nouveau too. Maybe someone with more knowledge than us will give an answer.
If you use Noveau, yes, it *will* crash.
Another thing i forgot to mention, this particular crashing problem only started happening after one of last weeks snapshots. It running really well up until then apart from a few duplicates.
Same here. The occasional duplicate phenomenon disappeared after switching to postgress db. -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday, 31 October 2017 11:24:16 GMT Knurpht - Gertjan Lettink wrote:
Op dinsdag 31 oktober 2017 12:20:00 CET schreef Ianseeks:
On Tuesday, 31 October 2017 10:39:50 GMT Luca Beltrame wrote:
Il giorno Tue, 31 Oct 2017 10:28:26 +0000
ianseeks <bingmybong@btinternet.com> ha scritto:
That could be the connection, i'm using nouveau too. Maybe someone with more knowledge than us will give an answer.
If you use Noveau, yes, it *will* crash.
Another thing i forgot to mention, this particular crashing problem only started happening after one of last weeks snapshots. It running really well up until then apart from a few duplicates.
Same here. The occasional duplicate phenomenon disappeared after switching to postgress db. Thats interesting, maybe I'll have to look at the postgress option. Have there been any responses from the team about mysql/mariadb being responsible for duplications?
-- opensuse:tumbleweed:20171029 Qt: 5.9.2 KDE Frameworks: 5.39.0 KDE Plasma: 5.11.2 kwin 5.11.2 kmail2 5.6.2 akonadiserver 5.6.2 Kernel: 4.13.9-1-default Nouveau: 1.0.15_1.2 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Dienstag, 31. Oktober 2017, 11:39:50 schrieb Luca Beltrame:
Il giorno Tue, 31 Oct 2017 10:28:26 +0000
ianseeks <bingmybong@btinternet.com> ha scritto:
That could be the connection, i'm using nouveau too. Maybe someone with more knowledge than us will give an answer.
If you use Noveau, yes, it *will* crash.
Hm, openSUSE's QtWebEngine package is patched to disable OpenGL usage on nouveau since a year. ( disable-gpu-when-using-nouveau-boo-1005323.diff ) That was intended to prevent those crashes... The patch seems to be incomplete (and therefore ineffictive) meanwhile though AFAICS, is this on purpose? Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Il giorno Tue, 31 Oct 2017 16:34:18 +0100 Wolfgang Bauer <wbauer@tmo.at> ha scritto:
The patch seems to be incomplete (and therefore ineffictive) meanwhile though AFAICS, is this on purpose?
I think not, but I don't have NVIDIA hardware so I cannot even test it. Antonio perhaps can weigh in.
Am Dienstag, 31. Oktober 2017, 16:40:51 schrieb Luca Beltrame:
Il giorno Tue, 31 Oct 2017 16:34:18 +0100
Wolfgang Bauer <wbauer@tmo.at> ha scritto:
The patch seems to be incomplete (and therefore ineffictive) meanwhile though AFAICS, is this on purpose?
I think not, but I don't have NVIDIA hardware so I cannot even test it.
To be more precise, it is missing the part that actually disables OpenGL on nouveau in the current Tumbleweed packages (and in KDE:Qt5). I.e. this part from Leap is not there in TW/KDE:Qt5: @@ -263,8 +295,21 @@ WebEngineContext::WebEngineContext() GLContextHelper::initialize(); + bool disableGpu = qEnvironmentVariableIsSet("QT_WEBENGINE_DISABLE_GPU"); + + if (!qEnvironmentVariableIsSet("QT_WEBENGINE_DISABLE_NOUVEAU_WORKAROUND") && openGLVendor() == QStringLiteral("nouveau")) + { + qWarning() << "Nouveau openGL driver detected. Qt WebEngine will disable usage of the GPU.\n" + "Please consider using the propietary NVIDIA drivers.\n\n" + "Alternatively, you can set the QT_WEBENGINE_DISABLE_NOUVEAU_WORKAROUND\n" + "environment variable before running this application, but this is \n" + "not recommended since this usually causes applications to crash as\n" + "Nouveau openGL drivers don't support multithreaded rendering"; + disableGpu = true; + } + const char *glType = 0; - if (!usingANGLE() && !usingSoftwareDynamicGL() && !usingQtQuick2DRenderer()) { + if (!usingANGLE() && !usingSoftwareDynamicGL() && !usingQtQuick2DRenderer() && !disableGpu) { if (qt_gl_global_share_context()) { if (!strcmp(qt_gl_global_share_context()->nativeHandle().typeName(), "QEGLNativeContext")) { if (qt_gl_global_share_context()->isOpenGLES()) { IOW, it's a no-op currently and doesn't actually do anything. Apparently it would still be needed though... Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Btw, seems it got lost during the update to Qt 5.9.2... Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
To answer my own question, it probably wasn't on purpose as it is still (or again?) there in KDE:Qt:5.10. I just wanted to work on re-adding the missing part, but I see Fabian has done so already: https://build.opensuse.org/package/rdiff/KDE:Qt5/libqt5-qtwebengine?linkrev=base&rev=111 So, should be fixed again soon in Tumbleweed... Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op dinsdag 31 oktober 2017 10:25:43 CET schreef ianseeks:
Hi
Is anyone else getting this problem? Kmail or Kontact crash at will and sometimes crashes out using the crash handler and sometimes just dies without it. It seems to happen when you access an email, read or unread, i've not had it crash for any other action so far.
I will log a bug if it seems to be happening to others as well.
I was going to delete the akonadi database to see if it makes any difference on a fresh database as there are loads of duplicates in it but i'm fed up with recreating the kmail settings etc, is there anyway i can remove the data without removing the settings?
Regards
Ian
No regular crashes here, but an easy to produce one here: new mail, start typing the emailaddress, after four or five characters kontact/kmail crashes. -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op dinsdag 31 oktober 2017 12:00:59 CET schreef Knurpht - Gertjan Lettink:
Op dinsdag 31 oktober 2017 10:25:43 CET schreef ianseeks:
Hi
Is anyone else getting this problem? Kmail or Kontact crash at will and sometimes crashes out using the crash handler and sometimes just dies without it. It seems to happen when you access an email, read or unread, i've not had it crash for any other action so far.
I will log a bug if it seems to be happening to others as well.
I was going to delete the akonadi database to see if it makes any difference on a fresh database as there are loads of duplicates in it but i'm fed up with recreating the kmail settings etc, is there anyway i can remove the data without removing the settings?
Regards
Ian
No regular crashes here, but an easy to produce one here: new mail, start typing the emailaddress, after four or five characters kontact/kmail crashes.
Using fully updated Tumbleweed with kontact for months now without any crashes. Previous I did suffer from crashes. Using radeon as graphical device driver. You can export contacts and import these afterwards. Only groups are not saved. -- fr.gr. Freek de Kruijf member openSUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Dienstag, 31. Oktober 2017, 12:00:59 CET schrieb Knurpht - Gertjan Lettink:
No regular crashes here, but an easy to produce one here: new mail, start typing the emailaddress, after four or five characters kontact/kmail crashes.
Seen that as well - it may be the search-db (xapian?) that is broken. Best, Axel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Dienstag, 31. Oktober 2017, 12:00:59 CET schrieb Knurpht - Gertjan Lettink:
No regular crashes here, but an easy to produce one here: new mail, start typing the emailaddress, after four or five characters kontact/kmail crashes.
Seen that as well - it may be the search-db (xapian?) that is broken.
Best, Axel And you know what? After yesterday and today's updates I can't reproduce the
Op dinsdag 31 oktober 2017 12:37:33 CET schreef Axel Braun: phenomenon....... Entering an email address now behaves as it should. -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op dinsdag 31 oktober 2017 13:07:46 CET schreef Knurpht - Gertjan Lettink:
Op dinsdag 31 oktober 2017 12:37:33 CET schreef Axel Braun:
Am Dienstag, 31. Oktober 2017, 12:00:59 CET schrieb Knurpht - Gertjan
Lettink:
No regular crashes here, but an easy to produce one here: new mail, start typing the emailaddress, after four or five characters kontact/kmail crashes.
Seen that as well - it may be the search-db (xapian?) that is broken.
Best, Axel
And you know what? After yesterday and today's updates I can't reproduce the phenomenon....... Entering an email address now behaves as it should.
And regression arrived, Same issue is back again. Anyone else seeing the phenomenon in the quoted lines. If so, I'll report a bug at KDE and openSUSE -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Dienstag, 7. November 2017, 16:11:14 schrieb Knurpht - Gertjan Lettink:
And regression arrived, Same issue is back again. Anyone else seeing the phenomenon in the quoted lines. If so, I'll report a bug at KDE and openSUSE
Well, there are at least 2 KDE bug reports already about this problem: https://bugs.kde.org/show_bug.cgi?id=383107 https://bugs.kde.org/show_bug.cgi?id=386545 Both are crashes in Xapian, likely caused by a corrupted database. (the main question I suppose is *why* it gets corrupted though...) Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op dinsdag 7 november 2017 19:41:47 CET schreef Wolfgang Bauer:
Am Dienstag, 7. November 2017, 16:11:14 schrieb Knurpht - Gertjan Lettink:
And regression arrived, Same issue is back again. Anyone else seeing the phenomenon in the quoted lines. If so, I'll report a bug at KDE and openSUSE Well, there are at least 2 KDE bug reports already about this problem: https://bugs.kde.org/show_bug.cgi?id=383107 https://bugs.kde.org/show_bug.cgi?id=386545
Both are crashes in Xapian, likely caused by a corrupted database. (the main question I suppose is *why* it gets corrupted though...)
Kind Regards, Wolfgang
I've rebuilt the db a while ago, first a mysql database, then a postgress db. Issue existed in both. So, then both produce a corrupt database from scratch. A workaround is to select addresses from the addressbook. A search in the addressbook works fine. -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Il giorno Wed, 08 Nov 2017 12:22:09 +0100 Knurpht - Gertjan Lettink <knurpht@opensuse.org> ha scritto:
I've rebuilt the db a while ago, first a mysql database, then a postgress db. Issue existed in both. So, then both produce a corrupt
The search database is independent from what Akonadi uses, and you'll find it in ~/.local/share/baloo/email{Contacts}/ The PIM people upstream have a plan (ongoing) to make search more robust and less crash prone.
Op woensdag 8 november 2017 12:29:10 CET schreef Luca Beltrame:
Il giorno Wed, 08 Nov 2017 12:22:09 +0100
Knurpht - Gertjan Lettink <knurpht@opensuse.org> ha scritto:
I've rebuilt the db a while ago, first a mysql database, then a postgress db. Issue existed in both. So, then both produce a corrupt
The search database is independent from what Akonadi uses, and you'll find it in ~/.local/share/baloo/email{Contacts}/
The PIM people upstream have a plan (ongoing) to make search more robust and less crash prone.
Thanks Luca, What would you suggest to repair or rebuild these data? -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op woensdag 8 november 2017 12:29:10 CET schreef Luca Beltrame:
Il giorno Wed, 08 Nov 2017 12:22:09 +0100
Knurpht - Gertjan Lettink <knurpht@opensuse.org> ha scritto:
I've rebuilt the db a while ago, first a mysql database, then a postgress db. Issue existed in both. So, then both produce a corrupt
The search database is independent from what Akonadi uses, and you'll find it in ~/.local/share/baloo/email{Contacts}/
The PIM people upstream have a plan (ongoing) to make search more robust and less crash prone.
Thanks for the hint, Luca. I checked all the databases in .local/share/baloo and indeed xapian-check reports corruption on (only) emailContacts. Removed it and it seems to do the trick, i.e. no crash. -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (12)
-
Andrei Borzenkov -
Axel Braun -
Axel Braun
-
Axel Braun
-
Freek de Kruijf -
Ianseeks -
ianseeks
-
J. F. Lemaire -
Knurpht - Gertjan Lettink -
Luca Beltrame -
Markus Feilner -
Wolfgang Bauer