| Summary: | KPagageKit crashes on any action | ||
|---|---|---|---|
| Product: | [Unmaintained] kpackagekit | Reporter: | cn_kde <chne> |
| Component: | general | Assignee: | Steven M. Parrish <smparrish> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | dantti12, saverio001 |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
cn_kde
2010-10-27 21:44:00 UTC
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! |