| Summary: | KDE deamon crash when play film in fullscreen [QMetaObject::activate, PackageKit::Transaction::finished, PackageKit::ClientPrivate::serviceOwnerChanged] | ||
|---|---|---|---|
| Product: | [Unmaintained] kpackagekit | Reporter: | Martin Naď <martin.nad89> |
| Component: | general | Assignee: | Steven M. Parrish <smparrish> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | andreas.hencke, attila.alexovics, baronvaile, belegs, blueowl, conorcarroll, dantti12, greg.martyn, grosser.meister.morti, jameschums, jamundso, juddpwr, kstone277, lopezdebrinas, marcelo011982, ndbecker2, rado.kljucevsek, robert, simon.trevor, TheWHAMBurglar, veli-matti.sorvala, wojdi666, xsxixmx |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi |
||
and I have installed libindicate-qt-0.2.2-1.fc12.x86_64 from non-distribution way *** Bug 219699 has been marked as a duplicate of this bug. *** *** Bug 219768 has been marked as a duplicate of this bug. *** It's a bug in pk-qt, I'll try to fix this, it should be a feature and not a bug :P *** Bug 220368 has been marked as a duplicate of this bug. *** *** Bug 220546 has been marked as a duplicate of this bug. *** *** Bug 220499 has been marked as a duplicate of this bug. *** I found a 'workaround' to this problem which needs to be backported to 0.5 versions of packagekit-qt the weird part is that this does not happen in kpackagekit bin or kcms only on kded module pretty weird. Hopefully on the next release you will have this fixed, as for now I'd disable the update checks in system settings -> advanced -> services -> kpackagekit, so kded4 can keep up working... Best, Daniel. *** Bug 220624 has been marked as a duplicate of this bug. *** *** Bug 220597 has been marked as a duplicate of this bug. *** *** Bug 220830 has been marked as a duplicate of this bug. *** *** Bug 220854 has been marked as a duplicate of this bug. *** *** Bug 220887 has been marked as a duplicate of this bug. *** *** Bug 220984 has been marked as a duplicate of this bug. *** *** Bug 220991 has been marked as a duplicate of this bug. *** *** Bug 221095 has been marked as a duplicate of this bug. *** *** Bug 221061 has been marked as a duplicate of this bug. *** *** Bug 221112 has been marked as a duplicate of this bug. *** *** Bug 221147 has been marked as a duplicate of this bug. *** *** Bug 221212 has been marked as a duplicate of this bug. *** *** Bug 221246 has been marked as a duplicate of this bug. *** *** Bug 221194 has been marked as a duplicate of this bug. *** *** Bug 221326 has been marked as a duplicate of this bug. *** *** Bug 221328 has been marked as a duplicate of this bug. *** *** Bug 221400 has been marked as a duplicate of this bug. *** *** Bug 221401 has been marked as a duplicate of this bug. *** *** Bug 221464 has been marked as a duplicate of this bug. *** *** Bug 221505 has been marked as a duplicate of this bug. *** *** Bug 221576 has been marked as a duplicate of this bug. *** (In reply to comment #8) > I found a 'workaround' to this problem which needs to be backported to 0.5 > versions of packagekit-qt the weird part is that this does not happen in > kpackagekit bin or kcms only on kded module pretty weird. > Hopefully on the next release you will have this fixed, as for > now I'd disable the update checks in system settings -> advanced -> services -> > kpackagekit, so kded4 can keep up working... > Best, > Daniel. is it possible to fix this problem with new kpackagekit version? i don't want to disable update checks feature... *** Bug 221604 has been marked as a duplicate of this bug. *** *** Bug 221598 has been marked as a duplicate of this bug. *** *** Bug 221654 has been marked as a duplicate of this bug. *** *** Bug 221676 has been marked as a duplicate of this bug. *** *** Bug 221691 has been marked as a duplicate of this bug. *** *** Bug 221692 has been marked as a duplicate of this bug. *** *** Bug 221824 has been marked as a duplicate of this bug. *** *** Bug 221878 has been marked as a duplicate of this bug. *** *** Bug 221982 has been marked as a duplicate of this bug. *** *** Bug 221999 has been marked as a duplicate of this bug. *** *** Bug 222015 has been marked as a duplicate of this bug. *** *** Bug 222017 has been marked as a duplicate of this bug. *** *** Bug 222005 has been marked as a duplicate of this bug. *** *** Bug 222144 has been marked as a duplicate of this bug. *** *** Bug 222318 has been marked as a duplicate of this bug. *** *** Bug 222327 has been marked as a duplicate of this bug. *** *** Bug 222483 has been marked as a duplicate of this bug. *** Created attachment 39833 [details]
New crash information added by DrKonqi
kpackagekit and other services crash when update service is enabled
*** Bug 222621 has been marked as a duplicate of this bug. *** *** Bug 222788 has been marked as a duplicate of this bug. *** *** Bug 223252 has been marked as a duplicate of this bug. *** *** Bug 222117 has been marked as a duplicate of this bug. *** *** Bug 223427 has been marked as a duplicate of this bug. *** *** Bug 223425 has been marked as a duplicate of this bug. *** *** Bug 223462 has been marked as a duplicate of this bug. *** *** Bug 223594 has been marked as a duplicate of this bug. *** *** Bug 223619 has been marked as a duplicate of this bug. *** *** Bug 223653 has been marked as a duplicate of this bug. *** *** Bug 223645 has been marked as a duplicate of this bug. *** *** Bug 223636 has been marked as a duplicate of this bug. *** *** Bug 223631 has been marked as a duplicate of this bug. *** (In reply to comment #30) > (In reply to comment #8) > > I found a 'workaround' to this problem which needs to be backported to 0.5 > > versions of packagekit-qt the weird part is that this does not happen in > > kpackagekit bin or kcms only on kded module pretty weird. > > Hopefully on the next release you will have this fixed, as for > > now I'd disable the update checks in system settings -> advanced -> services -> > > kpackagekit, so kded4 can keep up working... > > Best, > > Daniel. > > > is it possible to fix this problem with new kpackagekit version? i don't want > to disable update checks feature... Yes, KPackageKit > 0.5.3 already fix this. *** Bug 223725 has been marked as a duplicate of this bug. *** *** Bug 223751 has been marked as a duplicate of this bug. *** *** Bug 223864 has been marked as a duplicate of this bug. *** *** Bug 223854 has been marked as a duplicate of this bug. *** *** Bug 223913 has been marked as a duplicate of this bug. *** *** Bug 223927 has been marked as a duplicate of this bug. *** *** Bug 223928 has been marked as a duplicate of this bug. *** *** Bug 224007 has been marked as a duplicate of this bug. *** *** Bug 223998 has been marked as a duplicate of this bug. *** *** Bug 224132 has been marked as a duplicate of this bug. *** *** Bug 224157 has been marked as a duplicate of this bug. *** *** Bug 224284 has been marked as a duplicate of this bug. *** *** Bug 224321 has been marked as a duplicate of this bug. *** *** Bug 224387 has been marked as a duplicate of this bug. *** *** Bug 224413 has been marked as a duplicate of this bug. *** *** Bug 224401 has been marked as a duplicate of this bug. *** *** Bug 224417 has been marked as a duplicate of this bug. *** *** Bug 224472 has been marked as a duplicate of this bug. *** Is Fedora team aware of this bug? Would it be possible to offer an online update for KPackageKit to upgrade it to > 0.5.3? Not that I don't mind closing all duplicates, but since it affects daily work, the fix should reach users soon. Yes, please test, provide feedback, https://admin.fedoraproject.org/updates/F12/FEDORA-2010-0874 *** Bug 224476 has been marked as a duplicate of this bug. *** Since Sunday I've been running kpackagekit-0.5.4-1.fc12.i686. I'm getting update notifications again, and I haven't seen any crashes that seem to fit this. I think it's resolved. Last weekend I upgraded my Fedora 12 directly via yum. Kpackagetkit got upgraded and now i'm getting update notifications without problems. *** Bug 224491 has been marked as a duplicate of this bug. *** *** Bug 224495 has been marked as a duplicate of this bug. *** *** Bug 224505 has been marked as a duplicate of this bug. *** *** Bug 224568 has been marked as a duplicate of this bug. *** *** Bug 224571 has been marked as a duplicate of this bug. *** *** Bug 224631 has been marked as a duplicate of this bug. *** Is there an update for fc12.x86_64? I ran the update from the Fedora repository and the latest release is 0.5.2-1.fc12.x86_64 and this still has the bug. The update referenced in comment #82 is currently in updates-testing *** Bug 224742 has been marked as a duplicate of this bug. *** *** Bug 224804 has been marked as a duplicate of this bug. *** I updated kpackagekit to 0.5.4-1.fc12.x86_64 from fedora test repository and now it always crashes when it starts to look for software updates. Application: Systemeinstellungen (systemsettings), signal: Segmentation fault [KCrash Handler] #5 0x0000003815022f85 in KpkPackageModel::data(QModelIndex const&, int) const () from /usr/lib64/libkpackagekitlib.so #6 0x00007fd3072e5e51 in ?? () from /usr/lib64/kde4/kcm_kpk_update.so #7 0x00007fd3072e6fca in ?? () from /usr/lib64/kde4/kcm_kpk_update.so #8 0x000000395a55408c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4 #9 0x00007fd307722faf in PackageKit::Transaction::finished(PackageKit::Transaction::ExitStatus, unsigned int) () from /usr/lib64/libpackagekit-qt.so.12 #10 0x00007fd3077281bf in PackageKit::TransactionPrivate::finished(QString const&, unsigned int) () from /usr/lib64/libpackagekit-qt.so.12 #11 0x00007fd307729bf6 in PackageKit::TransactionPrivate::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libpackagekit-qt.so.12 #12 0x000000395a55408c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4 #13 0x00007fd30772b2c6 in PackageKit::TransactionProxy::Finished(QString const&, unsigned int) () from /usr/lib64/libpackagekit-qt.so.12 #14 0x00007fd30772bb74 in PackageKit::TransactionProxy::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libpackagekit-qt.so.12 #15 0x0000003959822e84 in ?? () from /usr/lib64/libQtDBus.so.4 #16 0x000000395982a61f in ?? () from /usr/lib64/libQtDBus.so.4 #17 0x000000395a54e401 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4 #18 0x00000036d7b8f65c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #19 0x00000036d7b968ce in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #20 0x00000036d6011a66 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #21 0x000000395a53ee6c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4 #22 0x000000395a53fa42 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4 #23 0x000000395a567573 in ?? () from /usr/lib64/libQtCore.so.4 #24 0x0000003950c3922e in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #25 0x0000003950c3cc18 in ?? () from /lib64/libglib-2.0.so.0 #26 0x0000003950c3cd3a in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #27 0x000000395a5671e6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #28 0x00000036d7c21ffe in ?? () from /usr/lib64/libQtGui.so.4 #29 0x000000395a53d772 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #30 0x000000395a53db44 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #31 0x000000395a53fcd9 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4 #32 0x000000000040c229 in _start () I couldn't install the debug packages (debuginfo-install foo) because of "No debuginfo packages available to install". fedora's kpackagekit-0.5.4-1 included a botched patch, 0.5.4-2 has been queue'd which should fix that. *** Bug 225077 has been marked as a duplicate of this bug. *** *** Bug 225111 has been marked as a duplicate of this bug. *** (In reply to comment #97) > fedora's kpackagekit-0.5.4-1 included a botched patch, 0.5.4-2 has been queue'd > which should fix that. kpackagekit-0.5.4-2 works well, thanks a lot. Now I'll observe the KDE crashes I had before. I hope they are resolved too. *** Bug 225186 has been marked as a duplicate of this bug. *** *** Bug 225190 has been marked as a duplicate of this bug. *** *** Bug 225208 has been marked as a duplicate of this bug. *** To anyone who reported this "kded4 crashing" bug: The crash is caused by a bug in package "kpackagekit". A fixed version is provided as an update for Fedora 12 that has been released today. Note that it may be possible that this bug actually prevents kpackagekit from upgrading the package, so you may have to "manually" update it using the "yum update kpackagekit" command inside a root console. Please make sure you update to version kpackagekit-0.5.4-2.fc12 of the package. Further information about yum can be found on http://docs.fedoraproject.org/yum/en/ If you need help, contact Fedora forums or other support channels. After this message, I will clear out the CC list, so if you would like to get further notification about this bug, you have to manually subscribe to it using the "Add CC" field. *** Bug 225225 has been marked as a duplicate of this bug. *** *** Bug 225229 has been marked as a duplicate of this bug. *** *** Bug 225250 has been marked as a duplicate of this bug. *** *** Bug 225259 has been marked as a duplicate of this bug. *** *** Bug 225287 has been marked as a duplicate of this bug. *** *** Bug 225298 has been marked as a duplicate of this bug. *** *** Bug 225311 has been marked as a duplicate of this bug. *** *** Bug 225334 has been marked as a duplicate of this bug. *** *** Bug 225338 has been marked as a duplicate of this bug. *** *** Bug 225346 has been marked as a duplicate of this bug. *** *** Bug 225512 has been marked as a duplicate of this bug. *** *** Bug 225542 has been marked as a duplicate of this bug. *** *** Bug 225607 has been marked as a duplicate of this bug. *** *** Bug 226208 has been marked as a duplicate of this bug. *** *** Bug 226390 has been marked as a duplicate of this bug. *** *** Bug 226373 has been marked as a duplicate of this bug. *** *** Bug 226920 has been marked as a duplicate of this bug. *** *** Bug 230547 has been marked as a duplicate of this bug. *** Created attachment 41647 [details]
New crash information added by DrKonqi
Attempting to install Google Chrome, why well normally Firefox does play Fash movies okay, I have noticed that all Flash moviesplay too fast, also the same in Konqueror and I had just installed Opera. I was going to try Google Chrome. Even Gnash and SWFDEC play flash movies too fast.
*** Bug 230950 has been marked as a duplicate of this bug. *** *** Bug 235470 has been marked as a duplicate of this bug. *** Created attachment 49779 [details]
New crash information added by DrKonqi
When I try to get updates, after I klicked the reload-button following report is shown:
An unexpected Error is occured. Please report that problem with the desctiption of fault.
Error Type:
Error Value: coercing to Unicode: need string or buffer, exceptions.SystemError found
File : /usr/share/PackageKit/helpers/apt/aptBackend.py, line 2216, in
main()
File : /usr/share/PackageKit/helpers/apt/aptBackend.py, line 2213, in main
run(args, options.single)
File : /usr/share/PackageKit/helpers/apt/aptBackend.py, line 2175, in run
backend.dispatcher(args)
File : /usr/lib/python2.6/dist-packages/packagekit/backend.py, line 699, in dispatcher
self.dispatch_command(args[0], args[1:])
File : /usr/lib/python2.6/dist-packages/packagekit/backend.py, line 606, in dispatch_command
self.refresh_cache(force)
File : /usr/share/PackageKit/helpers/apt/aptBackend.py, line 202, in _locked_cache
func(*args, **kwargs)
File : /usr/share/PackageKit/helpers/apt/aptBackend.py, line 1498, in refresh_cache
format_string(error.message))
File : /usr/lib/python2.6/dist-packages/packagekit/backend.py, line 723, in format_string
txt = unicode(text, encoding, errors='replace')
*** Bug 248069 has been marked as a duplicate of this bug. *** *** Bug 255748 has been marked as a duplicate of this bug. *** *** Bug 267304 has been marked as a duplicate of this bug. *** |
Application: kded4 ($Id: kded.cpp 1031637 2009-10-05 16:58:19Z lunakl $) KDE Platform Version: 4.3.85 (KDE 4.3.85 (KDE 4.4 Beta2)) (Compiled from sources) Qt Version: 4.6.0 Operating System: Linux 2.6.31.6-166.fc12.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: when I play film in smplayer fullscreen ,KDE daemon crash kwin efekt enable The crash can be reproduced some of the times. -- Backtrace: Application: KDE démon (kded4), signal: Segmentation fault 82 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) The current source language is "auto; currently asm". [KCrash Handler] #5 0x0000003c8ff78ad8 in QMetaObject::activate (sender=0xbba460, m=<value optimized out>, local_signal_index=11, argv=0x7fff30c58480) at kernel/qobject.cpp:3217 #6 0x0000003c95c226cf in PackageKit::Transaction::finished(PackageKit::Transaction::ExitStatus, unsigned int) () from /usr/lib64/libpackagekit-qt.so.12 #7 0x0000003c95c1e089 in PackageKit::ClientPrivate::serviceOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib64/libpackagekit-qt.so.12 #8 0x0000003c95c1f948 in PackageKit::ClientPrivate::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libpackagekit-qt.so.12 #9 0x0000003c8ff78833 in QMetaObject::activate (sender=0x8eebe0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x7fff30c58660) at kernel/qobject.cpp:3294 #10 0x0000003c9185c67f in QDBusConnectionInterface::serviceOwnerChanged (this=<value optimized out>, _t1=<value optimized out>, _t2=<value optimized out>, _t3=) at .moc/release-shared/moc_qdbusconnectioninterface.cpp:210 #11 0x0000003c9185c914 in QDBusConnectionInterface::qt_metacall (this=0x8eebe0, _c=InvokeMetaMethod, _id=2, _a=0x7fff30c588e0) at .moc/release-shared/moc_qdbusconnectioninterface.cpp:137 #12 0x0000003c8ff78833 in QMetaObject::activate (sender=0x8eebe0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x7fff30c588e0) at kernel/qobject.cpp:3294 #13 0x0000003c9185c5af in QDBusConnectionInterface::NameOwnerChanged (this=<value optimized out>, _t1=<value optimized out>, _t2=<value optimized out>, _t3=) at .moc/release-shared/moc_qdbusconnectioninterface.cpp:238 #14 0x0000003c9185c97c in QDBusConnectionInterface::qt_metacall (this=0x8eebe0, _c=InvokeMetaMethod, _id=6, _a=0x7fff30c58cb0) at .moc/release-shared/moc_qdbusconnectioninterface.cpp:141 #15 0x0000003c9182520e 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 0x0000003c9182d21f in QDBusCallDeliveryEvent::placeMetaCall (this=0x4, object=<value optimized out>) at qdbusintegrator_p.h:101 #17 0x0000003c8ff75791 in QObject::event (this=0x8eebe0, e=0xbbff90) at kernel/qobject.cpp:1260 #18 0x0000003c933ab9cc in QApplicationPrivate::notify_helper (this=0x8f0e70, receiver=0x8eebe0, e=0xbbff90) at kernel/qapplication.cpp:4242 #19 0x0000003c933b1f65 in QApplication::notify (this=<value optimized out>, receiver=0x8eebe0, e=0xbbff90) at kernel/qapplication.cpp:4125 #20 0x0000003df1a04ca6 in KApplication::notify (this=<value optimized out>, receiver=<value optimized out>, event=<value optimized out>) at /home/namar/rpmbuild/BUILD/kdelibs-4.3.85/kdeui/kernel/kapplication.cpp:302 #21 0x0000003c8ff65a0c in QCoreApplication::notifyInternal (this=0x7fff30c59710, receiver=0x8eebe0, event=0xbbff90) at kernel/qcoreapplication.cpp:704 #22 0x0000003c8ff66887 in sendEvent (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.h:215 #23 QCoreApplicationPrivate::sendPostedEvents (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.cpp:1345 #24 0x0000003c8ff8f283 in sendPostedEvents () at kernel/qcoreapplication.h:220 #25 postEventSourceDispatch () at kernel/qeventdispatcher_glib.cpp:276 #26 0x0000003c88a3922e in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #27 0x0000003c88a3cc18 in ?? () from /lib64/libglib-2.0.so.0 #28 0x0000003c88a3cd3a in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #29 0x0000003c8ff8edc3 in QEventDispatcherGlib::processEvents (this=0x8c1470, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:407 #30 0x0000003c93457ebe in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #31 0x0000003c8ff64342 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149 #32 0x0000003c8ff6471c in QEventLoop::exec (this=0x7fff30c59660, flags=...) at kernel/qeventloop.cpp:201 #33 0x0000003c8ff66b39 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981 #34 0x0000003df200ac97 in kdemain (argc=<value optimized out>, argv=<value optimized out>) at /home/namar/rpmbuild/BUILD/kdelibs-4.3.85/kded/kded.cpp:932 #35 0x0000003c84a1eb1d in __libc_start_main (main=<value optimized out>, argc=<value optimized out>, ubp_av=<value optimized out>, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=<value optimized out>) at libc-start.c:226 #36 0x0000000000400709 in _start () Reported using DrKonqi