Bug 451339 - ksysguard crashes when started (nvidia related)
Summary: ksysguard crashes when started (nvidia related)
Status: RESOLVED DUPLICATE of bug 451148
Alias: None
Product: ksysguard
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2022-03-09 22:06 UTC by Christoph Feck
Modified: 2022-03-09 23:08 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph Feck 2022-03-09 22:06:55 UTC
Application: ksysguard (5.22.80)

Qt Version: 5.15.2
Frameworks Version: 5.92.0
Operating System: Linux 5.16.8-1-default x86_64
Windowing System: X11
Distribution: openSUSE Tumbleweed
DrKonqi: 5.24.80 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
Just starting ksysguard from master causes this crash. This worked fine about two weeks ago.

The crash can be reproduced every time.

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

[KCrash Handler]
#4  0x00007fef5550a556 in QHash<long, KSysGuard::Process*>::value (akey=<synthetic pointer>: 1157, this=<error reading variable: Cannot access memory at address 0x10>) at /usr/include/qt5/QtCore/qhash.h:656
#5  KSysGuard::Processes::getProcess (this=0x0, pid=1157) at /usr/src/debug/libksysguard5-5.24.80git.20220228T165743~1b36ab8c-ku.35.1.x86_64/processcore/processes.cpp:109
#6  0x00007fef5551a329 in KSysGuard::ProcessDataProvider::getProcess (this=0x563d8b0a9170, pid=1157) at /usr/src/debug/libksysguard5-5.24.80git.20220228T165743~1b36ab8c-ku.35.1.x86_64/processcore/process_data_provider.cpp:44
#7  0x00007fef4c8857aa in operator() (__closure=<optimized out>) at /usr/src/debug/libksysguard5-5.24.80git.20220228T165743~1b36ab8c-ku.35.1.x86_64/processcore/plugins/nvidia/nvidia.cpp:84
#8  QtPrivate::FunctorCall<QtPrivate::IndexesList<>, QtPrivate::List<>, void, NvidiaPlugin::setup()::<lambda()> >::call (arg=<optimized out>, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146
#9  QtPrivate::Functor<NvidiaPlugin::setup()::<lambda()>, 0>::call<QtPrivate::List<>, void> (arg=<optimized out>, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256
#10 QtPrivate::QFunctorSlotObject<NvidiaPlugin::setup()::<lambda()>, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=<optimized out>, this_=0x563d8b0a8560, r=<optimized out>, a=<optimized out>, ret=<optimized out>) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443
#11 0x00007fef53c6d493 in QtPrivate::QSlotObjectBase::call (a=0x7ffea88cca90, r=0x563d8b0a9170, this=0x563d8b0a8560) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#12 doActivate<false> (sender=0x563d8b0ae1b0, signal_index=15, argv=0x7ffea88cca90) at kernel/qobject.cpp:3886
#13 0x00007fef53c6695f in QMetaObject::activate (sender=<optimized out>, m=m@entry=0x7fef53f0a6e0 <QProcess::staticMetaObject>, local_signal_index=local_signal_index@entry=6, argv=argv@entry=0x7ffea88cca90) at kernel/qobject.cpp:3946
#14 0x00007fef53ba22dd in QProcess::readyReadStandardOutput (this=<optimized out>, _t1=...) at .moc/moc_qprocess.cpp:367
#15 0x00007fef53ba7a6d in QProcessPrivate::tryReadFromChannel (this=0x563d8b0a8360, channel=0x563d8b0a8470) at io/qprocess.cpp:1073
#16 0x00007fef53ba7fa5 in QProcessPrivate::_q_canReadStandardError (this=<optimized out>) at io/qprocess.cpp:1092
#17 QProcess::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=0x7ffea88ccc30) at .moc/moc_qprocess.cpp:210
#18 0x00007fef53c6d4c8 in doActivate<false> (sender=0x563d8b0a7eb0, signal_index=3, argv=0x7ffea88ccc30) at kernel/qobject.cpp:3898
#19 0x00007fef53c6695f in QMetaObject::activate (sender=sender@entry=0x563d8b0a7eb0, m=m@entry=0x7fef53f0cac0 <QSocketNotifier::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffea88ccc30) at kernel/qobject.cpp:3946
#20 0x00007fef53c7086f in QSocketNotifier::activated (this=this@entry=0x563d8b0a7eb0, _t1=..., _t2=<optimized out>, _t3=...) at .moc/moc_qsocketnotifier.cpp:178
#21 0x00007fef53c7106b in QSocketNotifier::event (this=0x563d8b0a7eb0, e=0x7ffea88ccd50) at kernel/qsocketnotifier.cpp:302
#22 0x00007fef5488da7f in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x563d8b0a7eb0, e=0x7ffea88ccd50) at kernel/qapplication.cpp:3632
#23 0x00007fef53c36dca in QCoreApplication::notifyInternal2 (receiver=0x563d8b0a7eb0, event=0x7ffea88ccd50) at kernel/qcoreapplication.cpp:1064
#24 0x00007fef53c8eecd in socketNotifierSourceDispatch (source=source@entry=0x563d8af79590) at kernel/qeventdispatcher_glib.cpp:107
#25 0x00007fef51656e22 in g_main_dispatch (context=0x7fef48005010) at ../glib/gmain.c:3381
#26 g_main_context_dispatch (context=0x7fef48005010) at ../glib/gmain.c:4099
#27 0x00007fef516571b8 in g_main_context_iterate (context=context@entry=0x7fef48005010, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/gmain.c:4175
#28 0x00007fef5165726f in g_main_context_iteration (context=0x7fef48005010, may_block=1) at ../glib/gmain.c:4240
#29 0x00007fef53c8e314 in QEventDispatcherGlib::processEvents (this=0x563d8af79600, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#30 0x00007fef53c357cb in QEventLoop::exec (this=this@entry=0x7ffea88ccf60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#31 0x00007fef53c3daa0 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#32 0x0000563d89df96ca in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/ksysguard5-5.24.80git.20220301T085737~1367cb0d-ku.18.1.x86_64/gui/ksysguard.cpp:626
[Inferior 1 (process 26417) detached]

Possible duplicates by query: bug 442023, bug 441881, bug 437230, bug 433838, bug 433733.

Reported using DrKonqi
Comment 1 Christoph Feck 2022-03-09 23:01:56 UTC
Could be a duplicate of bug 451148, let me check.
Comment 2 Christoph Feck 2022-03-09 23:08:40 UTC
*** This bug has been marked as a duplicate of bug 451148 ***