Ubuntu
totem package

totem crashed with SIGSEGV

Bug #758472 reported by shuddhasattwa on 2011-04-12

10

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	totem (Ubuntu)	Expired	Medium	Unassigned

Bug Description

Binary package hint: totem

It is crap

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: totem 2.32.0-0ubuntu10
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelModules: wl
Architecture: i386
Date: Tue Apr 12 12:27:01 2011
Disassembly: => 0x91e8ff1: Cannot access memory at address 0x91e8ff1
ExecutablePath: /usr/bin/totem
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: totem /home/username/Desktop/Python\ Workshop-1A.avi
ProcEnviron:
LANGUAGE=en_IN:en
LANG=en_IN
LC_MESSAGES=en_IN.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x91e8ff1: Cannot access memory at address 0x91e8ff1
PC (0x091e8ff1) ok
Stack memory exhausted (SP below stack segment)
SP (0xa7b6d2f0) ok
Reason could not be automatically determined.
Signal: 11
SourcePackage: totem
Stacktrace:
#0 0x091e8ff1 in ?? ()
No symbol table info available.
Cannot access memory at address 0xa7b6d2f0
StacktraceTop: ?? ()
Title: totem crashed with SIGSEGV
UpgradeStatus: Upgraded to natty on 2011-04-10 (2 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

shuddhasattwa (paulshuddhasattwa) wrote on 2011-04-12:

#1

Dependencies.txt Edit (5.8 KiB, text/plain; charset="utf-8")
GstreamerVersions.txt Edit (2.0 KiB, text/plain; charset="utf-8")
LogAlsaMixer.txt Edit (3.4 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (57.5 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (776 bytes, text/plain; charset="utf-8")
Registers.txt Edit (490 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (1.3 KiB, text/plain; charset="utf-8")
XorgLog.gz Edit (6.4 KiB, application/x-gzip)
XsessionErrors.txt Edit (1.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2011-04-12:

#2

Stacktrace:
#0 0x091e8ff1 in ?? ()
No symbol table info available.
Cannot access memory at address 0xa7b6d2f0
StacktraceTop: ?? ()

Revision history for this message

Apport retracing service (apport) wrote on 2011-04-12: ThreadStacktrace.txt

#3

ThreadStacktrace.txt Edit (1.3 KiB, text/plain)

tags:	added: apport-failed-retrace
tags:	removed: need-i386-retrace

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2011-04-12:

#4

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):
importance:	Undecided → Medium
status:	New → Incomplete
visibility:	private → public

Revision history for this message

Omer Akram (om26er) wrote on 2011-06-04:

#5

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message

Launchpad Janitor (janitor) wrote on 2011-08-04:

#7

[Expired for totem (Ubuntu) because there has been no activity for 60 days.]

Changed in totem (Ubuntu):
status:	Incomplete → Expired

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.