Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 196930 - broken groupware support in kmail-3.5.8
Summary: broken groupware support in kmail-3.5.8
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo KDE team
URL: http://bugs.kde.org/show_bug.cgi?id=1...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-24 14:36 UTC by Darren Dale
Modified: 2008-01-25 19:29 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Darren Dale 2007-10-24 14:36:24 UTC
Support for groupware using IMAP broke when I upgraded from kde-3.5.7 to 3.5.8. The problem has been reported with kubuntu as well:

https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/139433

Reproducible: Always

Steps to Reproduce:
1.configure kmail, misc, groupware, enable IMAP resource functionality
2.if you had this enabled before now, the resources are not available (contacts, notes, addressbook entries, etc)
3.try adding a new entry in the calendar, get an Error saying "No writable resource was found, daving will not be possible. Reconfigure KMail first"

Actual Results:  
groupware IMAP resources are not recognized
Comment 1 Thomas Scheffler 2007-11-03 20:42:20 UTC
I can confirm this bug on two different installations.
Comment 2 Wulf Krueger (RETIRED) gentoo-dev 2008-01-25 19:29:13 UTC
Please use the workaround given on one of the upstream bugs:

"A workaround appears to be to edit your $KDEHOME/share/config/kmailrc and find something like this:

[IMAP Resource]
HideGroupwareFolders=false
TheIMAPResourceEnabled=true
TheIMAPResourceFolderParent=306242713

And to add the line:
TheIMAPResourceAccount=306242713

where that number is the same as the number on TheIMAPResourceFolderParent (excluding any other text on that line)"

Please follow http://bugs.kde.org/show_bug.cgi?id=150790 (the main upstream bug about this issue) and re-open this bug once there's progress that would allow us to fix this problem.