Bug 215606 - kpackagekit crashed when loading
Summary: kpackagekit crashed when loading
Status: RESOLVED DUPLICATE of bug 204767
Alias: None
Product: kpackagekit
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Steven M. Parrish
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-21 22:32 UTC by nuclearandy
Modified: 2009-11-21 23:34 UTC (History)
2 users (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 nuclearandy 2009-11-21 22:32:42 UTC
Application that crashed: kpackagekit
Version of the application: 0.4.2
KDE Version: 4.3.1 (KDE 4.3.1) "release 6"
Qt Version: 4.5.3
Operating System: Linux 2.6.31.5-0.1-default i686
Distribution: "openSUSE 11.2 (i586)"

What I was doing when the application crashed:
I was running YaST2 at the same time and it always crashes when I run both together. This could proberbly be because they are both package managers. This bug is easily reproducable. first run YaST2 package manager then run kpackagekit

 -- Backtrace:
Application: KPackageKit (kpackagekit), signal: Segmentation fault
[KCrash Handler]
#6  0xb714ad69 in PackageKit::Transaction::allowCancel() () from /usr/lib/libpackagekit-qt.so.12
#7  0xb654d0e8 in KpkTransactionBar::nextTransaction (this=0x819b5e8) at /usr/src/debug/kpackagekit-0.4.2/libkpackagekit/KpkTransactionBar.cpp:89
#8  0xb654d638 in KpkTransactionBar::addTransaction (this=0x819b5e8, trans=0x0) at /usr/src/debug/kpackagekit-0.4.2/libkpackagekit/KpkTransactionBar.cpp:117
#9  0xb34aca8e in KpkUpdate::displayUpdates(KpkTransaction::<anonymous enum>) (this=0x8160328, status=Success) at /usr/src/debug/kpackagekit-0.4.2/Updater/KpkUpdate.cpp:201
#10 0xb34acbd7 in KpkUpdate::load (this=0x8160328) at /usr/src/debug/kpackagekit-0.4.2/Updater/KpkUpdate.cpp:104
#11 0xb34ab4ce in KcmKpkUpdate::load (this=0x8183220) at /usr/src/debug/kpackagekit-0.4.2/Updater/KcmKpkUpdate.cpp:52
#12 0xb34ab1e9 in KcmKpkUpdate::qt_metacall (this=0x8183220, _c=InvokeMetaMethod, _id=34, _a=0x819b3c0) at /usr/src/debug/kpackagekit-0.4.2/build/Updater/moc_KcmKpkUpdate.cpp:67
#13 0xb66b204a in QMetaCallEvent::placeMetaCall(QObject*) () from /usr/lib/libQtCore.so.4
#14 0xb66b3796 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#15 0xb690f230 in QWidget::event(QEvent*) () from /usr/lib/libQtGui.so.4
#16 0xb68b88fc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#17 0xb68c029e in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#18 0xb7640ce1 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#19 0xb66a332e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#20 0xb66a3fdc in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4
#21 0xb66a419c in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4
#22 0xb66cf4dd in ?? () from /usr/lib/libQtCore.so.4
#23 0xb597f4c2 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#24 0xb5982d98 in ?? () from /usr/lib/libglib-2.0.so.0
#25 0xb5982ebe in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#26 0xb66cf011 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#27 0xb695a29a in ?? () from /usr/lib/libQtGui.so.4
#28 0xb66a198d in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#29 0xb66a1dd9 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#30 0xb66a4270 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#31 0xb68b8774 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#32 0x0804e44b in main (argc=5, argv=0xbfafa4c4) at /usr/src/debug/kpackagekit-0.4.2/KPackageKit/main.cpp:66

Reported using DrKonqi
Comment 1 Dario Andres 2009-11-21 23:34:35 UTC
Merging with bug 204767. Thanks

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