Bug 341415 - 'unable to create io-slave' when setting up a cardav resource in kaddressbook
Summary: 'unable to create io-slave' when setting up a cardav resource in kaddressbook
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kaddressbook
Classification: Applications
Component: general (show other bugs)
Version: 4.13.2
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-29 20:33 UTC by Helmut Fedder
Modified: 2017-01-07 21:32 UTC (History)
2 users (show)

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 Helmut Fedder 2014-11-29 20:33:04 UTC
Setting up a caldav / carddav resource fails due to an error that occurrs when clicking the 'fetch' button


Reproducible: Always

Steps to Reproduce:
The following reproduces the bug.

contacts -> 'add addressbook' -> DAV groupware resource -> enter my credentials -> select 'configure the source manually' -> finish -> add -> select carddav -> enter the server - click fetch


Actual Results:  
an error message pops up saying:

There was a problem with the request.
Could not start process Unable to create io-slave:
klauncher said: Unknown protocol ''.
. (0).


Expected Results:  
I guess it should finally show me a list where I can finally select / confirm the desired carddav resource.
Comment 1 Helmut Fedder 2014-11-29 20:39:47 UTC
Sorry, it turned out that my URL was wrong. So it is fixed now.
Nevertheless, the error message could have been more informative such as 'could not connect to server'
Comment 2 Denis Kurz 2016-09-24 20:51:52 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:32:42 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.