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 128370 - nautilus crash in gstreamer
nautilus crash in gstreamer
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
0.6.3
Other Linux
: High critical
: 0.3.3
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-12-02 16:21 UTC by david.hawthorne
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description david.hawthorne 2003-12-02 16:21:15 UTC
using a gnome-2.5 build from 02 Dec 2003.

I'm unsure if this is accessibility related or not, feel free to remove
keyword if not.

steps leading to crash:

- launched gnopernicus with speech and braille
- launched nautilus
- pressed <tab> once
- nautilus crashed with a fatal error

the following is the gdb stack trace at point of crash


  • #0 wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 waitpid
    from /lib/i686/libpthread.so.0
  • #3 libgnomeui_segv_handle
    at gnome-ui-init.c line 738
  • #4 pthread_sighandler
    from /lib/i686/libpthread.so.0
  • #5 <signal handler called>
  • #6 g_logv
    at gmessages.c line 518
  • #7 g_log
    at gmessages.c line 541
  • #8 gst_scheduler_factory_make
    at gstscheduler.c line 944
  • #9 gst_pipeline_init
    at gstpipeline.c line 115
  • #10 g_type_create_instance
    at gtype.c line 1595
  • #11 g_object_constructor
    at gobject.c line 1044
  • #12 gst_object_constructor
    at gstobject.c line 190
  • #13 g_object_newv
    at gobject.c line 941
  • #14 g_object_new_valist
    at gobject.c line 984
  • #15 g_object_new
    at gobject.c line 822
  • #16 gst_element_factory_create
    at gstelementfactory.c line 280
  • #17 gst_element_factory_make
    at gstelementfactory.c line 319
  • #18 gst_gdk_animation_iter_create_pipeline
    at gstgdkanimation.c line 255
  • #19 gst_gdk_animation_get_iter
    at gstgdkanimation.c line 415
  • #20 gdk_pixbuf_animation_get_iter
    at gdk-pixbuf-animation.c line 408
  • #21 gst_loader_load_animation
    at gst_loader.c line 166
  • #22 gst_loader_load
    at gst_loader.c line 188
  • #23 _gdk_pixbuf_generic_image_load
    at gdk-pixbuf-io.c line 654
  • #24 gdk_pixbuf_new_from_file
    at gdk-pixbuf-io.c line 761
  • #25 gnome_gdk_pixbuf_new_from_uri
    at gnome-vfs-util.c line 100
  • #26 gnome_thumbnail_factory_generate_thumbnail
    at gnome-thumbnail.c line 909
  • #27 thumbnail_thread_start
    at nautilus-thumbnails.c line 565
  • #28 pthread_start_thread
    from /lib/i686/libpthread.so.0


The following lines continously scroll in between the above stack trace lines:

BFD: BFD 2.13.90 20020903 assertion fail libbfd.c:1132
BFD: BFD 2.13.90 20020903 assertion fail libbfd.c:1132
BFD: BFD 2.13.90 20020903 assertion fail libbfd.c:1132
BFD: BFD 2.13.90 20020903 assertion fail libbfd.c:1132
BFD: BFD 2.13.90 20020903 assertion fail libbfd.c:1132
BFD: BFD 2.13.90 20020903 assertion fail libbfd.c:1132

.....
Comment 1 padraig.obriain 2003-12-02 16:24:25 UTC
Does the crash occur if accessibility is not enabled?
Comment 2 david.hawthorne 2003-12-02 16:26:31 UTC
update:

This is reproducible with the same steps on my machine.
Comment 3 david.hawthorne 2003-12-02 16:46:34 UTC
The cause of the problem seems to be the .avi file.
Comment 4 Elijah Newren 2003-12-08 05:11:41 UTC
FWIW, this appears to be a unique stack trace according to the
simple-dup-finder.  Setting priority->high & severity->critical (it's
a crasher), and adding bugsquad and STACKTRACE keywords.
Comment 5 Thomas Vander Stichele 2003-12-16 13:00:17 UTC
I can't reproduce, but judging from the stacktrace, you didn't run
gst-register.

Also, this is caused by the experimental gst pixbuf loader, which I am
removing from the build today.  uninstall your gst-plugins and then
reinstall them after update.  So it shouldn't happen again.