* Sun Oct 23 2016 fabian@ritter-vogt.de
- Enable PACKAGERS_BUILD=ON to detect cpu capabilities during runtime
* Mon Sep 18 2016 schwab@suse.de
- narrowing-warning.patch: Fix compilation of PsCommentLexer.cpp on
platforms where char is unsigned
* Mon May 30 2016 wbauer@tmo.at
- Re-enable building against Vc-devel-static, it builds fine again
- Remove some unnecessary part from the specfile
Calligra version is 2.9.11-7.1.
It didn’t work for me starting with Tumbleweed snapshot 20161020, the one that introduced 4.8 kernel. It was working prior to that build.
Well, so this problem somehow got introduced by the kernel upgrade I’d say.
And the “fix” to enable PACKAGERS_BUILD=ON is ineffective and unnecessary.
I somehow expected all the time that it won’t help, as it worked before as well.
If somebody still has a kernel 4.7 installed, it would probably be a good idea to boot that and see if calligra works then I suppose.
Would at least show if it is really related to the kernel update or something else…
Krita is the KF5 based version.
And one difference is that it’s built without Vc support currently, because the only available Vc in openSUSE (even in Tumbleweed) is too old.
So it’s probably some breakage there, wouldn’t be the first time.
I’ll build calligra packages without Vc support, would be great if you can test them.
(will take a while though)
Would also explain why it doesn’t crash on 13.2 and Leap, because Vc is only enabled in Tumbleweed.
Vc is a library with “portable, zero-overhead C++ types for explicitly data-parallel programming”.
Simply put it enables calligra to use SSE instructions to speed up certain things.
(I don’t know the details either, I have to admit…)
Apparently something goes wrong with the CPU type detection currently though, so it uses instructions not supported by your CPU (which causes the crash).
The strange thing is just that neither calligra nor Vc has been changed in any way in the last months…
I absolutely agree that correct course of action is fixing the underlying problem, but until that happens it’s better to have a working version in the official repo IMHO.
Yeah, but that would disable it for all systems, even where it might work.
OTOH, I just noticed that Vc has been upgraded to 1.3.0 in the devel project today, as soon as this enters Tumbleweed we’d need to disable Vc for calligra anyway as the KDE4 version only supports Vc 0.7. So we probably might do it now already anyway, I’d say (that’s nothing that I will decide though).
Anyway, I do experience the crash in my Tumbleweed VM too, so I can do some more investigation myself.
) expected, the calligra apps don’t segfault anymore.