[Nepomuk] Problem with storage crashing repeatedly
Lindsay Mathieson
lindsay.mathieson at gmail.com
Thu Jun 20 12:11:18 UTC 2013
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/nepomuk/attachments/20130620/9824683d/attachment.sig>
More information about the Nepomuk
mailing list