Bug 160961 - crashes when ripping or encoding
crashes when ripping or encoding
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: grip (Show other bugs)
4
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Adrian Reber
Fedora Extras Quality Assurance
http://www.langgat.org/grip-trace.txt
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-06-19 05:46 EDT by Jørgen Langgåt
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-06-21 01:44:59 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Jørgen Langgåt 2005-06-19 05:46:03 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4

Description of problem:
When starting to encode the second track of a cd grip crashes. I have tried diferent riping programs (interlan cdparanoia, external cdparanoia, cdd2wav), and different encoders (lame and oggenc), and same problem. The website shows the "trace" I get in the terminal I started grip in.

Version-Release number of selected component (if applicable):
grip-3.2.0-4, libogg-1.1.2-2, id3lib-3.8.3-10, 

How reproducible:
Always

Steps to Reproduce:
1. insert cd
2. starting grip
3. start rip/encode of cd


Actual Results:  When the second song is about to get encoded, grip crashes

Expected Results:  Grip should continue to encode the next wav-file which is ready.

Additional info:
Comment 1 Jørgen Langgåt 2005-06-19 05:54:56 EDT
It looks like I had a bit of a haste with this bugraport.. I moved away the old
.grip that I got from another system, and startet again, with a fresh config.
Haven't crashed yet.
Comment 2 Adrian Reber 2005-06-20 14:20:56 EDT
Can I close the bug?
Comment 3 Jørgen Langgåt 2005-06-20 16:25:03 EDT
yes

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