Bug 268737 - Kopete crashes when changing the resource name of a connected Jabber account
Summary: Kopete crashes when changing the resource name of a connected Jabber account
Status: RESOLVED FIXED
Alias: None
Product: kopete
Classification: Unmaintained
Component: Jabber Plugin (other bugs)
Version First Reported In: 1.0.80
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-17 10:56 UTC by european.swallow
Modified: 2013-11-07 17:36 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In: 4.11
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description european.swallow 2011-03-17 10:56:46 UTC 
Version:           1.0.80 (using KDE 4.5.5) 
OS:                Linux

Configuration : 
Kopete is configured with a GoogleTalk/Jabber account.
A gateway (from another server than the GoogleTalk server, because google does not provide that service) is registered to the MSN network.
The MSN account is also registered directly within kopete without a jabber gateway (but not active/online)

Observed behaviour :
When changing the local resource's name, kopete crashes

Reproducible: Always

Steps to Reproduce:
1 - Start Kopete.
2 - Connect the jabber ccount
3 - Open the jabber account properties
4 - Change the resource name
5 - Hit "apply"
6 - Hit "OK"

Actual Results:  
Kopete crashes and an ABRT popup appears to report the incident

Expected Results:  
Not crashing

The bug does not appear and the resource name is correctly changed when the jabber account is not activated.
Comment 1 Pali Rohár 2013-11-07 17:36:28 UTC 
This should be fixed in KDE 4.11. If not reopen bug.