Skip to content
This repository has been archived by the owner on Aug 20, 2022. It is now read-only.

current VM screen lock comes on too soon #80

Closed
DANAJK opened this issue Apr 22, 2018 · 9 comments
Closed

current VM screen lock comes on too soon #80

DANAJK opened this issue Apr 22, 2018 · 9 comments

Comments

@DANAJK
Copy link
Contributor

DANAJK commented Apr 22, 2018

Screen lock comes on too soon and sirfuser does not appear to have permission to change time to lock.

@KrisThielemans
Copy link
Member

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?

@KrisThielemans
Copy link
Member

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.

paskino added a commit that referenced this issue Apr 24, 2018
@paskino
Copy link
Contributor

paskino commented Apr 24, 2018

By the way, I'm quite surprised this is an issue at all.
Maybe I forgot to run first_run.sh?

@KrisThielemans
Copy link
Member

not sure how we could check if you ran it.
would this explain #78?

@paskino
Copy link
Contributor

paskino commented Apr 24, 2018

Possibly. I'll do that now and upload again.
When you do too many things together...

@KrisThielemans
Copy link
Member

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.

@paskino
Copy link
Contributor

paskino commented Apr 24, 2018

One obvious way to check if I 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.

@KrisThielemans
Copy link
Member

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?)

@KrisThielemans
Copy link
Member

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.

@paskino paskino closed this as completed in 54126d3 May 9, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants