Bug 352693

When configuring a path for a calendar file on disk the akonadi ical file resource takes the path literally with protocol prefix and appends that to the home directory. It is thus impossible to specify a path for a calendar file.

Note that this is a regression that only occurred since about one week after updating to the current git version of akonadi/kdepim from Kubuntu continuous integration. As of source version from today (14.09.2015) the bug still exists.

Reproducible: Always

Steps to Reproduce:
1. Add a new ICal calendar file resource using Akonadi Console
2. input a path and filename for the resource file, e.g. in your home directory: "/home/$USER/blatestfile" (note that the file does not have to exist!)
3. click ok

Actual Results:  
A file "blatestfile" is created but in the path "/home/$USER/file:/home/$USER/blatestfile"
Note the "file:" protocol component in the path. 

Expected Results:  
A file "blatestfile" should be created or used if already existent with the path of "/home/$USER/blatestfile"

It seems as if the path is taken literally as a string with the "file:" protocol part included and appended to you home directory.