Bug 606024 - [abrt] crash in dvgrab-3.4-3.fc12: raise: Process /usr/bin/dvgrab was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in dvgrab-3.4-3.fc12: raise: Process /usr/bin/dvgrab was killed ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: dvgrab
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jay Fenlason
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:c102e819edfbc9c08c9febba297...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-20 01:11 UTC by Stan King
Modified: 2014-08-31 23:29 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-27 18:36:19 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (9.04 KB, text/plain)
2010-06-20 01:11 UTC, Stan King
no flags Details

Description Stan King 2010-06-20 01:11:49 UTC
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: dvgrab -format mpeg2 -guid 1 -d 33min
component: dvgrab
crash_function: raise
executable: /usr/bin/dvgrab
global_uuid: c102e819edfbc9c08c9febba297ecdc48798fc74
kernel: 2.6.32.14-127.fc12.i686.PAE
package: dvgrab-3.4-3.fc12
rating: 4
reason: Process /usr/bin/dvgrab was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

comment
-----
My command line was "dvgrab -format mpeg2 -guid 1 -d 33min".

Here are the last messages before it crashed.
There were dozens of "invalid packet sync_bytes" messages beforehand:

...
Invalid packet sync_byte 0x29!
Invalid packet sync_byte 0x82!
Invalid packet sync_byte 0x3f!
Invalid packet sync_byte 0xbd!
Capture Started
>>> Error writing frame!
"dvgrab-002.m2t":     0.00 MiB 0 frames timecode -1458390987:-1435810519:-964444403.-1640976801 date -1616836063.2048237821.714096515 -1972388652:-2112666666:-706633712
Capture Stopped
terminate called after throwing an instance of 'std::string'
^C/home/stan/bin/grab_stb: line 5:



How to reproduce
-----
1. Tried to grab from a Motorola QIP 7100 HD set-top box
2.
3.

Comment 1 Stan King 2010-06-20 01:11:50 UTC
Created attachment 425404 [details]
File: backtrace

Comment 2 Bug Zapper 2010-11-03 13:02:31 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Stan King 2010-11-22 08:32:37 UTC
I've verified that this bug still happens with Fedora 13, using dvgrab 3.5.1.

The error occurs when using dvgrab against a set-top box stream that's "encrypted" rather than a stream that's in-the-clear.

I'd be happy to try test versions or recompilations that you might suggest.

Stan

Comment 4 Bug Zapper 2011-06-02 10:13:57 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Bug Zapper 2011-06-27 18:36:19 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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