Bug 433733 - KSysGuard crashed when closed after having killed a VLC process
Summary: KSysGuard crashed when closed after having killed a VLC process
Status: RESOLVED UNMAINTAINED
Alias: None
Product: ksysguard
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: 5.20.5
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2021-02-28 08:26 UTC by Emanuele Spirito
Modified: 2024-09-23 21:00 UTC (History)
2 users (show)

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


Attachments
New crash information added by DrKonqi (4.79 KB, text/plain)
2021-03-26 15:59 UTC, Lastique
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Emanuele Spirito 2021-02-28 08:26:42 UTC
Application: ksysguard (5.20.5)

Qt Version: 5.15.2
Frameworks Version: 5.78.0
Operating System: Linux 5.10.16-200.fc33.x86_64 x86_64
Windowing system: X11
Distribution: Fedora 33 (KDE Plasma)

-- Information about the crash:
- What I was doing when the application crashed:
I opened KSysGuard from application bar. Then I searched for VLC process because I needed to stop it. I commanded to stop and then to kill it. When killed, I closed KSysGuard and then KSysGuard crashed.

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

[KCrash Handler]
#4  0x00007f3ba86f2bdc in operator==(QString const&, QString const&) () from /lib64/libQt5Core.so.5
#5  0x00007f3ba955ddb9 in QLabel::setText(QString const&) () from /lib64/libQt5Widgets.so.5
#6  0x00007f3baa30cf03 in TopLevel::answerReceived(int, QList<QByteArray> const&) () from /lib64/libkdeinit5_ksysguard.so
#7  0x00007f3baa06be1b in KSGRD::SensorAgent::processAnswer(char const*, int) () from /lib64/libksgrd.so.9
#8  0x00007f3baa06ef20 in KSGRD::SensorShellAgent::msgRcvd() () from /lib64/libksgrd.so.9
#9  0x00007f3ba8838386 in void doActivate<false>(QObject*, int, void**) () from /lib64/libQt5Core.so.5
#10 0x00007f3ba879a0d1 in QProcess::readyReadStandardOutput(QProcess::QPrivateSignal) () from /lib64/libQt5Core.so.5
#11 0x00007f3ba879db1d in QProcessPrivate::tryReadFromChannel(QProcessPrivate::Channel*) () from /lib64/libQt5Core.so.5
#12 0x00007f3ba879dfe5 in QProcess::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /lib64/libQt5Core.so.5
#13 0x00007f3ba88383c0 in void doActivate<false>(QObject*, int, void**) () from /lib64/libQt5Core.so.5
#14 0x00007f3ba883b77a in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /lib64/libQt5Core.so.5
#15 0x00007f3ba883bf21 in QSocketNotifier::event(QEvent*) () from /lib64/libQt5Core.so.5
#16 0x00007f3ba9425ec3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5
#17 0x00007f3ba8808bd8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5
#18 0x00007f3ba8856157 in socketNotifierSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5
#19 0x00007f3b9f5caa9f in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#20 0x00007f3b9f61ca98 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0
#21 0x00007f3b9f5c7e73 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#22 0x00007f3ba88556f3 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#23 0x00007f3ba880757b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#24 0x00007f3ba880f1b4 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5
#25 0x00007f3baa30ca1d in kdemain () from /lib64/libkdeinit5_ksysguard.so
#26 0x00007f3baa0fd1e2 in __libc_start_main () from /lib64/libc.so.6
#27 0x000055e35447e0ae in _start ()
[Inferior 1 (process 24574) detached]

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

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

Reported using DrKonqi
Comment 1 Lastique 2021-03-26 15:59:36 UTC
Created attachment 137090 [details]
New crash information added by DrKonqi

ksysguard (5.19.5) using Qt 5.14.2

- What I was doing when the application crashed:

I opened KSysGuard, sent a SIGINT signal to a process and then closed KSysGuard when it crashed.

-- Backtrace (Reduced):
#4  0x00007ff881c5fd2d in operator==(QString const&, QString const&) (s1=..., s2=...) at text/qstring.cpp:3383
#5  0x00007ff882b2fe79 in QLabel::setText(QString const&) (this=0x55aab9465490, text=...) at widgets/qlabel.cpp:287
[...]
#7  0x00007ff8835df122 in KSGRD::SensorAgent::processAnswer(char const*, int) () at /usr/lib/x86_64-linux-gnu/libksgrd.so.9
[...]
#9  0x00007ff881df32e6 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fffde2446d0, r=0x55aab976fb70, this=0x55aab93df450) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#10 doActivate<false>(QObject*, int, void**) (sender=0x55aab9782290, signal_index=15, argv=argv@entry=0x7fffde2446d0) at kernel/qobject.cpp:3870
Comment 2 Christoph Cullmann 2024-09-23 21:00:15 UTC
ksysguard is no longer maintained, in Plasma 6 there is the Plasma system monitor for this task.

If your issue still happens with the Plasma 6 replacement, please re-open and we can move this bug to the new product, thanks!