Bug 548148 - ABRT is not seeing installed debuginfo packages
Summary: ABRT is not seeing installed debuginfo packages
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jiri Moskovcak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-16 19:07 UTC by Steven Stern
Modified: 2015-02-01 22:50 UTC (History)
10 users (show)

Fixed In Version: abrt-1.0.7-1.fc12
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-02-23 05:38:43 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Steven Stern 2009-12-16 19:07:46 UTC
Abrt says it can't report a firefox crash because I need to
"debuginfo-install firefox". I did that, downloading and installing
127MB of stuff.  Now, there's been another Firefox crash and abrt is
telling me the same thing.  When I open the current item in abrt, it displays "13 debuginfo missing" or something like that and grinds for a while, then displays, in red, the need to run "debuginfo-install firefox".



trying debuginfo-install again shows that everything is installed.

$ sudo debuginfo-install firefox
Package firefox-debuginfo-3.5.5-1.fc12.i686 already installed and latest
version
Package glibc-debuginfo-2.11-2.i686 already installed and latest version
Package glibc-debuginfo-2.11-2.i686 already installed and latest version
Package alsa-lib-debuginfo-1.0.21-3.fc12.i686 already installed and
latest version
Package atk-debuginfo-1.28.0-1.fc12.i686 already installed and latest
version
Package cairo-debuginfo-1.8.8-3.fc12.i686 already installed and latest
version
Package glibc-debuginfo-2.11-2.i686 already installed and latest version
Package glibc-debuginfo-2.11-2.i686 already installed and latest version
Package glibc-debuginfo-2.11-2.i686 already installed and latest version
Package glibc-debuginfo-2.11-2.i686 already installed and latest version
Package glibc-debuginfo-2.11-2.i686 already installed and latest version
Package glibc-debuginfo-2.11-2.i686 already installed and latest version
Package glibc-debuginfo-2.11-2.i686 already installed and latest version
Package glibc-debuginfo-2.11-2.i686 already installed and latest version
Package glibc-debuginfo-2.11-2.i686 already installed and latest version
Package glibc-debuginfo-2.11-2.i686 already installed and latest version
Package glibc-debuginfo-2.11-2.i686 already installed and latest version
Package fontconfig-debuginfo-2.8.0-1.fc12.i686 already installed and
latest version
Package freetype-debuginfo-2.3.11-3.fc12.i686 already installed and
latest version
Package gcc-debuginfo-4.4.2-7.fc12.i686 already installed and latest version
Package gcc-debuginfo-4.4.2-7.fc12.i686 already installed and latest version
Package gcc-debuginfo-4.4.2-7.fc12.i686 already installed and latest version
Package GConf2-debuginfo-2.28.0-2.fc12.i686 already installed and latest
version
Package gtk2-debuginfo-2.18.4-3.fc12.i686 already installed and latest
version
Package gtk2-debuginfo-2.18.4-3.fc12.i686 already installed and latest
version
Package glib2-debuginfo-2.22.3-1.fc12.i686 already installed and latest
version
Package glib2-debuginfo-2.22.3-1.fc12.i686 already installed and latest
version
Package glib2-debuginfo-2.22.3-1.fc12.i686 already installed and latest
version
Package gnome-vfs2-debuginfo-2.24.2-2.fc12.i686 already installed and
latest version
Package glib2-debuginfo-2.22.3-1.fc12.i686 already installed and latest
version
Package glib2-debuginfo-2.22.3-1.fc12.i686 already installed and latest
version
Package gtk2-debuginfo-2.18.4-3.fc12.i686 already installed and latest
version
Package glibc-debuginfo-2.11-2.i686 already installed and latest version
Package nspr-debuginfo-4.8.2-1.fc12.i686 already installed and latest
version
Package pango-debuginfo-1.26.1-1.fc12.i686 already installed and latest
version
Package pango-debuginfo-1.26.1-1.fc12.i686 already installed and latest
version
Package pango-debuginfo-1.26.1-1.fc12.i686 already installed and latest
version
Package nspr-debuginfo-4.8.2-1.fc12.i686 already installed and latest
version
Package nspr-debuginfo-4.8.2-1.fc12.i686 already installed and latest
version
Package glibc-debuginfo-2.11-2.i686 already installed and latest version
Package glibc-debuginfo-2.11-2.i686 already installed and latest version
Package glibc-debuginfo-2.11-2.i686 already installed and latest version
Package glibc-debuginfo-2.11-2.i686 already installed and latest version
Package startup-notification-debuginfo-0.10-2.fc12.i686 already
installed and latest version
Package gcc-debuginfo-4.4.2-7.fc12.i686 already installed and latest version
Package gcc-debuginfo-4.4.2-7.fc12.i686 already installed and latest version
Package xulrunner-debuginfo-1.9.1.5-1.fc12.i686 already installed and
latest version
Package xulrunner-debuginfo-1.9.1.5-1.fc12.i686 already installed and
latest version
No debuginfo packages available to install

Comment 1 Denys Vlasenko 2009-12-17 15:47:53 UTC
What version of abrt do you have installed?

