On 22.02.2017 20:33, Yves-Alexis Perez wrote: > Then please identify which update started it, because right now I don't have > any idea what happened. It certainly not reproducible on any box I have.
Not sure how to do that, but I replaced lxdm with lightdm again and the problem persists. What can I do to get to the root of the problem? Best, Sebastian
