nepomukserver crashed with SIGSEGV in sendmsg()

[Indra]

ugraded to ubuntu precise daily beta, got this

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: kde-runtime 4:4.7.97-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-9.16-generic 3.2.1
Uname: Linux 3.2.0-9-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.90-0ubuntu2
Architecture: amd64
Date: Tue Jan 17 11:25:09 2012
ExecutablePath: /usr/bin/nepomukserver
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: /usr/bin/nepomukserver
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fc7ecd42b53 <_ZN9QHashData14detach_helper2EPFvPNS_4NodeEPvEPFvS1_Eii+227>: mov (%rax,%rdx,8),%rbx
 PC (0x7fc7ecd42b53) ok
 source "(%rax,%rdx,8)" (0x00000041) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: kde-runtime
StacktraceTop:
 sendmsg () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
Title: nepomukserver crashed with SIGSEGV in sendmsg()
UpgradeStatus: Upgraded to precise on 2012-01-16 (0 days ago)
UserGroups: adm admin cdrom dialout fax floppy libvirtd lp lpadmin plugdev sambashare scanner syslog vboxusers

[Apport retracing service (apport)]

StacktraceTop:
 sendmsg () at ../sysdeps/unix/syscall-template.S:82
 _dbus_write_socket_with_unix_fds_two (fd=3, buffer1=<optimized out>, start1=<optimized out>, len1=<optimized out>, buffer2=<optimized out>, start2=<optimized out>, len2=77, fds=0x0, n_fds=0) at ../../dbus/dbus-sysdeps-unix.c:476
 do_writing (transport=<optimized out>) at ../../dbus/dbus-transport-socket.c:607
 do_writing (transport=0x20d6780) at ../../dbus/dbus-transport-socket.c:494
 socket_do_iteration (transport=0x20d6780, flags=1, timeout_milliseconds=-1) at ../../dbus/dbus-transport-socket.c:1075

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.