Comment 6 for bug 1891785

Hello gregrwn and thanks for confirming those threads are about this very issue.

There's certainly place in Launchpad for upstream bugs, provided that they're recognized as such. In this case it doesn't seems that upstream recognizes the new behavior as a bug (this is why in comment 4 I refer to it as an "upstream change", and not to an "upstream bug"). Given that upstream doesn't recognize the change as a bug, and that the change doesn't affect Ubuntu users so badly to justify permanently diverging from upstream to make the package behave differently from what upstream intended, it is difficult to consider this "a bug in Ubuntu".

I think the most appropriate status for this report is Opinion ("Doesn't fit with the project, but can we discussed"). This is not to dismiss your report, but rather not to set false expectations.