Description of problem:
abrt fails to generate a backtrace because of missing debuginfo.
The error message needs to be more specific so I can take care of the problem.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.try to generate a backtrace
abrt fails to generate a backtrace with the message:
Coredump references 133 debuginfo files, 1 of them are not installed
Looking for needed packages in repositories
Can't find packages for 1 debuginfo files
Missing debuginfo file: /usr/lib/debug/.build-id/-/.debug
Backtrace is generated and saved, 54915 bytes
/usr/lib exists but not /usr/lib/debug
abrt could tell me which package this missing debuginfo file is related to, and more things I could use to remedy the problem. The message now leaves me in the dark about how to fix the problem.
> Missing debuginfo file: /usr/lib/debug/.build-id/-/.debug
seems like there was involved a binary without build_id - which means that it didn't come from Fedora official package. Or it can be a bug in ABRT. Would you mind uploading the core (please note, that the coredump contains the memory of the crashed process, so it can contain some sensitive data you don't want to share...)
No problem, I'll upload it if I can.
Are you referring to the "coredump" file? It is 200 Mb and bugzilla will only let me upload 20 Mb. Can I extract the data you need to make it smaller?
Yes, that's the file, uploading the output of:
$ eu-unstrip -n --core coredump
should give us some clues.
Created attachment 504537 [details]
eu-unstrip -n --core coredump
Problematic lines are:
0x344f200000+0x30c000 - /usr/lib64/nvidia/libGL.so.1 - libGL.so.1
0x3449000000+0x202000 - /usr/lib64/nvidia/tls/libnvidia-tls.so.270.41.06 - libnvidia-tls.so.270.41.06
0x344d000000+0x1c4d000 - /usr/lib64/nvidia/libnvidia-glcore.so.270.41.06 - libnvidia-glcore.so.270.41.06
You are using binary blob from Nvidia and we can do nothing for you :-/
Ok, I understand that, but could abrt at least say that?
That would save a lot of troubleshooting time for users.
Like if it could say "We cannot analyze this as you are using Nvidias proprietary driver"?
Does this also mean that no crash can ever be reported in this way until nouveau reaches maturity?
(In reply to comment #7)
> Does this also mean that no crash can ever be reported in this way until
> nouveau reaches maturity?
- if only one debuginfo is missing then there is a chance that the backtrace will be usable, the problem is if the crash is somewhere in the nvidia library - that's nothing we (Fedora) can fix.
I think we can improve the message to say:
Should be fixed in git 87a55b3f93d61a789f5538cb5e0937e80ea78398.
The tool now does not attempt to download debuginfo for build ids '-' and instead reports the executable without the build id.
abrt-2.0.9-1.fc17, libreport-2.0.10-1.fc17 has been submitted as an update for Fedora 17.
Package abrt-2.0.9-1.fc17, libreport-2.0.10-1.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing abrt-2.0.9-1.fc17 libreport-2.0.10-1.fc17'
as soon as you are able to, then reboot.
Please go to the following url:
then log in and leave karma (feedback).
abrt-2.0.10-1.fc17,libreport-2.0.10-2.fc17 has been submitted as an update for Fedora 17.
abrt-2.0.10-1.fc17, libreport-2.0.10-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.