Bug 704237

Summary: Can't create new calendar appointments
Product: [Fedora] Fedora Reporter: Peter Robinson <pbrobinson>
Component: evolution-mapiAssignee: Matthew Barnes <mbarnes>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: high    
Version: 15CC: mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-13 11:37:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
error dialog none

Description Peter Robinson 2011-05-12 14:10:37 UTC
Created attachment 498549 [details]
error dialog

with the latest version of evolution/evolution-mapi I can't create new appointments.

evolution-data-server-3.0.1-1.fc15.x86_64
evolution-3.0.1-1.fc15.x86_64
evolution-NetworkManager-3.0.1-1.fc15.x86_64
evolution-mapi-3.0.1-2.fc15.x86_64
evolution-help-3.0.1-1.fc15.noarch
samba4-libs-4.0.0-25.alpha11.fc15.x86_64
openchange-0.9-16.fc15.x86_64


I get the following errors on the terminal 

(evolution:1322): calendar-gui-WARNING **: comp-util.c:250: file e-cal.c: line 2226: assertion `priv->gdbus_cal' failed

(evolution:1322): libecal-CRITICAL **: file e-cal.c: line 3645: assertion `priv->gdbus_cal' failed

(evolution:1322): libecal-CRITICAL **: file e-cal.c: line 4041: assertion `priv->gdbus_cal' failed

(evolution:1322): libecal-CRITICAL **: file e-cal.c: line 1888: assertion `priv->gdbus_cal' failed

(evolution:1322): libecal-CRITICAL **: file e-cal.c: line 2226: assertion `priv->gdbus_cal' failed

(evolution:1322): calendar-gui-WARNING **: comp-util.c:250: file e-cal.c: line 2226: assertion `priv->gdbus_cal' failed

(evolution:1322): libecal-CRITICAL **: file e-cal.c: line 3645: assertion `priv->gdbus_cal' failed

(evolution:1322): libecal-WARNING **: Failed to dispose cal view: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface `org.gnome.evolution.dataserver.CalendarView' on object at path /org/gnome/evolution/dataserver/CalendarView/1838/17

(evolution:1322): libecal-WARNING **: Failed to dispose cal view: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface `org.gnome.evolution.dataserver.CalendarView' on object at path /org/gnome/evolution/dataserver/CalendarView/1838/19
(evolution:1322): libecal-DEBUG: e-cal.c:452: ECal GDBus connection is closed, remote peer vanished

(evolution:1322): libecal-WARNING **: gdbus_cal_disconnect: Failed to close calendar, GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface `org.gnome.evolution.dataserver.Calendar' on object at path /org/gnome/evolution/dataserver/Calendar/1965/1

(evolution:1322): libecal-DEBUG: e-cal.c:452: ECal GDBus connection is closed, remote peer vanished

(evolution:1322): libecal-WARNING **: gdbus_cal_disconnect: Failed to close calendar, GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface `org.gnome.evolution.dataserver.Calendar' on object at path /org/gnome/evolution/dataserver/Calendar/1965/2


(evolution:1322): libecal-WARNING **: Failed to dispose cal view: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.14 was not provided by any .service files
(evolution:1322): libecal-DEBUG: GDBus connection is closed, remote peer vanished

Comment 1 Milan Crha 2011-05-13 06:11:17 UTC
Thanks for a bug report. It usually means that your e-calendar-factory crashed. Could you run it under gdb from a console and repeat the issue, to see what it'll do, please? You can do that like this:
a) close evolution and make sure no e-calendar-factory is running
b) run calendar factory from a console like this:
   $ gdb /usr/libexec/e-calendar-factory --ex r --ex "t a a bt" --ex c --ex q
   which will run the factory, prints the state of the application in a case
   it crashed, and then either continues the process or quits gdb.
   Lines after "Server is up and running..." message will help.
c) run evolution from another console and reproduce the issue.

Thanks in advance.

Comment 2 Peter Robinson 2011-05-13 09:04:05 UTC
Hi Milan,

When I got in to the office this morning i discovered I had a couple of abrt back traces so I've submitted those (unsurprisingly both the same)

https://bugzilla.redhat.com/show_bug.cgi?id=704466

Comment 3 Peter Robinson 2011-05-13 11:37:57 UTC

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