The Evolution program crashed after I went to new calender and selected google. I then put in my google information so that I could have my google calender synced with evolution (version 3.2.0). Then all of a sudden an error message came up saying: "no backend factory for google vevent"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
evolution (Ubuntu) |
Invalid
|
Medium
|
Unassigned |
Bug Description
The Evolution program crashed after I went to new calender and selected google. I then put in my google information so that I could have my google calender synced with evolution (version 3.2.0). Then all of a sudden an error message came up saying: "no backend factory for google vevent"
1) Ubuntu 11.10
2) Evolution version 3.2.0
3) I expected my google calender to sync in evolution program
4) Instead an error came up saying: no backend factory for google vevent
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: evolution 3.2.0-0ubuntu2
ProcVersionSign
Uname: Linux 3.0.0-12-generic i686
ApportVersion: 1.23-0ubuntu3
Architecture: i386
Date: Wed Oct 19 12:09:57 2011
ExecutablePath: /usr/bin/evolution
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: evolution
UpgradeStatus: No upgrade log present (probably fresh install)
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.
If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.
If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit. apport/ apport- qt --crash- file=/var/ crash/_ my_crash_ report. crash in a terminal - where _my_crash_ report. crash is the crash you would like to report.
If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/
I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.