totem crashed with SIGSEGV in selector_active_pad_changed()

[Raghuram O S]

Binary package hint: totem

It actually hung. Then I closed it using force quit I think.

ProblemType: Crash
Architecture: i386
Date: Mon Nov 9 02:26:43 2009
Disassembly: 0x0: Cannot access memory at address 0x0
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/totem
NonfreeKernelModules: nvidia
Package: totem 2.28.1-0ubuntu4
ProcCmdline: totem --enqueue file:///media/22205BA1205B7B2D/music/music_from_more/10_ALAIPAYUTHE
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_IN
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: totem
StacktraceTop:
 ?? ()
 selector_active_pad_changed (selector=0x94829d0,
 IA__g_cclosure_marshal_VOID__PARAM (closure=0xb2be7be8,
 IA__g_closure_invoke (closure=0xb2be7be8, return_value=0x0,
 signal_emit_unlocked_R (node=<value optimized out>,
Title: totem crashed with SIGSEGV in selector_active_pad_changed()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

 * Is this reproducible?
 * If so, what specific steps should we take to recreate this bug?

 This will help us to find and resolve the problem.

[Raghuram O S (raghuramos1987)]

I was just watching an avi file. This is not exactly reproduceable. Happens
sometimes. On a side note totem also freezes sometimes (again randomly) and
starts continuing after skipping few frames. When it freezes I can hear my
CPU going on overdrive (basically the fan starts whenever this freeezes). It
might not be related to the sigsev. Sorry I couldnt be of more help. I will
try to record more data next time this happens.

On Tue, Nov 10, 2009 at 4:02 PM, Sebastien Bacher <email address hidden> wrote:

> Thank you for taking the time to report this bug and helping to make Ubuntu
> better. Please answer these questions:
>
> * Is this reproducible?
> * If so, what specific steps should we take to recreate this bug?
>
> This will help us to find and resolve the problem.
>
> ** Changed in: totem (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: totem (Ubuntu)
> Status: New => Incomplete
>
> ** Changed in: totem (Ubuntu)
> Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
>
> --
> totem crashed with SIGSEGV in selector_active_pad_changed()
> https://bugs.launchpad.net/bugs/480080
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Regards,
Raghuram.O.S

[Victor Vargas (kamus)]

Since this behaviour was not reproducible I will close this report for now but if you encounter that this issue is still occurring with latest release of totem included in Ubuntu Maverick please reopened again. Thanks