Bug 422780 - KDE Plasma crash on 5.19 after trying to change widgets
Summary: KDE Plasma crash on 5.19 after trying to change widgets
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (show other bugs)
Version: 5.19.0
Platform: openSUSE Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
: 421732 423394 425375 429585 432551 (view as bug list)
Depends on:
Blocks:
 
Reported: 2020-06-10 20:55 UTC by mintystezz
Modified: 2022-03-28 13:48 UTC (History)
11 users (show)

See Also:
Latest Commit:
Version Fixed In: Probably 5.20


Attachments
New crash information added by DrKonqi (3.10 KB, text/plain)
2020-06-11 08:17 UTC, Kushagra Chaturvedy
Details
attachment-27199-0.html (1.36 KB, text/html)
2020-06-30 02:43 UTC, mintystezz
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mintystezz 2020-06-10 20:55:43 UTC
Application: plasmashell (5.19.0)

Qt Version: 5.15.0
Frameworks Version: 5.70.0
Operating System: Linux 5.6.14-1-default x86_64
Windowing system: X11
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed: just fixing up the widgets (e.g disk/cp usage) and plasma crash. Also it has stopped showing the sensors

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

[KCrash Handler]
#4  0x000055e58a024810 in  ()
#5  0x00007fd68ebb8933 in qQmlPropertyCacheProperty<QV4::String const*>(QJSEngine*, QObject*, QV4::String const*, QQmlContextData*, QQmlPropertyData&) (engine=<optimized out>, obj=obj@entry=0x55e584a8c690, name=0x7ffd99a34f40, name@entry=0x7fd6821af5a8, context=context@entry=0x55e588e36fc0, local=...) at /usr/include/qt5/QtCore/qstring.h:681
#6  0x00007fd68ebb4135 in QQmlPropertyCache::property(QJSEngine*, QObject*, QV4::String const*, QQmlContextData*, QQmlPropertyData&) (engine=<optimized out>, obj=obj@entry=0x55e584a8c690, name=name@entry=0x7fd6821af5a8, context=context@entry=0x55e588e36fc0, local=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.1.x86_64/src/qml/qml/qqmlpropertycache.cpp:1046
#7  0x00007fd68eaa1707 in QV4::QObjectWrapper::findProperty(QV4::ExecutionEngine*, QObject*, QQmlContextData*, QV4::String*, QV4::QObjectWrapper::RevisionMode, QQmlPropertyData*) (engine=engine@entry=0x55e584948a80, o=o@entry=0x55e584a8c690, qmlContext=qmlContext@entry=0x55e588e36fc0, name=name@entry=0x7fd6821af5a8, revisionMode=revisionMode@entry=QV4::QObjectWrapper::CheckRevision, local=local@entry=0x7ffd99a34fa0) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.1.x86_64/include/QtQml/5.15.0/QtQml/private/../../../../../src/qml/jsruntime/qv4engine_p.h:195
#8  0x00007fd68eaa53b7 in QV4::QObjectWrapper::getQmlProperty(QV4::ExecutionEngine*, QQmlContextData*, QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, bool*, QQmlPropertyData**) (engine=engine@entry=0x55e584948a80, qmlContext=qmlContext@entry=0x55e588e36fc0, object=0x55e584a8c690, name=0x7fd6821af5a8, revisionMode=revisionMode@entry=QV4::QObjectWrapper::CheckRevision, hasProperty=hasProperty@entry=0x7ffd99a35068, property=0x7ffd99a35070) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.1.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:371
#9  0x00007fd68ea84d1a in QV4::QQmlContextWrapper::getPropertyAndBase(QV4::QQmlContextWrapper const*, QV4::PropertyKey, QV4::Value const*, bool*, QV4::Value*, QV4::Lookup*) (resource=<optimized out>, id=..., receiver=<optimized out>, hasProperty=0x7ffd99a350e7, base=0x0, lookup=0x0) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.1.x86_64/include/QtQml/5.15.0/QtQml/private/../../../../../src/qml/common/qv4staticvalue_p.h:325
#10 0x00007fd68ea855e3 in QV4::QQmlContextWrapper::resolveQmlContextPropertyLookupGetter(QV4::Lookup*, QV4::ExecutionEngine*, QV4::Value*) (l=0x55e5875d9b30, engine=0x55e584948a80, base=0x0) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.1.x86_64/include/QtQml/5.15.0/QtQml/private/../../../../../src/qml/common/qv4staticvalue_p.h:325
#11 0x00007fd65acc7cc2 in  ()
#12 0x0000000000000000 in  ()
[Inferior 1 (process 2234) detached]

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

