No response to bug #189571