Bug 238706 - delayed contact adding
Summary: delayed contact adding
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kaddressbook
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian unstable Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-24 18:04 UTC by Salvo "LtWorf" Tomaselli
Modified: 2017-01-07 22:00 UTC (History)
2 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 Salvo "LtWorf" Tomaselli 2010-05-24 18:04:59 UTC 
Version:           unspecified (using KDE 4.4.3) 
OS:                Linux

I added a contact on the local addressbook, then i tried to search for it and it wasn't there. After a couple of minutes a dialog to insert username and password to access the google phonebook appeared (because using kwallet is apparently too complicated) and after i inserted those, my contact in my local phonebook appeared.
I don't know if the problem is here or in akonadi.

Reproducible: Didn't try




OS: Linux (x86_64) release 2.6.34-vulcano
Compiler: cc
Comment 1 Tobias Koenig 2010-05-24 18:25:22 UTC 
Hej,

has the contact be added to your local or google address book?

Ciao,
Tobias
Comment 2 Salvo "LtWorf" Tomaselli 2010-05-24 18:48:09 UTC 
in the local one
Comment 3 Salvo "LtWorf" Tomaselli 2015-07-28 08:23:30 UTC 
Which additional info was expected?
Comment 4 Laurent Montel 2015-07-28 08:46:08 UTC 
Do you have still this bug in last kdepim ?
Comment 5 Denis Kurz 2016-09-24 20:53:24 UTC 
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kaddressbook (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 6 Denis Kurz 2017-01-07 22:00:36 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.