Something crashes. Crash assistant appears. Pressing 'install debug symbols' button pops up a terminal window, it doesn't install anything. Unable to report a crash because debug symbols cannot be installed. The problem appears to be that in the terminal window, it is calling the command 'pkexec debuginfo-install' Not 'pkexec debuginfo-install ktorrent' Because drkonqi doesn't specify the package to install debug symbols for, the command fails and symbols can never be installed by the assistant. The only workaround is to go to a terminal and manually enter 'debuginfo-install ktorrent' Reproducible: Always Expected Results: drkonqi knows what package it needs debug symbols for. It should be able to call the install command correctly. $ rpm -q --whatprovides /usr/libexec/kde4/drkonqi kde-runtime-4.9.2-1.fc17.x86_64
Please report this to the fedora bug tracker. The packagers are the people responsible for providing this functionality in drkonqi, therefore it's their bug to fix. Thanks.
Uhm, if DrKonqi is passing an empty list to the debuginfo installation script, how is it supposed to know what it should install? Maybe the real problem is that nothing useful is showing up in the backtrace, so DrKonqi doesn't know what to request symbols for?
Created attachment 76766 [details] List of missing bits Shows list of files needing debug info, but none even remotely similar in Yum Extender.
Created attachment 76767 [details] DUH error message Not helpful at all.
Created attachment 76768 [details] First window that comes up This is the original window that comes up first asking for "symbols", what ever they are. (Aren't they actually debug packages?)
I will also add that these symbols (?) are needed by the KDE system tool from KDE system components, and they have nothing to do with Fedora. If the KDE person who made the program components failed to create the debug components, there would be nothing to package by any one else.
> Shows list of files needing debug info, but none even remotely similar in Yum Extender. Because those are file names, not package names. > DUH error message > > Not helpful at all. You mention in comment #6 that you're using Fedora, but what version of Fedora are you using? (In current Fedora, you should be seeing a Konsole window in which you can see the actual error message.) > This is the original window that comes up first asking for "symbols", what ever they > are. (Aren't they actually debug packages?) Debugging symbols are what debugging information contains, and debugging information is what debug(info) packages contain. > I will also add that these symbols (?) are needed by the KDE system tool from KDE > system components, and they have nothing to do with Fedora. DrKonqi is indeed part of kde-runtime as shipped by KDE, but the script it invokes to install debugging information is distribution-specific. > If the KDE person who made the program components failed to create the debug > components, there would be nothing to package by any one else. That's not at all how debugging information works. It is generated automatically by the compiler when the compiler is invoked with correct flags (-g) and Fedora's build process splits it into separate -debuginfo subpackages, which you are asked to install. Debugging information is not installed by default because it is not necessary for normal program operation.
I filed a report with Fedora, but nothing has come of it yet https://bugzilla.redhat.com/show_bug.cgi?id=866262
Kerry N, your issue is probably not the same as the one in comment #3 (whose reporter unfortunately hijacked your bug report). In your case, I need the backtrace without debugging information, which might give a hint as to why installing the debugging information required to get a complete backtrace fails. (As I said in the Fedora bug report, I suspect that it is because the backtrace does not mention any executable or shared library, e.g. because it is in code produced at runtime by a just-in-time (JIT) compiler, or for some other reason.)
And in the case of comment #3 and followups, I need the error message printed inside the Konsole window. I cannot do anything with only the dialog from comment #4.
Fedora 17
Don't know how to get Konsole window stuff to help with this.
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!
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!
Related/duplicate https://bugs.kde.org/show_bug.cgi?id=326070
my report about this issue: bug 400386
Closing for downstream. Generally you should file bugs about failed debug installation to the distribution first as the installer itself is distribution-specific tooling. If and only they find it to be not a bug in the installer itself is it worth filing a bug in drkonqi about whatever is wrong with drkonqi. Assuming the original problem here really was an empty list of files this should no longer happen. There is a guard in place to prevent showing the install button when no libraries are detected as missing.