Comment # 36 on bug 1046268 from
I can also confirm that a recent update to Leap 42.2 has also created this
problem on Leap 42.2.


You are receiving this mail because: