totem crashed with SIGSEGV in g_type_module_use()

[Fábio Carlos]

Binary package hint: totem

xxx

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Sun Oct 11 15:42:42 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/totem
NonfreeKernelModules: nvidia
Package: totem 2.28.1-0ubuntu1
ProcCmdline: totem /home/fabio/Vídeos/FILMES/Pres.By.Rodrigobs.www.baixarfilmesdublados.net.rmvb
ProcEnviron:
 LANGUAGE=pt_BR.UTF-8
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-13.44-generic
Signal: 11
SourcePackage: totem
StacktraceTop:
 ?? ()
 g_type_module_use ()
 totem_plugins_engine_activate_plugin ()
 ?? ()
 ?? ()
Title: totem crashed with SIGSEGV in g_type_module_use()
Uname: Linux 2.6.31-13-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
SegvAnalysis:
 Segfault happened at: 0x4539b8: callq *0x160(%rax)
 PC (0x004539b8) ok
 source "*0x160(%rax)" ok
 destination "(%rsp)" (0x7fff999546b0) ok
 SP (0x7fff999546b0) ok
 Reason could not be automatically determined.
SegvReason: Reason could not be automatically determined.

[Apport retracing service (apport)]

StacktraceTop:totem_python_module_load (
g_type_module_use ()
totem_plugins_engine_activate_plugin (
totem_plugins_engine_load_dir (
totem_plugins_engine_load_dir (

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible.
This will help us to find and resolve the problem.

[Paul Hooijenga (hackedd)]

Hi, since my bug report is marked a duplicate of this, I thought I might as well just answer the questions:

This bug is reproducable by starting totem (either by opening a media file, or by running totem from the command line or 'Run Application' box). Totem will crash every time.

-- Paul

[Omer Akram (om26er)]

Thanks for the bug report and sorry for not getting back to you sooner, Could anyone please confirm if the issue is still there with Ubuntu-10.10?

[Paul Hooijenga (hackedd)]

No problem, upgrading seems to have fixed the problem though.

[Omer Akram (om26er)]

thanks for a quick reply, closing this bug but feel free to report any other bugs you may find