tracker-extract crashed with SIGSEGV

Bug #146316 reported by CC
68
Affects Status Importance Assigned to Milestone
bluez-utils (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: tracker

entire system became unstable and frozen for a minute, then the program crash occurred (so many programs crashed at once, i don't know which report this is but "tracker" was autochosen for me)

ProblemType: Crash
Architecture: i386
Date: Fri Sep 21 16:49:10 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/tracker-extract
NonfreeKernelModules: ath_hal cdrom
Package: tracker 0.6.2-2ubuntu2
PackageArchitecture: i386
ProcCmdline: tracker-extract /home/fallendarling/Vacancy[2007]DvDrip.AC3[Eng]-aXXo/Vacancy[2007]DvDrip.AC3[Eng]-aXXo/Vacancy[2007]DvDrip.AC3[Eng]-aXXo.avi video/x-msvideo
ProcCwd: /home/fallendarling
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: tracker
Stacktrace:
 #0 0xb71d076a in ?? () from /usr/lib/gstreamer-0.10/libgstbluetooth.so
 #1 0xbff5462c in ?? ()
 #2 0x00000000 in ?? ()
StacktraceTop:
 ?? () from /usr/lib/gstreamer-0.10/libgstbluetooth.so
 ?? ()
 ?? ()
ThreadStacktrace:
 .
 Thread 1 (process 8047):
 #0 0xb71d076a in ?? () from /usr/lib/gstreamer-0.10/libgstbluetooth.so
 #1 0xbff5462c in ?? ()
 #2 0x00000000 in ?? ()
Title: tracker-extract crashed with SIGSEGV
Uname: Linux cc-new-laptop 2.6.22-11-generic #1 SMP Mon Sep 17 03:45:58 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Tags: apport-crash
Revision history for this message
CC (fallendarling) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace 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 tracker:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in bluez-utils:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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