Application that crashed: akonadi_nepomuk_email_feeder Version of the application: 0.1 KDE Version: 4.2.90 (KDE 4.2.90 (KDE 4.3 Beta2)) Qt Version: 4.5.1 Operating System: Linux 2.6.26-1-686-bigmem i686 Distribution: Debian GNU/Linux testing (squeeze) What I was doing when the application crashed: I was in the akonadi configuration window, when i finished i exited and (to me) it exited fine, but the crash report assistant appeared telling me that it was closed unexpectedly, so here am i reporting it. -- Backtrace: Application: Akonadi Agent (akonadi_nepomuk_email_feeder), signal: Segmentation fault [KCrash Handler] #6 0xb7ec5bf8 in Soprano::FilterModel::containsAnyStatement (this=0x8b3b420, statement=@0xbff71cb4) at /home/franco/descargas/kde4/src/system/kde4/kdesupport/soprano/soprano/filtermodel.cpp:140 #7 0xb77262d8 in Nepomuk::ResourceData::exists (this=0x8b3b520) at /home/franco/descargas/kde4/src/system/kde4/kdelibs/nepomuk/core/resourcedata.cpp:500 #8 0xb77276c1 in Nepomuk::ResourceData::store (this=0x8b3b520) at /home/franco/descargas/kde4/src/system/kde4/kdelibs/nepomuk/core/resourcedata.cpp:278 #9 0xb772835b in Nepomuk::ResourceData::setProperty (this=0x8b3b520, uri=@0xbff71f38, value=@0xbff71f34) at /home/franco/descargas/kde4/src/system/kde4/kdelibs/nepomuk/core/resourcedata.cpp:413 #10 0xb77406b2 in Nepomuk::Resource::setProperty (this=0xbff71f78, uri=@0xbff71f38, value=@0xbff71f34) at /home/franco/descargas/kde4/src/system/kde4/kdelibs/nepomuk/core/resource.cpp:293 #11 0x08076ac6 in Nepomuk::Message::setMessageSubject () #12 0x08061328 in _start () Reported using DrKonqi
I see now that perhaps the bug was incorrectly reported. the issue seems to be with one of the (agents?) i added to akonadi. Was the one to feed emails to nepomuk (i was playing around with akonadi cause i just made it work :) ) the thing is, i added that, and never appeared, and now this crash handler keeps appearing (even that i'm hitting the "Close" button) and i cannot remove the thing causing it cause is not listed with the others... help...
*** This bug has been marked as a duplicate of bug 194408 ***