Bug 299481 - A periodically repeated error message that reports that a request for saving an address book failed
Summary: A periodically repeated error message that reports that a request for saving ...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kaddressbook
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-06 04:20 UTC by K. A. Sayeed
Modified: 2017-01-07 21:25 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description K. A. Sayeed 2012-05-06 04:20:26 UTC
1. When a contact in the Contact module of KDE Kontact was copied and pasted into the same address book, the following error message was repeatedly displayed:

1.1. " Address Book: Request for saving the address book failed. Probably locked by another application" 

Reproducible: Didn't try

Steps to Reproduce:
1. Copy and paste a contact address into the same address book.
2.
3.
Actual Results:  
As described in the "Details" section above.

Expected Results:  
1. There should be no error message.

1. Kubuntu Linux 12.04 was the operating system being used.

2. KDE Kontact was provided with the Linux distribution. 

3. The error message continued to be repeated even after KDE Kontact was closed and restarted.
Comment 1 K. A. Sayeed 2012-05-06 04:31:44 UTC
1. This bug has been found to be reproducible by following the steps outlined in the bug report.
Comment 2 Denis Kurz 2016-09-24 20:52:49 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 3 Denis Kurz 2017-01-07 21:25:46 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.