Bug 265087 - Plasma crashed when Kopete use Address Book Link
Summary: Plasma crashed when Kopete use Address Book Link
Status: RESOLVED DUPLICATE of bug 261593
Alias: None
Product: plasma4
Classification: Plasma
Component: desktop (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-01 13:38 UTC by Richard Feciskanin
Modified: 2011-02-05 00:43 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
backtrace (7.82 KB, text/plain)
2011-02-02 10:02 UTC, Richard Feciskanin 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Feciskanin 2011-02-01 13:38:10 UTC 
Version:           unspecified (using KDE 4.6.0) 
OS:                Linux

Plasma crashes when Kopete starting if there is contact with Address Book Link defined.
If there is none Kopete starts OK.
Adding Address Book Link to contact cause Plasma crash.
Using Akonadi Address Book (Personal Contacts resource)

Reproducible: Always

Steps to Reproduce:
a)
1. in Kopete - any contact -> properties -> adressbook link (change)
b) if link is set
1. start Kopete

Actual Results:  
Plasma crash and restart

Expected Results:  
Plasma doesn't crash

I found what cause Plasma crash on Kopete start removing config files and setting settings again.

Kopete 1.0.80
Comment 1 Aaron J. Seigo 2011-02-01 19:59:17 UTC 
this is probably the IncidentBase crash that has already been fixed; a backtrace is required, however. thanks.
Comment 2 Richard Feciskanin 2011-02-02 10:02:06 UTC 
Created attachment 56778 [details]
backtrace
Comment 3 Richard Feciskanin 2011-02-03 15:17:36 UTC 
changed status, backtrace provided
Comment 4 Dario Andres 2011-02-05 00:43:43 UTC 
[Comment from a bug triager]
Aaron probably refers to bug 261593 (should that report be closed?); and the backtrace matches. Merging.
Regards

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