Comment 2 for bug 2018660

Unfortunately, it also happens with a new (default) library. Would it be possible for you to test it with a virtual (or real) machine on Kubuntu 22.04? Or would it be possible for me to try to pinpoint which code change is responsible for the behaviour in my system?