If you try to start a session and there is no space left, the screen will blink
for a moment and it will present you the logging screen again.

I think some kind of error (instead of crashing?) would be pretty handy :)

Not sure if this is the right package for this...

Thanks!

No space left where? Honestly, I don't think it's the role of the login
manager to remember you to do the basi sysadmin tasks.

Regards,

not sure who is in fault... the device had a very small disk and basically
a / partition

Its my belief that the dm is in charge of inform the user of problems
during the login, even if this erros are generated by another layer

What layer do you think should report this error if at all, Yves ?

Basically what i am asking with this bug is, should this error be reported
to the user by the DM or not at all and let the user put this puzzle
together by themselves as any aceptable and responsible grown up should be
able to do anyway??

Regards


On Sun, Jul 19, 2015 at 9:38 PM, Yves-Alexis Perez <corsac@debian.org> wrote:

Yes. There's so many things which won't work if you can't write to the
disk that it's not possible to handle them soundly.

Sorry, for the snarky comment... Debian as a whole feels overcritical at
times and I just snapped :P


So many things wont work without space, but everything worked up to the
point of login... and wont work afterwards. That looks like a good point to
inform the user about the problem

I dont expect the dm to check for space all the time, but whatever layer is
failing, the session in this case, will report an error (or crash? i dont
really know what is happening) and the dm will take over again. I dont feel
we are being too friendly with the user if we show them an error for a very
common problem

Handling it soundly would be to recover. Or to be able to get the error
from the session or possible a third thing i dont know about

That would be nice, but I dont expect that. I expect a one line check for
space that will get 80% of the benefits with 1% of the time of a proper
solution

I wont defend this any longer tho... If you still disagree, please close
this bug

thanks for maintaining lightdm!