Ubuntu
totem package

[apport] totem-video-indexer crashed with SIGSEGV in start_thread()

Bug #88701 reported by Jonah on 2007-02-28

Affects		Status	Importance	Assigned to	Milestone
	totem (Ubuntu)	Invalid	Medium	Ubuntu Desktop Bugs

Bug Description

Binary package hint: totem

not sure what happened

ProblemType: Crash
Architecture: amd64
Date: Wed Feb 28 16:49:44 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/totem-video-indexer
Package: totem-xine 2.17.92-0ubuntu1
ProcCmdline: totem-video-indexer uid:jPy1f5Oj1Eu9pYddyfEBPQ
ProcCwd: /home/jonah
ProcEnviron:
SHELL=/bin/bash
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
Signal: 11
SourcePackage: totem
StacktraceTop:
?? () from /lib64/ld-linux-x86-64.so.2
?? () from /lib64/ld-linux-x86-64.so.2
?? () from /lib64/ld-linux-x86-64.so.2
?? () from /lib64/ld-linux-x86-64.so.2
start_thread () from /lib/libpthread.so.0
Uname: Linux jonah-desktop 2.6.20-9-generic #2 SMP Sun Feb 25 22:59:06 UTC 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video

Revision history for this message

Jonah (jonah) wrote on 2007-02-28:

Dependencies.txt Edit (4.5 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (660 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (37.6 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (692 bytes, text/plain; charset="utf-8")
Registers.txt Edit (1012 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (414 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (1.8 KiB, text/plain; charset="utf-8")

Revision history for this message

Sebastien Bacher (seb128) wrote on 2007-03-05:

Thanks for your bug report. Please try to obtain a debug backtrace (http://wiki.ubuntu.com/DebuggingProgramCrash) and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in totem:
assignee:	nobody → desktop-bugs
importance:	Undecided → Medium
status:	Unconfirmed → Needs Info

Revision history for this message

Sebastien Bacher (seb128) wrote on 2007-04-16:

As described in the previous comments, your report lacks the information we need to investigate the problem further. We'll close this report for now - please reopen it if you can give us the missing information.