Application: kpackagekit (0.5.4) KDE Platform Version: 4.4.00 (KDE 4.4.0) (Compiled from sources) Qt Version: 4.6.2 Operating System: Linux 2.6.31.12-174.2.22.fc12.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: switching from A/C to battery & losing eth0 in the process. -- Backtrace: Application: KPackageKit (kpackagekit), signal: Segmentation fault 82 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [KCrash Handler] #5 QObject::property (this=0x100000000, name=0x395a836596 "Percentage") at kernel/qobject.cpp:3462 #6 0x000000395422f3a9 in QDBusAbstractInterface::internalPropGet (this=<value optimized out>, propname=<value optimized out>) at qdbusabstractinterface.cpp:595 #7 0x000000395a8226f5 in percentage (this=<value optimized out>) at transactionproxy.h:57 #8 PackageKit::Transaction::percentage (this=<value optimized out>) at transaction.cpp:135 #9 0x000000395a42a2d2 in KpkTransactionBar::updateUi (this=0x1443ab0) at /usr/src/debug/kpackagekit-0.5.4/libkpackagekit/KpkTransactionBar.cpp:159 #10 0x000000395a416bac in KpkTransactionBar::qt_metacall (this=0x1443ab0, _c=InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff8229d4f0) at /usr/src/debug/kpackagekit-0.5.4/x86_64-redhat-linux-gnu/libkpackagekit/moc_KpkTransactionBar.cpp:75 #11 0x000000395356a2af in QMetaObject::activate (sender=0x1471e60, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3293 #12 0x000000395a823a5a in PackageKit::Transaction::qt_metacall (this=0x1471e60, _c=InvokeMetaMethod, _id=0, _a=0x7fff8229d6c0) at transaction.moc:198 #13 0x000000395356a2af in QMetaObject::activate (sender=0x19e7fe0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3293 #14 0x000000395a82aac4 in PackageKit::TransactionProxy::qt_metacall (this=0x19e7fe0, _c=InvokeMetaMethod, _id=3, _a=0x7fff8229e4c0) at transactionproxy.moc:235 #15 0x0000003954221c26 in QDBusConnectionPrivate::deliverCall (this=<value optimized out>, object=<value optimized out>, msg=<value optimized out>, metaTypes=..., slotIdx=<value optimized out>) at qdbusintegrator.cpp:904 #16 0x000000395422be1f in QDBusCallDeliveryEvent::placeMetaCall (this=0x152bc50, object=<value optimized out>) at qdbusintegrator_p.h:101 #17 0x0000003953566921 in QObject::event (this=0x19e7fe0, e=0x1b16ca0) at kernel/qobject.cpp:1248 #18 0x0000003956daa9dc in QApplicationPrivate::notify_helper (this=0x10d56e0, receiver=0x19e7fe0, e=0x1b16ca0) at kernel/qapplication.cpp:4300 #19 0x0000003956db0aab in QApplication::notify (this=<value optimized out>, receiver=0x19e7fe0, e=0x1b16ca0) at kernel/qapplication.cpp:4183 #20 0x00000039584067a6 in KApplication::notify (this=0x7fff8229efb0, receiver=0x19e7fe0, event=0x1b16ca0) at /usr/src/debug/kdelibs-4.4.0/kdeui/kernel/kapplication.cpp:302 #21 0x000000395355774c in QCoreApplication::notifyInternal (this=0x7fff8229efb0, receiver=0x19e7fe0, event=0x1b16ca0) at kernel/qcoreapplication.cpp:704 #22 0x0000003953558497 in sendEvent (receiver=0x0, event_type=<value optimized out>, data=0x10af530) at kernel/qcoreapplication.h:215 #23 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0x10af530) at kernel/qcoreapplication.cpp:1345 #24 0x000000395357d523 in sendPostedEvents (s=<value optimized out>) at kernel/qcoreapplication.h:220 #25 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:276 #26 0x000000394a03920e in g_main_dispatch (context=0x10d8520) at gmain.c:1960 #27 IA__g_main_context_dispatch (context=0x10d8520) at gmain.c:2513 #28 0x000000394a03cbf8 in g_main_context_iterate (context=0x10d8520, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2591 #29 0x000000394a03cd1a in IA__g_main_context_iteration (context=0x10d8520, may_block=1) at gmain.c:2654 #30 0x000000395357d063 in QEventDispatcherGlib::processEvents (this=0x10aec50, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412 #31 0x0000003956e49a1e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204 #32 0x0000003953556192 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149 #33 0x000000395355645c in QEventLoop::exec (this=0x7fff8229ef00, flags=...) at kernel/qeventloop.cpp:201 #34 0x0000003953558749 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981 #35 0x0000000000406082 in main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kpackagekit-0.5.4/KPackageKit/main.cpp:66 Possible duplicates by query: bug 228798. Reported using DrKonqi
The backtrace is related to the crash on bug 220344 - Does the application crash again if you repeat the situation you described ? Regards
Hi Dario, The problem continues to occur. Its impact has become so severe that I must restart the laptop. I suspect this may be related to the initial O/S installation and I'm going to reinstall soon but simply install using default settings. I'll keep you posted. Best Wishes, David Phillips -----Original Message----- From: bugzilla_noreply@kde.org [mailto:bugzilla_noreply@kde.org] On Behalf Of Dario Andres Sent: Sunday, February 28, 2010 8:17 AM To: dcphillips01@gmail.com Subject: [Bug 228851] KPackageKit crash during change from A/C power & etho to battery & wlan0 https://bugs.kde.org/show_bug.cgi?id=228851 Dario Andres <andresbajotierra@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andresbajotierra@gmail.com --- Comment #1 from Dario Andres <andresbajotierra gmail com> 2010-02-28 14:16:44 --- The backtrace is related to the crash on bug 220344 - Does the application crash again if you repeat the situation you described ? Regards -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You reported the bug.
*** Bug 228798 has been marked as a duplicate of this bug. ***
*** Bug 235786 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 220344 ***