maemo.org Bugzilla – Bug 6909
Calendar launches automatically at 4:00 each night
Last modified: 2010-05-27 17:42:49 UTC
You need to
before you can comment on or make changes to this bug.
SOFTWARE VERSION: 1.2009.42-11
EXACT STEPS LEADING TO PROBLEM:
1. Make sure calendar is set to remove items older than 1 month
2. Boot device
3. Don't launch any apps (especially not the calendar)
4. Set clock to a few minutes before 4:00
5. At 4:00 the calendar now launches automatically
Calendar should not automatically launch at any time
Calendar launches at 4:00 when you have it set to remove items older than 1
Always. But as soon as you set "remove old items" to "never" it stops
happening. Put it back to "remove items older than 1 month" and it continues
happening. This also appears to happen every night at exactly 4:00 - not just
the first night after rebooting.
EXTRA SOFTWARE INSTALLED:
The device is retail hardware and the software that came with it. I have not
installed any 3rd party apps on it nor do I have any strange configurations. No
calendar synching is configured.
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_8; en-us)
AppleWebKit/531.21.8 (KHTML, like Gecko) Version/4.0.4 Safari/531.21.10
Thanks for reporting this.
For future reference, please use the internal bug database directly if you have
access to it.
This has been fixed in package
which is part of the internal build version
(Note: 2009/2010 is the year, and the number after is the week.)
A future public update released with the year/week later than this internal
build version will include the fix. (This is not always already the next public
Please verify that this new version fixes the bug by marking this bug report as
VERIFIED after the public update has been released and if you have some time.
To answer popular followup questions:
* Nokia does not announce release dates of public updates in advance.
* There is currently no access to these internal, non-public build versions.
A Brainstorm proposal to change this exists at
Setting explicit PR1.2 milestone (so it's clearer in which public release the
fix will be available to users).
Sorry for the bugmail noise (you can filter on this message).
*** Bug 9690 has been marked as a duplicate of this bug. ***
Confirming as fixed in PR1.2.