Evolution Calendar alarms are not displayed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evolution |
New
|
Unknown
|
|||
evolution (Ubuntu) |
Invalid
|
Low
|
Unassigned |
Bug Description
Binary package hint: evolution
1. 10.10
2. Evolution 2.30.3-1ubuntu7.1
3. I expected calendar alarms to display (at the requested time), as they have with all earlier versions of Ubuntu, i.e. in a pop-up window.
4. No display of alarms.
I have just upgraded to 10.10 from 10.04.1, using a fresh install of 10.10 in a re-formatted HDD, then adding /home via a grsync back-up, & Evolution settings via Evolution backup/restore.
My usage of Evolution is simple, only using mail, contacts & calendar, as supplied, no extras, no outside systems.
My contacts were OK.
Sending & receiving mail worked OK.
Previously recorded calendar events did not work immediately, but did on my next boot, perhaps because I had checked every possible setting.
However, the alarms do not display, whereas they have with all earlier versions of Ubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: evolution 2.30.3-1ubuntu7.1
ProcVersionSign
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Sat Nov 27 07:50:59 2010
ExecutablePath: /usr/bin/evolution
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: evolution
Changed in evolution: | |
status: | Unknown → New |
Changed in evolution (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Low |
I posted the following comment to #738982 on 29/05/11. It is my workaround for this problem.
Regards, Garry.
2 weeks ago, I upgraded to 11.04.
Again Calendar alarms would not work.
I checked file "/usr/lib/ evolution/ X.XX/evolution" . It had 2.32, but evolution/ 2.30/evolution" , which was the value used
the Evolution Alarm notifier in Start-up Applications was requesting to
run file "/usr/lib/
in 10.10, i.e. prior to the upgrade.
If I have the only installation that has this problem (presumably that
is why this bug expired), what could there be about my installation that
does not allow these 2 elements to be co-ordinated?
Regards, Garry.