Bug 278420 - GroupDAV resource details get lost
Summary: GroupDAV resource details get lost
Status: RESOLVED FIXED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: DAV Resource (show other bugs)
Version: 1.6.0
Platform: openSUSE Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 282484 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-07-24 21:20 UTC by docali
Modified: 2011-10-06 05:55 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 4.7.2


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description docali 2011-07-24 21:20:51 UTC
Version:           1.6.0 (using KDE 4.6.5) 
OS:                Linux

Frequently when opening KAdressbook nothing is shown. Same with Korganizer.

When I have a look in the Akonadi system settings panel I still find my GroupDAV resource listed but when I choose Edit the same window i get when creating a new ressource pops up. 
In other cases the password to the server gets lost. 


Reproducible: Sometimes

Steps to Reproduce:
Until now I cannot intentionally reproduce the bug but it happens almost every time. 


Expected Results:  
The groupdav ressource should keep the provided settings

Using GroupDAV with EGroupware 1.8.001
Comment 1 Grégory Oestreicher 2011-07-25 08:04:59 UTC
Hi,

Which version of KDEPIM are you using?

Cheers,
Grégory
Comment 2 docali 2011-07-26 10:09:00 UTC
I use kdepim  4.6.1-1.4 and kdepimlibs4 4.6.5-224.2
Comment 3 Grégory Oestreicher 2011-07-27 20:57:12 UTC
And what's you kdepim-runtime package version?
Comment 4 docali 2011-07-27 21:37:37 UTC
 kdepim4-runtime                       4.6.1-1.2
Comment 5 docali 2011-07-28 20:22:22 UTC
still happens with

kdepim4          4.7.0-10.1
kdepim4-runtime  4.7.0-5.1  
kdepim4-wizards  4.7.0-10.1 
kdepimlibs4      4.7.0-5.1  
libkdepim4       4.7.0-10.1 
libkdepimlibs4   4.7.0-5.1
Comment 6 Grégory Oestreicher 2011-07-28 20:39:35 UTC
While working on something else I found a nasty bug with egroupware and the 4.7 branch. This was fixed today, so it won't find its way in a stable release before 4.7.1, due in a month. You should consider switching back to 4.6 for now.

Unfortunately, this does not explain your issue… When you are trying to reconfigure the resource and the wizard pops up, do you still have the file ~/.kde/share/config/akonadi_davgroupware_resource_Xrc (with X some number)?

If so, can you check that its content looks OK?
Comment 7 docali 2011-07-28 21:11:06 UTC
Content does not look okay, just the [General] line and the next display name are shown. The remoteurls line is empty.
Comment 8 Grégory Oestreicher 2011-09-22 20:44:21 UTC
*** Bug 282484 has been marked as a duplicate of this bug. ***
Comment 9 Jens Westemeier 2011-09-23 10:45:17 UTC
Tried to monitor changes in the akonadi_davgroupware_resourceXrc file. It's unchanged from the working initial state and the non-working state after a restart of akonadi. In both cases it is not containing the exchange server password, which is required to re-connect.

[General]
displayName=Company
remoteUrls=loginname|CalDav|http://localhost:1080/users/ExchangeEmailAddress/calendar/,loginname|CardDav|http://localhost:1080/users/ExchangeEmailAddress/contacts
Comment 10 Grégory Oestreicher 2011-09-23 11:22:20 UTC
Hi Jens,

The password is stored in KWallet, not as-is in the configuration file.

Cheers,
Grégory
Comment 11 Jens Westemeier 2011-09-23 14:56:06 UTC
kwallet is disabled on my computer. I did not got asked for enabling it when I entered the password.
Comment 12 Grégory Oestreicher 2011-10-01 10:49:13 UTC
Hi Jens,

It seems I was too quick merging both bugs. KWallet is required for the resource to work. Enabling it should resolve your issue. For 4.8 I'll add a message to prevent confusing users.

As for the initial bug I'm still not able to reproduce this issue… Maybe some kind of D-Bus race condition.

Cheers,
Grégory
Comment 13 Grégory Oestreicher 2011-10-01 19:18:17 UTC
Hi,

In fact this bug was fixed "inadvertently", by finding the same bug and not remembering the details of this report.

Cheers,
Grégory
Comment 14 Jens Westemeier 2011-10-02 17:39:54 UTC
Hi Grégory,

thanks, enabling kwallet helped.

Nevertheless, I would suggest a different bugfix. Be consistent with other credental handling in kmail / akonadi. Installing my pop3 account I was asked for kwallet, I denied and after a warning my credential were stored locally (I don't know where). For consistency I would like to have the same behaviour all over akonadi.

I also would like to suggest a small enhancement. Please add the davmail frontend to the select buttons or provide an "Other Connections" or something similar to the dialog used to select the connection. Going via "Abort" into the desired dialog is somehow weired.

Greetings, jens.
Comment 15 Grégory Oestreicher 2011-10-02 20:23:58 UTC
Hi Jens,

I don't see the benefits of letting the resource store your passwords in unencrypted files scattered through your hard drive (and I doubt that everybody has access to military-grade data destruction facilities ;). The benefit of using KWallet is that your passwords are encrypted and theorically safe (though I'm not sure that using KWallet without a password is not a glorified spreadsheet with all your passwords ripe for recovery in it). I'm unlikely to do this kind of thing in the resource and would oppose this kind of modification that would result in a lesser security for the user, unless re-inventing KWallet.

The best I could do is to have the resource not store any password and prompt the user for it at each start.

For davmail are the URLs that appear in your configuration file (https://bugs.kde.org/show_bug.cgi?id=278420#c9) standard, and can they be used as a template? Adding this is a matter of minutes, but will not be shipped before KDE SC 4.8 (there are translations issues).

Finally regarding the "Abort" this was fixed in KDE SC 4.7 iirc. Though I'm not sure when I committed this, so I may very well be wrong and in that case it'll be in KDE SC 4.8.

Cheers,
Grégory
Comment 16 docali 2011-10-06 05:55:47 UTC
Thanks for fixing the bug. I will try the new version this weekend. 

I vote for the option to enter the password alternatively once for every session either at startup or first sync when not using kwallet.