Version: 0.5.0-0.1.20090902svn (using KDE 4.3.1) OS: Linux Installed from: Fedora RPMs Description of problem: When refreshing the Software Updates listing kpackagekit crashes. It doesn't matter if there are updates or not. This applies to the standalone version as to systemsettings -> Add and Remove Software. Version-Release number of selected component (if applicable): kpackagekit-0.5.0-0.1.20090902svn.fc12.x86_64 How reproducible: Steps to Reproduce: 1. Start Software Management (KPackagekit) 2. Go to Software Updates 3. Press the "Refresh" button Actual results: KPackagekit crashes and starts KCrash Handler. Expected results: The updates listing is refreshed Output of KCrash Handler: --- Start of KCrash Report --- Application: KPackageKit (kpackagekit), signal: Segmentation fault 82 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) The current source language is "auto; currently asm". [KCrash Handler] #5 0x0000003204a23daf in PackageKit::Transaction::role (this=0x7fff63679020) at transaction.cpp:136 #6 0x00000032046164c0 in KpkTransaction::setTransaction (this=0x16c8720, trans=<value optimized out>) at /usr/src/debug/kpackagekit-0.5.0/libkpackagekit/KpkTransaction.cpp:141 #7 0x0000003204616f6f in KpkTransaction::KpkTransaction (this=0x16c8720, trans=<value optimized out>, flags=<value optimized out>, parent=<value optimized out>) at /usr/src/debug/kpackagekit-0.5.0/libkpackagekit/KpkTransaction.cpp:88 #8 0x00007f6b2242f25e in KpkUpdate::refresh (this=0x15f18a0) at /usr/src/debug/kpackagekit-0.5.0/Updater/KpkUpdate.cpp:188 #9 0x00007f6b2242f9fc in on_refreshPB_clicked (this=<value optimized out>) at /usr/src/debug/kpackagekit-0.5.0/Updater/KpkUpdate.cpp:247 #10 KpkUpdate::qt_metacall (this=<value optimized out>) at /usr/src/debug/kpackagekit-0.5.0/x86_64-redhat-linux-gnu/Updater/KpkUpdate.moc:105 #11 0x00000031fe554acc in QMetaObject::activate (sender=0x15fc330, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x170a901) at kernel/qobject.cpp:3112 #12 0x0000003200f8b0c7 in QAbstractButton::clicked (this=0x7fff63679020, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:200 #13 0x0000003200ceecdb in QAbstractButtonPrivate::emitClicked (this=0x15fc370) at widgets/qabstractbutton.cpp:543 #14 0x0000003200cf08db in QAbstractButtonPrivate::click (this=0x15fc370) at widgets/qabstractbutton.cpp:536 #15 0x0000003200cf0b35 in QAbstractButton::mouseReleaseEvent (this=0x15fc330, e=0x7fff63679a30) at widgets/qabstractbutton.cpp:1115 #16 0x00000032009ddda8 in QWidget::event (this=0x15fc330, event=0x7fff63679a30) at kernel/qwidget.cpp:7549 #17 0x000000320098f6bc in QApplicationPrivate::notify_helper (this=0x128e800, receiver=0x15fc330, e=0x7fff63679a30) at kernel/qapplication.cpp:4056 #18 0x0000003200996761 in QApplication::notify (this=<value optimized out>, receiver=0x15fc330, e=0x7fff63679a30) at kernel/qapplication.cpp:3758 #19 0x00007f6b2ba00b46 in KApplication::notify (this=0x7fff6367b940, receiver=0x15fc330, event=0x7fff63679a30) at /usr/src/debug/kdelibs-4.3.1/kdeui/kernel/kapplication.cpp:302 #20 0x00000031fe53f88c in QCoreApplication::notifyInternal (this=0x7fff6367b940, receiver=0x15fc330, event=0x7fff63679a30) at kernel/qcoreapplication.cpp:610 #21 0x0000003200996050 in sendSpontaneousEvent (event=<value optimized out>, receiver=<value optimized out>) at ../../src/corelib/kernel/qcoreapplication.h:216 #22 QApplicationPrivate::sendMouseEvent (event=<value optimized out>, receiver=<value optimized out>) at kernel/qapplication.cpp:2924 #23 0x00000032009fba6e in QETWidget::translateMouseEvent (this=0x12dc3f0, event=<value optimized out>) at kernel/qapplication_x11.cpp:4404 #24 0x00000032009fab28 in QApplication::x11ProcessEvent (this=<value optimized out>, event=0x7fff6367b560) at kernel/qapplication_x11.cpp:3545 #25 0x0000003200a227fc in x11EventSourceDispatch (s=<value optimized out>, callback=<value optimized out>, user_data=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:146 #26 0x00007f6b2a2aa2ae in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #27 0x00007f6b2a2adc98 in ?? () from /lib64/libglib-2.0.so.0 #28 0x00007f6b2a2addba in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #29 0x00000031fe567c26 in QEventDispatcherGlib::processEvents (this=0x12697b0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327 #30 0x0000003200a21fae in QGuiEventDispatcherGlib::processEvents (this=0x7fff63679020, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #31 0x00000031fe53e1c2 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149 #32 0x00000031fe53e594 in QEventLoop::exec (this=0x7fff6367b890, flags=...) at kernel/qeventloop.cpp:201 #33 0x00000031fe540729 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #34 0x00000000004075d2 in main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kpackagekit-0.5.0/KPackageKit/main.cpp:66 --- End KCrash Report report ---
Hi, I'm not sure if it is related or if it is another bug, but today I pressed the History-button (next to Refresh). It also crashed kpackagekit. gdb gives no information. In the next comment you'll find the KCrash report. If it's an other bug I'll hear it. Martin Kho
Created attachment 36740 [details] Output kcrash handler - history button
*** Bug 206573 has been marked as a duplicate of this bug. ***
Hi, Yesterday kpackagekit was updated to version kpackagekit-0.5.0-0.1.20090908svn.fc12.x86_64. Pressing the Refresh-button didn't crash kpackagekit - it refreshed the list as expected. The History-button was grayed out, so I couldn't test this. I think (hope?) the issue is solved, and the bug report can be closed? Martin Kho
Sorry, for not saying anything before here, but I`m with a few time to look at bug reports, as you said that this issue was solved (the refresh button), I`ll close the bug report. The history button was disabled because it was a bug in packagekit-qt (fixed but PackageKit 0.5.3 was not release yet).
*** Bug 213324 has been marked as a duplicate of this bug. ***
*** Bug 213658 has been marked as a duplicate of this bug. ***