Bug 194739 - Added a simple contact to a recently created akonadi address folder
Summary: Added a simple contact to a recently created akonadi address folder
Status: RESOLVED DUPLICATE of bug 194408
Alias: None
Product: nepomuk
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-31 11:25 UTC by Alexander Jenisch
Modified: 2009-05-31 11:29 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Jenisch 2009-05-31 11:25:10 UTC
Application that crashed: akonadi_nepomuk_contact_feeder
Version of the application: 0.1
KDE Version: 4.2.87 (KDE 4.2.87 (KDE 4.3 >= 20090519))
Qt Version: 4.5.1
Operating System: Linux 2.6.29-ARCH i686
Distribution: "(none)"

What I was doing when the application crashed:
Using kmail, i had trouble adding any contacts until i found a solution somewhere in the web. i had to configure akonadi first -> terrible terrible usabilty culprit.

after adding a simple folder based address book, i was able to add contacts in kmail, but after pressing ok, this crash occured.

 -- Backtrace:
Application: Akonadi Agent (akonadi_nepomuk_contact_feeder), signal: Segmentation fault
[KCrash Handler]
#6  0xb7b330d8 in Soprano::FilterModel::containsAnyStatement () from /usr/lib/libsoprano.so.4
#7  0xb7be94f4 in Nepomuk::ResourceData::exists () from /usr/lib/libnepomuk.so.4
#8  0xb7be9d6b in Nepomuk::ResourceData::store () from /usr/lib/libnepomuk.so.4
#9  0xb7beb818 in Nepomuk::ResourceData::setProperty () from /usr/lib/libnepomuk.so.4
#10 0xb7c04402 in Nepomuk::Resource::setProperty () from /usr/lib/libnepomuk.so.4
#11 0xb7c0453d in Nepomuk::Resource::setLabel () from /usr/lib/libnepomuk.so.4
#12 0x0806e6c8 in _start ()
Comment 1 Christophe Marin 2009-05-31 11:29:14 UTC

*** This bug has been marked as a duplicate of bug 194408 ***