[CCPPETMR/CCPPETMR_VM] current VM screen lock comes on too soon (#80)
David Atkinson
Screen lock comes on too soon and sirfuser does not appear to have permission to change time to lock.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
Kris Thielemans
typing the following in the terminal disables it
gsettings set org.gnome.desktop.screensaver lock-enabled false
gsettings set org.gnome.desktop.screensaver idle-activation-enabled false
@paskino, can this be added at creation time?
Kris Thielemans
actually, what the above does is make sure you don't have to type the password. the screensaver still comes on. could just increase the delay I guess.
Edoardo Pasca
By the way, I'm quite surprised this is an issue at all.
Maybe I forgot to run first_run.sh?
Kris Thielemans
not sure how we could check if you ran it.
would this explain #78?
Edoardo Pasca
Possibly. I'll do that now and upload again.
When you do too many things together...
Kris Thielemans
not sure if it's worth uploading now? There's a few other VM issues that need sorting out as well. Depends on how much effort this is for you.
Edoardo Pasca
One obvious way to check if I'd run it is to see if the cursor is large. It is large in my VM. So I've run the first_run.py script.
Kris Thielemans
yup. large in mine as well. Also a bunch of portuguese etc languages installed (but not UK English). I guess you'll have to create a new one from scratch and just check it yourself (did you put the virtualbox (attempted) fixes in?)
Kris Thielemans
running update_VGA.sh myself seems to have fixed my VM. I've rebooted it about 6 times without trouble. hard to be sure of course.
can others please try the new VM, run updateVGA.sh and then use it for a while, restart etc. We could just tell users to run update_VGA.sh after installation.