Red Hat Bugzilla – Bug 150744
LDAP Contacts Free Busy URL not working
Last modified: 2007-11-30 17:11:01 EST
Description of problem: When creating a meeting, and including a LDAP contact that has a Free Busy URL as per RFC2739, the value is not used. Free Busy URLs in local contacts work fine. Version-Release number of selected component (if applicable): Evolution 2.0.2 How reproducible: Everytime Steps to Reproduce: 1. Create an LDAP contact with RFC2739 attributes and include a Free/Busy URL 2. Go to calendar, create a meeting and invite the LDAP contact 3. Go to the Scheduling tab - note how LDAP contact available time is not present Actual results: Avaliable time not present. Test URL to ensure the Free/Busy file is available. Tested with local contact, and confirmed working ok. Expected results: Additional info:
Hi - came across this bug again - any news? Obviously there aren't many people sufferring from the same problem. I'm on 2.0.4 now, and still have the same problem. Will likely upgrade to 2.2 soon to see if its fixed there.
Thanks for filing this bug report. I'm sorry it went for so long without apparent activity. Concerning the new evolution package, you'll also want to ensure that your evolution-data-server package is as up-to-date as possible too, as this contains the LDAP code. If you open the local and LDAP contacts in one of the contacts views and browse in the dialog to the "Personal Information" tab, "Web Addresses" section, there's a field for the Free/Busy URL. Is this getting populated for either type of contact? If this isn't fixed in the FC4 or rawhide versions of Evolution, the best way to make sure your problem will get looked on is to report it to the authors of the program. Most upstream authors use a bug tracking system like bugzilla, and more people who know the code will be looking at the bug report there. The upstream bug tracking system to use is: http://bugzilla.gnome.org/ Please make sure the bug isn't already in the upstream bug tracker before filing it.
Closing due to lack of response.