Comment 2 Steven Stern 2009-12-17 19:51:58 UTC
$ rpm -qa |grep abrt
abrt-plugin-sqlite3-1.0.0-1.fc12.i686
abrt-addon-ccpp-1.0.0-1.fc12.i686
abrt-1.0.0-1.fc12.i686
abrt-plugin-kerneloopsreporter-1.0.0-1.fc12.i686
abrt-plugin-bugzilla-1.0.0-1.fc12.i686
abrt-addon-python-1.0.0-1.fc12.i686
abrt-addon-kerneloops-1.0.0-1.fc12.i686
abrt-desktop-1.0.0-1.fc12.i686
abrt-gui-1.0.0-1.fc12.i686
abrt-libs-1.0.0-1.fc12.i686
abrt-plugin-logger-1.0.0-1.fc12.i686

Comment 3 Denys Vlasenko 2009-12-18 14:53:06 UTC
We were working on improving debuginfo install in recent versions. Latest one even has a log window, which helps with diagnosing this kind of problems.

Unfortunately, 1.0.1 had a simple but nasty bug and debuginfo installs didn't work at all :( but 1.0.2 is out already!

(1.0.3+ will likely have even more fixes, but you'll need to wait for it)

Can you install 1.0.2 and try again? abrt-gui in 1.0.2 has a possibility to regenerate a backtrace.

Comment 4 Steven Stern 2009-12-18 16:29:06 UTC
Installing abrt from updates-testing. Will report back after the next Ff crash.

Comment 5 Steven Stern 2009-12-19 17:05:53 UTC
Crash in compiz...  ABRT has been looking for debuginfo for the last 10 minutes.  Here's the command line it's running. I don't think it's going to finish in my lifetime, so I'm killing it.

/usr/bin/yum --enablerepo=*debuginfo* --quiet provides /usr/lib/debug/.build-id/60/e56607981d360f5b92a876477ce224f4125529.debug /usr/lib/debug/.build-id/63/91727667c5490a7ea9bf623922198e37d4fab3.debug /usr/lib/debug/.build-id/73/520e6ba473ddd4ca6c54aac2da3ac03ff59cd5.debug /usr/lib/debug/.build-id/8d/b52870bc789270f14b0459eaf02c679c177178.debug /usr/lib/debug/.build-id/93/b75283b58aae0ac5a340351f28b58ef4f06cb6.debug /usr/lib/debug/.build-id/bf/6c0e557eb8ef5c07f4fd8c632c07d996e87160.debug /usr/lib/debug/.build-id/bf/ad3faf24656c4d519ff6e0617ed56eb1489050.debug /usr/lib/debug/.build-id/f6/a786585bf3ed3bb06ec73e608a16b7f171c39c.debug

Comment 6 Christopher Beland 2010-01-05 03:14:21 UTC
I'm not sure Comment 5 represents the same problem as the original report; you might want to re-test with Firefox specifically since you've already installed everything for that.  If it's not crashing on its own, you should be able to induce a crash with "killall -SEGV firefox", though the particular type of crash might make a difference.  (Obviously, you should save anything important open in your browser first.)

I've been looking at similar bugs (e.g. Bug 547027, Bug 552435) and it seems the "unusable" backtrace that *is* produced (visible on the screen when you get the reported error, but also saved in /var/cache/abrt/) sometimes contains useful hints as to what has gone wrong.  That might be useful to attach to this report if you can still reproduce the problem.

---

Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 7 Denys Vlasenko 2010-01-05 10:38:34 UTC
(In reply to comment #5)
> Crash in compiz...  ABRT has been looking for debuginfo for the last 10
> minutes.  Here's the command line it's running. I don't think it's going to
> finish in my lifetime, so I'm killing it.
>
> /usr/bin/yum --enablerepo=*debuginfo* --quiet provides
> /usr/lib/debug/.build-id/60/e56607981d360f5b92a876477ce224f4125529.debug
> /usr/lib/debug/.build-id/63/91727667c5490a7ea9bf623922198e37d4fab3.debug
> /usr/lib/debug/.build-id/73/520e6ba473ddd4ca6c54aac2da3ac03ff59cd5.debug
> /usr/lib/debug/.build-id/8d/b52870bc789270f14b0459eaf02c679c177178.debug
> /usr/lib/debug/.build-id/93/b75283b58aae0ac5a340351f28b58ef4f06cb6.debug
> /usr/lib/debug/.build-id/bf/6c0e557eb8ef5c07f4fd8c632c07d996e87160.debug
> /usr/lib/debug/.build-id/bf/ad3faf24656c4d519ff6e0617ed56eb1489050.debug
> /usr/lib/debug/.build-id/f6/a786585bf3ed3bb06ec73e608a16b7f171c39c.debug  

I, as one of abrt developers, is at a loss what to do here. I _need_ the information from this command. What should I do to make abrt not fall in this trap - kill this command after some timeout and classify it as "failed to get debuginfos"? This can be done, but it would be almost as bad.

I created a RFE to yum people, bug 533832, where I ask for yum to give a bit more information about its progress, so that such problems can be better diagnosed. Knowing *why* yum is stuck, and showing it to abrt user, would be an improvement.

Comment 8 Denys Vlasenko 2010-02-11 16:57:11 UTC
Added -R2 ("wait max 2 minutes") to yum.

Comment 9 Fedora Update System 2010-02-15 14:07:08 UTC
abrt-1.0.7-1.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/abrt-1.0.7-1.fc12

Comment 10 Fedora Update System 2010-02-18 22:31:01 UTC
abrt-1.0.7-1.fc12 has been pushed to the Fedora 12 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update abrt'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-1598

Comment 11 Fedora Update System 2010-02-23 05:37:05 UTC
abrt-1.0.7-1.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.