tracker-extract crashed with SIGSEGV in gst_type_find_factory_call_function()

Bug #144197 reported by Per Christian Henden
6
Affects Status Importance Assigned to Milestone
tracker (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: tracker

I do not know why this happened. I was not actively doing anything on my system, just playing music with amarok while leaving my computer alone. I hope the crash-dump will show what the problem is.

ProblemType: Crash
Architecture: amd64
Date: Sun Sep 23 11:25:08 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/tracker-extract
NonfreeKernelModules: ath_hal nvidia
Package: tracker 0.6.2-2ubuntu2
PackageArchitecture: amd64
ProcCmdline: tracker-extract /home/perchrh/musikk/Sun.Yan-zi.-.Hai.Pa.mp3 audio/mpeg
ProcCwd: /home/perchrh
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
StacktraceTop:
 ?? ()
 gst_type_find_factory_call_function ()
 gst_type_find_helper_get_range ()
 ?? ()
 gst_pad_set_active ()
Title: tracker-extract crashed with SIGSEGV in gst_type_find_factory_call_function()
Uname: Linux perchrh-desktop 2.6.22-12-generic #1 SMP Sat Sep 22 17:45:57 GMT 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Tags: apport-crash
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:gst_type_find_factory_call_function (factory=0x6bc1c0, find=0x7ffff41f8140)
gst_type_find_helper_get_range (obj=0x75b000, func=<value optimized out>,
gst_type_find_element_activate (pad=0x74f5c0) at gsttypefindelement.c:719
gst_pad_set_active (pad=0x74f5c0, active=1) at gstpad.c:648
activate_pads (pad=0x74f458, ret=0x7ffff41f8310, active=0x3) at gstelement.c:2486

Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in tracker:
importance: Undecided → Medium
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.