Summary: | After upgrading from fedora 20 to 24 everything crashes on startup, KDE unusable | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | kde.org |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED UPSTREAM | ||
Severity: | crash | CC: | gissf1, kde.org |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.7.5 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
STDERR from startx
New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi |
Description
kde.org
2016-09-19 23:05:03 UTC
Created attachment 101191 [details]
STDERR from startx
The backtrace is unfortunately missing debug symbols. Please install debug packages for KWin and Qt and add a new backtrace. *** Bug 380444 has been marked as a duplicate of this bug. *** (In reply to Christoph Feck from comment #3) > *** Bug 380444 has been marked as a duplicate of this bug. *** Does that imply that I am missing debug symbols in the Bug 380444 bug report as well? This was a different problem on a completely different machine (and a different distro). I just want to make sure if I'm reporting bugs that they are useful information rather than spam. Also, the machine that generated this Fedora bug report will likely not come back online any time soon. It ended up having a hardware issue and purchasing the replacement hardware is not a high priority. I may just do a data backup and junk the machine. I would consider this older bug report closed for me unless the other person on CC has something to add. Brian, correct, your backtrace lacks even more debug symbols than this one. If you can provide a backtrace from a recent version with KWin/Qt debug information (including line numbers), please add a comment. Created attachment 107727 [details]
New crash information added by DrKonqi
kwin_x11 (5.10.5) using Qt 5.7.1
- What I was doing when the application crashed:
Starting up. This time in fedora 26.
I've installed debuginfo packages this time. Let me know if I'm missing any you think are critical.
-- Backtrace (Reduced):
#6 0x00007f7827c4fdb0 in QTJSC::ExecutablePool::systemAlloc(unsigned long) () at /lib64/libQt5Script.so.5
#7 0x00007f7827cdffda in QTJSC::JSGlobalData::JSGlobalData(bool) () at /lib64/libQt5Script.so.5
#8 0x00007f7827ce0428 in QTJSC::JSGlobalData::create() () at /lib64/libQt5Script.so.5
#9 0x00007f7827d8a9e0 in QScriptEnginePrivate::QScriptEnginePrivate() () at /lib64/libQt5Script.so.5
#10 0x00007f7827d8b5ff in QScriptEngine::QScriptEngine(QObject*) () at /lib64/libQt5Script.so.5
New backtrace. Sorry, but that backtrace isn't better. It seems pretty complete to me. What do you think is missing? (In reply to kde.org from comment #9) > It seems pretty complete to me. What do you think is missing? It isn't. It's lacking debug symbols. We don't have code lines, we don't have variable values, etc. etc. Created attachment 107741 [details]
New crash information added by DrKonqi
kwin_x11 (5.10.5) using Qt 5.7.1
- What I was doing when the application crashed:
starting up.
If these debug symbols are not enough please tell me the commands to use to install the debug symbols needed.
-- Backtrace (Reduced):
#6 0x00007fbc2f41fdb0 in QTJSC::FixedVMPoolAllocator::FixedVMPoolAllocator(unsigned long, unsigned long) (totalHeapSize=2147483648, commonSize=<optimized out>, this=0x55c2605b5050) at /usr/src/debug/qtscript-opensource-src-5.7.1/src/3rdparty/javascriptcore/JavaScriptCore/jit/ExecutableAllocatorFixedVMPool.cpp:314
#7 0x00007fbc2f41fdb0 in QTJSC::ExecutablePool::systemAlloc(unsigned long) (size=size@entry=16384) at /usr/src/debug/qtscript-opensource-src-5.7.1/src/3rdparty/javascriptcore/JavaScriptCore/jit/ExecutableAllocatorFixedVMPool.cpp:447
#8 0x00007fbc2f4affda in QTJSC::ExecutablePool::ExecutablePool(unsigned long) (n=16384, this=0x7fbc08596960) at /usr/src/debug/qtscript-opensource-src-5.7.1/src/3rdparty/javascriptcore/JavaScriptCore/jit/ExecutableAllocator.h:258
#9 0x00007fbc2f4affda in QTJSC::ExecutablePool::create(unsigned long) (n=16384) at /usr/src/debug/qtscript-opensource-src-5.7.1/src/3rdparty/javascriptcore/JavaScriptCore/jit/ExecutableAllocator.h:97
#10 0x00007fbc2f4affda in QTJSC::ExecutableAllocator::ExecutableAllocator() (this=0x7fbc085909c8) at /usr/src/debug/qtscript-opensource-src-5.7.1/src/3rdparty/javascriptcore/JavaScriptCore/jit/ExecutableAllocator.h:150
That backtrace is better! We see that the crash happens in scripting module inside Qt. If you want you can report the bug against Qt, but please note that your Qt version is no longer maintained by Qt. To workaround you can try to disable all scripts. Created attachment 111540 [details]
New crash information added by DrKonqi
kwin_x11 (5.12.2) using Qt 5.9.4
- What I was doing when the application crashed:
starting up, just like before.
How do I disable qt scripts?
-- Backtrace (Reduced):
#6 0x00007f14d5223b20 in QTJSC::FixedVMPoolAllocator::FixedVMPoolAllocator(unsigned long, unsigned long) (totalHeapSize=2147483648, commonSize=<optimized out>, this=0x56094d8add50) at ../3rdparty/javascriptcore/JavaScriptCore/jit/ExecutableAllocatorFixedVMPool.cpp:314
#7 0x00007f14d5223b20 in QTJSC::ExecutablePool::systemAlloc(unsigned long) (size=size@entry=16384) at ../3rdparty/javascriptcore/JavaScriptCore/jit/ExecutableAllocatorFixedVMPool.cpp:447
#8 0x00007f14d52b2b03 in QTJSC::ExecutablePool::ExecutablePool(unsigned long) (n=16384, this=0x7f14a1cf6960) at ../3rdparty/javascriptcore/JavaScriptCore/jit/ExecutableAllocator.h:258
#9 0x00007f14d52b2b03 in QTJSC::ExecutablePool::create(unsigned long) (n=16384) at ../3rdparty/javascriptcore/JavaScriptCore/jit/ExecutableAllocator.h:97
#10 0x00007f14d52b2b03 in QTJSC::ExecutableAllocator::ExecutableAllocator() (this=0x7f14a1cf09c8) at ../3rdparty/javascriptcore/JavaScriptCore/jit/ExecutableAllocator.h:150
|