Description of problem:
There is a bug in NM DHCP code that causes a duplicate removal of the same event source. Most of the times this generates a warning (or a crash if debug=fatal-warnings is enabled in NM configuration), but since source events are indexed by id, it is possible that we remove an unrelated event source with the same id, which would be very bad.
The fix is trivial and is already merged upstream:
Version-Release number of selected component (if applicable):
Always when there is a dispatch error in the DHCP client.
FAF crash report:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.