Bug 316341 – gstreamer0.8-ffmpeg 0.8.6-0 makes totem lock hard when watching dvd

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 316341 - gstreamer0.8-ffmpeg 0.8.6-0 makes totem lock hard when watching dvd


Summary:	gstreamer0.8-ffmpeg 0.8.6-0 makes totem lock hard when watching dvd


Status:	RESOLVED WONTFIX

Product:	GStreamer
Classification:	Platform
Component:	gst-libav
Version:	0.8.6
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	git master
Assigned To:	GStreamer Maintainers
QA Contact:	GStreamer Maintainers

URL:
Whiteboard:

Duplicates:	320492 321317 322512 324363 326216 327139 331488 334147 341540 (view as bug list)
Depends on:
Blocks:

Reported:	2005-09-14 21:10 UTC by surak
Modified:	2006-07-10 16:54 UTC

See Also:
GNOME target:	---
GNOME version:	2.11/2.12

Description surak 2005-09-14 21:10:52 UTC

Distribution/Version: ubuntu breezy daily-live from sept 14

Open totem
tell it to open any dvd
it will lock almost immediately

Running it with gdb says:
Program received signal SIGFPE, Arithmetic exception.
[Switching to Thread -1231230032 (LWP 20650)]
0xb665cd07 in gst_ffmpegdeinterlace_register () from
/usr/lib/gstreamer-0.8/libgstffmpeg.so

in gdb prompt, a thread apply all bt will say:

+ Trace 63015

Thread 3 (Thread -1231291472 (LWP 21477))

#0 gst_ffmpegdeinterlace_register
from /usr/lib/gstreamer-0.8/libgstffmpeg.so
#1 gst_ffmpegdeinterlace_register
from /usr/lib/gstreamer-0.8/libgstffmpeg.so
#2 gst_ffmpegdeinterlace_register
from /usr/lib/gstreamer-0.8/libgstffmpeg.so
#3 gst_ffmpeg_img_convert
from /usr/lib/gstreamer-0.8/libgstffmpeg.so
#4 gst_pad_call_chain_function
from /usr/lib/libgstreamer-0.8.so.1
#5 gst_pad_push
from /usr/lib/libgstreamer-0.8.so.1
#6 gst_mpeg_demux_get_type
from /usr/lib/gstreamer-0.8/libgstmpegstream.so
#7 gst_dvd_demux_get_type
from /usr/lib/gstreamer-0.8/libgstmpegstream.so
#8 gst_mpeg_demux_get_type
from /usr/lib/gstreamer-0.8/libgstmpegstream.so
#9 gst_mpeg_parse_get_type
from /usr/lib/gstreamer-0.8/libgstmpegstream.so
#10 ??
from /usr/lib/gstreamer-0.8/libgstoptscheduler.so
#11 ??
#12 ??
#13 ??
from /usr/lib/gstreamer-0.8/libgstoptscheduler.so
#14 ??
from /usr/lib/gstreamer-0.8/libgstoptscheduler.so
#15 ??
#16 ??
#17 ??
from /usr/lib/gstreamer-0.8/libgstoptscheduler.so
#18 ??
#19 ??
#20 ??
#21 ??
#22 ??
from /usr/lib/gstreamer-0.8/libgstoptscheduler.so
#23 ??
#24 ??
#25 ??
#26 ??
from /usr/lib/gstreamer-0.8/libgstoptscheduler.so
#27 ??
#28 ??
#29 ??
from /usr/lib/gstreamer-0.8/libgstoptscheduler.so
#30 ??
from /usr/lib/gstreamer-0.8/libgstoptscheduler.so
#31 ??
#32 ??
#33 ??
from /usr/lib/gstreamer-0.8/libgstoptscheduler.so
#34 ??
#35 ??
#36 ??
#37 ??
from /usr/lib/gstreamer-0.8/libgstoptscheduler.so
#38 _gst_registry_auto_load
from /usr/lib/libgstreamer-0.8.so.1
#39 ??
from /usr/lib/gstreamer-0.8/libgstoptscheduler.so
#40 ??
from /usr/lib/gstreamer-0.8/libgstoptscheduler.so
#41 ??
#42 ??
#43 ??
#44 ??
#45 ??
#46 ??
from /usr/lib/gstreamer-0.8/libgstoptscheduler.so
#47 ??
#48 _gst_registry_auto_load
from /usr/lib/libgstreamer-0.8.so.1
#49 ??
#50 ??
from /usr/lib/gstreamer-0.8/libgstoptscheduler.so
#51 ??
#52 ??
#53 ??
from /usr/lib/gstreamer-0.8/libgstoptscheduler.so
#54 ??
from /usr/lib/gstreamer-0.8/libgstoptscheduler.so
#55 ??
#56 ??
#57 ??
from /usr/lib/gstreamer-0.8/libgstoptscheduler.so
#58 ??
#59 ??
#60 pthread_mutex_lock
from /lib/tls/i686/cmov/libpthread.so.0

