Bug 433838 - System monitor crashes after terminating a zombie Gwenview
Summary: System monitor crashes after terminating a zombie Gwenview
Status: RESOLVED WORKSFORME
Alias: None
Product: ksysguard
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: 5.19.5
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2021-03-02 06:52 UTC by Vincent LaConte
Modified: 2022-12-31 05:25 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vincent LaConte 2021-03-02 06:52:17 UTC
Application: ksysguard (5.19.5)

Qt Version: 5.14.2
Frameworks Version: 5.74.0
Operating System: Linux 5.8.0-43-generic x86_64
Windowing system: X11
Distribution: Ubuntu 20.10

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

Gwenview has a history of crashing on my system (I keep using it because even with multiple crashes per session it's a damn useful little app), and sometimes fails to exit fully afterwards. When I use System Monitor to find and issue either SIGTERM or SIGKILL -- often with a keyboard SHIFT-DEL -- a significant % of the time, maybe 20-25% of the time, System Monitor crashes immediately after successful termination of Gwenview. 

I believe one or two other apps have caused a similar ksysguard crash before, but I failed to note which. I will pay more attention next time and submit further info if warranted.

-- Backtrace:
Application: System Monitor (ksysguard), signal: Segmentation fault

[KCrash Handler]
#4  0x00007fae41ec6d2d in operator==(QString const&, QString const&) (s1=..., s2=...) at text/qstring.cpp:3383
#5  0x00007fae42d96e79 in QLabel::setText(QString const&) (this=0x56234c0b6250, text=...) at widgets/qlabel.cpp:287
#6  0x00007fae43b039db in TopLevel::answerReceived(int, QList<QByteArray> const&) (this=0x56234c3a8990, id=<optimized out>, answerList=...) at ./gui/ksysguard.cpp:466
#7  0x00007fae43846122 in KSGRD::SensorAgent::processAnswer(char const*, int) (this=0x56234c3eed30, buf=<optimized out>, buflen=<optimized out>) at ./ksgrd/SensorAgent.cpp:91
#8  0x00007fae4384c325 in KSGRD::SensorShellAgent::msgRcvd() (this=0x56234c3eed30) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qarraydata.h:208
#9  0x00007fae4205a2e6 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffd6961b450, r=0x56234c3eed30, this=0x56234c13a340) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#10 doActivate<false>(QObject*, int, void**) (sender=0x56234c010620, signal_index=15, argv=argv@entry=0x7ffd6961b450) at kernel/qobject.cpp:3870
#11 0x00007fae42054068 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=<optimized out>, m=m@entry=0x7fae422adde0 <QProcess::staticMetaObject>, local_signal_index=local_signal_index@entry=6, argv=argv@entry=0x7ffd6961b450) at kernel/qobject.cpp:3930
#12 0x00007fae41f919c1 in QProcess::readyReadStandardOutput(QProcess::QPrivateSignal) (this=<optimized out>, _t1=...) at .moc/moc_qprocess.cpp:367
#13 0x00007fae41f9711d in QProcessPrivate::tryReadFromChannel(QProcessPrivate::Channel*) (this=0x56234c134cc0, channel=0x56234c134dd0) at io/qprocess.cpp:1057
#14 0x00007fae41f97675 in QProcessPrivate::_q_canReadStandardError() (this=<optimized out>) at io/qprocess.cpp:1084
#15 QProcess::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=0x7ffd6961b600) at .moc/moc_qprocess.cpp:210
#16 0x00007fae4205a320 in doActivate<false>(QObject*, int, void**) (sender=0x56234c3fb550, signal_index=3, argv=argv@entry=0x7ffd6961b600) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395
#17 0x00007fae42054068 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x56234c3fb550, m=m@entry=0x7fae422b01c0 <QSocketNotifier::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd6961b600) at kernel/qobject.cpp:3930
#18 0x00007fae4205d8b5 in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) (this=this@entry=0x56234c3fb550, _t1=<optimized out>, _t2=...) at .moc/moc_qsocketnotifier.cpp:141
#19 0x00007fae4205dc51 in QSocketNotifier::event(QEvent*) (this=0x56234c3fb550, e=0x7ffd6961b700) at kernel/qsocketnotifier.cpp:266
#20 0x00007fae42c60013 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=<optimized out>, receiver=0x56234c3fb550, e=0x7ffd6961b700) at kernel/qapplication.cpp:3685
#21 0x00007fae420241ca in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x56234c3fb550, event=0x7ffd6961b700) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:153
#22 0x00007fae4207c425 in socketNotifierSourceDispatch(GSource*, GSourceFunc, gpointer) (source=0x56234b74b8b0) at kernel/qeventdispatcher_glib.cpp:107
#23 0x00007fae396d74db in g_main_dispatch (context=0x7fae28005000) at ../../../glib/gmain.c:3325
#24 g_main_context_dispatch (context=0x7fae28005000) at ../../../glib/gmain.c:4016
#25 0x00007fae396d7788 in g_main_context_iterate (context=context@entry=0x7fae28005000, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../../../glib/gmain.c:4092
#26 0x00007fae396d7853 in g_main_context_iteration (context=0x7fae28005000, may_block=may_block@entry=1) at ../../../glib/gmain.c:4157
#27 0x00007fae4207b843 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x56234b755e50, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#28 0x00007fae42022a4b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ffd6961b910, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136
#29 0x00007fae4202afc6 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:118
#30 0x00007fae4256ede0 in QGuiApplication::exec() () at kernel/qguiapplication.cpp:1860
#31 0x00007fae42c5ff89 in QApplication::exec() () at kernel/qapplication.cpp:2825
#32 0x00007fae43b04af3 in kdemain(int, char**) (argc=<optimized out>, argv=<optimized out>) at ./gui/ksysguard.cpp:627
#33 0x00007fae438d4cb2 in __libc_start_main (main=0x5623498d5060 <main>, argc=1, argv=0x7ffd6961bb38, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffd6961bb28) at ../csu/libc-start.c:314
#34 0x00005623498d509e in _start ()
[Inferior 1 (process 379566) detached]

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

Possible duplicates by query: bug 433733, bug 428064, bug 425064, bug 425045, bug 423382.

Reported using DrKonqi
Comment 1 Justin Zobel 2022-12-01 05:21:58 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 2 Bug Janitor Service 2022-12-16 05:15:22 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 3 Bug Janitor Service 2022-12-31 05:25:26 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!