| Summary: | Various KCMs randomly crash in their destructors when switching to a different KCM | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Thiago Sueto <herzenschein> |
| Component: | generic-crash | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | crash | CC: | 79625490833, a.nicastro.pub+kde, adressepoub.rl, aleixpol, anchebooh, bugseforuns, cchinicz, charlesetheridge2, epost.kde, fa09d8sf94rdaf, fastos2016, filhocf, gt.ajustis.i, Jarlrusseln, kde-bi82, kde, kdelibs-bugs, levy.santanna, lyrixcaz, manoel.miguel1737, matejm98mthw, nate, nemanjamucalovic, plasma-bugs, qianshangyin631, qydwhotmail, rafael.palma.lima, rsntheking, rstreeter78 |
| Priority: | HI | Keywords: | drkonqi |
| Version: | 5.20.4 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| See Also: |
https://bugs.kde.org/show_bug.cgi?id=439192 https://bugs.kde.org/show_bug.cgi?id=464893 |
||
| Latest Commit: | https://invent.kde.org/qt/qt/qtdeclarative/-/commit/d1b9a4cacfb966cf0a37983d8f8044f3aedf5de3 | Version Fixed In: | Qt 6.5.0 |
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
Thiago Sueto
2020-09-01 05:58:20 UTC
Additional information: Opening each of the faulty KCMs individually works, but clicking on any other KCM leads to the same crash. Likewise, closing System Settings also leads to the same crash. Just tested this: it's Wayland-only, impossible to reproduce on Xorg. No longer reproducible on master. Created attachment 131647 [details]
New crash information added by DrKonqi
systemsettings5 (5.19.5) using Qt 5.15.0
- What I was doing when the application crashed:
I have been using it completely normal, but for me it happened most often when i was changing between multiple pages
-- Backtrace (Reduced):
#5 0x00007f7277df73f7 in QQuickItemLayer::~QQuickItemLayer (this=0x55994ed4d870, __in_chrg=<optimized out>) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.3.x86_64/src/quick/items/qquickitem.cpp:8335
#6 0x00007f7277df7439 in QQuickItemLayer::~QQuickItemLayer (this=0x55994ed4d870, __in_chrg=<optimized out>) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.3.x86_64/src/quick/items/qquickitem.cpp:8333
#7 0x00007f7277f6e3f3 in QAccessibleQuickItem::role (this=0x55994f0bef80) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.3.x86_64/include/QtQuick/../../src/quick/items/qquickitem.h:468
#8 0x00007f7273ccb3da in AtSpiAdaptor::pathForInterface (this=this@entry=0x55994dd65c90, interface=0x55994f0bef80) at atspiadaptor.cpp:1538
#9 0x00007f7273ccd594 in AtSpiAdaptor::notifyStateChange (this=this@entry=0x55994dd65c90, interface=<optimized out>, state=..., value=0) at atspiadaptor.cpp:873
Anyone still experiencing this issue on Wayland? Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! Based on a duplicate report, this is okay on Wayland now, but still crashing on X11. *** Bug 428879 has been marked as a duplicate of this bug. *** *** Bug 429076 has been marked as a duplicate of this bug. *** *** Bug 428461 has been marked as a duplicate of this bug. *** *** Bug 427516 has been marked as a duplicate of this bug. *** *** Bug 429412 has been marked as a duplicate of this bug. *** *** Bug 427444 has been marked as a duplicate of this bug. *** *** Bug 421556 has been marked as a duplicate of this bug. *** Created attachment 133508 [details]
New crash information added by DrKonqi
systemsettings5 (5.20.80) using Qt 5.15.1
I still getting it consistently on wayland
-- Backtrace (Reduced):
#4 0x00007f88402ad5fa in QQmlData::wasDeleted (object=0x5570cf7b2630) at /usr/src/debug/libqt5-qtdeclarative-5.15.1-ku.2.1.x86_64/include/QtQml/5.15.1/QtQml/private/../../../../../src/qml/qml/qqmldata_p.h:338
#5 QV4::QObjectWrapper::getQmlProperty (engine=engine@entry=0x5570cf722cc0, qmlContext=qmlContext@entry=0x5570cf72e750, object=0x5570cf7b2630, name=0x7f88247115e8, revisionMode=revisionMode@entry=QV4::QObjectWrapper::CheckRevision, hasProperty=hasProperty@entry=0x7ffe6ec0a128, property=0x7ffe6ec0a130) at /usr/src/debug/libqt5-qtdeclarative-5.15.1-ku.2.1.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:360
#6 0x00007f884028d01a in QV4::QQmlContextWrapper::getPropertyAndBase (resource=<optimized out>, id=..., receiver=<optimized out>, hasProperty=0x7ffe6ec0a1a7, base=0x0, lookup=0x0) at /usr/src/debug/libqt5-qtdeclarative-5.15.1-ku.2.1.x86_64/include/QtQml/5.15.1/QtQml/private/../../../../../src/qml/common/qv4staticvalue_p.h:325
#7 0x00007f884028d8e3 in QV4::QQmlContextWrapper::resolveQmlContextPropertyLookupGetter (l=0x5570cf7fa330, engine=0x5570cf722cc0, base=0x0) at /usr/src/debug/libqt5-qtdeclarative-5.15.1-ku.2.1.x86_64/include/QtQml/5.15.1/QtQml/private/../../../../../src/qml/common/qv4staticvalue_p.h:325
#8 0x00007f88402ca160 in QV4::Moth::VME::interpret (frame=0x7ffe6ec0a390, engine=0x5570cf722cc0, code=0x7f881ffeaadb "\030\n(P\030\r\247g\001") at /usr/src/debug/libqt5-qtdeclarative-5.15.1-ku.2.1.x86_64/src/qml/jsruntime/qv4vme_moth.cpp:585
Created attachment 133692 [details]
New crash information added by DrKonqi
systemsettings5 (5.20.2) using Qt 5.15.2
- What I was doing when the application crashed:
Changing the wallpaper category of the "Wallpaper of the day" plugin, afterwards i locked the screen to see the changes, then closed the lock screen appareance settings and while the application exited, it also crashed upon exit.
- Custom settings of the application:
Had the "Wallpaper of the day" plugin enabled.
-- Backtrace (Reduced):
#4 0x00007fa5321f48aa in QQmlData::wasDeleted (object=0x558dbe34af00) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-1.1.x86_64/include/QtQml/5.15.2/QtQml/private/../../../../../src/qml/qml/qqmldata_p.h:338
#5 QV4::QObjectWrapper::getQmlProperty (engine=engine@entry=0x558dbe319f80, qmlContext=qmlContext@entry=0x558dbe322fb0, object=0x558dbe34af00, name=0x7fa4bd3185e8, revisionMode=revisionMode@entry=QV4::QObjectWrapper::CheckRevision, hasProperty=hasProperty@entry=0x7fffd81593c8, property=0x7fffd81593d0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-1.1.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:360
#6 0x00007fa5321d42ca in QV4::QQmlContextWrapper::getPropertyAndBase (resource=<optimized out>, id=..., receiver=<optimized out>, hasProperty=0x7fffd8159447, base=0x0, lookup=0x0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-1.1.x86_64/include/QtQml/5.15.2/QtQml/private/../../../../../src/qml/common/qv4staticvalue_p.h:325
#7 0x00007fa5321d4b93 in QV4::QQmlContextWrapper::resolveQmlContextPropertyLookupGetter (l=0x558dbe3947c0, engine=0x558dbe319f80, base=0x0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-1.1.x86_64/include/QtQml/5.15.2/QtQml/private/../../../../../src/qml/common/qv4staticvalue_p.h:325
#8 0x00007fa532211410 in QV4::Moth::VME::interpret (frame=0x7fffd8159630, engine=0x558dbe319f80, code=0x7fa4bccf8a0b "\030\n(N\030\r\247a\001") at /usr/src/debug/libqt5-qtdeclarative-5.15.2-1.1.x86_64/src/qml/jsruntime/qv4vme_moth.cpp:585
*** Bug 429786 has been marked as a duplicate of this bug. *** *** Bug 429983 has been marked as a duplicate of this bug. *** *** Bug 430496 has been marked as a duplicate of this bug. *** *** Bug 431103 has been marked as a duplicate of this bug. *** *** Bug 431040 has been marked as a duplicate of this bug. *** *** Bug 431249 has been marked as a duplicate of this bug. *** *** Bug 431409 has been marked as a duplicate of this bug. *** *** Bug 431419 has been marked as a duplicate of this bug. *** Created attachment 134783 [details]
New crash information added by DrKonqi
systemsettings5 (5.20.5) using Qt 5.15.2
- What I was doing when the application crashed:
Configuring global shotcuts
- Unusual behavior I noticed:
I saved the shortcuts with apply button but they didn't actually works, also all shorcuts are unconfigured, I can't do an Alt + Tab
- Custom settings of the application:
-- Backtrace (Reduced):
#4 0x00007fcd25320504 in KGlobalShortcutInfo::componentUniqueName() const () from /lib64/libKF5GlobalAccel.so.5
#6 0x00007fccf0cad232 in QtPrivate::QFunctorSlotObject<GlobalAccelModel::addApplication(QString const&, QString const&)::{lambda()#2}::operator()() const::{lambda()#2}, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () from /usr/lib64/qt5/plugins/kcms/kcm_keys.so
#7 0x00007fcd2670b386 in void doActivate<false>(QObject*, int, void**) () from /lib64/libQt5Core.so.5
#8 0x00007fcd254ae383 in QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) () from /lib64/libQt5DBus.so.5
#9 0x00007fcd26703d1e in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5
That last trace (#26) is quite different. I've split as https://bugs.kde.org/show_bug.cgi?id=431508 Created attachment 134791 [details]
New crash information added by DrKonqi
systemsettings5 (5.20.5) using Qt 5.15.2
- What I was doing when the application crashed:
While inside the Screen Lock configuration menu for the Workspace Behavior section, i backed out by hitting "All Settings" which resaulted in my system settings app crashing, i tried to replicate the bug by following the same steps, and it occurs essentially every time.
The same bug also occured in 5.20.4, So it stands to reason this bug is a consistent/longstanding bug as opposed to a new one.
Hopefully the attatched crash info will be of use in bugfixing.
Using KDE 5.20.5 on OpenSUSE Tumbleweed 20210110
- Custom settings of the application:
-- Backtrace (Reduced):
#4 0x00007f04628dc8aa in QQmlData::wasDeleted (object=0x56115daae200) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-1.1.x86_64/include/QtQml/5.15.2/QtQml/private/../../../../../src/qml/qml/qqmldata_p.h:338
#5 QV4::QObjectWrapper::getQmlProperty (engine=engine@entry=0x56115cf66520, qmlContext=qmlContext@entry=0x56115da31cc0, object=0x56115daae200, name=0x7f04015995e8, revisionMode=revisionMode@entry=QV4::QObjectWrapper::CheckRevision, hasProperty=hasProperty@entry=0x7ffc657360b8, property=0x7ffc657360c0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-1.1.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:360
#6 0x00007f04628bc2ca in QV4::QQmlContextWrapper::getPropertyAndBase (resource=<optimized out>, id=..., receiver=<optimized out>, hasProperty=0x7ffc65736137, base=0x0, lookup=0x0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-1.1.x86_64/src/qml/jsruntime/qv4qmlcontext.cpp:316
#7 0x00007f04628bcb93 in QV4::QQmlContextWrapper::resolveQmlContextPropertyLookupGetter (l=0x56115d0b0500, engine=0x56115cf66520, base=0x0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-1.1.x86_64/src/qml/jsruntime/qv4qmlcontext.cpp:481
#8 0x00007f04628f9410 in QV4::Moth::VME::interpret (frame=0x7ffc65736320, engine=0x56115cf66520, code=0x7f0400b3aadb "\030\n(P\030\r\247g\001") at /usr/src/debug/libqt5-qtdeclarative-5.15.2-1.1.x86_64/src/qml/jsruntime/qv4vme_moth.cpp:585
*** Bug 431472 has been marked as a duplicate of this bug. *** Lowering priority as most of the duplicate bug reports were in fact examples of Bug 431419. *** Bug 435962 has been marked as a duplicate of this bug. *** This doesn't seem to be reproducible for me on Plasma 5.22.4 on X11 or Wayland now. *** Bug 449589 has been marked as a duplicate of this bug. *** *** Bug 450164 has been marked as a duplicate of this bug. *** From Bug 450164, it seems that installing the package that provides qqmldata_p.h may fix it. Is anyone else able to reproduc ethat? (In reply to Nate Graham from comment #35) > From Bug 450164, it seems that installing the package that provides > qqmldata_p.h may fix it. Is anyone else able to reproduc ethat? Can't find that file on my system nor within a package on tumblewed, i have not hit this bug in a long time though. In a fresh unstable image, the mageia version of plasma https://madb.mageia.org/rpm/show/application/0/release/cauldron/arch/x86_64/name/task-plasma5-5.23.4-1.mga9.noarch.rpm/source/0/t_media/3 *** Bug 449589 has been marked as a duplicate of this bug. *** No duplicate reports in nearly a year. Are you able to reproduce this issue at all in any capacity, Thiago? I reported one of the duplicates of this bug. For me all is working fine now, no more crashes since a long time. Great news. Can you confirm this, Thiago? I haven't been able to reproduce this since 2020 when I reported this if I'm not misremembering. Can confirm I can't reproduce this in either X11 or Wayland with current openSUSE Tumbleweed and on MicroOS Desktop Plasma. Great news! Let's call it fixed, then. *** Bug 468753 has been marked as a duplicate of this bug. *** Got another report with the same backtrace in Plasma 5.27. Re-opening. Should be fixed in Plasma6. |