Comment 1 surak 2005-09-14 21:19:29 UTC

Oh, I forgot to mention. This does not happen with gstreamer-0.8.4. downgrading
to it will make it work.

Comment 2 Luca Ognibene 2005-09-19 19:25:14 UTC

Wich cpu do you have? Are you using packages or have you comiled from sources?
Are you using "strange" CFLAGS?

Comment 3 surak 2005-09-19 19:34:48 UTC

I tested it with ubuntu breezy live on the following machines:

- pentium 4
- celeron d
- amd sempron
- amd64 (using i386 build)

All seems to suffer the same effects. The stack trace is from a Intel(R)
Pentium(R) 4 CPU 2.00GHz, cpu family 15, model 2, stepping 9.

These are standard ubuntu breezy packages.

Comment 4 Luca Ognibene 2005-09-24 10:30:05 UTC

Are you able to reproduce also in a installed ubuntu breezy? Or only with the
live cd?

Comment 5 surak 2005-09-27 17:01:03 UTC

Luca, I did not test it on installed one.

Comment 6 Ronald Bultje 2005-10-19 15:39:08 UTC

Please try to reproduce with debug symbols, the backtrace is unfortunately not
very useful. Thanks.

Comment 7 surak 2005-10-31 21:17:06 UTC

how can I do this?

Comment 8 Ronald Bultje 2005-10-31 23:03:09 UTC

Seb, can you help him with obtaining debug packages?

Comment 9 Christian Kirbach 2005-11-17 09:36:02 UTC

*** Bug 321317 has been marked as a duplicate of this bug. ***

Comment 10 Christian Kirbach 2005-11-17 09:37:09 UTC

*** Bug 320492 has been marked as a duplicate of this bug. ***

Comment 11 Christian Kirbach 2005-11-17 09:40:09 UTC

Thanks for the bug report. Unfortunately, that stack trace is not very useful in 
determining the cause of the crash. Can anyone of you get us one with debugging 
symbols? Please see http://live.gnome.org/GettingTraces for more information on 
how to do so.

Comment 12 Christian Kirbach 2005-12-17 03:52:04 UTC

Knock knock ... is the problem still there with a newer version?

Comment 13 Martin Wehner 2005-12-18 02:31:34 UTC

*** Bug 324363 has been marked as a duplicate of this bug. ***

Comment 14 Elijah Newren 2005-12-23 01:29:07 UTC

*** Bug 322512 has been marked as a duplicate of this bug. ***

Comment 15 Sebastien Bacher 2006-01-08 18:14:23 UTC

*** Bug 326216 has been marked as a duplicate of this bug. ***

Comment 16 James "Doc" Livingston 2006-01-16 01:18:13 UTC

*** Bug 327139 has been marked as a duplicate of this bug. ***

Comment 17 Karsten Bräckelmann 2006-02-17 02:21:02 UTC

*** Bug 331488 has been marked as a duplicate of this bug. ***

Comment 18 Sergej Kotliar 2006-03-10 19:17:57 UTC

*** Bug 334147 has been marked as a duplicate of this bug. ***

Comment 19 Christian Kirbach 2006-03-17 10:38:28 UTC

Thanks for the bug report. Unfortunately, that stack trace is not very useful
in 
determining the cause of the crash. Can anyone of you get us one with debugging 
symbols? Please see http://live.gnome.org/GettingTraces for more information on 
how to do so.

Comment 20 surak 2006-03-19 17:01:22 UTC

I will try to. And I will try to see if newer versions still have the issue.

Comment 21 Jan Schmidt 2006-05-06 19:51:04 UTC

Ping? Any change on this? Can we close the bug?

Comment 22 Karsten Bräckelmann 2006-05-12 20:59:31 UTC

*** Bug 341540 has been marked as a duplicate of this bug. ***

Comment 23 Wim Taymans 2006-07-10 16:54:03 UTC

closing, version is really too old now.