Open SpecialBomb opened 1 year ago
👋 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.
I got the same error running whipper on NixOS. Downgrading cdrdao from 1.2.5 to 1.2.4 fixed the issue for me, so this may be a subtle variation on https://github.com/whipper-team/whipper/issues/591.
I got the same error running whipper on NixOS. Downgrading cdrdao from 1.2.5 to 1.2.4 fixed the issue for me, so this may be a subtle variation on #591.
I will give this a shot and see what it results in for me, thanks for pointing me in the right direction for the time being. I suppose someone should probably get in contact with the cdrdao maintainers.
Yeah, I think @Thra11 is right here. I ran into this on Fedora 38 (just upgraded my only system with an optical disc drive from 37 to 38...) and applying https://github.com/cdrdao/cdrdao/pull/21 to cdrdao does seem to fix it. So I think we can call this effectively the same as 591, caused by cdrdao.
I'm encountering this issue even with Arch's patched 1.2.5-3 (and 1.2.5-2), but I didn't before. Not sure what has changed, the 1.2.5-3 rebuild from a couple days ago didn't change any of the actual contents of the package and was just regenerating a missing metadata file.
Even with discs that worked before, I have the issue. Any ideas?
Nevermind, it turns out my drive numbering inexplicably changed. For some reason I get the FileNotFoundError mentioned instead of a message saying there's no CD in the drive. The drive giving me this issue is a TSSTcorp CDDVDW SH-222BB, although the drive seems to be dying because it won't read DVDs anymore and makes metallic noises with CDs (in other words, this may not be a software fault).
This applies to whipper version
0.10.0
within a Void Linux environment. Whipper was obtained from the official Void package repository.when using
whipper cd rip
, I appear to get an error regarding not being able to find a runtime directory that whipper generates in/tmp
. I don't know what might be causing this. Here is an example of the output generated by the error:Absolutely no clue why this is happening. I thought maybe for some reason my
/tmp/
directory had restricted permissions, but they are completely normal. What could be going on here?