Reported using DrKonqi
Comment 1 Kushagra Chaturvedy 2020-06-11 08:17:48 UTC
Created attachment 129220 [details]
New crash information added by DrKonqi

plasmashell (5.19.0) using Qt 5.14.2

- What I was doing when the application crashed:
I was configuring the memory usage widget and after I changed the style of the display from Pie chart to line chart and hit apply, Plasma crashed abruptly. I tried to to reproduce the crash and have observed that Plasma crashes sometimes(but not every time) when I right click on the widget and click Configure... If it manages to get past that, then it crashes when I try to apply my settings. So far, I observed it for the Memory Usage widget only.

- Unusual behavior I noticed:
The Memory Usage widget wasn't displaying anything and was totally blank which is why I tried to configure it in the first place. Also, if it helps, the configure widget icon has the following unusual text(with matching case,symbols and spacing): &Configure System monitor Sensor

-- Backtrace (Reduced):
#4  0x00007fe29cbf531d in qQmlPropertyCacheProperty<QV4::String const*> (engine=<optimized out>, obj=obj@entry=0x562d7ebf2a70, name=name@entry=0x7fe280c9d720, context=context@entry=0x562d816e05f0, local=...) at qml/qqmlpropertycache.cpp:1020
#5  0x00007fe29cbee905 in QQmlPropertyCache::property (engine=<optimized out>, obj=obj@entry=0x562d7ebf2a70, name=name@entry=0x7fe280c9d720, context=context@entry=0x562d816e05f0, local=...) at qml/qqmlpropertycache.cpp:1032
#6  0x00007fe29cae26f0 in QV4::QObjectWrapper::findProperty (engine=engine@entry=0x562d766b2040, o=o@entry=0x562d7ebf2a70, qmlContext=qmlContext@entry=0x562d816e05f0, name=name@entry=0x7fe280c9d720, revisionMode=revisionMode@entry=QV4::QObjectWrapper::CheckRevision, local=local@entry=0x7ffe239e0b60) at jsruntime/qv4qobjectwrapper.cpp:230
#7  0x00007fe29cae975c in QV4::QObjectWrapper::getQmlProperty (engine=engine@entry=0x562d766b2040, qmlContext=qmlContext@entry=0x562d816e05f0, object=0x562d7ebf2a70, name=0x7fe280c9d720, revisionMode=revisionMode@entry=QV4::QObjectWrapper::CheckRevision, hasProperty=hasProperty@entry=0x7ffe239e0c38, property=0x7ffe239e0c40) at jsruntime/qv4qobjectwrapper.cpp:371
#8  0x00007fe29cac17ab in QV4::QQmlContextWrapper::getPropertyAndBase (resource=<optimized out>, id=..., receiver=receiver@entry=0x0, hasProperty=hasProperty@entry=0x7ffe239e0cb7, base=base@entry=0x7fe280c9d6f8, lookup=0x0, lookup@entry=0x562d7aa57040) at jsruntime/qv4qmlcontext.cpp:316
Comment 2 Dmitry 2020-06-13 03:49:09 UTC
My Plasma also crashed after trying to configure Widgets, and Widgets were empty, such as using CPU and Network speed, tried to add other Widgets, such as Disk Usage and Hard Disk Activity, they were empty too, tried to change themes - it didn’t help, it’s on OpenSUSE Tumbleweed with the updated Plasma 5.19. Update: today a system update has arrived, and some Widgets display has started working, but not all styles work correctly, and Plasma also crashes sometimes when trying to configure them ...
Comment 3 Dmitry 2020-06-30 02:30:47 UTC
I will add more information on the situation today. I have four widgets on my desktop: Clock, Weather, CPU Usage, Network Usage. CPU Usage widget (line chart) does not work correctly, namely, after turning on the PC, only the initial state of the widget is displayed and it is static, but if I only make Log out and then Log in again, this widget starts working properly.
I have Operating System: openSUSE Tumbleweed 20200627
KDE Plasma Version: 5.19.2
KDE Frameworks Version: 5.71.0
Qt Version: 5.15.0
Kernel Version: 5.7.5-1-default
Comment 4 mintystezz 2020-06-30 02:43:10 UTC
Created attachment 129781 [details]
attachment-27199-0.html

