I have figured out that this happens if the account with which you login into LXDM isn't loged in before. If I login with the console first and then with LXDM the problem doesn't happen anymore (this is why the "restart lxdm" workaround worked).
I have figured out that this happens if the account with which you login into LXDM isn't loged in before. If I login with the console first and then with LXDM the problem doesn't happen anymore (this is why the "restart lxdm" workaround worked).