Bug 231512 - ical file on FTP ressource doesn't remember authorization
Summary: ical file on FTP ressource doesn't remember authorization
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: ICal file resource (show other bugs)
Version: 4.4
Platform: Ubuntu Unspecified
: NOR normal
Target Milestone: ---
Assignee: Volker Krause
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-21 11:06 UTC by Andreas Pietzowski
Modified: 2017-01-07 21:40 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Pietzowski 2010-03-21 11:06:45 UTC 
Version:            (using KDE 4.4.1)
Installed from:    Ubuntu Packages

I have a remote ical file and set the reload interval to 10 minutes. Every 10 minutes KDE askes me again for username and password - although every data is known and already filled in in the dialog.

I have to click OK every 10 minutes and close this annoying dialog otherwise following kio_slaves are not working because the FTP autorization dialog blocks all remote connections like FTP.
Comment 1 Andreas Pietzowski 2010-03-31 11:31:52 UTC 
This bug is still existing in 4.4.2! Come on guys. KDE claims to be network transparent but one of the core components (the calendar from kontact in this case) can not even handle FTP in the background since months right now?
Comment 2 Andreas Pietzowski 2011-03-04 22:01:34 UTC 
The mentioed solution above with runnung dbus-launch and setting the system variables only work if you are NOT logged in to your KDE desktop at the remote machine itself :-(
Comment 3 Denis Kurz 2016-09-24 20:40:29 UTC 
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 4 Denis Kurz 2017-01-07 21:40:40 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.