Comment # 17 on bug 1206500 from Friedrich Haubensak

any progress on this issue and how best to avoid these nasty messages?

obviously the current problem was introduced by suse patch 2022:4499; would be
helpful if bsc#1179465, linked in the announcement, would be accessible to see
what exactly the patch was supposed to solve, and to find a reasonable work
around for the current problem.