there's a similar bug on the upstream tracker: https://sourceforge.net/p/lxde/bugs/634/. it seems to me that the issue can happen for several reasons, none of which have to do with lxsession itself. however, i think that how lxsession handles logs makes no sense.
there's a similar bug on the upstream tracker: https:/ /sourceforge. net/p/lxde/ bugs/634/. it seems to me that the issue can happen for several reasons, none of which have to do with lxsession itself. however, i think that how lxsession handles logs makes no sense.