Bug 1370606

Summary:	Loops continuously when given -a option by root
Product:	[Fedora] Fedora	Reporter:	Jon LaBadie <jbug>
Component:	calendar	Assignee:	David Cantrell <dcantrell>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	24	CC:	dcantrell
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-08 16:50:20 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Jon LaBadie 2016-08-26 18:35:34 UTC

Description of problem:
I've been using calendar since my UNIX days, circa 1980.
If run nightly from root's cron with the "-a" (all) option, calendar will check for calendar files under each users home directory and sends the user email for
any soon to occur events.

I recently upgraded from Fedora 22 to 23, ran that for a week, and then upgraded to 24. These were done using the dnf "system-upgrade" plugin.

The first morning after the upgrade I found mailboxs full of emails from calendar, my mail server had over 400,000 undelivered messages in its queue, and calendar was still running.

After cleaning the mess up I determined that an ordinary user could run calendar from the CLI and it would function properly. I didn't check root as there was no calendar file in its home dir. Then, as root, I ran "calendar -a"
and interupted it (Ctrl-C) after a brief time. It had already looped over 50 times and I had another mess to clean up (much smaller).

Version-Release number of selected component (if applicable):
1.28-4.20140613cvs.fc24

How reproducible:
Only attempts described above, ocurred twice in two tries, once from cron and once from command line.

Steps to Reproduce:
1. Create ~/calendar files for several users with soon to happen events
2. run, as root, "calendar -a"
3.

Actual results:
Repeating duplicate emails from calendar to users about upcoming events.

Expected results:
Either zero or one email per user

Additional info:
My environment has only 3 users. The workaround is to create separate crontable "calendar" entries for each user.

Comment 1 Fedora End Of Life 2017-07-25 22:40:43 UTC

This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2017-08-08 16:50:20 UTC

Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.