Bug 265931

Summary: installing flash update while vnc ssh session was starting
Product: [Unmaintained] kpackagekit Reporter: musician_man
Component: generalAssignee: Steven M. Parrish <smparrish>
Status: RESOLVED DUPLICATE    
Severity: crash CC: adaptee, dantti12, www.shue
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: New crash information added by DrKonqi

Description musician_man 2011-02-09 21:35:26 UTC
Application: kpackagekit (0.5.4)
KDE Platform Version: 4.4.5 (KDE 4.4.5)
Qt Version: 4.6.3
Operating System: Linux 2.6.32.26-175.fc12.i686.PAE i686
Distribution (Platform): Fedora RPMs

-- Information about the crash:
While the flash pkg. was installing locally, I logged in from a remote host with vnc over ssh tunnel. With out starting any apps., I went back to the local host to see the progress of the update. I then saw the crash window. I started to report the bug and while that was churning, I went back to the VNC session. I then saw another KPkg crash window on the VNC session, which I left alone. I'll reboot and try the update, without the VNC session that time.

 -- Backtrace:
Application: KPackageKit (kpackagekit), signal: Segmentation fault
[KCrash Handler]
#6  0x062af95b in isSignalConnected (sender=0x87309b0, m=0x77c5144, local_signal_index=11, argv=0xbfdf1b44) at kernel/qobject_p.h:227
#7  QMetaObject::activate (sender=0x87309b0, m=0x77c5144, local_signal_index=11, argv=0xbfdf1b44) at kernel/qobject.cpp:3218
#8  0x0779f9ea in PackageKit::Transaction::finished (this=0x87309b0, _t1=ExitFailed, _t2=0) at transaction.moc:313
#9  0x0779a2b7 in PackageKit::ClientPrivate::serviceOwnerChanged (this=0x84c5430, name=..., oldOnwer=..., newOwner=...) at clientprivate.cpp:101
#10 0x0779c053 in PackageKit::ClientPrivate::qt_metacall (this=0x84c5430, _c=InvokeMetaMethod, _id=<value optimized out>, _a=0xbfdf1cd0) at clientprivate.moc:80
#11 0x062a07eb in QMetaObject::metacall (object=0x84c5430, cl=InvokeMetaMethod, idx=6, argv=0xbfdf1cd0) at kernel/qmetaobject.cpp:237
#12 0x062af6e5 in QMetaObject::activate (sender=0x858a2c8, m=0x601a388, local_signal_index=2, argv=0xbfdf1cd0) at kernel/qobject.cpp:3295
#13 0x060024d0 in QDBusConnectionInterface::serviceOwnerChanged (this=0x858a2c8, _t1=..., _t2=..., _t3=...) at .moc/release-shared/moc_qdbusconnectioninterface.cpp:210
#14 0x0600282b in QDBusConnectionInterface::qt_metacall (this=0x858a2c8, _c=InvokeMetaMethod, _id=2, _a=0xbfdf1ea0) at .moc/release-shared/moc_qdbusconnectioninterface.cpp:137
#15 0x062a07eb in QMetaObject::metacall (object=0x858a2c8, cl=InvokeMetaMethod, idx=7, argv=0xbfdf1ea0) at kernel/qmetaobject.cpp:237
#16 0x062af6e5 in QMetaObject::activate (sender=0x858a2c8, m=0x601a388, local_signal_index=6, argv=0xbfdf1ea0) at kernel/qobject.cpp:3295
#17 0x06002370 in QDBusConnectionInterface::NameOwnerChanged (this=0x858a2c8, _t1=..., _t2=..., _t3=...) at .moc/release-shared/moc_qdbusconnectioninterface.cpp:238
#18 0x060028bb in QDBusConnectionInterface::qt_metacall (this=0x858a2c8, _c=InvokeMetaMethod, _id=6, _a=0xbfdf20ac) at .moc/release-shared/moc_qdbusconnectioninterface.cpp:141
#19 0x05fc728c in QDBusConnectionPrivate::deliverCall (this=0x84c51c8, object=0x858a2c8, msg=..., metaTypes=..., slotIdx=11) at qdbusintegrator.cpp:904
#20 0x05fd1e18 in QDBusCallDeliveryEvent::placeMetaCall (this=0x88b1128, object=0x858a2c8) at qdbusintegrator_p.h:101
#21 0x062abe5e in QObject::event (this=0x858a2c8, e=0x88b1128) at kernel/qobject.cpp:1248
#22 0x04c376cc in QApplicationPrivate::notify_helper (this=0x840f168, receiver=0x858a2c8, e=0x88b1128) at kernel/qapplication.cpp:4306
#23 0x04c3e206 in QApplication::notify (this=0xbfdf297c, receiver=0x858a2c8, e=0x88b1128) at kernel/qapplication.cpp:3710
#24 0x05701a6b in KApplication::notify (this=0xbfdf297c, receiver=0x858a2c8, event=0x88b1128) at /usr/src/debug/kdelibs-4.4.5/kdeui/kernel/kapplication.cpp:302
#25 0x0629bd53 in QCoreApplication::notifyInternal (this=0xbfdf297c, receiver=0x858a2c8, event=0x88b1128) at kernel/qcoreapplication.cpp:726
#26 0x0629e1dc in sendEvent (receiver=0x0, event_type=<value optimized out>, data=0x83f2868) at kernel/qcoreapplication.h:215
#27 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0x83f2868) at kernel/qcoreapplication.cpp:1367
#28 0x0629e35e in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1260
#29 0x062c45d0 in sendPostedEvents (s=0x8412d10) at kernel/qcoreapplication.h:220
#30 postEventSourceDispatch (s=0x8412d10) at kernel/qeventdispatcher_glib.cpp:276
#31 0x00d1bfb8 in g_main_dispatch (context=0x8412c90) at gmain.c:1960
#32 IA__g_main_context_dispatch (context=0x8412c90) at gmain.c:2513
#33 0x00d1f8e8 in g_main_context_iterate (context=0xb270b0, block=1, dispatch=1, self=0x8412f20) at gmain.c:2591
#34 0x00d1fa14 in IA__g_main_context_iteration (context=0x8412c90, may_block=1) at gmain.c:2654
#35 0x062c40c6 in QEventDispatcherGlib::processEvents (this=0x83f2340, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#36 0x04ce5e86 in QGuiEventDispatcherGlib::processEvents (this=0x83f2340, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#37 0x0629a42a in QEventLoop::processEvents (this=0xbfdf28d4, flags=...) at kernel/qeventloop.cpp:149
#38 0x0629a76a in QEventLoop::exec (this=0xbfdf28d4, flags=...) at kernel/qeventloop.cpp:201
#39 0x0629e427 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#40 0x04c37778 in QApplication::exec () at kernel/qapplication.cpp:3585
#41 0x0804cd6b in main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kpackagekit-0.5.4/KPackageKit/main.cpp:66

This bug may be a duplicate of or related to bug 225404.

Possible duplicates by query: bug 265355, bug 262246, bug 262242, bug 261351, bug 261046.

Reported using DrKonqi
Comment 1 james 2011-02-26 05:59:49 UTC
Created attachment 57538 [details]
New crash information added by DrKonqi

I DONT KNOW WHAT HAPPENED IT JUST SHUT OFF
Comment 2 Jekyll Wu 2012-07-06 14:50:47 UTC

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