tracker-extract crashed with SIGSEGV in dbus_connection_dispatch()

Bug #355991 reported by ichudov
6
Affects Status Importance Assigned to Milestone
tracker (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Binary package hint: tracker

I thought I disabled this tracker in Intrepid? And here it is again, hogging my CPU and memory. I had to kill it with kill -9. What a mystery.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/tracker/tracker-extract
Package: tracker 0.6.92-1ubuntu1
ProcCmdline: /usr/lib/tracker/tracker-extract
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: tracker
StacktraceTop:
 ?? () from /usr/lib/tracker/libtracker-common.so.0
 ?? () from /usr/lib/libhal.so.1
 dbus_connection_dispatch () from /lib/libdbus-1.so.3
 ?? () from /usr/lib/libdbus-glib-1.so.2
 IA__g_main_context_dispatch (context=0x9e6f280)
Title: tracker-extract crashed with SIGSEGV in dbus_connection_dispatch()
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

Revision history for this message
ichudov (igor-chudov) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? () from /usr/lib/tracker/libtracker-common.so.0
?? () from /usr/lib/libhal.so.1
dbus_connection_dispatch (connection=0xa3de004)
message_queue_dispatch (source=0x9f63f98, callback=0,
IA__g_main_context_dispatch (context=0x9e6f280)

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in tracker (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Changed in tracker (Ubuntu):
status: New → Triaged
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.