Bug 321808 - drkonqi isn't able to find/install missing kactivitymanagerd dbg packages
Summary: drkonqi isn't able to find/install missing kactivitymanagerd dbg packages
Status: RESOLVED DOWNSTREAM
Alias: None
Product: drkonqi
Classification: Applications
Component: general (show other bugs)
Version: 2.1.5
Platform: Ubuntu Linux
: NOR major
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-01 00:43 UTC by Eugene
Modified: 2019-07-02 14:03 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eugene 2013-07-01 00:43:55 UTC
Kactivitymanagerd crashed but drkonqi wasn't be able to find debug symbols:

libkactivities-dbg
kde-runtime-dbg

 although they was installed.

Reproducible: Always

Steps to Reproduce:
1. When kactivitymanagerd crashes try to install debug-symbols pushing the appropriate button.
2. 
3.
Actual Results:  
drkonqi can't find debug symbols needed for kactivitymanagerd. But if we look for libkactivities-dbg, kde-runtime-dbg, we find they're installed already.


Kubuntu 13.04 x86_64
KDE 4.11 beta2
Comment 1 Eugene 2013-07-01 00:45:52 UTC
The similar bug on launchpad.net: https://bugs.launchpad.net/kubuntu-ppa/+bug/941753
Comment 2 Tomasz Kaźmierczak 2013-07-07 12:23:17 UTC
Same problem here, with KDevelop. I've installed the KDevelop debugging symbols package (kdevelop-dbg), but drkonqi stubbornly claims that it's not there and sees only the following crash message:
Application: KDevelop (kdevelop), signal: Aborted


Debian Jessie x86_64
KDE 4.8.4
For reference, the version of both kdevelop and kdevelop-dbg packages is: 4:4.3.1-3+b1
Comment 3 Christoph Feck 2013-07-19 01:04:06 UTC
Could you add the incomplete backtrace to check which libraries miss debug symbols? I guess the distribution-specific code has to figure out exact package names.
Comment 4 Tomasz Kaźmierczak 2013-07-19 07:49:23 UTC
in my case the only message in the backtrace textedit is this:
Application: KDevelop (kdevelop), signal: Aborted

Or do you mean a gdb backtrace produced when running it from command line? I can send it, but not until next wednesday
Comment 5 Eugene 2013-07-19 18:21:48 UTC
I must wait when kactivitymanagerd crashed to send you backtrace. Since that crash there was no one again.
Comment 6 Tomasz Kaźmierczak 2013-07-22 13:10:47 UTC
I've just had a crash of KDevelop on my other system - Kubuntu 13.04 with KDE 4.10.5. This time drkonqui had no problems with generating debug output, so perhaps this was an issue in an older version of KDE. Or can it be distribution specific? Maybe I'll wait till Debian upgrades KDE to some newer version and recheck this.
Comment 7 Andrew Crouthamel 2018-11-10 03:18:57 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Andrew Crouthamel 2018-11-20 04:03:07 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Harald Sitter 2019-07-02 14:03:58 UTC
Resolution and installation of debug packages is driven by distribution-specific tooling. If that doesn't work well enough you'll have to take that up with your distribution unfortunately.