Confirmed. Crash virtuoso when some operations are going on in the storage service. The main repository's parent will be set as 0, and then reset to the new virtuoso model. In the middle the other threads can access it and they assert cause the parent of the model = 0.
This can probably be fixed with a mutex. I'm not sure exactly how to go about it. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-runtime in Ubuntu. https://bugs.launchpad.net/bugs/912060 Title: nepomukservicestub crashed with SIGSEGV in select() To manage notifications about this bug go to: https://bugs.launchpad.net/kde-runtime/+bug/912060/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs