Hi All Master, my Pc with Zorin Os 17.3 Core would not auto sign-in after Pc starts anymore. I wonder if it is due to the few updates that were going on and there is 1 update that failed [attached photo] which would display a notification every time when the Pc start.
I have tried to the followings in setting,
Reset password.
Turn-off auto sign-in & restart. Then turn-on auto sign-in again & restart
Delete all the keys that are at Utilities> Passwords & Keys
Hi Aravisian, once again thank you for your quick reply.
Well, the update failure is not a big concern. It is booting up the PC & opening of Apps that do not need to key-in password would be my primary reason for this query.
Please tell me how to do this?
Are you asking about how if you launch Chromium Based browsers like Chrome or Brave, that they ask for the keyring to be authenticated?
If so, elevating to root, then navigating to /usr/share/applications and opening the .desktop file for your browser and changing the Exec line to:
As Zorin 17 is a fork of Ubuntu 22.04, Brave A.I. suggests:
Autologin Not Working Ubuntu 22.04
If you're experiencing issues with enabling automatic login on Ubuntu 22.04, there are several potential causes and solutions. One common issue is that the autologin option in the settings might not persist, which can be resolved by manually editing configuration files. For example, you can edit the /etc/gdm3/custom.conf file to enable autologin by adding the following lines:
After making these changes, save the file and reboot your system If you're using a different display manager, such as LightDM or SDDM, the configuration steps may vary. For LightDM, you can create a file in /etc/lightdm/lightdm.conf.d/ with the following content:
For SDDM, you might need to edit /etc/sddm.conf or create an auto-login.conf file in the appropriate directory Additionally, if you're using a server edition of Ubuntu, you might need to configure the getty service to enable autologin. This involves creating a service file in /etc/systemd/system/getty@tty1.service.d/override.conf and specifying the user to autologin If these steps do not resolve the issue, it might be helpful to check the system logs for any errors related to the display manager or authentication process.