I was playing an mp3 from download.khinsider.com in firefox and refreshed the page. Totem crashed suddenly and the page froze.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libgstreamer0.10-0 0.10.35-1
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Tue Sep 20 19:14:54 2011
ExecutablePath: /usr/lib/totem/totem-plugin-viewer
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110824)
ProcCmdline: /usr/lib/totem/totem-plugin-viewer --plugin-type cone --user-agent Mozilla/5.0\ (X11;\ Linux\ x86_64;\ rv:9.0a1)\ Gecko/20110920\ Firefox/9.0a1 --referrer http://66.90.118.45/soundtracks/spyro-3-psx-rip-/fnjrwtpnwc/01.mp3 --mimetype audio/mpeg
SegvAnalysis:
Segfault happened at: 0x7fb3bff4578b <g_object_set+107>: cmpq $0x50,(%rax)
PC (0x7fb3bff4578b) ok
source "$0x50" ok
destination "(%rax)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed writable region)!
Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gstreamer0.10
StacktraceTop:
g_object_set () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
gst_play_sink_reconfigure (playsink=0x7fb3c50dc130) at gstplaysink.c:2603
no_more_pads_cb (decodebin=0x7fb3c521c0d0, group=0x7fb3c50da1a0) at gstplaybin2.c:2791
g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: totem-plugin-viewer crashed with SIGSEGV in g_object_set()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #844509, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.