Bug 350344

Summary: desktop crash
Product: [Unmaintained] plasma4 Reporter: mjc7129
Component: generalAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED UNMAINTAINED    
Severity: crash Keywords: drkonqi
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description mjc7129 2015-07-18 15:07:16 UTC
Application: plasma-desktop (4.11.20)
KDE Platform Version: 4.14.9 (Compiled from sources)
Qt Version: 4.8.6
Operating System: Linux 3.16.7-21-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:

Configuring the desktop to change the desktop screen background.

-- Backtrace:
Application: Plasma Desktop Shell (plasma-desktop), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1edb33e780 (LWP 2021))]

Thread 4 (Thread 0x7f1eb101d700 (LWP 2024)):
#0  0x00007f1ed9bf905f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f1ecc4868cb in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0x7f1ecc784f00 <QTWTF::pageheap_memory>) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x00007f1ecc486909 in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=<optimized out>) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x00007f1ed9bf50a4 in start_thread () from /lib64/libpthread.so.0
#4  0x00007f1ed896208d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f1e2ab41700 (LWP 2026)):
#0  0x00007f1ed8959c5d in poll () from /lib64/libc.so.6
#1  0x00007f1ed5a6cbe4 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f1ed5a6ccec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f1ed9fba0de in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#4  0x00007f1ed9f8be6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#5  0x00007f1ed9f8c165 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#6  0x00007f1ed9e890bf in QThread::exec() () from /usr/lib64/libQtCore.so.4
#7  0x00007f1ed9f6d783 in ?? () from /usr/lib64/libQtCore.so.4
#8  0x00007f1ed9e8b79f in ?? () from /usr/lib64/libQtCore.so.4
#9  0x00007f1ed9bf50a4 in start_thread () from /lib64/libpthread.so.0
#10 0x00007f1ed896208d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f1e29c6d700 (LWP 2029)):
#0  0x00007f1ed8959c5d in poll () from /lib64/libc.so.6
#1  0x00007f1ed5a6cbe4 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f1ed5a6ccec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f1ed9fba0de in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#4  0x00007f1ed9f8be6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#5  0x00007f1ed9f8c165 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#6  0x00007f1ed9e890bf in QThread::exec() () from /usr/lib64/libQtCore.so.4
#7  0x00007f1ed9f6d783 in ?? () from /usr/lib64/libQtCore.so.4
#8  0x00007f1ed9e8b79f in ?? () from /usr/lib64/libQtCore.so.4
#9  0x00007f1ed9bf50a4 in start_thread () from /lib64/libpthread.so.0
#10 0x00007f1ed896208d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f1edb33e780 (LWP 2021)):
[KCrash Handler]
#5  scopeChain (this=<error reading variable: Cannot access memory at address 0x6c00700000009d>) at ../3rdparty/javascriptcore/JavaScriptCore/interpreter/Register.h:203
#6  scopeChain (this=<error reading variable: Cannot access memory at address 0x6c00700000009d>) at ../3rdparty/javascriptcore/JavaScriptCore/interpreter/CallFrame.h:45
#7  globalData (this=<error reading variable: Cannot access memory at address 0x6c00700000009d>) at ../3rdparty/javascriptcore/JavaScriptCore/interpreter/CallFrame.h:74
#8  jsString (s=..., exec=<error reading variable: Cannot access memory at address 0x6c00700000009d>) at ../3rdparty/javascriptcore/JavaScriptCore/runtime/JSString.h:484
#9  QScriptDeclarativeClass::Value::Value (this=0x7fff2bdeae20, eng=0x4c12b18, value=...) at bridge/qscriptdeclarativeclass.cpp:132
#10 0x00007f1ecbd62e7b in toValue (e=0x4725bf0, this=0x7fff2bdeab10) at qml/qdeclarativeobjectscriptclass.cpp:867
#11 QDeclarativeObjectMethodScriptClass::callMethod (this=this@entry=0x4faf140, object=0x436eca0, index=32, returnType=<optimized out>, argCount=argCount@entry=0, argTypes=argTypes@entry=0x0, ctxt=ctxt@entry=0x7f1e15c8d1e0) at qml/qdeclarativeobjectscriptclass.cpp:988
#12 0x00007f1ecbd639bb in QDeclarativeObjectMethodScriptClass::callPrecise (this=0x4faf140, object=0x436eca0, data=..., ctxt=0x7f1e15c8d1e0) at qml/qdeclarativeobjectscriptclass.cpp:953
#13 0x00007f1ecbd6442b in QDeclarativeObjectMethodScriptClass::call (this=<optimized out>, o=<optimized out>, ctxt=<optimized out>) at qml/qdeclarativeobjectscriptclass.cpp:922
#14 0x00007f1ecc4fd9a4 in QScript::DeclarativeObjectDelegate::call (exec=<optimized out>, callee=<optimized out>, thisValue=..., args=...) at bridge/qscriptdeclarativeobject.cpp:154
#15 0x00007f1ecc3f8cf8 in QTJSC::NativeFuncWrapper::operator() (this=this@entry=0x7fff2bdeaed0, exec=0x7f1e15c8d1e0, jsobj=jsobj@entry=0x7f1eb93e5b40, thisValue=..., argList=...) at ../3rdparty/javascriptcore/JavaScriptCore/runtime/CallData.cpp:46
#16 0x00007f1ecc3d6c90 in QTJSC::cti_op_call_NotJSFunction (args=0x7fff2bdeaf20) at ../3rdparty/javascriptcore/JavaScriptCore/jit/JITStubs.cpp:1780
#17 0x00007f1e309da22a in ?? ()
#18 0x0000000000000000 in ?? ()

Reported using DrKonqi
Comment 1 Nate Graham 2018-06-08 18:36:24 UTC
Hello!

This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug has already been resolved in Plasma 5.

Accordingly, we hope you understand why we must close this bug report. If the issue described  here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham