On 2018-11-03 17:11:07 [+0000], Scott Kitterman wrote: > Does anyone still have this problem with 0.100.2? It's been out awhile and > this bug has gone quiet.
I would suggest to close it. I never had any luck to reproduce it. It may or may not be a problem but without any additional help to get a reproducer there is nothing that we can do to either fix it ourself or throw at upstream. I'm not sure if severity `critical' applies here after all. > Scott K Sebastian
