After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 380799 - Ekiga can not check duplicate account
Ekiga can not check duplicate account
Status: RESOLVED WONTFIX
Product: ekiga
Classification: Applications
Component: general
unspecified
Other All
: Normal enhancement
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2006-11-30 07:33 UTC by vicky.sun
Modified: 2020-06-06 16:28 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description vicky.sun 2006-11-30 07:33:33 UTC
When add a account, Ekiga2.0.3 can not check if the same account exist already, so a account can be added many times. I suggest adding this feature in the future.
Comment 1 Jan Schampera 2007-01-02 05:18:28 UTC
When is an account double? When "user" and "registrar" are identical?

J.
Comment 2 vicky.sun 2007-01-04 01:54:13 UTC
I means all the items are same, including account name, registrar, user,passswork and so on.



Comment 3 Jan Schampera 2008-09-13 08:42:34 UTC
In 3.x, this check should go into the engine I guess.
Comment 4 Snark 2008-09-14 18:43:56 UTC
Each bank should take care of this.
Comment 5 Eugen Dedu 2009-07-14 21:45:44 UTC
In my opinion, in the assistant, an account is duplicated if the registrar and the user given are identical to what already exists in the accounts "database".  Is it difficult to fix this?
Comment 6 Snark 2009-07-15 06:22:25 UTC
Depends.

Damien's way : the ui loops on all accounts, reads what's in them, decides there's a duplicate, hence doesn't add the new account. Very difficult since I enginized the account stack : now accounts are just structures anymore, they're serious classes which hide their implementations.

Snark's way : the opal account code knows what an opal account is, so when the ignorant ui asks to add a new opal account, it sees it has a duplicate and doesn't add the duplicate. Quite simple I would say.

This is the longer way of saying "Each bank should take care of this.", as comment #4.
Comment 7 Damien Sandras 2009-07-15 06:54:23 UTC
Keep your mocking comments for yourself, everybody knows you have a superior intelligence.

There was a loop in the time when accounts where stored in a pure single-linked list.

Oh, I don't even know why I still read your comments and answer them. I should probably simply ignore them.
Comment 8 Eugen Dedu 2009-07-15 08:18:27 UTC
I didn't want to say how it should be done.  I wanted just to:
- I think only the name and the registrar should be checked (this is what makes an account unique; we cannot have two different accounts which differ only on their password)
- could this be implemented soon, i.e. is it difficult?
Comment 9 André Klapper 2020-06-06 16:28:48 UTC
Ekiga is not under active development anymore:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/273

Ekiga saw its last release 7 years ago. The last code commits were 4 years ago.

Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (and transfer the project to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the responsibility for active Ekiga development again in the future.