Comment 6 for bug 1888184

Revision history for this message
Christian Ehrhardt  (paelzer) wrote (last edit ):

Hi,
coming around cleaning older cases ...

Thanks everyone for the discussion!
On one hand I'm glad we managed to collect a bunch of log suppression and configuration workarounds. On the other hand it is sad that this seems to be mostly just "as it is" with no great way out (e.g. a fix in a later version one could try to backport).

After Bill outlined - out of the upstream Forum - that it is a known issue with likely no fix I'd say until there is any further insight how to address this in a package update there isn't much one can act on.

The bug will stay around and be helpful for anyone searching for the error message, but I'll set the task to incomplete until there is any change to the overall situation that allows to act and improve it.