Summary: | KPackageKit crashed while updating (PackageKit::Transaction::tid, KpkTransaction::setTransaction, KpkTransaction) | ||
---|---|---|---|
Product: | [Frameworks and Libraries] kpackagekit | Reporter: | Kvikende <kvikende> |
Component: | general | Assignee: | Steven M. Parrish <smparrish> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | andresbajotierra, dantti12, luislain |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Kvikende
2009-08-23 14:41:03 UTC
*** Bug 208882 has been marked as a duplicate of this bug. *** Bug 208882 got a complete backtrace: --- -- Backtrace: Application: KPackageKit (kpackagekit), signal: Segmentation fault [KCrash Handler] #5 PackageKit::Transaction::tid (this=0x0) at transaction.cpp:89 #6 0x0000003d9cc15f36 in KpkTransaction::setTransaction (this=0x2016790, trans=0x0) at /usr/src/debug/kpackagekit-0.4.2/libkpackagekit/KpkTransaction.cpp:108 #7 0x0000003d9cc169ba in KpkTransaction::KpkTransaction(struct PackageKit::Transaction *, QFlags<KpkTransaction::BehaviorFlag>, struct QWidget *) (this=0x2016790, trans=<value optimized out>, flags=<value optimized out>, parent=<value optimized out>) at /usr/src/debug/kpackagekit-0.4.2/libkpackagekit/KpkTransaction.cpp:84 #8 0x00007fefe007fb5f in KpkUpdate::applyUpdates (this=0x1ccabb0) at /usr/src/debug/kpackagekit-0.4.2/Updater/KpkUpdate.cpp:123 Sorry for not replying to these bug reports, thanks Dario for filtering them, well I still not sure why this happens the only thing that might cause this is that when the user trigger apply a transaction is not created and when setTransaction() is called it asks for the tid() on a transaction with errors. Hopefully this won't happen in 0.5 since now we have an error() to check if anything wrong happened.. I don't know which status to set this bug since I can't reproduce it all the time and I'm too busy these days .. :( Thanks. *** Bug 235557 has been marked as a duplicate of this bug. *** *** Bug 241820 has been marked as a duplicate of this bug. *** Does the reporter still get this issue? I have tested 0.6.0 on a F13 and didn't see the problem. I am no longer using KDE so cannot confirm. Hopefully it is. Ok, I'll close it as works for me. Thanks. |