Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 27035 - media-video/drip-0.9.0_rc1 sometimes crashes while encoding
Summary: media-video/drip-0.9.0_rc1 sometimes crashes while encoding
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: media-video herd
Depends on:
Reported: 2003-08-21 01:24 UTC by David
Modified: 2003-10-08 23:43 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description David 2003-08-21 01:24:26 UTC
uname -a
Linux x 2.4.20-gentoo-r1 #2 Wed May 7 11:14:07 CEST 2003 i686 Mobile Intel(R)
Pentium(R) 4 - M CPU 2.00GHz GenuineIntel GNU/Linux
On compile:
In file included from demuxer.hh:32,
                 from demuxer.cpp:21:
mpeg2_internal.h:141: 'mpeg2_fbuf_t' is used as a type, but is not defined as a 
mpeg2_internal.h:145: 'mpeg2_decoder_t' is used as a type, but is not defined 
   as a type.
mpeg2_internal.h:151: `action' was not declared in this scope
mpeg2_internal.h:151: ISO C++ forbids declaration of `mpeg2_state_t' with no 
mpeg2_internal.h:151: function `int mpeg2_state_t(mpeg2dec_s*)' is initialized 
   like a variable
make[2]: *** [libencoder_la-demuxer.lo] Error 1
make[2]: Leaving directory `/var/tmp/portage/drip-0.9.0_alpha3/work/drip/encoder'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/drip-0.9.0_alpha3/work/drip'
make: *** [all] Error 2

!!! ERROR: media-video/drip-0.9.0_alpha3 failed.
!!! Function src_compile, Line 70, Exitcode 2
!!! (no error message)

Reproducible: Always
Steps to Reproduce:
Comment 1 Martin Holzer (RETIRED) gentoo-dev 2003-10-02 04:41:40 UTC
try rc1
Comment 2 David 2003-10-02 14:10:50 UTC
drip-0.9.0_rc1 compiled ok.
Crashes on encoding, submitted bug to drip devels.
Comment 3 Patrick Kursawe (RETIRED) gentoo-dev 2003-10-08 00:56:17 UTC
David, I'm a bit confused now. Could you point me to the SF bugtracker ID
where I can read about your report and the developers' reactions?
Comment 4 David 2003-10-08 11:16:12 UTC
Sorry about the confusion. I didn't submit it through sf, but it's baically
the same as you'll find at
It's apperently a known problem, in th FAQ (
they have:
6. Xlib: unexpected async reply (sequence 0xXXXX)

-: We put a lot of effort into making Drip thread save , but there're still
some bugs. Either supply us with a detailed bug report or hope somebody else
finds it.. Try rerunning Drip.

Here's the output I get when I already have a .vob-file and choose to "Copy
MPEG" until it dies:
<init> : Avifile RELEASE-0.7.38-030918-08:44-Configured with: /var/tmp/portage/gcc-3.2.3-r1/work/gcc-3.2.3/configure
--prefix=/usr --bindir=/usr/i686-pc-linux-gnu/gcc-bin/3.2 --includedir=/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3/include
--datadir=/usr/share/gcc-data/i686-pc-linux-gnu/3.2 --mandir=/usr/share/gcc-data/i686-pc-linux-gnu/3.2/man
--infodir=/usr/share/gcc-data/i686-pc-linux-gnu/3.2/info --enable-shared
--host=i686-pc-linux-gnu --target=i686-pc-linux-gnu --with-system-zlib --enable-languages=c,c++,ada,f77,objc,java
--enable-threads=posix --enable-long-long --disable-checking --enable-cstdio=stdio
--enable-clocale=generic --enable-__cxa_atexit --enable-version-specific-runtime-libs
--with-local-prefix=/usr/local --enable-shared --enable-nls --without-included-gettext
gcc version 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r1, propolice)
<init> : Available CPU flags: fpu vme de pse tsc msr pae mce cx8 sep mtrr
pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm
<init> : 1993.74 MHz Mobile Intel(R) Pentium(R) 4 - M CPU 2.00GHz processor
<LDT keeper> : Installed fs segment: 0x4127d000
<codec keeper> : Found 12 plugins (/usr/lib/avifile-0.7,A:42,V:87)
./cache//dripcache_01_0.vob should be encoded
Xlib: unexpected async reply (sequence 0x3a4c)!
Comment 5 Patrick Kursawe (RETIRED) gentoo-dev 2003-10-08 23:43:31 UTC
Ok, so the original compiling problem is solved, and the crash is a known
upstream problem which the developers don't know how to fix. So I guess we
can't :-/
Updating summary line and closing as cantfix.