[Bug 1265399] Re: debug packages invalid in 13.10/saucy and probably trusty too

Harald Sitter sitter.harald at gmail.com
Thu Jan 2 10:40:10 UTC 2014


'Application: digikam (digikam), signal: Aborted'

If that is all there is then the retracer simply doesn't manage to get a
backtrace which is why it cannot find debug packages. Without files
affected by the crash it cannot find packages that provide debug symbols
for those files. Essentially the crash information is itself defunct
because of a very severe crash. If it is is reproducible please file a
bug manually at http://bugs.kde.org detailing how you can trigger the
crash.

FWIW, the .debug files are normal, they still pertain to so files etc
but their name reflect that they themselves are not so files and which
exact binary artifact they belong to (thus reliablity mapping a specific
build's .so to the same build's .debug).

** Changed in: digikam (Ubuntu)
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to digikam in Ubuntu.
https://bugs.launchpad.net/bugs/1265399

Title:
  debug packages invalid in 13.10/saucy and probably trusty too

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/digikam/+bug/1265399/+subscriptions




More information about the kubuntu-bugs mailing list