strigidaemon crashed with SIGSEGV in _start()

Bug #151125 reported by jeroenl
16
Affects Status Importance Assigned to Milestone
strigi (Ubuntu)
Expired
Medium
Unassigned

Bug Description

strigidaemon crashed during KDE-start.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Tue Oct 9 18:13:44 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/strigidaemon
NonfreeKernelModules: video
Package: strigi-daemon 0.5.6-0ubuntu1
PackageArchitecture: i386
ProcCmdline: strigidaemon clucene
ProcCwd: /home/jeroen
ProcEnviron:
 PATH=/home/jeroen/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: strigi
Stacktrace: #0 0x0804ec90 in _start ()
StacktraceTop: _start ()
Title: strigidaemon crashed with SIGSEGV in _start()
Uname: Linux k-uptown 2.6.22-14-generic #1 SMP Tue Oct 9 09:51:52 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video
SegvAnalysis:
 Segfault happened at: 0x804ec90 <_ZN6Strigi21AnalyzerConfigurationC1Ev@plt+8724>: mov (%eax),%edx
 PC (0x0804ec90) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA

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

StacktraceTop:ClientInterface::getIndexedFiles (this=0xbf82a1b8) at /build/buildd/strigi-0.5.6/src/daemon/clientinterface.h:74
ClientInterface::getIndexedFiles (this=0x809b158) at /build/buildd/strigi-0.5.6/src/daemon/clientinterface.h:74
PrivateDBusClientInterface::getIndexedFiles (this=0x80ae428, msg=0x80acd08, conn=0x80a2bc0)
PrivateDBusClientInterface::handleCall (this=0x80ae428, connection=0x80a2bc0, msg=0x80acd08)
DBusObjectCallHandler::handleCall (this=0x80a25f8, msg=0x80acd08) at /build/buildd/strigi-0.5.6/src/daemon/dbus/dbuscpp/dbusobjectcallhandler.cpp:118

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in strigi:
importance: Undecided → Medium
Revision history for this message
Harald Sitter (apachelogger) wrote : Re: [gutsy] strigidaemon crashed with SIGSEGV in _start()

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Changed in strigi:
status: New → Incomplete
Revision history for this message
Harald Sitter (apachelogger) 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 strigi:
status: Incomplete → Invalid
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

This still happens, it seems. (We got a dupe)

Changed in strigi (Ubuntu):
status: Invalid → Confirmed
Kees Cook (kees)
description: updated
Revision history for this message
Thomas Hotz (thotz-deactivatedaccount) wrote :

Jonathan does this still happen starting with Ubuntu versions 10.04 LTS?

Changed in strigi (Ubuntu):
status: Confirmed → Incomplete
summary: - [gutsy] strigidaemon crashed with SIGSEGV in _start()
+ strigidaemon crashed with SIGSEGV in _start()
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in strigi (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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