I think it makes more sense to use bug 1946499 to track the issue happening in Ubuntu 21.10. The patches in this bug landed two years ago, so it would be confusing to reopen it.
I think it makes more sense to use bug 1946499 to track the issue happening in Ubuntu 21.10. The patches in this bug landed two years ago, so it would be confusing to reopen it.