I'm no longer on openSUSE tumbleweed with KDE. I'm on Void Linux with
Cinnamon.

On Tue, 30 Jun 2020, 12:30 pm Dmitry, <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=422780
>
> --- Comment #3 from Dmitry <doctor.wotson@gmail.com> ---
> I will add more information on the situation today. I have four widgets on
> my
> desktop: Clock, Weather, CPU Usage, Network Usage. CPU Usage widget (line
> chart) does not work correctly, namely, after turning on the PC, only the
> initial state of the widget is displayed and it is static, but if I only
> make
> Log out and then Log in again, this widget starts working properly.
> I have Operating System: openSUSE Tumbleweed 20200627
> KDE Plasma Version: 5.19.2
> KDE Frameworks Version: 5.71.0
> Qt Version: 5.15.0
> Kernel Version: 5.7.5-1-default
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 5 Nate Graham 2020-11-24 16:34:35 UTC
*** Bug 423394 has been marked as a duplicate of this bug. ***
Comment 6 Nate Graham 2020-11-24 16:35:04 UTC
*** Bug 429585 has been marked as a duplicate of this bug. ***
Comment 7 Nate Graham 2020-11-24 16:36:36 UTC
*** Bug 421732 has been marked as a duplicate of this bug. ***
Comment 8 Nate Graham 2020-11-24 16:37:28 UTC
Scary backtrace not obviously in any KDE code. :/
Comment 9 Nate Graham 2021-02-06 22:00:23 UTC
*** Bug 432551 has been marked as a duplicate of this bug. ***
Comment 10 Nate Graham 2021-02-27 05:06:17 UTC
*** Bug 425375 has been marked as a duplicate of this bug. ***
Comment 11 Nate Graham 2022-03-25 15:44:40 UTC
No reports from Plasma 5.20 or newer, and none within the past 13 months; looks like this was fixed somehow, probably in 5.20.
Comment 12 Berker 2022-03-28 10:48:38 UTC
(In reply to Nate Graham from comment #11)
> No reports from Plasma 5.20 or newer, and none within the past 13 months;
> looks like this was fixed somehow, probably in 5.20.

Sorry to report but me on my Manjaro (testing) KDE Plasma and my friend who uses Manjaro (stable) KDE Plasma have this issue. It mostly crashes when I right-click on desktop and press "Configure Desktop and Wallpaper...". I ran "sudo systemctl -f" before I tried reproducing the bug. Plasmashell core dumped but I don't know how to add the output here without making my reply so long.

My
KDE Plasma Version: 5.24.3
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel: 5.16.17-1-MANJARO (64-bit)
Graphics Platform: X11
Comment 13 Nate Graham 2022-03-28 13:48:00 UTC
It's almost certainly a different issue, and anyway we'd need a backtrace of the crash to be sure. Can you open a new bug report and make sure to include a backtrace of the crash?