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 146399 - gstreamer-properties crash
gstreamer-properties crash
Status: RESOLVED DUPLICATE of bug 146082
Product: general
Classification: Other
Component: general
unspecified
Other other
: Normal critical
: ---
Assigned To: Unknown User
Unknown User
: 160209 160764 163291 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-06-07 07:32 UTC by izico
Modified: 2005-01-15 16:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6



Description izico 2004-07-09 04:21:22 UTC
Distribution: Fedora Core release 2 (Tettnang)
Package: GStreamer
Severity: critical
Version: GNOME2.6. 2.6.0
Gnome-Distributor: Red Hat, Inc
Synopsis: gstreamer-properties crash
Bugzilla-Product: GStreamer
Bugzilla-Component: gstreamer (core)
Bugzilla-Version: 2.6.0
BugBuddy-GnomeVersion: 2.0 (2.6.0)
Description:
Description of the crash:


Steps to reproduce the crash:
1. 
2. 
3. 

Expected Results:


How often does this happen?


Additional Information:



Debugging Information:

Backtrace was generated from '/usr/bin/gstreamer-properties'

(no debugging symbols found)...Using host libthread_db library
"/lib/tls/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)...[Thread debugging using libthread_db enabled]
[New Thread -150327168 (LWP 7272)]
(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)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...0x00212402 in ?? ()

Thread 1 (Thread -150327168 (LWP 7272))

  • #0 ??
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
  • #5 raise
    from /lib/tls/libc.so.6
  • #6 abort
    from /lib/tls/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 gst_scheduler_factory_make
    from /usr/lib/libgstreamer-0.8.so.1
  • #10 gst_thread_get_type
    from /usr/lib/libgstreamer-0.8.so.1
  • #11 g_type_create_instance
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #13 gst_object_get_type
    from /usr/lib/libgstreamer-0.8.so.1
  • #14 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #17 gst_element_factory_create
    from /usr/lib/libgstreamer-0.8.so.1
  • #18 gst_element_factory_make
    from /usr/lib/libgstreamer-0.8.so.1
  • #19 _gst_parse__yyparse
    from /usr/lib/libgstreamer-0.8.so.1
  • #20 ??
  • #0 ??




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-09 00:21 -------


Unknown version 2.6.0 in product general. Setting version to "unspecified".
Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "general".
   Setting to default milestone for this product, '---'
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 izico@21cn.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.

Comment 1 Elijah Newren 2004-07-17 17:35:57 UTC
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 146082 ***
Comment 2 Vincent Noel 2004-12-03 18:26:11 UTC
*** Bug 160209 has been marked as a duplicate of this bug. ***
Comment 3 Sebastien Bacher 2005-01-15 15:58:57 UTC
*** Bug 163291 has been marked as a duplicate of this bug. ***
Comment 4 Sebastien Bacher 2005-01-15 16:00:24 UTC
*** Bug 160764 has been marked as a duplicate of this bug. ***