Looks like this has been fixed in g-s-m 2.23.5-0ubuntu1 :-). I now get bug #248683 instead, but that was expected.
Looks like this has been fixed in g-s-m 2.23.5-0ubuntu1 :-). I now get bug #248683 instead, but that was expected.