totem crashed with SIGSEGV in g_object_set()

Bug #888566 reported by Colan Schwartz
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gstreamer0.10 (Ubuntu)
New
Undecided
Unassigned

Bug Description

I was trying to play a WAV file downloaded from a Thunderbird e-mail attachment. Open with -> /usr/bin/totem

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libgstreamer0.10-0 0.10.35-1
ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
Uname: Linux 3.0.0-13-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Wed Nov 9 22:00:48 2011
ExecutablePath: /usr/bin/totem
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
ProcCmdline: /usr/bin/totem /tmp/msg0002.wav
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/zsh
SegvAnalysis:
 Segfault happened at: 0x7f3c54553fdb <g_object_set+107>: cmpq $0x50,(%rax)
 PC (0x7f3c54553fdb) ok
 source "$0x50" ok
 destination "(%rax)" (0x6641414141594143) not located in a known VMA region (needed writable region)!
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
 ?? () from /usr/lib/gstreamer-0.10/libgstplaybin.so
 ?? () from /usr/lib/gstreamer-0.10/libgstplaybin.so
 g_object_set_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_set () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: totem crashed with SIGSEGV in g_object_set()
UpgradeStatus: Upgraded to oneiric on 2011-10-02 (38 days ago)
UserGroups: adm admin cdrom dialout dip fax floppy fuse logcheck lp lpadmin mail netdev plugdev powerdev sambashare tape vboxusers video

Revision history for this message
Colan Schwartz (colan) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #830790, 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.

tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.