strigi crash with SIGABRT

Bug #649668 reported by Vu Ngoc San
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
strigi (Ubuntu)
New
Undecided
Unassigned

Bug Description

I launch strigi from the standard Kubuntu settings, it starts then stops...

Here is the trace from dbg:

gdb --args nepomukservicestub nepomukstrigiservice
GNU gdb (GDB) 7.1-ubuntu
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/nepomukservicestub...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/nepomukservicestub nepomukstrigiservice
[Thread debugging using libthread_db enabled]
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
[New Thread 0x7fffeb96c710 (LWP 10906)]
nepomukservicestub: /build/buildd/strigi-0.7.2/src/streamanalyzer/lineeventanalyzer.cpp :180 : void Strigi::LineEventAnalyzer::handleUtf8Data(const char*, uint32_t): L'assertion « !(sawCarriageReturn && missingBytes > 0) » a échoué.

Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffeb96c710 (LWP 10906)]
0x00007ffff5a97a75 in raise () from /lib/libc.so.6

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: libstreamanalyzer0 0.7.2-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-24.43-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic x86_64
Architecture: amd64
Date: Tue Sep 28 11:17:27 2010
InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
ProcEnviron:
 LANGUAGE=
 PATH=(custom, user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: strigi

Revision history for this message
Vu Ngoc San (san-vu-ngoc) wrote :
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.