I have been having a conversation on the openSUSE forums about logouts

I'm not sure who is the best group to discuss this so I'll do it in both.

Here is the scenario I described in the openSUSE

....

A teacher goes into a shared teaching room
Then logs on and opens a number of apps
One of these is SIMS ( if you don't work in a school - it contains all the students details, educational, personal, home issues etc )
The teacher then clicks logout and gets up and leaves the room
//// here is where you say they should have closed all the open apps and check that the logout was successful ////
Maybe because teachers are 'different' or they were distracted or they assumed clicking on logout did actually do that
Now app 'someapp' cancels the logout but the teacher doesn't notice or doesn't check
Next period the room is used by students as a study room or a form room
Suddenly every student gets an A* in every subject, the whole school finds out that student X attempted suicide and then we all go to prison for massive GDPR breach.

Not good

There should be a way that logout means logout even if that means that open files just get dumped


Any thoughts anyone

Ta

Mal

I agree that even in single-user setups it is a little frustrating if I try to restart (to apply updates, for example), walk away expecting it to run through the reboot sequence and come back with it ready for me to log back in again only to be presented with a Save This dialog when I get back.

If there isn't a reliable way to shut everything down, it should at least lock the session after a timeout so that only said user can unlock it and finish actually logging out if need be; while still allowing other users to open separate sessions.