Accepting calendar invitations fails with "Unable to send item to calendar '<calendar-name>'. No such interface `org.gnome.evolution.dataserver.Calendar' on object at path /org/gnome/evolution/dataserver/Calendar/12376/19"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
evolution (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
When clicking "Accept" button on incoming calendar invitation the first click does nothing. Second click on the "Accept" button gives an error message "Unable to send item to calendar '<calendar-name>'. No such interface `org.gnome.
An interesting finding is that before accepting calendar invitation the e-calendar-factory process was running with PID 12376:
uomjarv@L343:~$ ps -aef | grep evolution
tuomjarv 2314 1 0 Oct21 ? 00:00:13 /usr/lib/
tuomjarv 2421 1856 0 Oct21 ? 00:00:13 /usr/lib/
tuomjarv 2596 1 2 Oct21 ? 01:59:30 evolution
tuomjarv 12376 1 0 10:54 ? 00:00:00 /usr/lib/
tuomjarv 12441 11483 0 10:56 pts/1 00:00:00 grep --color=auto evolution
After clicking the accept button the e-calendar-factory process seems to be running with PID 12446:
tuomjarv@L343:~$ ps -aef | grep evolution
tuomjarv 2314 1 0 Oct21 ? 00:00:13 /usr/lib/
tuomjarv 2421 1856 0 Oct21 ? 00:00:13 /usr/lib/
tuomjarv 2596 1 2 Oct21 ? 01:59:31 evolution
tuomjarv 12446 1 0 10:56 ? 00:00:00 /usr/lib/
tuomjarv 12451 11483 0 10:56 pts/1 00:00:00 grep --color=auto evolution
Perhaps e-calendar-factory crashes when adding calendar entry to the calendar?
The calendar in question is a google calendar.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: evolution 3.2.1-0ubuntu1
ProcVersionSign
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelMo
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
Date: Mon Oct 24 10:48:06 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: evolution
UpgradeStatus: Upgraded to oneiric on 2011-10-19 (5 days ago)
Status changed to 'Confirmed' because the bug affects multiple users.