Bug 432858 - Plasma crashes in DataContainer::checkForUpdate() wheno openig the configuration of Thermal Monitor
Summary: Plasma crashes in DataContainer::checkForUpdate() wheno openig the configurat...
Status: RESOLVED WORKSFORME
Alias: None
Product: libplasma
Classification: Frameworks and Libraries
Component: libplasma (other bugs)
Version First Reported In: 5.71.0
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Marco Martin
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2021-02-12 15:03 UTC by benz.martin
Modified: 2022-12-31 05:25 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
New crash information added by DrKonqi (4.45 KB, text/plain)
2021-02-12 16:55 UTC, benz.martin
Details
New crash information added by DrKonqi (4.45 KB, text/plain)
2021-02-12 17:05 UTC, benz.martin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description benz.martin 2021-02-12 15:03:53 UTC
Application: plasmashell (5.18.6)

Qt Version: 5.12.7
Frameworks Version: 5.71.0
Operating System: Linux 5.3.18-lp152.63-default x86_64
Windowing system: X11
Distribution: "openSUSE Leap 15.2"

-- Information about the crash:
- What I was doing when the application crashed:
I opened the configuration dialog of the thermal monitor widget.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
[KCrash Handler]
#4  QObject::objectName (this=0x7f0c24bc44d0) at kernel/qobject.cpp:1177
#5  0x00007f0c51011d9c in ?? () from /usr/lib64/libKF5Plasma.so.5
#6  0x00007f0c50ffc569 in Plasma::DataContainer::checkForUpdate() () from /usr/lib64/libKF5Plasma.so.5
#7  0x00007f0c02743609 in ExecutableContainer::finished (this=0x55c80fc0fd10, exitCode=<optimized out>, exitStatus=<optimized out>) at /usr/src/debug/plasma5-workspace-5.18.6-lp152.3.3.1.x86_64/dataengines/executable/executable.cpp:45
#8  0x00007f0c4ca10e35 in QMetaObject::activate (sender=sender@entry=0x55c8122eef80, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffe65c587d0) at kernel/qobject.cpp:3804
#9  0x00007f0c4ca11547 in QMetaObject::activate (sender=sender@entry=0x55c8122eef80, m=m@entry=0x7f0c4ce8dc60 <QProcess::staticMetaObject>, local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffe65c587d0) at kernel/qobject.cpp:3657
#10 0x00007f0c4c95ae5f in QProcess::finished (this=this@entry=0x55c8122eef80, _t1=<optimized out>, _t2=<optimized out>) at .moc/moc_qprocess.cpp:338
#11 0x00007f0c4c961ca7 in QProcessPrivate::_q_processDied (this=0x55c80bff5e30) at io/qprocess.cpp:1177
#12 0x00007f0c4c961dc9 in QProcess::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=0x7ffe65c58980) at .moc/moc_qprocess.cpp:215
#13 0x00007f0c4ca10e35 in QMetaObject::activate (sender=sender@entry=0x55c812a07e00, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe65c58980) at kernel/qobject.cpp:3804
#14 0x00007f0c4ca11547 in QMetaObject::activate (sender=sender@entry=0x55c812a07e00, m=m@entry=0x7f0c4ce8fbe0 <QSocketNotifier::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe65c58980) at kernel/qobject.cpp:3657
#15 0x00007f0c4ca1d778 in QSocketNotifier::activated (this=this@entry=0x55c812a07e00, _t1=<optimized out>, _t2=...) at .moc/moc_qsocketnotifier.cpp:140
#16 0x00007f0c4ca1db32 in QSocketNotifier::event (this=0x55c812a07e00, e=0x7ffe65c58c60) at kernel/qsocketnotifier.cpp:266
#17 0x00007f0c4dcbbf2c in QApplicationPrivate::notify_helper (this=this@entry=0x55c80bccb760, receiver=receiver@entry=0x55c812a07e00, e=e@entry=0x7ffe65c58c60) at kernel/qapplication.cpp:3701
#18 0x00007f0c4dcc3540 in QApplication::notify (this=0x7ffe65c58fd0, receiver=0x55c812a07e00, e=0x7ffe65c58c60) at kernel/qapplication.cpp:3447
#19 0x00007f0c4c9e1328 in QCoreApplication::notifyInternal2 (receiver=0x55c812a07e00, event=0x7ffe65c58c60) at kernel/qcoreapplication.cpp:1088
#20 0x00007f0c4c9e14fe in QCoreApplication::sendEvent (receiver=<optimized out>, event=event@entry=0x7ffe65c58c60) at kernel/qcoreapplication.cpp:1476
#21 0x00007f0c4ca3f018 in socketNotifierSourceDispatch (source=0x55c80bca1f40) at kernel/qeventdispatcher_glib.cpp:106
#22 0x00007f0c462e94a4 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#23 0x00007f0c462e9840 in ?? () from /usr/lib64/libglib-2.0.so.0
#24 0x00007f0c462e98cc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#25 0x00007f0c4ca3e3af in QEventDispatcherGlib::processEvents (this=0x55c80be69e30, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#26 0x00007f0c4c9df57a in QEventLoop::exec (this=this@entry=0x7ffe65c58e80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#27 0x00007f0c4c9e8780 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1389
#28 0x000055c809b06b14 in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/plasma5-workspace-5.18.6-lp152.3.3.1.x86_64/shell/main.cpp:228
[Inferior 1 (process 2974) detached]

