On Thu, 20 Jun 2013 09:57:41 PM you wrote:
> On Thu, 20 Jun 2013 04:51:28 PM you wrote:
> > Please file a bug report, and add the backtrace.
> > 
> > You can produce the backtrace by running the storage service manually
> > 
> > $ gdb nepomukstorage
> 
> Still no stacktrace unfortunately.
> 
> Program received signal SIGPIPE, Broken pipe.
> [Switching to Thread 0x7fffea83e700 (LWP 23753)]
> 0x00007ffff4e6cf17 in send () from /lib/x86_64-linux-gnu/libc.so.6

The more I test it seems to be a problem with virtuoso-t - it crashes, storage 
gets a broken pipe signal and doesn't recover.

Which repo does virtuoso-t get build from? kdesupport?

-- 
Lindsay

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
Nepomuk mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/nepomuk

Reply via email to