open the Zorin menu >> click System Tools >> right click Software and add to desktop
right click the desktop shortcut and select properties
in the box labelled 'command' add 'pkexec ' before 'gnome-software %U'
But when I select properties, there is no box labeled "command". What I see instead is "basic", "permissions" and "open with". Under "basic" I see "org.gnome.Software.desktop", so I'm guessing that this is the "command" box.
How do I adapt the previous solution to get rid of password prompts? Or is there another way to do that? I don't need prompts because I'm the only one that uses my computer, I'm in a rural area so there aren't any neighbors that can see my internet, and I can't see any reason for security that I don't need.
I think the "solution" you linked was probably for a somewhat older version. I am in the same situation as you: my non-portable desktop computer is only accessible to my wife and me. I've tried several so called solutions but none of them were effective. I just have to put in a keyring password when I restart and an authentication password once in a while when I do something the system thinks needs more security. I decided to just live with it because there are so many plusses to using Zorin over windows.
I don't want to have to give a password when I turn on my laptop or when I leave and come back. I also don't want to have to give a password every time I use the terminal.
For this, You can activate Automatic Login like @Aravisian already wrote. You can find that in the Settings and there the User Settings. First, you have to unlock in the upper right Corner and then, you can activate the toggle for Automatic Login:
The Terminal Thing is a different Situation. The Passoword is asked because for Permission but when You type it in one Time and the Terminal stays open, You don't have to type it in again.
That doesn't seem reasonable. Even "autologin" doesn't login, which makes me wonder why it's called "autologin" to begin with.
There has to be a way. Someone, somewhere, must have written a small program to do this. Yeh, yeh, Linux is supposed to be more secure, but the level should be up to the user. I wish I could remember how to program in C so I could do it myself, but those days are long gone.
Is there a way to set the system to not sleep for 4 or 6 hours? That might help.
Another thing I tried was using gsettings set org.gnome.settings-daemon.plugins.power lid-clos-battery-action 'nothing' but it still put it in sleep mode.
It is reasonable. What you are describing is a catch-22 for a developer.
On Any OS, including Mac or Windows, it is covered with Admin Password requests.
End Users want Security, but do not want to have to do any actual work like popping in a small password. Gotta cut your losses. You cannot expect developers to meet both conflicting demands.
If you close the lid and the computer does not sleep, the battery dies.
Yes, you can leave a notebook computer plugged in and yes, disable sleep when closing the lid - by default, the developers will set it to preserve battery life.
sudo nano /etc/systemd/logind.conf
Uncomment and set to ignore: HandleLidSwitch=ignore
Has someone out in the wilds made a script that allows them to bypass all password requests? Yes. With some searching, I am sure you can find some.
But for me, it is a catch-22 to detail in a thread how to bypass passwords.
Actually, I set my Windows 10 to never ask for a password. I haven't used a password for a very long time.
Seems reasonable to me since I live in a rural area and no one else sees my wifi, I don't take my laptop anywhere, and I'm the only person in the house.
With autologin set to ON you should not have to log in manually on restarting. However note what @Aravisian said above: apparently that doesn't apply when recovering from sleep. You should be able to avoid going into sleep mode on closing the lid by going into settings/power but like he said that's probably not something you want to do unless always plugged in. I don't have that issue because my computer is a desktop machine which is always plugged in and no lid to close. You'll probably need to just live with some measure of entering passwords.
We can become focused on a goal, and lose sight as to whether the goal is worthwhile. I know I can, at least.
The simplest method would be to create a short or empty password, using the method I outlined above to remove the strict 8 character min length, then set a new password as a short PIN or even blank, so the user only need to bap the submit button or enter key upon a prompt.
But bypassing the prompt has risks that are not just limited to security.
