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 115925 - All GStreamer applications crash
All GStreamer applications crash
Status: RESOLVED NOTABUG
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
0.3.3
Other other
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-06-25 12:02 UTC by Rodrigo Moya
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Rodrigo Moya 2003-06-25 12:07:43 UTC
Package: GStreamer
Severity: major
Version: 0.6.2
Synopsis: All GStreamer applications crash
Bugzilla-Product: GStreamer
Bugzilla-Component: gstreamer (core)
BugBuddy-GnomeVersion: 2.0 (2.2.1)

Description:
Description of Problem:


Steps to reproduce the problem:
1. Start a Gstreamer app (gnome-sound-recorder, rhythmbox)

Actual Results:
Crash on gst_ functions

Expected Results:
Working app

How often does this happen?
For all GStreamer applications, since I last upgraded my debian sid
GStreamer packages.

Additional Information:




Debugging Information:

Backtrace was generated from '/usr/bin/gnome-sound-recorder'

(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)...[New Thread 16384 (LWP 29447)]
(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)...0x40953af9 in wait4 () from
/lib/libc.so.6

Thread 1 (Thread 16384 (LWP 29447))

  • #0 wait4
    from /lib/libc.so.6
  • #1 sys_sigabbrev
    from /lib/libc.so.6
  • #2 ??
  • #3 waitpid
    from /lib/libc.so.6
  • #4 waitpid
    from /lib/libpthread.so.0
  • #5 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #6 __pthread_sighandler
    from /lib/libpthread.so.0
  • #7 <signal handler called>
  • #8 kill
    from /lib/libc.so.6
  • #9 pthread_kill
    from /lib/libpthread.so.0
  • #10 raise
    from /lib/libpthread.so.0
  • #11 abort
    from /lib/libc.so.6
  • #12 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #13 g_log
    from /usr/lib/libglib-2.0.so.0
  • #14 gst_scheduler_factory_make
    from /usr/lib/libgstreamer-0.6.so.0
  • #15 gst_pipeline_get_type
    from /usr/lib/libgstreamer-0.6.so.0
  • #16 g_type_create_instance
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #21 gst_element_factory_create
    from /usr/lib/libgstreamer-0.6.so.0
  • #22 gst_element_factory_make
    from /usr/lib/libgstreamer-0.6.so.0
  • #23 gst_pipeline_new
    from /usr/lib/libgstreamer-0.6.so.0
  • #24 gsr_window_close
  • #25 gsr_window_close
  • #26 g_type_create_instance
    from /usr/lib/libgobject-2.0.so.0
  • #27 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #28 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #29 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #30 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #31 gsr_window_new
  • #32 gsr_open_window
  • #33 main
  • #34 __libc_start_main
    from /lib/libc.so.6
  • #35 _start
  • #0 wait4
    from /lib/libc.so.6




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-06-25 08:07 -------

Unknown version unspecified in product GStreamer. Setting version to "0.3.3".
Reassigning to the default owner of the component, gstreamer-maint@bugzilla.gnome.org.

Comment 1 Ronald Bultje 2003-06-25 12:12:12 UTC
Please compile with debugging symbols. I guess you forgot to run
gst-register or so. Also see information in your console while
starting the app.
Comment 2 Benjamin Otte (Company) 2003-06-25 14:37:54 UTC
Nonetheless should GSTreamer handle the "no scheduler" situation 
gracefully and _not_ by segfaulting.

Once again a stupid use of g_error.
Comment 3 Ronald Bultje 2003-06-25 15:01:57 UTC
It wouldn't help, people would complain that their GStreamer app
doesn't start and doesn't give an (user-visible) error either...
Comment 4 Rodrigo Moya 2003-06-25 15:12:51 UTC
Right, running gst-register-0.6 fixed it. I guess the debian package
should call that at installation time?
Comment 5 Thomas Vander Stichele 2004-02-24 13:14:19 UTC
yep, it should.