nepomukservicestub crashed with SIGSEGV in select()

[Žilvinas Valinskas]

As usual , reboot pc after upgrade -> crashed on startup right after user logged in.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: kde-runtime 4:4.8.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-15.24-generic 3.2.5
Uname: Linux 3.2.0-15-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Mon Feb 13 15:34:24 2012
Disassembly: => 0x0: Cannot access memory at address 0x0
DuplicateOf: https://bugs.launchpad.net/bugs/912060
ExecutablePath: /usr/bin/nepomukservicestub
InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcCmdline: /usr/bin/nepomukservicestub nepomukstorage
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: kde-runtime
StacktraceTop:
 select () at ../sysdeps/unix/syscall-template.S:82
 qt_safe_select (nfds=22, fdread=0x7fff25716d60, fdwrite=0x7fff25716de0, fdexcept=0x0, orig_timeout=0x7fff25716d30) at kernel/qcore_unix.cpp:93
 select_msecs (nfds=<optimized out>, fdread=<optimized out>, fdwrite=<optimized out>, timeout=<optimized out>) at io/qprocess_unix.cpp:1004
 QProcessPrivate::waitForFinished (this=0xcf0790, msecs=30000) at io/qprocess_unix.cpp:1232
 QProcess::waitForFinished (this=0xc6ce70, msecs=30000) at io/qprocess.cpp:1761
Title: nepomukservicestub crashed with SIGSEGV in select()
UpgradeStatus: Upgraded to precise on 2012-01-07 (36 days ago)
UserGroups: adm admin cdrom dialout kvm lpadmin plugdev sambashare wireshark

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #912060, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.