Bug 112513 - Running 'record' causes reboot
Summary: Running 'record' causes reboot
Alias: None
Product: Fedora
Classification: Fedora
Component: xawtv
Version: 1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Than Ngo
QA Contact:
Depends On:
Blocks: FC3BugWeekTracker
TreeView+ depends on / blocked
Reported: 2003-12-21 23:17 UTC by adam.huffman
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2004-09-28 21:24:32 UTC
Type: ---

Attachments (Terms of Use)

Description adam.huffman 2003-12-21 23:17:21 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)

Description of problem:
When I try to use 'record', a console audio recorder which comes with
xawtv, it runs for a couple of seconds then causes the system to reboot.

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

How reproducible:

Steps to Reproduce:
1. Start /usr/bin/record

Actual Results:  Record starts though with no audio level meters, then
after a second or two the system reboots.

Expected Results:  Record should start normally.

Additional info:

The via82cxxx_audio module is being used, on an Asus Terminator K7 system.

I have also seen this problem on another system, using the
via82cxxx_audio module.

There is no such problem on another system using the maestro3 module.

Comment 1 Marcin Garski 2004-09-28 21:24:32 UTC
Thanks for the bug report. However, Red Hat no longer included xawtv
in Fedora Core. It has been replaced by tvtime.
Please upgrade to the latest version of Fedora Core and open a new bug
if the problem also occur in tvtime.

If you still use xawtv and this bug still persists, please report the
problem in upstream bug tracker or on mailing list
(usualy they can be found on xawtv website
If the project don't have bug tracker and mailing list, you should
sent bug report by email to xawtv maintainer.
Also Fedora Legacy Project (http://fedoralegacy.org/) maintains some
older releases, and if you believe this bug is interesting to them,
please report the problem in the bug tracker at:

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