nepomukindexer dumps core in icalparser indexing calendar message
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
strigi (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I'm running Ubuntu 11.10
kde-runtime: Installed: 4:4.7.2-0ubuntu1
I'm running `nepomukserver --nofork` from my home directory after telling Strigi to index my Windows NTFS drive. Strigi seems to be working fine.
I noticed a core file in my home directory, `file core` reports
core:ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style, from '/usr/bin/
This is a truncated command line, the actual argv[1] is to an IMAP mail message from Microsoft Exchange circa 2005 that does contain a meeting.ics calendar attachment. It is attached
I can reproduce the crash at will using nepomukindexer or xmlindexer, with xmlindexer the stack frame is the same down to frame 10 (libstreamanaly
The output from gdb follows.
Reading symbols from /usr/lib/
done.
[New LWP 11316]
warning: Can't read pathname for load map: Input/output error.
[Thread debugging using libthread_db enabled]
bt
Core was generated by `/usr/bin/
Program terminated with signal 11, Segmentation fault.
#0 __strchr_sse2 () at ../sysdeps/
48 ../sysdeps/
in ../sysdeps/
(gdb) bt
#0 __strchr_sse2 () at ../sysdeps/
#1 0x00007f80c818bb80 in icalparser_
#2 0x00007f80c818c030 in icalparser_get_line () from /usr/lib/
#3 0x00007f80c818cd1b in icalparser_parse () from /usr/lib/
#4 0x00007f80c818cec0 in icalparser_
#5 0x00007f80c84031c6 in KCalCore:
#6 0x00007f80c867b4ae in IcsEndAnalyzer:
#7 0x00007f80d4bc232a in ?? () from /usr/lib/
#8 0x00007f80d4ba05f9 in Strigi:
#9 0x00007f80d4bd4c6f in ?? () from /usr/lib/
#10 0x00007f80d4bc232a in ?? () from /usr/lib/
#11 0x0000000000406c62 in Nepomuk:
info=<optimized out>, resUri=<optimized out>, mtime=0)
at ../../.
#12 0x0000000000406e8b in Nepomuk:
resUri=
at ../../.
#13 0x0000000000406176 in main (argc=2, argv=0x7fff40db
at ../../.
affects: | kde-runtime (Ubuntu) → strigi (Ubuntu) |
Changed in strigi (Ubuntu): | |
status: | New → Fix Released |
From the stack trace, the bug might instead/also be in strigi- plugins
libical.so.0 from package libical0
, or
strigiea_ics.so from package kdepim-