Red Hat Bugzilla – Bug 1258902
[abrt] kdelibs: KCrash::defaultCrashHandler(): kdeinit4 killed by SIGSEGV
Last modified: 2015-11-23 11:19:29 EST
Description of problem:
Logged in to KDE.
Version-Release number of selected component:
cmdline: 'kdeinit4: plasma-desktop [kdeinit]' '' '' '' '' '' '' '' '' '' '' '' '' ''
runlevel: N 3
Thread no. 1 (10 frames)
#1 KCrash::defaultCrashHandler at /usr/src/debug/kdelibs-4.14.8/kdeui/util/kcrash.cpp:352
#10 QScript::GlobalObject::GlobalObject at bridge/qscriptglobalobject.cpp:45
#11 QScriptEnginePrivate::QScriptEnginePrivate at api/qscriptengine.cpp:981
Created attachment 1069010 [details]
Created attachment 1069011 [details]
Created attachment 1069012 [details]
Created attachment 1069013 [details]
Created attachment 1069014 [details]
Created attachment 1069015 [details]
Created attachment 1069016 [details]
Created attachment 1069017 [details]
Created attachment 1069018 [details]
Created attachment 1069019 [details]
*** Bug 1258824 has been marked as a duplicate of this bug. ***
KDE won't start as a result.
I tried to do a build of the latest Qt which includes some aarch64 fixes and also backported some other aarch64 fixes from Ubuntu. If that helps, we will need to either update Qt or backport all aarch64 related fixes. Anyway, here is a test build https://brewweb.devel.redhat.com/taskinfo?taskID=9786435.
(In reply to Jan Grulich from comment #13)
> I tried to do a build of the latest Qt which includes some aarch64 fixes and
> also backported some other aarch64 fixes from Ubuntu. If that helps, we will
> need to either update Qt or backport all aarch64 related fixes. Anyway, here
> is a test build https://brewweb.devel.redhat.com/taskinfo?taskID=9786435.
This build fixes it! I can successfully login to KDE and everything seems to work fine.
Fixed in qt-4.8.5-11.el7.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.