Bug 76163

Summary:	all entries randomly deleted or disappear while editing single entry
Product:	[Unmaintained] kab3	Reporter:	Jon Dean <jon.dean>
Component:	general	Assignee:	Tobias Koenig <tokoe>
Status:	RESOLVED UNMAINTAINED
Severity:	normal
Priority:	NOR
Version First Reported In:	3.2
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Jon Dean 2004-02-26 06:08:33 UTC

Version:           3.2 (using KDE 3.2 BRANCH >= 20040204,  (testing/unstable))
Compiler:          gcc version 3.3.3 20040214 (prerelease) (Debian)
OS:          Linux (i686) release 2.6.3

While editing a single kaddressbook entry, the rest of the entries disappear or are deleted. The .kde/share/apps/kabc/std.vcf file immediately changes file size to reflect only a single kaddressbook entry. 

No deliberate 'Save' command is executed by the user. The problem seems to only occur while typing text into a text field in a addressbook entry.

Comment 1 Jon Dean 2004-02-26 06:34:16 UTC

OK. Quite possibly this is occuring because I was missing a lot of kdepim libraries.

Comment 2 Tobias Koenig 2004-02-26 12:55:07 UTC


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

Comment 3 Hans-Georg Lerdo 2004-03-19 20:17:45 UTC

This bug shows as RESOLVED. I downloaded 3.2.1 for SuSE this week and still have the same bug. Only exporting the addressbook after each edit saves me from data loss... Bugs me!! ;^|

If it indeed is resolved: Where is the fix?

Comment 4 Tobias Koenig 2004-03-20 09:43:29 UTC

On Fri, Mar 19, 2004 at 07:17:47PM -0000, Hans-Georg Lerdo wrote:
Hi Hans-Georg,

> This bug shows as RESOLVED. I downloaded 3.2.1 for SuSE this week
> and still have the same bug.
> Only exporting the addressbook after each edit saves me from data loss... Bugs me!! ;^|
> 
> If it indeed is resolved: Where is the fix?
It's fixed in CVS HEAD.

Ciao,
Tobias

Comment 5 Tobias Koenig 2009-08-05 16:06:08 UTC

The development of the old KAddressBook will be discontinued for KDE 4.4.
Since the new application has the same name, but a completly new code base we close all bug reports against the old version and ask the submitters to resend there reports against the new product.