Application: kpackagekit (0.6.2) KDE Platform Version: 4.5.1 (KDE 4.5.1) Qt Version: 4.7.0 Operating System: Linux 2.6.35-22-generic x86_64 Distribution: Ubuntu 10.10 -- Information about the crash: If I open the app and try to click via mouse or select via keyboard the app crashes. The crash can be reproduced every time. -- Backtrace: Application: KPackageKit (kpackagekit), signal: Segmentation fault [Current thread is 1 (Thread 0x7f9927a81760 (LWP 13381))] Thread 2 (Thread 0x7f9912c84710 (LWP 13382)): #0 0x00007f99237521d3 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x00007f9920dc6009 in ?? () from /lib/libglib-2.0.so.0 #2 0x00007f9920dc645c in g_main_context_iteration () from /lib/libglib-2.0.so.0 #3 0x00007f99264191e6 in QEventDispatcherGlib::processEvents (this=0x7f990c0008b0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:417 #4 0x00007f99263eba02 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149 #5 0x00007f99263ebdec in QEventLoop::exec (this=0x7f9912c83db0, flags=) at kernel/qeventloop.cpp:201 #6 0x00007f99262f62fd in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:490 #7 0x00007f99263cb5f8 in QInotifyFileSystemWatcherEngine::run (this=0x1107240) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x00007f99262f927e in QThreadPrivate::start (arg=0x1107240) at thread/qthread_unix.cpp:266 #9 0x00007f99241a1971 in start_thread (arg=<value optimized out>) at pthread_create.c:304 #10 0x00007f992375e91d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x0000000000000000 in ?? () Thread 1 (Thread 0x7f9927a81760 (LWP 13381)): [KCrash Handler] #6 QList (this=0x48) at ../../include/QtCore/../../src/corelib/tools/qlist.h:118 #7 QDBusMessage::arguments (this=0x48) at qdbusmessage.cpp:706 #8 0x00007f9926c060cd in QDBusPendingReplyData::argumentAt (this=0x7fff63df7a80, index=0) at qdbuspendingreply.cpp:270 #9 0x00007f9926e3352d in PackageKit::Client::getTid() const () from /usr/lib/libpackagekit-qt.so.14 #10 0x00007f9926e451be in PackageKit::Transaction::Transaction(QString const&, QObject*) () from /usr/lib/libpackagekit-qt.so.14 #11 0x00007f9914e280d2 in ?? () from /usr/lib/kde4/kcm_kpk_update.so #12 0x00007f9914e283d8 in ?? () from /usr/lib/kde4/kcm_kpk_update.so #13 0x00007f9914e28611 in ?? () from /usr/lib/kde4/kcm_kpk_update.so #14 0x00007f99263febde in QObject::event (this=0x1092bc0, e=0x7fff63df79e0) at kernel/qobject.cpp:1219 #15 0x00007f9924a8f6df in QWidget::event (this=0x1092bc0, event=0x109eda0) at kernel/qwidget.cpp:8646 #16 0x00007f9924a39fdc in QApplicationPrivate::notify_helper (this=0xda8990, receiver=0x1092bc0, e=0x109eda0) at kernel/qapplication.cpp:4396 #17 0x00007f9924a3faed in QApplication::notify (this=0x7fff63df8ab0, receiver=0x1092bc0, e=0x109eda0) at kernel/qapplication.cpp:4277 #18 0x00007f9927489156 in KApplication::notify (this=0x7fff63df8ab0, receiver=0x1092bc0, event=0x109eda0) at ../../kdeui/kernel/kapplication.cpp:310 #19 0x00007f99263eccdc in QCoreApplication::notifyInternal (this=0x7fff63df8ab0, receiver=0x1092bc0, event=0x109eda0) at kernel/qcoreapplication.cpp:732 #20 0x00007f99263efc22 in sendEvent (receiver=0x0, event_type=<value optimized out>, data=0xd80be0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #21 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0xd80be0) at kernel/qcoreapplication.cpp:1373 #22 0x00007f9926419653 in sendPostedEvents (s=0xdabf80) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220 #23 postEventSourceDispatch (s=0xdabf80) at kernel/qeventdispatcher_glib.cpp:277 #24 0x00007f9920dc2342 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #25 0x00007f9920dc62a8 in ?? () from /lib/libglib-2.0.so.0 #26 0x00007f9920dc645c in g_main_context_iteration () from /lib/libglib-2.0.so.0 #27 0x00007f9926419193 in QEventDispatcherGlib::processEvents (this=0xd806f0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:415 #28 0x00007f9924aeca4e in QGuiEventDispatcherGlib::processEvents (this=0x7fff63df79e0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204 #29 0x00007f99263eba02 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149 #30 0x00007f99263ebdec in QEventLoop::exec (this=0x7fff63df8a00, flags=) at kernel/qeventloop.cpp:201 #31 0x00007f99263efebb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009 #32 0x0000000000411ee2 in _start () Reported using DrKonqi
is packagekitd process running when it crashes?
yes, it is: root 1180 1 0 15:58 ? 00:00:00 /usr/sbin/packagekitd
oh, sorry, wrong issue. I thought I handle another one. Hmm.., but I can not reproduce this issue anymore. Since a reboot KPackage works as expected.
Created attachment 64387 [details] New crash information added by DrKonqi kpackagekit (0.6.3.3) on KDE Platform 4.6.5 (4.6.5) using Qt 4.7.2 - What I was doing when the application crashed: restarted dbus with /etc/init.d/dbus restart - from that moment kpackagekit started to crash no matter what action I tool. - Unusual behavior I noticed: The full story is this: after a suspend/resume. kpackagekit would not start - it would just hang. Ran an strace on the process, and saw that kpackagekit was trying constantly to talk to dbus, getting a "resource temporarily unavailable" error: poll([{fd=8, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=8, revents=POLLOUT}]) writev(8, [{"5 \4\0\371\0\340\5]\1\0\0\26\0\26\0\231\4\5\0\372\0\340\5\371\0\340\5 \1\0\0"..., 3644}, {NULL, 0}, {"", 0}], 3) = 3644 poll([{fd=8, events=POLLIN}], 1, -1) = 1 ([{fd=8, revents=POLLIN}]) read(8, "\1 \370\3\0\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4096) = 1056 read(8, 0x1d73624, 4096) = -1 EAGAIN (Resource temporarily unavailable) sendmsg(11, {msg_name(0)=NULL, msg_iov(2)=[{"l\1\0\1+\0\0\0\17\0\0\0\220\0\0\0\1\1o\0\33\0\0\0/org/fre"..., 160}, {"\32\0\0\0org.freedesktop.PackageKit\0\0"..., 43}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 203 poll([{fd=11, events=POLLIN}], 1, 25000) = 1 ([{fd=11, revents=POLLIN}]) .. so I restarted dbus, and triggered this bug. -- Backtrace (Reduced): #6 QList (this=0x48) at ../../include/QtCore/../../src/corelib/tools/qlist.h:118 #7 QDBusMessage::arguments (this=0x48) at qdbusmessage.cpp:706 #8 0x00007ffe497cdcfe in QDBusPendingReplyData::argumentAt (this=0x7fffbd67c3a0, index=0) at qdbuspendingreply.cpp:270 #9 0x00007ffe499fdd14 in PackageKit::Client::getTid() const () from /usr/lib/libpackagekit-qt.so.14 #10 0x00007ffe49a0de9b in PackageKit::Transaction::Transaction(QString const&, QObject*) () from /usr/lib/libpackagekit-qt.so.14
Well the DBus system was never meant to be restarted, as it causes issues on several apps which is really hard to recover.
> Well the DBus system was never meant to be restarted, as it causes issues on > several apps which is really hard to recover. What I would think is, a segmentation fault is always a symptom of a serious issue, so it should be fixed; even if recovery is not possible, at least a graceful exit (and if possible an error message) would be appreciated. Then, there is the question of what to do if dbus restarts for a reason or another; I really think that forcing users to reboot is rather harsh, there has to be a better way. If the 'dbus stuck' condition again I will open another bug to have that fixed, but in the meanwhile it would be cool to get to the root cause of this crash.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
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!
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!