Bug 117289 - Error dialogue upon successful WebDAV upload
Summary: Error dialogue upon successful WebDAV upload
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: 3.4.2
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-29 18:02 UTC by Anders Berg
Modified: 2017-01-07 22:09 UTC (History)
0 users

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 Anders Berg 2005-11-29 18:02:19 UTC
Version:           3.4.2 (using KDE 3.4.2 Level "b" , SUSE 10.0)
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.13-15-default

I've used WebDAV for a while to publish my calendar at www.icalx.com.

Since a couple of days an error dialogue occurs at each upload of the calendar:
Error when saving "calendarname" remotely.

When I check the remote file though, it was changed, and in the background of the error dialogue the kioslave window for upload appears, and it shows upload progress as normal.

In ~/.xsession-errors I get:
korganizer: WARNING: LockNull::lock() force success. Doesn't actually lock.
korganizer: WARNING: ResourceRemote::save(): upload still in progress.

The error dialogue could tell some more information, it's not likely that an inexperienced user can find out what is wrong, or like in this case, that the upload was indeed succesful!

If a previous upload is marked as still in progress, shouldn't its upload progress window stay? It seems to me that there's some logic error in when and how it's being detected if a previous upload is not finished.

Ok, hope you've got enough information to work with. 

Cheers
/Anders
Comment 1 Thomas Themel 2006-03-15 08:03:13 UTC
Same thing happens to me on Debian with the 3.5.1-1 Debian package on occasion, backend is a self configured Apache2 server.

themel@sophokles:~$ korganizer --version
Qt: 3.3.5
KDE: 3.5.1
KOrganizer: 3.5
Comment 2 Andrew Ziem 2006-05-16 23:49:26 UTC
I think my problem may be the same with these differences:

- The message is "Error saving foo.ics on bar" where bar is the hostname of my WebDAV server.
- I don't have an ~/.xsession-errors files (and the console doesn't show any useful information).
- I get the error on the first change but not the second.  Then, I only get the error if I close the knotify daemon.  (But, I'm still testing this theory.)

I don't see any related errors in /var/log/httpd/error_log

My system is Fedora Core 5, KDE 3.5.2, Korganizer 1.2, Apache (for WebDAV), and I run GNOME 2.14.

At least, it would be good to have more information in the error dialog.
Comment 3 Reinhold Kainhofer 2006-11-02 19:13:32 UTC
Reassigning all KOrganizer bug reports and wishes to the newly created 
korganizer-devel mailing list.
Comment 4 trish 2007-11-08 14:23:44 UTC
The same problem occurs when saving your calender remotely using fish. It seems as if there were a counter triggering this error "dialog" whenever a saving process takes "too much" time. With my DSL internet connections this counter is almost always exceeded.

The problem extends: When an error actually occurs, this is mostly due to a korganizer crash, but in this case the error dialog won't appear, and the remote file is broken since with fish, korganizer unfortunately stores no backup copy. This crash happens every now and then and it seems to be connected with long remote saving processes. 
Comment 5 trish 2007-11-08 14:25:39 UTC
I'm sorry, I forgot to mention system data: Qt: 3.3.7, KDE: 3.5.5, KOrganizer: 3.5.5 on Debian Etch. Same problem occurs with Ubuntu packages.
Comment 6 Denis Kurz 2016-09-24 18:53:47 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 korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 7 Denis Kurz 2017-01-07 22:09:39 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.