Bug 423394 - Plasma 5.19 Crash when trying to interact with the fan speed monitor widget
Summary: Plasma 5.19 Crash when trying to interact with the fan speed monitor widget
Status: RESOLVED DUPLICATE of bug 422780
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.19.1
Platform: Neon Linux
: NOR crash
Target Milestone: 1.0
Assignee: David Edmundson
Keywords: drkonqi
Depends on:
Reported: 2020-06-23 13:27 UTC by Paddy
Modified: 2020-11-24 16:34 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description Paddy 2020-06-23 13:27:11 UTC
Application: plasmashell (5.19.1)

Qt Version: 5.14.2
Frameworks Version: 5.71.0
Operating System: Linux 5.3.0-59-generic x86_64
Windowing system: X11
Distribution: KDE neon User Edition 5.19

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

I was adding several system monitor widgets to my desktop that I had just downloaded from the discover app store, fanspeed monitor was one of these. I then was going to customise each of these widgets to see what data they could display. I right clicked the fanspeed monitor widget, and that is when plasma crashed.

- Custom settings of the application:

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault

[KCrash Handler]
#4  0x0000558c0070c2f0 in ?? ()
#5  0x00007f7201af431f in qQmlPropertyCacheProperty<QV4::String const*> (engine=<optimized out>, obj=obj@entry=0x558bfdcaeb80, name=name@entry=0x7f71e5b385a8, context=context@entry=0x558bf9599b90, local=...) at qml/qqmlpropertycache.cpp:1020
#6  0x00007f7201aed905 in QQmlPropertyCache::property (engine=<optimized out>, obj=obj@entry=0x558bfdcaeb80, name=name@entry=0x7f71e5b385a8, context=context@entry=0x558bf9599b90, local=...) at qml/qqmlpropertycache.cpp:1032
#7  0x00007f72019e16f0 in QV4::QObjectWrapper::findProperty (engine=engine@entry=0x558bf4598fe0, o=o@entry=0x558bfdcaeb80, qmlContext=qmlContext@entry=0x558bf9599b90, name=name@entry=0x7f71e5b385a8, revisionMode=revisionMode@entry=QV4::QObjectWrapper::CheckRevision, local=local@entry=0x7fffd711b1a0) at jsruntime/qv4qobjectwrapper.cpp:230
#8  0x00007f72019e875c in QV4::QObjectWrapper::getQmlProperty (engine=engine@entry=0x558bf4598fe0, qmlContext=qmlContext@entry=0x558bf9599b90, object=0x558bfdcaeb80, name=0x7f71e5b385a8, revisionMode=revisionMode@entry=QV4::QObjectWrapper::CheckRevision, hasProperty=hasProperty@entry=0x7fffd711b278, property=0x7fffd711b280) at jsruntime/qv4qobjectwrapper.cpp:371
#9  0x00007f72019c07ab in QV4::QQmlContextWrapper::getPropertyAndBase (resource=<optimized out>, id=..., receiver=receiver@entry=0x0, hasProperty=hasProperty@entry=0x7fffd711b2f7, base=base@entry=0x0, lookup=0x0, lookup@entry=0x558bf68fb940) at jsruntime/qv4qmlcontext.cpp:316
#10 0x00007f72019c0f75 in QV4::QQmlContextWrapper::resolveQmlContextPropertyLookupGetter (l=0x558bf68fb940, engine=0x558bf4598fe0, base=0x0) at jsruntime/qv4qmlcontext.cpp:481
#11 0x00007f71b111bd52 in ?? ()
#12 0x0000000000000000 in ?? ()

Possible duplicates by query: bug 422780, bug 421761, bug 421732, bug 421197, bug 420949.

Reported using DrKonqi
Comment 1 Nate Graham 2020-11-24 16:34:35 UTC

*** This bug has been marked as a duplicate of bug 422780 ***