totem crashed with SIGSEGV in g_type_name()

Bug #816740 reported by Rodolfo Pereira
332
This bug affects 68 people
Affects Status Importance Assigned to Milestone
Totem
Fix Released
Critical
libpeas (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

I was trying to play a video file with totem

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: totem 3.0.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-7.8-generic 3.0.0
Uname: Linux 3.0.0-7-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Tue Jul 26 21:08:02 2011
ExecutablePath: /usr/bin/totem
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: totem /media/ottoStorage/Videos/Series/The\ Big\ Bang\ Theory/Season\ 04/The.Big.Bang.Theory.S04E02.The.Cruciferous.Vegetable.Amplification.HDTV.XviD-FQM.avi
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f646c8c4b55 <g_type_name+85>: mov 0x28(%rax),%edi
 PC (0x7f646c8c4b55) ok
 source "0x28(%rax)" (0x6f1d7328) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: totem
StacktraceTop:
 g_type_name () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_typelib_get_dir_entry_by_gtype () from /usr/lib/libgirepository-1.0.so.1
 ?? () from /usr/lib/libgirepository-1.0.so.1
 g_hash_table_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_irepository_find_by_gtype () from /usr/lib/libgirepository-1.0.so.1
Title: totem crashed with SIGSEGV in g_type_name()
UpgradeStatus: Upgraded to oneiric on 2011-07-26 (0 days ago)
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

Revision history for this message
Rodolfo Pereira (phinpho) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_name (type=<value optimized out>) at /build/buildd/glib2.0-2.29.14/./gobject/gtype.c:3287
 g_typelib_get_dir_entry_by_gtype (typelib=0x7f646f191f20, fastpass=1, gtype=<value optimized out>) at girepository/gitypelib.c:206
 find_by_gtype_foreach (key=<value optimized out>, value=0x7f646f191f20, datap=0x7fff8027a410) at girepository/girepository.c:576
 find_by_gtype_foreach (key=<value optimized out>, value=0x7f646f191f20, datap=0x7fff8027a410) at girepository/girepository.c:566
 g_hash_table_foreach (hash_table=0x7f646f1f6c00, func=0x7f646ab1f1d0 <find_by_gtype_foreach>, user_data=0x7fff8027a410) at /build/buildd/glib2.0-2.29.14/./glib/ghash.c:1420

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
Changed in totem (Ubuntu):
status: New → Confirmed
visibility: private → public
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:
https://bugzilla.gnome.org/show_bug.cgi?id=655751

Changed in totem (Ubuntu):
status: Confirmed → Triaged
Changed in totem:
importance: Unknown → Critical
status: Unknown → New
Changed in totem:
status: New → Incomplete
Revision history for this message
Lukasz Olszewski (olszewskil) wrote :

Totem 3.1.x should be tested and made available in Oneiric (see https://bugzilla.gnome.org/show_bug.cgi?id=655751)

Revision history for this message
Nipas (nik8pol) wrote :

Totem window closes a moment after running the application. Is this the same bug? (Ubuntu 11.10 amd64 updates till now installed)

Revision history for this message
Rafał Cieślak (rafalcieslak256) wrote :

Maybe. That's the symptom I see.

Revision history for this message
Shyam (reddy-shyam) wrote :

Nipas, I think the same. Its been the case for almost over a week now my end.

Sam_ (and-sam)
tags: added: regression-release
Revision history for this message
Steve Langasek (vorlon) wrote :

This is a bug in libpeas 1.1.1, which is handling pointers in an incorrect (and 64-bit unsafe) manner.

I've just uploaded libpeas 1.1.1-0ubuntu2 to oneiric, fixing this bug.

affects: totem (Ubuntu) → libpeas (Ubuntu)
Changed in libpeas (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Rafał Cieślak (rafalcieslak256) wrote :

I confirm this is fixed.

Revision history for this message
Shyam (reddy-shyam) wrote :

I confirm this is fixed.

Revision history for this message
gireesh kumar k m (gireesh) wrote :

I confirm this is fixed.

Revision history for this message
Sam_ (and-sam) wrote :

Possibly dup Bug #824009

Changed in totem:
status: Incomplete → Fix Released
manzur (sl-solaris)
description: updated
Revision history for this message
Claudiu Vlad (claudiu-vlad) wrote :

How comes that I have libpeas-1.0-0 in my system, today, October 17th?

I cant understand that. I am updating 3 times a day since 01.10.2011.
An totem is still broken

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.