Bug 107711 - Recurring dataloss with KAddressbook
Summary: Recurring dataloss with KAddressbook
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kab3
Classification: Unmaintained
Component: general (show other bugs)
Version: 3.4.1
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Tobias Koenig
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-19 10:43 UTC by Arne Schmitz
Modified: 2009-08-05 16:25 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
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 Arne Schmitz 2005-06-19 10:43:52 UTC 
Version:           3.4.1 (using KDE 3.4.1 Level "a" , SUSE 9.3 UNSUPPORTED)
Compiler:          gcc version 3.3.5 20050117 (prerelease) (SUSE Linux)
OS:                Linux (i686) release 2.6.11.4-21.7-default

When using KAdressbook from within Kontact I have recurring datalosses. Most of the time I get some message like "foo.vcf is still locked" upon logout, and the next time foo.vcf is empty (0 Bytes).
Comment 1 Tobias Koenig 2005-06-20 13:10:57 UTC 
On Sun, Jun 19, 2005 at 08:43:53AM -0000, Arne Schmitz wrote:
Hi Arne,

> When using KAdressbook from within Kontact I have recurring datalosses.
> Most of the time I get some message like "foo.vcf is still locked" upon logout,
> and the next time foo.vcf is empty (0 Bytes).

What address books (resources) do you have configured? Are there any
other applications running which use the address book? What do you mean
with 'logout', closing KAddressBook or the session?

Ciao,
Tobias
Comment 2 Arne Schmitz 2005-06-20 13:17:58 UTC 
Am Montag, 20. Juni 2005 13:10 schrieb Tobias K
Comment 3 Tobias Koenig 2005-08-01 22:12:34 UTC 

*** This bug has been marked as a duplicate of 87163 ***
Comment 4 Tobias Koenig 2009-08-05 16:25:28 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.