Bug 280536

Summary: Cannot set a resource as 'not read only'
Product: [Frameworks and Libraries] Akonadi Reporter: Dimitrios Glentadakis <dglent>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: roland.leissa, smartins, stephan.diestelhorst, thorsten.schnebeck, web
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Mageia RPMs   
OS: Linux   
Latest Commit: Version Fixed In:

Description Dimitrios Glentadakis 2011-08-21 17:34:39 UTC 
Version:           1.0
OS:                Linux

When i edit a resource in personal informations i have the message : "You cannot use a read-only resource as standard."

Reproducible: Always

Steps to Reproduce:
1 Open systemsettings
2 Open personal informations in common look and behaviour
3 Edit akonadi resources (allready exists in my system from previous installation) with google contacts synchronisation
4 try to edit or just leave the menu
5 the message appears : "You cannot use a read-only resource as standard."

Actual Results:  
Even if i uncheck the box with the read only field, after reopening the window the read only checkbox is again chacked by itselfs

Expected Results:  
Be able to set the checkbox as not read only

OS: Linux (x86_64) release 2.6.38.8-desktop-4.mga
Compiler: gcc
Comment 1 Roland Leißa 2011-10-13 21:22:37 UTC 
same problem here with both: google resource and a zimbra resource.

using KDE 4.7.2 with arch packages x86_64
Comment 2 Roland Leißa 2011-10-13 21:41:37 UTC 
manuall fiddling in ~/.kde4/share/config/kresources/contact/stdrc
resolves this issue.

Seems that just the UI (the kcm) is broken. (The akonadi setting dialog there is really broken anyway...)
Comment 3 Christophe Marin 2011-10-14 00:49:47 UTC 
*** Bug 283857 has been marked as a duplicate of this bug. ***
Comment 4 Thorsten Schnebeck 2011-10-21 06:44:26 UTC 
duplicate of bug 273949?
https://bugs.kde.org/show_bug.cgi?id=273949
Comment 5 Sergio Martins 2011-11-23 10:36:27 UTC 

*** This bug has been marked as a duplicate of bug 273949 ***