Bug 68958 - it is not possible to change accountId (username) after creating an account
Summary: it is not possible to change accountId (username) after creating an account
Status: CONFIRMED
Alias: None
Product: kopete
Classification: Applications
Component: libkopete (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
: 83101 177173 192051 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-11-24 20:10 UTC by Rob Kaper
Modified: 2009-07-05 06:13 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Rob Kaper 2003-11-24 20:10:56 UTC 
Version:           unknown (using KDE 3.1.93 (CVS >= 20031111), compiled sources)
Compiler:          gcc version 3.2
OS:          Linux (i686) release 2.4.19

I mistyped my UIN for my ICQ account and wanted to modify the account, but modifying an ICQ account doesn't let users fix typos in their UIN, so I had to remove and re-add instead.
Comment 1 Till Gerken 2003-11-24 20:16:53 UTC 
This is a flaw in the current API and is known, but cannot be changed easily. The problem applies to all protocol plugins.
Comment 2 Richard Smith 2004-02-13 16:07:45 UTC 
In my opinion, accountId and username should be made orthogonal. Any objections?
Comment 3 Matt Rogers 2004-06-22 22:09:41 UTC 
*** Bug 83101 has been marked as a duplicate of this bug. ***
Comment 4 FiNeX 2008-11-16 15:36:32 UTC 
On current KDE 4 trunk it is still not possible to edit the account username. The input text field is locked!
Comment 5 Hemant Kumar 2009-02-08 10:38:07 UTC 
I second this. I was adding an Yahoo account and did a typo while adding and can't modify it now. I had to remove/re-add. This should be fixed.
Comment 6 Hemant Kumar 2009-02-08 10:38:17 UTC 
I second this. I was adding an Yahoo account and did a typo while adding and can't modify it now. I had to remove/re-add. This should be fixed.
Comment 7 Matt Rogers 2009-03-28 21:13:34 UTC 
*** Bug 177173 has been marked as a duplicate of this bug. ***
Comment 8 Matt Rogers 2009-07-05 06:13:11 UTC 
*** Bug 192051 has been marked as a duplicate of this bug. ***