Bug 306808 - Kopete crash when removing authorization to see status after deleting contact
Summary: Kopete crash when removing authorization to see status after deleting contact
Status: RESOLVED DUPLICATE of bug 298290
Alias: None
Product: kopete
Classification: Unmaintained
Component: Contact list (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-14 19:24 UTC by Holly
Modified: 2012-11-06 03:11 UTC (History)
0 users

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


Attachments
Stack trace from the crash (7.47 KB, text/plain)
2012-09-14 19:25 UTC, Holly
Details
Stack trace from another crash (8.84 KB, text/plain)
2012-09-14 19:26 UTC, Holly
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Holly 2012-09-14 19:24:22 UTC
Kopete crashes after I delete a contact, but choose to let the continue to see my status.  I've verified this with google talk contacts, specifically ones that I think were added by Google from G+ (username format: <random alphanumeric string>@public.talk.google.com)  This does not happen when deleting a MSN contact, when I did not get dialog asking about authorization to view display status.

Reproducible: Always

Steps to Reproduce:
1. Start Kopete
2. Select contact to delete
3. Right click, remove contact, select remove
4. Notifications asks "Do you also want to remove user <username>'s authorization to see your status?"  Click Keep.
5. Approximately 1 second later, crashes
Actual Results:  
Kopete crashed.

Expected Results:  
Contact should have been removed, and Kopete continued to run normally.

Archlinux
kdenetwork-kopete 4.9.1-1
Comment 1 Holly 2012-09-14 19:25:47 UTC
Created attachment 73915 [details]
Stack trace from the crash
Comment 2 Holly 2012-09-14 19:26:37 UTC
Created attachment 73916 [details]
Stack trace from another crash
Comment 3 Jekyll Wu 2012-11-06 03:11:45 UTC

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