Bug 358706 - Crash when closes
Summary: Crash when closes
Status: RESOLVED DUPLICATE of bug 350140
Alias: None
Product: ksysguard
Classification: Applications
Component: general (show other bugs)
Version: 5.4.2
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords: drkonqi
: 364325 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-01-28 21:25 UTC by Jesse Talavera-Greenberg
Modified: 2018-02-16 22:47 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Talavera-Greenberg 2016-01-28 21:25:15 UTC
Application: ksysguard (5.4.2)

Qt Version: 5.4.2
Operating System: Linux 4.2.0-25-generic x86_64
Distribution: Ubuntu 15.10

-- Information about the crash:
All I did was close the thing with the X button in the upper right corner.

-- Backtrace:
Application: System Monitor (ksysguard), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fdda8269840 (LWP 27895))]

Thread 2 (Thread 0x7fdda61f2700 (LWP 27938)):
#0  0x00007fddbf0238dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fddb4cc8bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007fddb4cca74f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007fdda7f0fa39 in QXcbEventReader::run (this=0x1fc1cd0) at qxcbconnection.cpp:1105
#4  0x00007fddbafd42be in QThreadPrivate::start (arg=0x1fc1cd0) at thread/qthread_unix.cpp:337
#5  0x00007fddb48a56aa in start_thread (arg=0x7fdda61f2700) at pthread_create.c:333
#6  0x00007fddbf02eeed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fdda8269840 (LWP 27895)):
[KCrash Handler]
#6  0x00007fddbbbc1f79 in QLabelPrivate::clearContents (this=this@entry=0x21b5e00) at widgets/qlabel.cpp:1268
#7  0x00007fddbbbc2acc in QLabel::setText (this=0x20edca0, text=...) at widgets/qlabel.cpp:282
#8  0x00007fddbf368349 in TopLevel::answerReceived (this=0x207ff70, id=<optimized out>, answerList=...) at ../../gui/ksysguard.cpp:447
#9  0x00007fddbe60b9cf in KSGRD::SensorAgent::processAnswer(char const*, int) () from /usr/lib/x86_64-linux-gnu/libksgrd.so.7
#10 0x00007fddbe6134e0 in ?? () from /usr/lib/x86_64-linux-gnu/libksgrd.so.7
#11 0x00007fddbb1e478a in QMetaObject::activate (sender=sender@entry=0x21b5f40, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=5, argv=argv@entry=0x0) at kernel/qobject.cpp:3717
#12 0x00007fddbb1e4f87 in QMetaObject::activate (sender=sender@entry=0x21b5f40, m=m@entry=0x7fddbb3e3300 <QProcess::staticMetaObject>, local_signal_index=local_signal_index@entry=5, argv=argv@entry=0x0) at kernel/qobject.cpp:3582
#13 0x00007fddbb0e1343 in QProcess::readyReadStandardOutput (this=this@entry=0x21b5f40) at .moc/moc_qprocess.cpp:270
#14 0x00007fddbb0ea6a2 in QProcessPrivate::tryReadFromChannel (this=0x21e0aa0, channel=0x21e0be8) at io/qprocess.cpp:966
#15 0x00007fddbb0eac00 in QProcessPrivate::_q_canReadStandardOutput (this=<optimized out>) at io/qprocess.cpp:977
#16 QProcess::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=0x7ffdee02fed0) at .moc/moc_qprocess.cpp:136
#17 0x00007fddbb1e478a in QMetaObject::activate (sender=sender@entry=0x215d580, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffdee02fed0) at kernel/qobject.cpp:3717
#18 0x00007fddbb1e4f87 in QMetaObject::activate (sender=sender@entry=0x215d580, m=m@entry=0x7fddbb3e7700 <QSocketNotifier::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffdee02fed0) at kernel/qobject.cpp:3582
#19 0x00007fddbb25d95e in QSocketNotifier::activated (this=this@entry=0x215d580, _t1=14) at .moc/moc_qsocketnotifier.cpp:133
#20 0x00007fddbb1f0d7b in QSocketNotifier::event (this=0x215d580, e=<optimized out>) at kernel/qsocketnotifier.cpp:296
#21 0x00007fddbba81b8c in QApplicationPrivate::notify_helper (this=this@entry=0x1fab9c0, receiver=receiver@entry=0x215d580, e=e@entry=0x7ffdee030140) at kernel/qapplication.cpp:3720
#22 0x00007fddbba87230 in QApplication::notify (this=0x7ffdee030460, receiver=0x215d580, e=0x7ffdee030140) at kernel/qapplication.cpp:3503
#23 0x00007fddbb1b3f1b in QCoreApplication::notifyInternal (this=0x7ffdee030460, receiver=0x215d580, event=event@entry=0x7ffdee030140) at kernel/qcoreapplication.cpp:935
#24 0x00007fddbb20b74d in QCoreApplication::sendEvent (event=0x7ffdee030140, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:228
#25 socketNotifierSourceDispatch (source=0x1fdc3b0) at kernel/qeventdispatcher_glib.cpp:101
#26 0x00007fddb3d19ff7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x00007fddb3d1a250 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x00007fddb3d1a2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x00007fddbb20b27f in QEventDispatcherGlib::processEvents (this=0x1fe4e20, flags=...) at kernel/qeventdispatcher_glib.cpp:418
#30 0x00007fddbb1b175a in QEventLoop::exec (this=this@entry=0x7ffdee030350, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#31 0x00007fddbb1b92cc in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1188
#32 0x00007fddbb4ce00c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1510
#33 0x00007fddbba7e025 in QApplication::exec () at kernel/qapplication.cpp:2956
#34 0x00007fddbf369ce9 in kdemain (argc=1, argv=<optimized out>) at ../../gui/ksysguard.cpp:594
#35 0x00007fddbef48a40 in __libc_start_main (main=0x400730 <main(int, char**)>, argc=1, argv=0x7ffdee0305a8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffdee030598) at libc-start.c:289
#36 0x0000000000400769 in _start ()

Possible duplicates by query: bug 345592.

Reported using DrKonqi
Comment 1 Christoph Feck 2016-06-15 12:30:36 UTC
*** Bug 364325 has been marked as a duplicate of this bug. ***
Comment 2 Christoph Feck 2018-02-16 22:47:26 UTC

*** This bug has been marked as a duplicate of bug 350140 ***