totem crashed with SIGSEGV in selector_active_pad_changed()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
totem (Ubuntu) |
Invalid
|
Low
|
Ubuntu Desktop Bugs |
Bug Description
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
NonfreeKernelMo
Package: totem 2.28.1-0ubuntu4
ProcCmdline: totem --enqueue file://
ProcEnviron:
SHELL=/bin/bash
LANG=en_IN
ProcVersionSign
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_
IA__g_
IA__g_
signal_
Title: totem crashed with SIGSEGV in selector_
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video
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.