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.
nepomukstorage(23725)/nepomuk (storage service)
Nepomuk2::Sync::ResourceIdentifier::runIdentification: KUrl("_:xob") -->
KUrl("nepomuk:/res/78dda6d9-31d3-49ef-be08-adae53f28904")
nepomukstorage(23725)/nepomuk (storage service)
Nepomuk2::Sync::ResourceIdentifier::runIdentification: KUrl("_:wob") -->
KUrl("nepomuk:/res/426ae868-acfe-48db-9984-993dd3147b58")
nepomukstorage(23725)/nepomuk (storage service)
Nepomuk2::Repository::slotVirtuosoStopped: Virtuoso was killed or crashed.
Restarting the repository.
nepomukstorage(23725)/nepomuk (storage service) Nepomuk2::Repository::close:
"main"
Program received signal SIGPIPE, Broken pipe.
[Switching to Thread 0x7fffea83e700 (LWP 23753)]
0x00007ffff4e6cf17 in send () from /lib/x86_64-linux-gnu/libc.so.6
Is the problem actually virtuoso_t perhaps?
When I start the service with gdb I get:
$ gdb nepomukstorage
Starting program: /usr/bin/nepomukstorage
warning: no loadable sections found in added symbol-file system-supplied DSO at
0x7ffff7ffa000
[Thread debugging using libthread_db enabled]
I did build with debug info.
Thanks,
--
Lindsay
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Nepomuk mailing list [email protected] https://mail.kde.org/mailman/listinfo/nepomuk
