GNOME Bugzilla – Bug 170220
nautilus segfaults when opening properties on mpeg file
Last modified: 2005-06-30 15:58:24 UTC
Distribution/Version: hoary i have a specific mpeg file that when i right click -> properties nautilus quits. i don't get the "this application has unexpectedly quit" dialog. it just exits. here's what gdb says when i invoke nautilus from the console and open the properties on the file: (gdb) r [blah blah blah] ---Type <return> to continue, or q <return> to quit--- (no debugging symbols found) ** Message: don't know how to handle video/mpeg, systemstream=(boolean)false, mpegversion=(int)1 (nautilus:12311): GLib-GObject-WARNING **: invalid unclassed pointer in cast to `GstStreamInfo' (nautilus:12311): GLib-GObject-WARNING **: invalid unclassed pointer in cast to `GObject' (nautilus:12311): GLib-GObject-CRITICAL **: g_object_set: assertion `G_IS_OBJECT (object)' failed ** (nautilus:12311): WARNING **: Couldn't open file:///home/desrt/media/carwreck.mpg: There were no decoders found to handle the stream in file "file:///home/desrt/media/carwreck.mpg", you might need to install the corresponding plugins Program received signal SIGSEGV, Segmentation fault.
+ Trace 56808
Thread NaN (LWP 12324)
Thread NaN (LWP 12568)
anyway. i've uploaded the file here: http://manic.desrt.ca/carwreck.mpg it's slightly distasteful, but definitely work-safe. feel free to attach a copy to the bug report if this is going to take a long time to fix and you're afraid that the file might go missing (i wasn't sure if i should attach a 1.5meg file to a report or not). i'm using ubuntu hoary preview up to date as of now. according to this spiffy synaptic thing, that means: libgstreamer0.8-0.8.9-1ubuntu2 gstreamer0.8-[various plugins]-0.8.8-0ubuntu1 cheers.
Thanks for the bug report. 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.
This doesn't happen anymore.