Bug 126150 - TVTime crashes after kernelupdate
Summary: TVTime crashes after kernelupdate
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: tvtime
Version: 2
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
Assignee: Than Ngo
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-06-16 19:01 UTC by Need Real Name
Modified: 2007-11-30 22:10 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2004-06-17 20:25:29 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Need Real Name 2004-06-16 19:01:28 UTC
Description of problem:
After a kernelupdate to kernel-2.6.6-1.435 tvtime crashes always with
the following output:

Running tvtime 0.9.12.
Reading configuration from /etc/tvtime/tvtime.xml
Reading configuration from /home/user/.tvtime/tvtime.xml
videoinput: Can't read frame. Error was: Input/output error (0).
videoinput: Can't read frame. Error was: Input/output error (0).
videoinput: Can't read frame. Error was: Input/output error (0).
Segmentation fault


it works with kernel-2.6.6-1.435.

Version-Release number of selected component (if applicable):
tvtime-0.9.12-5 kernel-2.6.6-1.435

Comment 1 Need Real Name 2004-06-16 19:05:49 UTC
> it works with kernel-2.6.6-1.435.

should be kernel-2.6.5-1.358

Comment 2 Billy Biggs 2004-06-22 12:49:10 UTC
Why was this closed and not forwarded upstream to me?

There is a known segfault in tvtime 0.9.12 that occurs if the first
few frames of video are all errors.  This can happen when some drivers
are in a bad state.  A workaround is sometimes to start tvtime on a
different input number.  I will try to post a 0.9.13 release that
fixes this problem, but even if I did you probably won't see anything
except a lot of errors from tvtime.

You should look at the output of dmesg and see if something is wrong
with the setup of your capture card driver.

Comment 3 David Juran 2004-08-10 21:55:48 UTC
I've opened up bug 129399 for the underlaying kernel bug.


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