Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Drive analysis fails #361

Closed
NovaPhoenix opened this issue Jan 29, 2019 · 2 comments · Fixed by #409
Closed

Drive analysis fails #361

NovaPhoenix opened this issue Jan 29, 2019 · 2 comments · Fixed by #409
Assignees
@JoeLametta
Labels
Accepted Accepted issue on our roadmap Bug Generic bug: can be used together with more specific labels Priority: low Low priority Sprintable Small enough to sprint on Stretch Optional goal for the current sprint (may not be delivered)
Milestone
0.8.0

Comments

@NovaPhoenix
Copy link

After running whipper drive analyse (both with and without drive specified) I get this error: CRITICAL:whipper.command.drive:cannot analyze the drive: is there a CD in it?
There is a CD in the drive and other programs are able to access it. I am able to play the CD using Clementine and other audio players. I'm using whipper 0.7.3 on Fedora 29. Here's my drive:

$ whipper drive list
drive: /dev/cdrom, vendor: HL-DT-ST, model: DVD+-RW GU90N   , release: A1C2

Logs attached.

Output of WHIPPER_DEBUG=DEBUG WHIPPER_LOGFILE=whipper.log whipper drive analyze
@welcome
Copy link

welcome bot commented Jan 29, 2019

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.

To help make it easier for us to investigate your issue, please follow the contributing instructions.

@JoeLametta JoeLametta added Bug Generic bug: can be used together with more specific labels Status: in progress Issue/pull request which is currently being worked on Accepted Accepted issue on our roadmap Priority: low Low priority Sprintable Small enough to sprint on Needed: patch A pull request is required labels Feb 2, 2019
@JoeLametta JoeLametta self-assigned this Feb 2, 2019
@JoeLametta JoeLametta added this to the 1.0 milestone Feb 2, 2019
@JoeLametta
Copy link
Collaborator

I've identified the issue, it will be fixed soon.

@JoeLametta JoeLametta added the Stretch Optional goal for the current sprint (may not be delivered) label Feb 2, 2019
JoeLametta added a commit that referenced this issue Jul 7, 2019
@JoeLametta
Fix erroneous result message for whipper drive analyze
048a31e 
If cdparanoia fails to analyze the drive, the drive is now marked as unable to defeat the cache.

Fixes #361.

Signed-off-by: JoeLametta <[email protected]>
@JoeLametta JoeLametta mentioned this issue Jul 7, 2019
Merged
@JoeLametta JoeLametta modified the milestones: 1.0, 0.8.0 Oct 21, 2019
@JoeLametta JoeLametta removed Status: in progress Issue/pull request which is currently being worked on Needed: patch A pull request is required labels Oct 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JoeLametta JoeLametta

Labels
Accepted Accepted issue on our roadmap Bug Generic bug: can be used together with more specific labels Priority: low Low priority Sprintable Small enough to sprint on Stretch Optional goal for the current sprint (may not be delivered)
Projects
None yet
Milestone
0.8.0
Development

Successfully merging a pull request may close this issue.

Fix erroneous result message for whipper drive analyze whipper-team/whipper
2 participants
@JoeLametta @NovaPhoenix