Re: lsdvd/tcprobe fails?

Steve Malenfant <[email protected]> Sat, 2 May 2009 22:47:35 -0400
Newsgroups gmane.comp.video.dvdrip.user
Message-ID <[email protected]>
The problem is with Perl I believe. I upgraded my version of perl from
Centos to RPMForge and everything stopped working.

I couldn't use dvdrip since.

On Thu, Apr 30, 2009 at 6:40 PM, JD <[email protected]> wrote:

>
>
> Noah Romer wrote:
>
>> Noah Romer wrote:
>>
>>> I too am running a CentOS system (5.3, 32-bit) and am seeing such
>>> behavior. Run from the command line, lsdvd produces a dvd table of contents,
>>> but dvd::rip appears to get stuck when calling it. Like the previous poster,
>>> the last thing in my log is:
>>>
>>> Tue Apr 21 19:32:57 2009 Start job 'Read TOC (lsdvd|tcprobe)'
>>> Tue Apr 21 19:32:57 2009 Start job 'Read TOC (lsdvd)'
>>> Tue Apr 21 19:32:57 2009 Executing command: execflow lsdvd -a -n -c -s -v
>>> -Op \/dev\/scd0 2>/dev/null && echo EXECFLOW_OK
>>>
>>> If another strace would be helpful, I'd be happy to provide one. I'm
>>> running dvd::rip 0.98.10 and lsdvd 0.16-2.el5.
>>>
>>
>> It doesn't appear to be lsdvd that's the problem. It looks like maybe an
>> issue with Event::ExecFlow. When I start dvd::rip, a `ps aufx` shows it
>> running with no child processes. However, immediately after I click the
>> "Read DVD table of contents" button, it acquires a zombie child process:
>>
>>
>> klevin    8906  2.7  0.8 138612 34696 ?        S    15:15   0:01
>> /usr/bin/perl /usr/bin/dvdrip
>> klevin    8969  0.0  0.0      0     0 ?        Z    15:16   0:00  \_ [sh]
>> <defunct>
>>
>> There's never any indication that lsdvd has actually been called (the
>> access light on the dvd drive never turns on, and I don't hear it spin up).
>>
>>
>>
> In my case (running it on FC7), clicking to read the TOC causes the dvd to
> spin up and you can hear it.
> It stays spinning for about 10-20 seconds (I did not time it). Then it
> stops. TOC is never displayed.
>
> I am amazed that not a single developer has directly replied to and
> addressed this problem.
> Is no one else having this problem on other platforms?
>
>