Hi
Anyone else having this issue? I can't even log a bug for it as the crash handler fails as well.
Regards
Ian
I have problem with akonadi repeating crashes, but not kmail.
m.
On nedeľa, 21. augusta 2016 10:52:58 CEST ianseeks wrote:
Hi
Anyone else having this issue? I can't even log a bug for it as the crash handler fails as well.
Regards
Ian
Hello,
Am Sonntag, 21. August 2016, 12:17:33 CEST schrieb Michal Hlavac:
I have problem with akonadi repeating crashes, but not kmail.
Same here.
Some debugging with fvogt on #opensuse-kde shows that this is probaby caused by building akonadi against the new libxapian30 (instead of the previous libxapian22).
For details, see the upstream bug https://bugs.kde.org/show_bug.cgi?id=363741
For those who didn't update Tumbleweed in the last days, it's probably a good idea to zypper al libxapian30 to avoid getting it and the rebuilt version of akonadi and kdepim.
Regards,
Christian Boltz
On Sunday, 21 August 2016 14:08:33 BST Christian Boltz wrote:
Hello,
Am Sonntag, 21. August 2016, 12:17:33 CEST schrieb Michal Hlavac:
I have problem with akonadi repeating crashes, but not kmail.
Same here.
Some debugging with fvogt on #opensuse-kde shows that this is probaby caused by building akonadi against the new libxapian30 (instead of the previous libxapian22).
For details, see the upstream bug https://bugs.kde.org/show_bug.cgi?id=363741
For those who didn't update Tumbleweed in the last days, it's probably a good idea to zypper al libxapian30 to avoid getting it and the rebuilt version of akonadi and kdepim.
Regards,
Christian Boltz
Yes, i do also have akonadi restarting itself whilst running kmail2 and i also have some coredump messages in the log. So i get both kmail2 and akonadi crashing
On Sunday, 21 August 2016 12:17:33 BST Michal Hlavac wrote:
I have problem with akonadi repeating crashes, but not kmail.
I have both. I see messages in the journal log for akonadi coredumping but no messages for kmail2 in the log when it seg faults 11
m.
On nedeľa, 21. augusta 2016 10:52:58 CEST ianseeks wrote:
Hi
Anyone else having this issue? I can't even log a bug for it as the crash handler fails as well.
Regards
Ian
Hello,
Am Sonntag, 21. August 2016, 14:08:33 CEST schrieb Christian Boltz:
Am Sonntag, 21. August 2016, 12:17:33 CEST schrieb Michal Hlavac:
I have problem with akonadi repeating crashes, but not kmail.
Same here.
Some debugging with fvogt on #opensuse-kde shows that this is probaby caused by building akonadi against the new libxapian30 (instead of the previous libxapian22).
For details, see the upstream bug https://bugs.kde.org/show_bug.cgi?id=363741
For those who didn't update Tumbleweed in the last days, it's probably a good idea to zypper al libxapian30 to avoid getting it and the rebuilt version of akonadi and kdepim.
I created a repo with the previous version of libxapian, and akonadi-* and baloo linkpac'd from Factory (so rebuilt against the old libxapian): https://build.opensuse.org/project/show/home:cboltz:branches:openSUSE:Factor... Packages at http://download.opensuse.org/repositories/home:/cboltz:/branches:/openSUSE:/...
Since I installled these packages (using zypper dup --from), I didn't see any akonadi crashes.
In other words: it's probably a good idea to revert the libxamian / xapian-core update in Tumbleweed (including akonadi-* and baloo rebuilds) until this bug gets fixed.
If someone wants to use the fixed packages _now_: I'll keep the repo as long as it's useful for me ;-)
Regards,
Christian Boltz
On dimanche, 21 août 2016 15.45:12 h CEST Christian Boltz wrote:
Hello,
Am Sonntag, 21. August 2016, 14:08:33 CEST schrieb Christian Boltz:
Am Sonntag, 21. August 2016, 12:17:33 CEST schrieb Michal Hlavac:
I have problem with akonadi repeating crashes, but not kmail.
I didn't see akonadi crashes directly (coredump) nor kmail dump. But trying to suppress messages lead to finding them again in the imap folders. So I also followed the discussion on #opensuse-kde channel.
I'm using a central postgresql server and this is how I fix the things. I've no special KDE repository (pure oss)
use akonadictl stop use balooctl stop (not necessary but doesn't eat kitten)
use administrative account on your postgresql database to do the following vaccumdb -vfz -d [your_akonadi_db] reindex -d [your_akonadi_db]
use a console to rm -fr ~/.local/share/akonadi/search_db
(I don't care about search it will be recreated afterwards, and I'm no customized searches)
akonadictl start balooctl start
akonadictl fsck
and if really you want you can rerun the akonadi vacuum
akonadictl vacuum
Afterward I can again use kmail normally from what I've seen
Same here. Doesn't crash on a specific action, just crashes randomly ( from what it looks like )
Op zondag 21 augustus 2016 12:17:33 CEST schreef Michal Hlavac:
I have problem with akonadi repeating crashes, but not kmail.
m.
On nedeľa, 21. augusta 2016 10:52:58 CEST ianseeks wrote:
Hi
Anyone else having this issue? I can't even log a bug for it as the crash handler fails as well.
Regards
Ian
On Sunday, 21 August 2016 15:45:12 BST Christian Boltz wrote:
Hello,
Am Sonntag, 21. August 2016, 14:08:33 CEST schrieb Christian Boltz:
Am Sonntag, 21. August 2016, 12:17:33 CEST schrieb Michal Hlavac:
I have problem with akonadi repeating crashes, but not kmail.
Same here.
Some debugging with fvogt on #opensuse-kde shows that this is probaby caused by building akonadi against the new libxapian30 (instead of the previous libxapian22).
For details, see the upstream bug https://bugs.kde.org/show_bug.cgi?id=363741
For those who didn't update Tumbleweed in the last days, it's probably a good idea to zypper al libxapian30 to avoid getting it and the rebuilt version of akonadi and kdepim.
I created a repo with the previous version of libxapian, and akonadi-* and baloo linkpac'd from Factory (so rebuilt against the old libxapian):
https://build.opensuse.org/project/show/home:cboltz:branches:openSUSE:Facto ry Packages at
http://download.opensuse.org/repositories/home:/cboltz:/branches:/openSUSE: /Factory/standard/
I tried to add this via Yast to try it out but it crashed out with a "cache_license_accceptance_needed" error - what ever that means
Since I installled these packages (using zypper dup --from), I didn't see any akonadi crashes.
In other words: it's probably a good idea to revert the libxamian / xapian-core update in Tumbleweed (including akonadi-* and baloo rebuilds) until this bug gets fixed.
If someone wants to use the fixed packages _now_: I'll keep the repo as long as it's useful for me ;-)
Regards,
Christian Boltz
Add the proper URL:
zypper ar -f -n AkonadiTMP http://download.opensuse.org/repositories/home:/ cboltz:/branches:/openSUSE:/Factory/standard/ AkonadiTMP zypper ref zypper dup --from AkonadiTMP
Op zondag 21 augustus 2016 16:30:01 CEST schreef ianseeks:
On Sunday, 21 August 2016 15:45:12 BST Christian Boltz wrote:
Hello,
Am Sonntag, 21. August 2016, 14:08:33 CEST schrieb Christian Boltz:
Am Sonntag, 21. August 2016, 12:17:33 CEST schrieb Michal Hlavac:
I have problem with akonadi repeating crashes, but not kmail.
Same here.
Some debugging with fvogt on #opensuse-kde shows that this is probaby caused by building akonadi against the new libxapian30 (instead of the previous libxapian22).
For details, see the upstream bug https://bugs.kde.org/show_bug.cgi?id=363741
For those who didn't update Tumbleweed in the last days, it's probably a good idea to zypper al libxapian30 to avoid getting it and the rebuilt version of akonadi and kdepim.
I created a repo with the previous version of libxapian, and akonadi-* and baloo linkpac'd from Factory (so rebuilt against the old libxapian):
https://build.opensuse.org/project/show/home:cboltz:branches:openSUSE:Fact o ry Packages at
http://download.opensuse.org/repositories/home:/cboltz:/branches:/openSUSE : /Factory/standard/
I tried to add this via Yast to try it out but it crashed out with a "cache_license_accceptance_needed" error - what ever that means
Since I installled these packages (using zypper dup --from), I didn't see any akonadi crashes.
In other words: it's probably a good idea to revert the libxamian / xapian-core update in Tumbleweed (including akonadi-* and baloo rebuilds) until this bug gets fixed.
If someone wants to use the fixed packages _now_: I'll keep the repo as long as it's useful for me ;-)
Regards,
Christian Boltz
And a big hand to Christian !! Kmail up and running again after finding it unusable.
Op zondag 21 augustus 2016 17:57:16 CEST schreef Knurpht - Gertjan Lettink:
Add the proper URL:
zypper ar -f -n AkonadiTMP http://download.opensuse.org/repositories/home:/ cboltz:/branches:/openSUSE:/Factory/standard/ AkonadiTMP zypper ref zypper dup --from AkonadiTMP
Op zondag 21 augustus 2016 16:30:01 CEST schreef ianseeks:
On Sunday, 21 August 2016 15:45:12 BST Christian Boltz wrote:
Hello,
Am Sonntag, 21. August 2016, 14:08:33 CEST schrieb Christian Boltz:
Am Sonntag, 21. August 2016, 12:17:33 CEST schrieb Michal Hlavac:
I have problem with akonadi repeating crashes, but not kmail.
Same here.
Some debugging with fvogt on #opensuse-kde shows that this is probaby caused by building akonadi against the new libxapian30 (instead of the previous libxapian22).
For details, see the upstream bug https://bugs.kde.org/show_bug.cgi?id=363741
For those who didn't update Tumbleweed in the last days, it's probably a good idea to zypper al libxapian30 to avoid getting it and the rebuilt version of akonadi and kdepim.
I created a repo with the previous version of libxapian, and akonadi-* and baloo linkpac'd from Factory (so rebuilt against the old libxapian):
https://build.opensuse.org/project/show/home:cboltz:branches:openSUSE:Fa ct o ry Packages at
http://download.opensuse.org/repositories/home:/cboltz:/branches:/openSU SE
/Factory/standard/
I tried to add this via Yast to try it out but it crashed out with a "cache_license_accceptance_needed" error - what ever that means
Since I installled these packages (using zypper dup --from), I didn't see any akonadi crashes.
In other words: it's probably a good idea to revert the libxamian / xapian-core update in Tumbleweed (including akonadi-* and baloo rebuilds) until this bug gets fixed.
If someone wants to use the fixed packages _now_: I'll keep the repo as long as it's useful for me ;-)
Regards,
Christian Boltz
Hello,
Am Sonntag, 21. August 2016, 16:30:01 CEST schrieb ianseeks:
On Sunday, 21 August 2016 15:45:12 BST Christian Boltz wrote:
...
https://build.opensuse.org/project/show/home:cboltz:branches:openSUS E:Facto ry Packages at
http://download.opensuse.org/repositories/home:/cboltz:/branches:/op enSUSE: /Factory/standard/
I tried to add this via Yast to try it out but it crashed out with a "cache_license_accceptance_needed" error - what ever that means
That means you'll need to open a bugreport for the YaST crash ;-) Please attach the y2logs - save_y2logs will help to grab them. (As usual, please report back the bug number here.)
Also, I'd guess you need to accept the signing key for my home repo (you'll have to trust me ;-) before you can use the packages. This doesn't exactly match the YaST error, but still sounds like the most likely reason for it. (Needless to say that it shouldn't crash at all, and instead ask to accept the signing key.)
To workaround the YaST crash, use zypper ar to add the repo, and then zypper dup --from to switch your libxepian, akonadi and baloo packages to it.
Regards,
Christian Boltz
Am Sonntag, 21. August 2016, 18:01:41 CEST schrieb Knurpht - Gertjan Lettink:
And a big hand to Christian !! Kmail up and running again after finding it unusable.
+1 Indeed, that saved the rest of my weekend.
On Sun, Aug 21, 2016 at 8:57 AM, Knurpht - Gertjan Lettink knurpht@opensuse.org wrote:
Add the proper URL:
zypper ar -f -n AkonadiTMP http://download.opensuse.org/repositories/home:/ cboltz:/branches:/openSUSE:/Factory/standard/ AkonadiTMP zypper ref zypper dup --from AkonadiTMP
this installed libxapian22
should libxapian30 be uninstalled?
Op zondag 21 augustus 2016 16:30:01 CEST schreef ianseeks:
On Sunday, 21 August 2016 15:45:12 BST Christian Boltz wrote:
Hello,
Am Sonntag, 21. August 2016, 14:08:33 CEST schrieb Christian Boltz:
Am Sonntag, 21. August 2016, 12:17:33 CEST schrieb Michal Hlavac:
I have problem with akonadi repeating crashes, but not kmail.
Same here.
Some debugging with fvogt on #opensuse-kde shows that this is probaby caused by building akonadi against the new libxapian30 (instead of the previous libxapian22).
For details, see the upstream bug https://bugs.kde.org/show_bug.cgi?id=363741
For those who didn't update Tumbleweed in the last days, it's probably a good idea to zypper al libxapian30 to avoid getting it and the rebuilt version of akonadi and kdepim.
I created a repo with the previous version of libxapian, and akonadi-* and baloo linkpac'd from Factory (so rebuilt against the old libxapian):
https://build.opensuse.org/project/show/home:cboltz:branches:openSUSE:Fact o ry Packages at
http://download.opensuse.org/repositories/home:/cboltz:/branches:/openSUSE : /Factory/standard/
I tried to add this via Yast to try it out but it crashed out with a "cache_license_accceptance_needed" error - what ever that means
Since I installled these packages (using zypper dup --from), I didn't see any akonadi crashes.
In other words: it's probably a good idea to revert the libxamian / xapian-core update in Tumbleweed (including akonadi-* and baloo rebuilds) until this bug gets fixed.
If someone wants to use the fixed packages _now_: I'll keep the repo as long as it's useful for me ;-)
Regards,
Christian Boltz
-- 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 Sunday, 21 August 2016 15:45:12 BST Christian Boltz wrote:
Hello,
Am Sonntag, 21. August 2016, 14:08:33 CEST schrieb Christian Boltz:
Am Sonntag, 21. August 2016, 12:17:33 CEST schrieb Michal Hlavac:
I have problem with akonadi repeating crashes, but not kmail.
Same here.
Some debugging with fvogt on #opensuse-kde shows that this is probaby caused by building akonadi against the new libxapian30 (instead of the previous libxapian22).
For details, see the upstream bug https://bugs.kde.org/show_bug.cgi?id=363741
For those who didn't update Tumbleweed in the last days, it's probably a good idea to zypper al libxapian30 to avoid getting it and the rebuilt version of akonadi and kdepim.
I created a repo with the previous version of libxapian, and akonadi-* and baloo linkpac'd from Factory (so rebuilt against the old libxapian):
https://build.opensuse.org/project/show/home:cboltz:branches:openSUSE:Facto ry Packages at
http://download.opensuse.org/repositories/home:/cboltz:/branches:/openSUSE: /Factory/standard/
Since I installled these packages (using zypper dup --from), I didn't see any akonadi crashes.
In other words: it's probably a good idea to revert the libxamian / xapian-core update in Tumbleweed (including akonadi-* and baloo rebuilds) until this bug gets fixed.
If someone wants to use the fixed packages _now_: I'll keep the repo as long as it's useful for me ;-)
Regards,
Christian Boltz
The release for akonadi-server up until today has been 16.08.1-56.4 and i always had to downgrade to your version. But today, it installed 16.08.1-2.6 - does this mean that your cboltz: package is no longer needed?
On Sunday, 21 August 2016 15:45:12 BST Christian Boltz wrote:
Hello,
Am Sonntag, 21. August 2016, 14:08:33 CEST schrieb Christian Boltz:
Am Sonntag, 21. August 2016, 12:17:33 CEST schrieb Michal Hlavac:
I have problem with akonadi repeating crashes, but not kmail.
Same here.
Some debugging with fvogt on #opensuse-kde shows that this is probaby caused by building akonadi against the new libxapian30 (instead of the previous libxapian22).
For details, see the upstream bug https://bugs.kde.org/show_bug.cgi?id=363741
For those who didn't update Tumbleweed in the last days, it's probably a good idea to zypper al libxapian30 to avoid getting it and the rebuilt version of akonadi and kdepim.
I created a repo with the previous version of libxapian, and akonadi-* and baloo linkpac'd from Factory (so rebuilt against the old libxapian):
https://build.opensuse.org/project/show/home:cboltz:branches:openSUSE:Facto ry Packages at
http://download.opensuse.org/repositories/home:/cboltz:/branches:/openSUSE: /Factory/standard/
Since I installled these packages (using zypper dup --from), I didn't see any akonadi crashes.
In other words: it's probably a good idea to revert the libxamian / xapian-core update in Tumbleweed (including akonadi-* and baloo rebuilds) until this bug gets fixed.
If someone wants to use the fixed packages _now_: I'll keep the repo as long as it's useful for me ;-)
Regards,
Christian Boltz
Update: just installed tumbleweed:20160924 and the release number is now upto 16.08.1-56.5, i'll run with this for a while and see how it goes
Am Sonntag, 25. September 2016, 11:17:02 schrieb ianseeks:
The release for akonadi-server up until today has been 16.08.1-56.4 and i always had to downgrade to your version. But today, it installed 16.08.1-2.6
- does this mean that your cboltz: package is no longer needed?
16.08.1-2.6 *is* the version in home:cboltz:branches:...
If it is still needed I cannot say (I'm using 13.2 with an old xapian). Other people reported that just deleting saved searches in kmail fixed the crashes too, even after switching back to the standard packages.
Kind Regards, Wolfgang
Am Sonntag, 25. September 2016, 15:35:48 schrieb ianseeks:
Update: just installed tumbleweed:20160924 and the release number is now upto 16.08.1-56.5, i'll run with this for a while and see how it goes
The version number of what?
AFAICS the KDE Applications in Tumbleweed have 16.08.1-1.1 currently, I don't find any package with version 16.08.1-56.5 in the Tumbleweed repo.
Maybe you should use YaST or zypper to check from which repo the installed Akonadi packages actually come from, not guess from the rebuild number... ;-)
Kind Regards, Wolfgang
On Sunday, 25 September 2016 17:08:02 BST Wolfgang Bauer wrote:
Am Sonntag, 25. September 2016, 15:35:48 schrieb ianseeks:
Update: just installed tumbleweed:20160924 and the release number is now upto 16.08.1-56.5, i'll run with this for a while and see how it goes
The version number of what?
AFAICS the KDE Applications in Tumbleweed have 16.08.1-1.1 currently, I don't find any package with version 16.08.1-56.5 in the Tumbleweed repo.
Maybe you should use YaST or zypper to check from which repo the installed Akonadi packages actually come from, not guess from the rebuild number... ;-)
Kind Regards, Wolfgang
Applications repro 16.08.1-83.1, downloaded from http://download.opensuse.org/ repositories/KDE:/Applications/openSUSE_Factory_standard Kmail5 is versioned as 16.08.1-83.1 in Yast, the list of files shows the name as kmail, but the Yast package name is kmail5 and kde.bugs only has kmail2 to log against. Too many different names and release numbers have got me all confused.
Am Sonntag, 25. September 2016, 18:19:28 schrieb ianseeks:
Applications repro 16.08.1-83.1, downloaded from http://download.opensuse.org/ repositories/KDE:/Applications/openSUSE_Factory_standard Kmail5 is versioned as 16.08.1-83.1 in Yast, the list of files shows the name as kmail, but the Yast package name is kmail5 and kde.bugs only has kmail2 to log against. Too many different names and release numbers have got me all confused.
And somebody else should know what you installed from where when you just throw those non-telling/confusing version numbers around?
As I think I already told you in the past (could have been to somebody else though), you do not really need KDE:Applications on Tumbleweed. The exact same packages are in the main repo (KDE:Applications is the devel project for Factory/Tumbleweed), they just get there a bit later, after review/staging/testing.
Kind Regards, Wolfgang
On Sunday, 25 September 2016 22:58:10 BST Wolfgang Bauer wrote:
Am Sonntag, 25. September 2016, 18:19:28 schrieb ianseeks:
Applications repro 16.08.1-83.1, downloaded from http://download.opensuse.org/ repositories/KDE:/Applications/openSUSE_Factory_standard Kmail5 is versioned as 16.08.1-83.1 in Yast, the list of files shows the name as kmail, but the Yast package name is kmail5 and kde.bugs only has kmail2 to log against. Too many different names and release numbers have got me all confused.
And somebody else should know what you installed from where when you just throw those non-telling/confusing version numbers around?
As I think I already told you in the past (could have been to somebody else though), you do not really need KDE:Applications on Tumbleweed. The exact same packages are in the main repo (KDE:Applications is the devel project for Factory/Tumbleweed), they just get there a bit later, after review/staging/testing.
Kind Regards, Wolfgang
Ok, thanks
2016-08-21 15:45 GMT+02:00 Christian Boltz opensuse@cboltz.de:
Hello,
Am Sonntag, 21. August 2016, 14:08:33 CEST schrieb Christian Boltz:
Am Sonntag, 21. August 2016, 12:17:33 CEST schrieb Michal Hlavac:
I have problem with akonadi repeating crashes, but not kmail.
Same here.
Some debugging with fvogt on #opensuse-kde shows that this is probaby caused by building akonadi against the new libxapian30 (instead of the previous libxapian22).
For details, see the upstream bug https://bugs.kde.org/show_bug.cgi?id=363741
For those who didn't update Tumbleweed in the last days, it's probably a good idea to zypper al libxapian30 to avoid getting it and the rebuilt version of akonadi and kdepim.
I created a repo with the previous version of libxapian, and akonadi-* and baloo linkpac'd from Factory (so rebuilt against the old libxapian): https://build.opensuse.org/project/show/home:cboltz:branches:openSUSE:Factor... Packages at http://download.opensuse.org/repositories/home:/cboltz:/branches:/openSUSE:/...
Since I installled these packages (using zypper dup --from), I didn't see any akonadi crashes.
In other words: it's probably a good idea to revert the libxamian / xapian-core update in Tumbleweed (including akonadi-* and baloo rebuilds) until this bug gets fixed.
If someone wants to use the fixed packages _now_: I'll keep the repo as long as it's useful for me ;-)
Using TW 20160927 and kmail crashes for me with yet another error, also with Christian's packages with the reverted Xapian. I'm not absolutely sure, but this is probably worth a separate bug report, is it? I'll try to install the necessary debug symbols, just asking, whether anyone has seen this also?
*** Error in `kmail': double free or corruption (fasttop): 0x00000000011f3070 *** ======= Backtrace: ========= /lib64/libc.so.6(+0x7218b)[0x7f3e21e8518b] /lib64/libc.so.6(+0x78546)[0x7f3e21e8b546] /lib64/libc.so.6(+0x78d3e)[0x7f3e21e8bd3e] /usr/lib64/dri/nouveau_dri.so(+0x462e9f)[0x7f3df306ae9f] /usr/lib64/dri/nouveau_dri.so(+0x4630de)[0x7f3df306b0de] /usr/lib64/dri/nouveau_dri.so(+0x4633e2)[0x7f3df306b3e2] /usr/lib64/dri/nouveau_dri.so(+0x1d4d1b)[0x7f3df2ddcd1b] /usr/lib64/dri/nouveau_dri.so(+0x1d4d60)[0x7f3df2ddcd60] /usr/lib64/libQt5Widgets.so.5(+0x1c94a9)[0x7f3e237884a9] /usr/lib64/libQt5Widgets.so.5(_ZN14QWidgetPrivate17sendComposeStatusEP7QWidgetb+0xc1)[0x7f3e237564c1] /usr/lib64/libQt5Widgets.so.5(_ZN14QWidgetPrivate17sendComposeStatusEP7QWidgetb+0x87)[0x7f3e23756487] /usr/lib64/libQt5Widgets.so.5(_ZN14QWidgetPrivate17sendComposeStatusEP7QWidgetb+0x87)[0x7f3e23756487] /usr/lib64/libQt5Widgets.so.5(_ZN14QWidgetPrivate17sendComposeStatusEP7QWidgetb+0x87)[0x7f3e23756487] /usr/lib64/libQt5Widgets.so.5(_ZN14QWidgetPrivate17sendComposeStatusEP7QWidgetb+0x87)[0x7f3e23756487] /usr/lib64/libQt5Widgets.so.5(_ZN14QWidgetPrivate17sendComposeStatusEP7QWidgetb+0x87)[0x7f3e23756487] /usr/lib64/libQt5Widgets.so.5(_ZN14QWidgetPrivate17sendComposeStatusEP7QWidgetb+0x87)[0x7f3e23756487] /usr/lib64/libQt5Widgets.so.5(_ZN14QWidgetPrivate17sendComposeStatusEP7QWidgetb+0x87)[0x7f3e23756487] /usr/lib64/libQt5Widgets.so.5(_ZN14QWidgetPrivate17sendComposeStatusEP7QWidgetb+0x87)[0x7f3e23756487] /usr/lib64/libQt5Widgets.so.5(_ZN14QWidgetPrivate17sendComposeStatusEP7QWidgetb+0x87)[0x7f3e23756487] /usr/lib64/libQt5Widgets.so.5(_ZN14QWidgetPrivate17sendComposeStatusEP7QWidgetb+0x87)[0x7f3e23756487] /usr/lib64/libQt5Widgets.so.5(+0x16e782)[0x7f3e2372d782] /usr/lib64/libQt5Widgets.so.5(+0x16f5ce)[0x7f3e2372e5ce] /usr/lib64/libQt5Widgets.so.5(+0x171e2a)[0x7f3e23730e2a] /usr/lib64/libQt5Widgets.so.5(+0x171fe9)[0x7f3e23730fe9] /usr/lib64/libQt5Widgets.so.5(_ZN14QWidgetPrivate16syncBackingStoreEv+0x4f)[0x7f3e2375095f] /usr/lib64/libQt5Widgets.so.5(_ZN7QWidget5eventEP6QEvent+0x3d8)[0x7f3e23768678] /usr/lib64/libQt5Widgets.so.5(_ZN11QMainWindow5eventEP6QEvent+0x16b)[0x7f3e23881b5b] /usr/lib64/libKF5XmlGui.so.5(_ZN11KMainWindow5eventEP6QEvent+0x57)[0x7f3e219206a7] /usr/lib64/libKF5XmlGui.so.5(_ZN13KXmlGuiWindow5eventEP6QEvent+0x25)[0x7f3e219655b5] /usr/lib64/libQt5Widgets.so.5(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x9c)[0x7f3e23722acc] /usr/lib64/libQt5Widgets.so.5(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x25f)[0x7f3e23727f6f] /usr/lib64/libQt5Core.so.5(_ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent+0x110)[0x7f3e229dc9b0] /usr/lib64/libQt5Core.so.5(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x2dc)[0x7f3e229de93c] /usr/lib64/libQt5Core.so.5(+0x2e0683)[0x7f3e22a32683] /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x2a7)[0x7f3e17560677] /usr/lib64/libglib-2.0.so.0(+0x4d8e0)[0x7f3e175608e0] /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7f3e1756098c] /usr/lib64/libQt5Core.so.5(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x5f)[0x7f3e22a32a8f] /usr/lib64/libQt5Core.so.5(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0xfa)[0x7f3e229da6fa] /usr/lib64/libQt5Core.so.5(_ZN16QCoreApplication4execEv+0x9c)[0x7f3e229e2f0c] kmail[0x403cbf] /lib64/libc.so.6(__libc_start_main+0xf1)[0x7f3e21e33291] kmail(_start+0x2a)[0x4043aa]
René
2016-09-29 9:35 GMT+02:00 René Krell renda.krell@gmail.com:
Using TW 20160927 and kmail crashes for me with yet another error, also with Christian's packages with the reverted Xapian. I'm not absolutely sure, but this is probably worth a separate bug report, is it? I'll try to install the necessary debug symbols, just asking, whether anyone has seen this also?
*** Error in `kmail': double free or corruption (fasttop):
This is somewhat different - I filed a separate bug report for it: https://bugs.kde.org/show_bug.cgi?id=369514. But might be related to the recent update of xf86-video-nouveau-1.0.13-1.1.x86_64.
René
On Thursday, 29 September 2016 09:51:36 BST René Krell wrote:
2016-09-29 9:35 GMT+02:00 René Krell renda.krell@gmail.com:
Using TW 20160927 and kmail crashes for me with yet another error, also with Christian's packages with the reverted Xapian. I'm not absolutely sure, but this is probably worth a separate bug report, is it? I'll try to install the necessary debug symbols, just asking, whether anyone has seen this also?
*** Error in `kmail': double free or corruption (fasttop):
This is somewhat different - I filed a separate bug report for it: https://bugs.kde.org/show_bug.cgi?id=369514. But might be related to the recent update of xf86-video-nouveau-1.0.13-1.1.x86_64.
René
From reading various bugs, there seems to be a conflict between nouveau and qtwebengine, related to threading and it points to nouveau being not so good at it. Maybe we'll have to install nvidia and see if there is a way to lock the kernel version and nvidia related stuff from updates within tumbleweed until its resolved.
On Thursday, 29 September 2016 09:51:36 BST René Krell wrote:
2016-09-29 9:35 GMT+02:00 René Krell renda.krell@gmail.com:
Using TW 20160927 and kmail crashes for me with yet another error, also with Christian's packages with the reverted Xapian. I'm not absolutely sure, but this is probably worth a separate bug report, is it? I'll try to install the necessary debug symbols, just asking, whether anyone has seen this also?
*** Error in `kmail': double free or corruption (fasttop):
This is somewhat different - I filed a separate bug report for it: https://bugs.kde.org/show_bug.cgi?id=369514. But might be related to the recent update of xf86-video-nouveau-1.0.13-1.1.x86_64.
René
Have a look at this bug report - look familiar?
Op donderdag 29 september 2016 11:42:56 CEST schreef ianseeks:
On Thursday, 29 September 2016 09:51:36 BST René Krell wrote:
2016-09-29 9:35 GMT+02:00 René Krell renda.krell@gmail.com:
Using TW 20160927 and kmail crashes for me with yet another error, also with Christian's packages with the reverted Xapian. I'm not absolutely sure, but this is probably worth a separate bug report, is it? I'll try to install the necessary debug symbols, just asking, whether anyone has seen this also?
*** Error in `kmail': double free or corruption (fasttop):
This is somewhat different - I filed a separate bug report for it: https://bugs.kde.org/show_bug.cgi?id=369514. But might be related to the recent update of xf86-video-nouveau-1.0.13-1.1.x86_64.
René
From reading various bugs, there seems to be a conflict between nouveau and qtwebengine, related to threading and it points to nouveau being not so good at it. Maybe we'll have to install nvidia and see if there is a way to lock the kernel version and nvidia related stuff from updates within tumbleweed until its resolved.
If NVIDIA, wouldn't it be a better option to use DKMS ( the blobs support it: NVIDIA....run --otheroptions --dkms Mind, dkms has to be installed for this to work.
* ianseeks bingmybong@btinternet.com [09-29-16 06:44]:
On Thursday, 29 September 2016 09:51:36 BST René Krell wrote:
2016-09-29 9:35 GMT+02:00 René Krell renda.krell@gmail.com:
Using TW 20160927 and kmail crashes for me with yet another error, also with Christian's packages with the reverted Xapian. I'm not absolutely sure, but this is probably worth a separate bug report, is it? I'll try to install the necessary debug symbols, just asking, whether anyone has seen this also?
*** Error in `kmail': double free or corruption (fasttop):
This is somewhat different - I filed a separate bug report for it: https://bugs.kde.org/show_bug.cgi?id=369514. But might be related to the recent update of xf86-video-nouveau-1.0.13-1.1.x86_64.
René
From reading various bugs, there seems to be a conflict between nouveau and qtwebengine, related to threading and it points to nouveau being not so good at it. Maybe we'll have to install nvidia and see if there is a way to lock the kernel version and nvidia related stuff from updates within tumbleweed until its resolved.
Why would you contrive to lock kernel and nvidia? The only requirement is that you reinstall the nvidia pkg on kernel updates.
On Thursday, 29 September 2016 10:00:29 BST Patrick Shanahan wrote:
- ianseeks bingmybong@btinternet.com [09-29-16 06:44]:
On Thursday, 29 September 2016 09:51:36 BST René Krell wrote:
2016-09-29 9:35 GMT+02:00 René Krell renda.krell@gmail.com:
Using TW 20160927 and kmail crashes for me with yet another error, also with Christian's packages with the reverted Xapian. I'm not absolutely sure, but this is probably worth a separate bug report, is it? I'll try to install the necessary debug symbols, just asking, whether anyone has seen this also?
*** Error in `kmail': double free or corruption (fasttop):
This is somewhat different - I filed a separate bug report for it: https://bugs.kde.org/show_bug.cgi?id=369514. But might be related to the recent update of xf86-video-nouveau-1.0.13-1.1.x86_64.
René
From reading various bugs, there seems to be a conflict between nouveau and qtwebengine, related to threading and it points to nouveau being not so good at it. Maybe we'll have to install nvidia and see if there is a way to lock the kernel version and nvidia related stuff from updates within tumbleweed until its resolved.
Why would you contrive to lock kernel and nvidia? The only requirement is that you reinstall the nvidia pkg on kernel updates.
I know but i thought it'll be less aggravation to lock it until nouveau/ qtwebengine is sorted out. Perhaps when i'm not so tired, i'll get the kernel/ nvidia sorted, i think i have to install a lot of other stuff first, its been a long time since i bothered with nvidia.
Am Sonntag, 21. August 2016, 15:45:12 schrieb Christian Boltz:
I created a repo with the previous version of libxapian, and akonadi-* and baloo linkpac'd from Factory (so rebuilt against the old libxapian):
FYI, the crash with Xapian 1.4 apparently has been fixed today: http://commits.kde.org/akonadi-search/1e70d63a9439f48b5f1a70accac531a10f4e42...
So with 16.08.2 (to be released next Thursday, it will take of course a little bit longer for it to reach Tumbleweed) those packages should not be needed any more.
Kind Regards, Wolfgang
On Monday, 10 October 2016 11:31:11 BST Wolfgang Bauer wrote:
Am Sonntag, 21. August 2016, 15:45:12 schrieb Christian Boltz:
I created a repo with the previous version of libxapian, and akonadi-*
and baloo linkpac'd from Factory (so rebuilt against the old libxapian):
FYI, the crash with Xapian 1.4 apparently has been fixed today: http://commits.kde.org/akonadi-search/1e70d63a9439f48b5f1a70accac531a10f4e42 39
So with 16.08.2 (to be released next Thursday, it will take of course a little bit longer for it to reach Tumbleweed) those packages should not be needed any more.
Kind Regards, Wolfgang
Thanks for the update
-
Andreas Mahel -
Bruno Friedmann -
Carl Symons -
Christian Boltz -
ianseeks -
ianseeks -
Knurpht - Gertjan Lettink -
Michal Hlavac -
Patrick Shanahan -
René Krell -
Wolfgang Bauer