GNOME Bugzilla – Bug 170261
"open DVD" causes immediate crash in gstreamer-player
Last modified: 2005-08-29 15:10:13 UTC
Distribution: Fedora Core release 3 (Heidelberg) Package: GStreamer Severity: normal Version: GNOME2.8.0 0.8.0 Gnome-Distributor: Red Hat, Inc Synopsis: "open DVD" causes immediate crash in gstreamer-player Bugzilla-Product: GStreamer Bugzilla-Component: gstreamer (core) Bugzilla-Version: 0.8.0 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: When I select "open DVD" with a DVD in the drive, gstreamer-player Steps to reproduce the crash: 1. start gstreamer-player 2. insert DVD 3. select "open DVD" in file menu Expected Results: DVD to open How often does this happen? Every time. Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gst-player' (no debugging symbols found)...Using host libthread_db library "/lib64/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 46912496436032 (LWP 3138)] [New Thread 1080043872 (LWP 3141)] [Thread debugging using libthread_db enabled] [New Thread 46912496436032 (LWP 3138)] [New Thread 1080043872 (LWP 3141)] [Thread debugging using libthread_db enabled] [New Thread 46912496436032 (LWP 3138)] [New Thread 1080043872 (LWP 3141)] [New Thread 1077942624 (LWP 3140)] [New Thread 1075841376 (LWP 3139)] 0x0000003f3c70c02a in waitpid () from /lib64/tls/libpthread.so.0
+ Trace 56829
Thread 1 (Thread 46912496436032 (LWP 3138))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-03-13 22:33 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "GStreamer". Setting to default milestone for this product, 'HEAD' Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 153227 ***