After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 233156 - Do not get resource is busy error for all day meetings
Do not get resource is busy error for all day meetings
Status: RESOLVED INCOMPLETE
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
1.1.x
Other All
: Normal minor
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
Depends on:
Blocks: 327514
 
 
Reported: 2002-11-01 19:34 UTC by Tim Lee
Modified: 2012-02-02 14:39 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Tim Lee 2002-11-01 19:34:19 UTC
Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:
When scheduling an all day meeting with a resource, if there is a conflict
with an already scheduled meeting in the resource's Calendar you don't get
an Error message "The resource 'blah@blah.com' is busy...". The resource
just has a Needs Action status.

Expected Results:
Should get an error when sending invitation

Additional Information:

Machine Configuration
------------------------------------------------------------------
Linux tlee.boston.ximian.com 2.4.18-3 #1 Thu Apr 18 07:37:53 EDT 2002 i686
unknown
soup-0.7.8.99-snap.ximian.200210280701
libgtkhtml20-1.0.4-2.ximian.1
libgal19-0.19.1-2
libgal20-0.21-0.ximian.1
gtkhtml1.1-1.1.5-0.ximian.1
gal-0.21-0.ximian.1
evolution-1.1.90-0.ximian.1
ximian-connector-1.1.90-0.ximian.1
gnome-pilot-conduits-0.10-1.ximian.1
pilot-link-0.11.5-1.ximian.3
gnome-pilot-0.1.66-1.ximian.1
gnome-pilot-applet-0.1.66-1.ximian.1
Comment 1 André Klapper 2012-01-04 12:33:16 UTC
Note that the package "evolution-exchange" is deprecated nowadays. Similar
functionality is now provided by "evolution-mapi" and "evolution-ews" packages.

This bug was reported against a version that is now not supported anymore.
Could you please check if the problem that you reported here still happens with
a recent version of Evolution (like 3.2 or 3.0) AND with either evolution-mapi
or evolution-ews? Thanks in advance!
Comment 2 André Klapper 2012-02-02 14:39:51 UTC
Closing this bug report as no updated information has been provided.

Please reopen this bug if the problem still occurs with a newer version of Evolution (currently this means: preferably version 3.2.x) and provide the information that was asked for in the previous comment.

Again thank you for reporting this bug and we are sorry it could not be fixed for the version that you originally used when reporting this problem.