GNOME Bugzilla – Bug 160764
a bug occured when I want to test Gstreamer properties, and ask me to re-run the application
Last modified: 2005-01-15 16:00:22 UTC
Distribution: Debian testing/unstable Package: GStreamer Severity: normal Version: GNOME2.8.1 2.8.0 Gnome-Distributor: Ubuntu Synopsis: a bug occured when I want to test Gstreamer properties, and ask me to re-run the application Bugzilla-Product: GStreamer Bugzilla-Component: don't know Bugzilla-Version: 2.8.0 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: in a bash : gstreamer-properties Steps to reproduce the crash: 1. in audio with out transform anything, 2. in sink, just try test 3. then it crash and ask if I want to start it again... Expected Results: I don't know by the way How often does this happen? always Additional Information: Thank's for all your work Debugging Information: Backtrace was generated from '/usr/bin/gstreamer-properties' (no debugging symbols found)...Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 1088427584 (LWP 17038)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0xffffe410 in __kernel_vsyscall ()
+ Trace 53287
Thread 1 (Thread 1088427584 (LWP 17038))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-12-08 08:14 ------- Unknown version 2.8.0 in product GStreamer. Setting version to "0.3.3". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "GStreamer". Setting to default milestone for this product, 'HEAD' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was bruno.berthelet@hasgard.net. 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 matches the stack trace in bug 148456, which was closed for lack of information--unfortunately, that stack trace is not very useful in determining the cause of the crash. Please make sure that the package was compiled with debugging symbols and see http://bugzilla.gnome.org/getting-traces.cgi for more information about useful stack traces.
if it is alsasink that crashed, please see bug #159210
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 146399 ***