GNOME Bugzilla – Bug 126632
Just crashed after extracting a CD
Last modified: 2009-08-15 18:40:50 UTC
Distribution: Fedora Core release 1 (Yarrow) Package: sound-juicer Severity: critical Version: GNOME2.4.0 0.5 Gnome-Distributor: GNOME.Org Synopsis: Just crashed after extracting a CD Bugzilla-Product: sound-juicer Bugzilla-Component: general Bugzilla-Version: 0.5 BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: Just crashed. Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? First CD that I have extracted. Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/sound-juicer' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread -1085316224 (LWP 4514)] (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... 0x0089ec32 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 41613
Thread 1 (Thread -1085316224 (LWP 4514))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-11-10 11:50 ------- Reassigning to the default owner of the component, sound-juicer-maint@bugzilla.gnome.org.
*** Bug 128521 has been marked as a duplicate of this bug. ***
Bug 128423 may also be a duplicate of this bug. Other than that and 128521 which was just marked as a duplicate of this bug, this appears to be a unique stack trace (according to the simple-dup-finder).
It is also totally useless. Does Fedora have debug-info packages for sound-juicer? If not, the only way to debug this is for the reporter to build sound-juicer from source.
*** Bug 129583 has been marked as a duplicate of this bug. ***
Unfortunately, the debuginfo rpms are not distributed. You can sometimes ask a Red Hat maintainer for them and get them, but that isn't quite optimal either... However, you can build the debuginfo rpms yourself (if you're running Fedora). Here's the method--hopefully one of the reporters is willing to give it a shot: Assuming you have everything setup (see below), you can just grab the relevant source rpm from your favorite Fedora mirror and run (assuming that the source rpm's name is some-package.src.rpm): rpmbuild --rebuild some-package.src.rpm Which should build all the relevant rpms for that package including the debuginfo rpm. After doing that, simply install the debuginfo rpm and you should be good to go. To be able to do this, you have to have two things done: (1) You have to have the relevant development libraries installed and (2) you have to have an rpm building environment setup. To make sure the first is done, you run redhat-config-packages (also found in the menu under System Settings->Add/Remove Applications) and make sure that Development Tools and GNOME Software Development groups of packages are installed. To make sure you have an rpm building environment setup, run the following: 1) mkdir -p ~/rpm/{SRPMS,RPMS,SOURCES,SPECS,BUILD} 2) mkdir -p ~/rpm/RPMS/{i386,i586,i686,noarch,athlon} 3) echo "%_topdir " ~/rpm >> .rpmmacros the above will set up the build environment and make it so that any built rpms (from the rpmbuild command) will end up under one of the subdirectories of ~/rpm/RPMS/.
I was wrong. Fedora does distribute debuginfo rpms. Can someone who has duplicated this bug please install the sound-juicer and gtk2 debuginfo rpms from http://download.fedora.redhat.com/pub/fedora/linux/core/1/i386/debug/ and then get us another stack trace?
*** Bug 135254 has been marked as a duplicate of this bug. ***
No response--closing.
*** Bug 137726 has been marked as a duplicate of this bug. ***