https://bugs.kde.org/show_bug.cgi?id=282489
--- Comment #7 from Christian Mollekopf 2011-09-26
16:47:29 ---
(In reply to comment #6)
> That probably fixes the original crash, but not the one with my BT. Do you
> want
> a new report for that?
Since it seems completely unrelated, yes please
https://bugs.kde.org/show_bug.cgi?id=282489
--- Comment #6 from András Manţia 2011-09-26 09:46:45 ---
That probably fixes the original crash, but not the one with my BT. Do you want
a new report for that?
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are re
https://bugs.kde.org/show_bug.cgi?id=282489
Christian Mollekopf changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugs.kde.org/show_bug.cgi?id=282489
Christophe Giboudeaux changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
CC|
https://bugs.kde.org/show_bug.cgi?id=282489
--- Comment #3 from András Manţia 2011-09-26 07:24:32 ---
Since yesterday I also got crashes from akonadi_nepomuk_feeder, different one
though:
Application: Akonadi Nepomuk Feeder (akonadi_nepomuk_feeder), signal:
Segmentation fault
[KCrash Handle
https://bugs.kde.org/show_bug.cgi?id=282489
--- Comment #2 from Luis Silva 2011-09-26 01:56:28 ---
Some updates. After some days of testing the nepomuk feeder is still crashing
every 15 minutes with no relation to virtuoso crashes. That one seemed to be a
one off.
However, deleting all my no
https://bugs.kde.org/show_bug.cgi?id=282489
Christophe Giboudeaux changed:
What|Removed |Added
AssignedTo|unassigned-b...@kde.org |to...@kde.org
--
Configure bugmail
https://bugs.kde.org/show_bug.cgi?id=282489
--- Comment #1 from Luis Silva 2011-09-22 18:29:33 ---
After some time I tracked the issue to a crash in virtuoso. That is, the feeder
puts the system under heavy load (mostly sorting out the data the old feeders
generated in nepomuk, I suspect) an
https://bugs.kde.org/show_bug.cgi?id=282489
András Manţia changed:
What|Removed |Added
CC||aman...@kde.org,
|
