Summary: | akonadi_nepomuk_feeder always crashes on startup | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | András Manţia <amantia> |
Component: | Nepomuk Feeder Agents | Assignee: | Christian Mollekopf <chrigi_1> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | chrigi_1, valir, vkrause, winter |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
András Manţia
2011-09-26 19:19:43 UTC
Cleaned my install dirs and disabled the old feeders to not autostart and no crash since. Aargh, I was too fast. As soon as I closed the report, it crashed. Created attachment 63998 [details]
New crash information added by DrKonqi
akonadi_nepomuk_feeder (4.7) on KDE Platform 4.7.2 (4.7.2) using Qt 4.8.0
- What I was doing when the application crashed:
I just compiled sources (git pull done 3 hours ago) the restarted the session to get this crash.
-- Backtrace (Reduced):
#7 0x00007f3be5ecafd0 in Akonadi::qt_plugin_instance () at /home/kde/src/kdepim/nepomuk_email_feeder/nepomukmailfeeder.cpp:249
#8 0x00007f3bf6ac9a20 in kde4Factory (lib=0x823c80) at /home/kde/work/kdelibs/kdecore/util/klibrary.cpp:149
#9 0x00007f3bf6ac9c5b in KLibrary::factory (this=0x823c80, factoryname=0x8d1008 "akonadi_nepomuk_email_feeder") at /home/kde/work/kdelibs/kdecore/util/klibrary.cpp:169
#10 0x00007f3bf6acffc1 in KPluginLoader::factory (this=0x7fff1dc4e4d0) at /home/kde/work/kdelibs/kdecore/util/kpluginloader.cpp:197
#11 0x000000000040d0ac in KService::createInstance<Akonadi::NepomukFeederPlugin> (this=0x82f900, parentWidget=0x0, parent=0x0, args=..., error=0x7fff1dc4e610) at /home/kde/include/kservice.h:549
I moved the emailfeeder to kdepim-runtime now, which removes the ugly unknown symbols hack. Since it seems to always crash in the emailfeeder that could be the reason for the crash (otherwise I don't really get whats happening). So please retry. Thanks, the crash seems to be gone. Now virtuoso-t is using a lot of CPU (183%, 4 cores), but at least the agent does not crash. Yes, that is due to all attemps to store something failing, due to duplicates in the SimpleResourceGraph. This is an issue being worked on, so I suggest to disable the feeder for now. Christian, what's the status of the fix for SimpleResourceGraph? can we close this? The merging was mostly fixed this week, for the remaining problem I just pushed to patches to master. The feeder work for me like this. In either case the original bug has been resolved, therefore I close this bug. |