Summary: | kopete crash in libkyahoo | ||
---|---|---|---|
Product: | [Applications] kopete | Reporter: | Paul Fee <paul.f.fee> |
Component: | general | Assignee: | Kopete Developers <kopete-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | andresbajotierra |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Paul Fee
2009-07-17 17:31:42 UTC
This looks related to bug 200186 / bug 200207 BTW, the debug package is named "kdenetwork-dbg", if you could install it and try to get a new backtrace it could be great. Thanks Hi Dario, Thanks for the info on where to find the debuginfo package. Curious that "dpkg -S /usr/lib/libkyahoo.so.1" showed that the library came from the kopete package, yet the debuginfo data is in kdenetwork-dbg. I've been following the convention of installing the package with the same name, but with a -dbg suffix. If this isn't always the case, do you have tips on how to find the right debuginfo package for other packages? I'll install kdenetwork-dbg and post a new backtrace should the crash happen again. Thanks, Paul Thanks. On Debian/Ubuntu like distributions, the KDE packages for installation uses the name of the app (they are splitted; like "kopete", "kget" ...); but the debug information packages uses the name of the whole module (kdebase, kdenetwork, kdegraphics, kdemultimedia) plus the "-dbg" suffix This particular bug hasn't recurred, so I'm unable to give a better stack trace at this time. I'm unable to say whether the bug has been fixed, if my usage pattern has changed or if Yahoo servers are behaving differently such that the relevant code containing the bug is not getting triggered. Thanks. I'm merging with bug 200186. *** This bug has been marked as a duplicate of bug 200186 *** |