The reporter indicates this bug may be a duplicate of or related to bug 422230.

Possible duplicates by query: bug 425500, bug 423969, bug 423776, bug 423713, bug 423296.

Reported using DrKonqi
Comment 1 Nate Graham 2021-02-12 16:39:50 UTC
#4  QObject::objectName (this=0x7f0c24bc44d0) at kernel/qobject.cpp:1177
#5  0x00007f0c51011d9c in ?? () from /usr/lib64/libKF5Plasma.so.5
#6  0x00007f0c50ffc569 in Plasma::DataContainer::checkForUpdate() () from /usr/lib64/libKF5Plasma.so.5

We're missing some relevant debug symbols. Could you install the missing debug symbols with `sudo zypper install libKF5Plasma5-debuginfo`, reproduce the crash, and attach a new backtrace? Thanks!
Comment 2 benz.martin 2021-02-12 16:55:26 UTC
Created attachment 135640 [details]
New crash information added by DrKonqi

plasmashell (5.18.6) using Qt 5.12.7

- What I was doing when the application crashed:
right klick on the Thermal Monitor widget -> choose "Thermal Monitor Einrichten" -> plasma crashes

-- Backtrace (Reduced):
#4  QMapNodeBase::nextNode (this=this@entry=0x564731f6e2c0) at tools/qmap.cpp:58
#5  0x00007fc62780a571 in QMapNode<unsigned int, Plasma::SignalRelay*>::nextNode (this=0x564731f6e2c0) at /usr/include/qt5/QtCore/qmap.h:118
#6  QMap<unsigned int, Plasma::SignalRelay*>::const_iterator::operator++ (this=<synthetic pointer>) at /usr/include/qt5/QtCore/qmap.h:494
#7  Plasma::DataContainer::checkForUpdate (this=this@entry=0x564734288bc0) at /usr/src/debug/plasma-framework-5.71.0-lp152.1.1.x86_64/src/plasma/datacontainer.cpp:356
#8  0x00007fc5d8ffc609 in ExecutableContainer::finished (this=0x564734288bc0, exitCode=<optimized out>, exitStatus=<optimized out>) at /usr/src/debug/plasma5-workspace-5.18.6-lp152.3.3.1.x86_64/dataengines/executable/executable.cpp:45
Comment 3 benz.martin 2021-02-12 17:05:53 UTC
Created attachment 135641 [details]
New crash information added by DrKonqi

plasmashell (5.18.6) using Qt 5.12.7

- What I was doing when the application crashed:
right klick on the Thermal Monitor widget -> choose "Thermal Monitor Einrichten" -> plasma crashes

-- Backtrace (Reduced):
#4  QMapNodeBase::nextNode (this=this@entry=0x55e0f173c1d0) at tools/qmap.cpp:58
#5  0x00007fcea0c5d571 in QMapNode<unsigned int, Plasma::SignalRelay*>::nextNode (this=0x55e0f173c1d0) at /usr/include/qt5/QtCore/qmap.h:118
#6  QMap<unsigned int, Plasma::SignalRelay*>::const_iterator::operator++ (this=<synthetic pointer>) at /usr/include/qt5/QtCore/qmap.h:494
#7  Plasma::DataContainer::checkForUpdate (this=this@entry=0x55e0f1a99f60) at /usr/src/debug/plasma-framework-5.71.0-lp152.1.1.x86_64/src/plasma/datacontainer.cpp:356
#8  0x00007fce52010609 in ExecutableContainer::finished (this=0x55e0f1a99f60, exitCode=<optimized out>, exitStatus=<optimized out>) at /usr/src/debug/plasma5-workspace-5.18.6-lp152.3.3.1.x86_64/dataengines/executable/executable.cpp:45
Comment 4 Nate Graham 2021-02-12 17:55:35 UTC
Thank you very much!

Frameworks 5.71 is a bit old at this point. I wonder if it could be already fixed in 5.79.
Comment 5 Justin Zobel 2022-12-01 05:22:03 UTC
Thank you for reporting this issue in KDE software. As it was reported on an older version, can we please ask you to see if you can reproduce the issue with a more recent software version?  
  
If you can confirm this issue still exists in a recent version, please change the version field and the status to "REPORTED" when replying. Thank you!
Comment 6 Bug Janitor Service 2022-12-16 05:15:19 UTC
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!
Comment 7 Bug Janitor Service 2022-12-31 05:25:24 UTC
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!