totem crashed with SIGSEGV in g_datalist_id_set_data_full()

[Daniel Holbach]

No idea what happened.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: totem 3.6.3-0ubuntu2
ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7
Uname: Linux 3.8.0-6-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
CheckboxSubmission: 2f383a1679e8525d7196eb2518a1921f
CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
Date: Fri Feb 15 18:22:43 2013
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2011-08-19 (546 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110817)
MarkForUpload: True
ProcCmdline: totem /home/username/Desktop/Boogie\ Belgique\ -\ Forever\ &\ ever-62943733.mp3 /home/username/Desktop/Poirier\ (feat\ Natalie\ Storm)\ -\ Gal\ U\ Good\ (BERT\ ON\ BEATS\ Remix)-77926193.mp3 /home/username/Desktop/JORGE\ BEN\ -\ A\ Jovem\ Samba\ (Klasick\ rmx)-56555259.mp3 /home/username/Desktop/file0199.mp3 /home/username/Desktop/DUBBWEBB\ -LIL\ JON\ SOUL.mp3
SegvAnalysis:
 Segfault happened at: 0x7f2c19226d43 <g_datalist_id_set_data_full+483>: mov (%rcx),%edi
 PC (0x7f2c19226d43) ok
 source "(%rcx)" (0xaaaaaaaaaaaaaaa8) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: totem
StacktraceTop:
 g_datalist_id_set_data_full () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/totem/plugins/chapters/libchapters.so
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: totem crashed with SIGSEGV in g_datalist_id_set_data_full()
UpgradeStatus: Upgraded to raring on 2013-01-17 (29 days ago)
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare utah

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1100937, 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.