Bug 16464

Description of problem: This is really starting to get to me...
I have emacs setup as my $EDITOR.  When I edit my crontab, sometimes it works; other times, the crontab comes up in emacs window and any attempt to make a change gives "Current buffer has no process"
The *Messages* buffer contains:
  File mode specification error: (wrong-type-argument processp nil)
  user-error: Current buffer has no process

I have no idea what triggers this behavior; but while it initially appears that I can't edit the file, I've just found a weird workaround...
While hitting most keys gives a beep and the above error message, I can delete a character in the file and then am able to input.  Another way is to use ^Q<anything> which accepts input.
After saving this modified buffer; the next edit may still have the problem or it may work normally again...

I understand this is not much to go on; but it happens quite often and I previously could not find workarounds, though it would just as mysteriously start to work again.

The other day, using 2 userids, I could make the problem appear/disappear just by issuing "crontab -e" from each. If userid1 then userid2 failed, issuing the commands from userid2, then userid1 would work.  Retested several times and the problem persisted -- until it mysteriously stopped.

Version-Release number of selected component (if applicable):  This has only ever occurred after upgrading to mga5.


How reproducible:  Random.  Still haven't found the trigger.


Steps to Reproduce:
1. edit a file with emacs (crontab seems most prone to this problem).
2.
3.


Reproducible: 

Steps to Reproduce: