Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 227435 - grip (and totem also) can't find audio CD
grip (and totem also) can't find audio CD
Product: Fedora
Classification: Fedora
Component: grip (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Adrian Reber
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-02-05 16:55 EST by Aaron Konstam
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:
Last Closed: 2007-03-22 15:58:57 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Aaron Konstam 2007-02-05 16:55:55 EST
Description of problem: When grip is run the program cannot find the audio CD
although it appears as an icon on my desktop. Neither can totem by the way.

Version-Release number of selected component (if applicable):

How reproducible:
always happens

Steps to Reproduce:
1.gzip /dev/cdrom-hdc
Actual results:
program opens but does not display and tracke to play.

Expected results:

plays the audio CD
Additional info:
Comment 1 Aaron Konstam 2007-02-05 17:25:26 EST
This is correction on previosu bug that identified gzip with Fedora Core rathere
than extras
Comment 2 Adrian Reber 2007-03-22 15:58:57 EDT
I cannot reproduce this in any way. It always finds the disc.

You are always talking about gzip, I hope this is just a typo and you really are
talking about grip.

According to the documentation (man grip; grip --help) the commandline you are
using is wrong. You should use grip --device=/dev/cdrom-hdc.

As this also happens with totem I would rather suspect this is a more common
problem with your system instead of totem/grip.

Please reopen if you are convinced that it is really a grip bug.

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