Ubuntu
evolution-exchange package

Unable to book a resource using Attendees dialog

Bug #187723 reported by Bill Gjestvang
40
This bug affects 6 people
Affects Status Importance Assigned to Milestone
evolution-exchange
New
Undecided
Unassigned
evolution-exchange (Ubuntu)
Confirmed
Low
Unassigned
Declined for Lucid by Sebastien Bacher
Declined for Maverick by Sebastien Bacher

Bug Description

Binary package hint: evolution-exchange

I get "Unable to book" failures while trying to book a resource, such as a conference room. This is repeatable.

Steps:
-On the calendar, click "New Meeting"
-Click the "Attendees..." button
-Search the GAL (global address list) for the conference room I want
-Select the conference room and click the "Add" button under "Resources"
-The conference room appears in the Resources list
-Click "close" to get back to the new meeting window
-The conference room is in the attendees list as a "Non-Participant"
-Go to "Free/Busy" and select an open time slot
-Add a meeting Summary, and click Save
-On the popup that asks whether you'd like to send invitations, click Send.
-A popup says "Unable to book". Click OK
-The meeting shows up in my calendar, with the resource, but the resource doesn't know about it.
-I know the resource wasn't busy, because I can go to Outlook or OWA (Outlook Web Access), and modify the meeting (delete and re-add the resource), and the resource gets booked fine.

If I don't use the "Attendees..." button and dialog box, but just the "Add" button in the main New Meeting dialog box, that seems to work OK. I add the conference room as a "Non-Participant" (which is extremely non-intuitive; but there is no "resource" option there).

Revision history for this message
Bill Gjestvang (bgjestvang) wrote :

The versions used were the current gutsy versions:

evolution-exchange 2.12.0-0ubuntu1

evolution 2.12.1-0ubuntu1
evolution-common 2.12.1-0ubuntu1
evolution-data-server 1.12.1-0ubuntu2
evolution-data-server-common 1.12.1-0ubuntu2
evolution-plugins 2.12.1-0ubuntu1
evolution-webcal 2.12.0-0ubuntu1

Revision history for this message
Bill Gjestvang (bgjestvang) wrote :

This still happens with the current gutsy code:

evolution 2.22.2-0ubuntu1.2
evolution-common 2.22.2-0ubuntu1.2
evolution-data-server 2.22.2-0ubuntu1
evolution-data-server-common 2.22.2-0ubuntu1
evolution-exchange 2.22.2-0ubuntu1
evolution-plugins 2.22.2-0ubuntu1.2
evolution-webcal 2.21.92-0ubuntu1

Revision history for this message
Bill Gjestvang (bgjestvang) wrote :

Setting to "confirmed" because it's repeatable, with the full procedure to reproduce it.

Changed in evolution-exchange:
status: New → Confirmed
Revision history for this message
Slick (slick666) wrote :

I'm able to repeat it as well

GNOME evolution 2.22.3.1

I know it's something that has worked in the past but now does not. I'm not able to determine which update broke it.

Revision history for this message
Kyle Guilbert (kguilbert) wrote :

Repeatable in Jaunty, using evolution version 2.26.1-0ubuntu1.

Revision history for this message
rod singleton (rod40cool) wrote :

Agree, not working in Jaunty 2.26.1-0ubuntu2 either...

Revision history for this message
rod singleton (rod40cool) wrote :

Sorry I retract that.
I have a different bug but with the same message. I'm using a Google calendar, not Exchange.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your report, that's something to send directly upstream at http://bugzilla.gnome.org by someone having the issue, for forwarding instructions please read http://wiki.ubuntu.com/Bugs/Upstream/GNOME, Thanks in advance.

Changed in evolution-exchange (Ubuntu):
importance: Undecided → Low
Revision history for this message
Peter Kelder (peter-kelder-quicknet) wrote :

Experiencing the same problem.
We are running a Open Desktop pilot based on ubuntu within a large company and this functionality is fital to us.

Revision history for this message
Peter Kelder (peter-kelder-quicknet) wrote :

See the importance is currently low.
Although from a technical or home user point of view this kind of functionality seems to be low priority, it is vital to large organisations. If open desktop Ubuntu wants to gain enterprise adoption this kind of functionality has handled with higher priority.

Revision history for this message
Juanjo Vázquez (juanjo-vazquez) wrote :

Same problem for me. Agreed this feature is greatly important in an enterprise environment. Please increase the priority!. Thanks.

Revision history for this message
Juanjo Vázquez (juanjo-vazquez) wrote :

Sorry, I forgot to add my environment:

GNOME Evolution 2.28.1

Linux 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 17:01:44 UTC 2009 x86_64 GNU/Linux
Ubuntu 9.10 Karmic Koala

Revision history for this message
Prostar (tsmith-z28) wrote :

I would like to add a "me too". This is very important in the work environment. I didn't know there was a work around, and have had to adjust meetings in OWA. This is very embarrassing when trying to convince co-workers that my Linux is just as good in the workplace (coupled with all the Evolution-OWA screw ups).

Ubuntu 9.10 (Karmic Koala)
2.6.31-20-generic i686
Gnome
Evolution 2.28.1

Revision history for this message
file offset (fileoffset) wrote :

I am getting the same error however it is when I receive a Meeting Request from a fellow employee.

I click 'Accept' in the Meeting Request and get an 'Unable to Book' error message.

Versions:

Ubuntu 10.0.4 Beta 2
2.6.32-19-generic x86_64
Gnome
Evolution 2.28.3

Revision history for this message
Andreas Göransson (andgoransson) wrote :

Also getting "Unable to book" when I accept a meeting request.

Versions:
Ubuntu 10.04 LTS
Evolution 2.28.3

Revision history for this message
Andreas Göransson (andgoransson) wrote :

Could possibly be related to this bug:
https://bugs.launchpad.net/evolution-mapi/+bug/361993

I guess that the booking request does not get sent because of that bug.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.