totem crashed with SIGSEGV in g_type_check_is_value_type()

Bug #565923 reported by IKT
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
totem (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: totem

Was playing a stream, then after I loaded another radio stream from an m3u file it crashed.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: totem 2.30.0git20100413-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CrashCounter: 1
Date: Sun Apr 18 22:04:34 2010
ExecutablePath: /usr/bin/totem
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
ProcCmdline: totem /home/username/Downloads/102.m3u
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f3e4efbc9b0: mov (%rdx),%edi
 PC (0x7f3e4efbc9b0) ok
 source "(%rdx)" (0x125ae3f0) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: totem
StacktraceTop:
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_type_check_is_value_type ()
 g_value_type_compatible ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist ()
Title: totem crashed with SIGSEGV in g_type_check_is_value_type()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
IKT (ikt) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_type_check_is_value_type ()
 g_value_type_compatible ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in totem (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you taking the time to report this bug and helping to make Ubuntu better. However, processing the crash report to get detailed information for the developers failed as the retracer did not generate a useful symbolic stack trace.
Please try to obtain a backtrace manually following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in totem (Ubuntu):
status: New → Incomplete
Revision history for this message
IKT (ikt) wrote :

It's not possible to run a backtrace because this isn't an easily reproducible problem, I open and close m3u files all the time now and it hasn't occurred since.

Revision history for this message
IKT (ikt) wrote :

I'll just set to invalid, if anyone else gets this bug more frequently here's the place to run a backtrace :)

Changed in totem (Ubuntu):
status: Incomplete → Invalid
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.