Bug 145271 - remote-file addressbook ressource over fish, zero-sized file
Summary: remote-file addressbook ressource over fish, zero-sized file
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kab3
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Debian stable Linux
: NOR normal
Target Milestone: ---
Assignee: Tobias Koenig
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-10 17:17 UTC by Carsten Wolff
Modified: 2009-08-05 16:33 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Carsten Wolff 2007-05-10 17:17:46 UTC
Version:            (using KDE KDE 3.5.5)
Installed from:    Debian stable Packages

Hi.

I'm using a remote vcs-file over fish to store and access my contacts from two different computers (never simultanously).

Every now and then, all my addresses are gone and the vcs-file has zero size. Good thing, I have daily backups.

I have a feeling (couldn't exactly proof it), that the culprit is the birthday-ressource in korganizer and that the problem only occurs, if the reminder daemon ist started while my laptop does not have network access, but gets network access later, after KDE and the reminder daemon are already running.

Greetings
Carsten
Comment 1 Kevin Krammer 2009-03-14 14:30:40 UTC
SVN commit 939239 by krake:

Fixes a bug reported here:
https://bugzilla.novell.com/show_bug.cgi?id=480957

Basically the vcard data is written into the temporay file but not to the file system yet, thus resulting in a zero sized file at the remote target location.

Could be related to the following old bug
CCBUG: 145271


 M  +2 -0      resourcenet.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=939239
Comment 2 Tobias Koenig 2009-08-05 16:33:21 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.