This bug has been created based on an anonymous crash report requested by the package maintainer.
Report URL: http://faf.lab.eng.brq.redhat.com/faf/reports/bthash/774ec67a405f6ce3083d3a55d2876c2c5cc247b2/
The bug is present only in a package built from a master snapshot.
reopening as I've seen it again
Created attachment 1370049 [details]
[PATCH] settings: avoid assertion when deleting connections
(In reply to Beniamino Galvani from comment #5)
> Created attachment 1370049 [details]
> [PATCH] settings: avoid assertion when deleting connections
I generally think it's a bug (misfeature) that we might re-add a connection -- and the need to clear the "removed" flag. Optimally, a connection instance doesn't get reused after being removed once.
According to a9384452ed61ca3f1c6e1db175f499307da9c388, it's due to the NM_CONTROLLED=no instances. I think we shouldn't create such pseudo instances just to track the unmanaged-spec. IOW, we should drop create_unhandled_connection().
Can you add a "FIXME:" comment to nm_settings_connection_added() that this shouldn't really happen bug might?
the patch lgtm for the moment.
Added comment and applied to master:
Backported to nm-1-10 as well.
I can still see this, was it fixed?
is it a duplicate?
The stack trace at http://faf.lab.eng.brq.redhat.com/faf/problems/bthash/?bth=4872a3cccce41d5dbcd7180cf735487c9254c089 :
is different from the original one:
Can you file a new bug entry?
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.