bug #1840508 looks like the same report. Let's close this one since the error tracker reference has no report since 17.10 which suggests that even if the error is similar that was probably a different problem
bug #1840508 looks like the same report. Let's close this one since the error tracker reference has no report since 17.10 which suggests that even if the error is similar that was probably a different problem