Bug 267183 - monitor crashed when closing kpackagekit(root)
Summary: monitor crashed when closing kpackagekit(root)
Status: RESOLVED DUPLICATE of bug 235156
Alias: None
Product: ksysguard
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-26 00:42 UTC by maninred
Modified: 2011-03-08 19:42 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 maninred 2011-02-26 00:42:36 UTC
Application: ksysguard (4.6.00 (4.6.0))
KDE Platform Version: 4.6.00 (4.6.0)
Qt Version: 4.7.1
Operating System: Linux 2.6.37.1-2-desktop x86_64
Distribution: "openSUSE 11.4 RC 1 (x86_64)"

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

I´ve tried to closed a hanging kpackagekit(root) with monitor. The password popup appeares in the background so that I couldn´t  see and use it. After some tries of kill process, the message that I don´t have the permission to kill a root process appears several times, monitor crashed.

-- Backtrace:
Application: Systemmonitor (kdeinit4), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f56a5249760 (LWP 13894))]

Thread 2 (Thread 0x7f568bf44700 (LWP 14747)):
#0  0x00007f56a2959503 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=<value optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f569f7cb114 in g_main_context_poll (context=0xa287f0, block=1, dispatch=1, self=<value optimized out>) at gmain.c:3404
#2  g_main_context_iterate (context=0xa287f0, block=1, dispatch=1, self=<value optimized out>) at gmain.c:3086
#3  0x00007f569f7cba35 in g_main_loop_run (loop=0xa287d0) at gmain.c:3299
#4  0x00007f568c638244 in gdbus_shared_thread_func (data=<value optimized out>) at gdbusprivate.c:276
#5  0x00007f569f7f2466 in g_thread_create_proxy (data=0xa288e0) at gthread.c:1897
#6  0x00007f56a3ba7a3f in start_thread (arg=0x7f568bf44700) at pthread_create.c:297
#7  0x00007f56a296267d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#8  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f56a5249760 (LWP 13894)):
[KCrash Handler]
#6  0x00007f56a31122d5 in QWidget::effectiveWinId() const () from /usr/lib64/libQtGui.so.4
#7  0x00007f56a4d38db5 in KMessageBox::sorry(QWidget*, QString const&, QString const&, QFlags<KMessageBox::Option>) () from /usr/lib64/libkdeui.so.5
#8  0x00007f5694304f50 in KSysGuardProcessList::killProcesses(QList<long long> const&, int) () from /usr/lib64/libprocessui.so.4
#9  0x00007f56943062dd in KSysGuardProcessList::killSelectedProcesses() () from /usr/lib64/libprocessui.so.4
#10 0x00007f569430758d in KSysGuardProcessList::actionTriggered(QObject*) () from /usr/lib64/libprocessui.so.4
#11 0x00007f569430778b in KSysGuardProcessList::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libprocessui.so.4
#12 0x00007f56a3f34def in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4
#13 0x00007f56a3f38be2 in QSignalMapper::mapped(QObject*) () from /usr/lib64/libQtCore.so.4
#14 0x00007f56a3f38d15 in QSignalMapper::map(QObject*) () from /usr/lib64/libQtCore.so.4
#15 0x00007f56a3f39410 in QSignalMapper::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libQtCore.so.4
#16 0x00007f56a3f34def in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4
#17 0x00007f56a30c8982 in QAction::triggered(bool) () from /usr/lib64/libQtGui.so.4
#18 0x00007f56a30c8b7a in QAction::activate(QAction::ActionEvent) () from /usr/lib64/libQtGui.so.4
#19 0x00007f56a34fee63 in ?? () from /usr/lib64/libQtGui.so.4
#20 0x00007f56a3504e7a in ?? () from /usr/lib64/libQtGui.so.4
#21 0x00007f56a3120538 in QWidget::event(QEvent*) () from /usr/lib64/libQtGui.so.4
#22 0x00007f56a350606b in QMenu::event(QEvent*) () from /usr/lib64/libQtGui.so.4
#23 0x00007f56a30ced14 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#24 0x00007f56a30d7aac in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#25 0x00007f56a4bc39e6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#26 0x00007f56a3f1fbfc in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#27 0x00007f56a30cfd25 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) () from /usr/lib64/libQtGui.so.4
#28 0x00007f56a314e054 in ?? () from /usr/lib64/libQtGui.so.4
#29 0x00007f56a314c4c9 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib64/libQtGui.so.4
#30 0x00007f56a31740f2 in ?? () from /usr/lib64/libQtGui.so.4
#31 0x00007f569f7cabd3 in g_main_dispatch (context=0x6b68e0) at gmain.c:2440
#32 g_main_context_dispatch (context=0x6b68e0) at gmain.c:3013
#33 0x00007f569f7cb3b0 in g_main_context_iterate (context=0x6b68e0, block=1, dispatch=1, self=<value optimized out>) at gmain.c:3091
#34 0x00007f569f7cb650 in g_main_context_iteration (context=0x6b68e0, may_block=1) at gmain.c:3154
#35 0x00007f56a3f4a91f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#36 0x00007f56a3173d8e in ?? () from /usr/lib64/libQtGui.so.4
#37 0x00007f56a3f1f052 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#38 0x00007f56a3f1f265 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#39 0x00007f56a3f236ab in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#40 0x00007f5694593453 in kdemain () from /usr/lib64/libkdeinit4_ksysguard.so
#41 0x00000000004075e9 in _start ()

Possible duplicates by query: bug 257137, bug 251223, bug 235156.

Reported using DrKonqi
Comment 1 Dario Andres 2011-03-08 19:42:43 UTC
[Comment from a bug triager]
This issue is being tracked at bug 235156.
Merging. Thanks

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