I am unable to login to Zorin after entering my Usual password which hasn't changed. After entering the password, it looks as if it is about to load the desktop and then the screen resets and it is prompting for my password again.
If I click on my Username, then on the settings cog and select "Login to Zorin with Xorg", I can see the desktop loading but my dock driver's etc don't work. Instead, I would like to use the default option of "Login with Zorin Desktop" which has just stopped working.
I do get a password error when I type my password wrong (which I did as a test). I searched the forums and similar issues have happened but not similar enough Well just didn't have luck finding the solution.
I know it is a simple thing, but we have had a few cases where NumLock has switched on the keyboard integrated numeric keys and caused login and other typing errors.
Note: Linux is sensitive to CAPS and lower case characters.
Understand it's a perfectly valid question to ask if you can't login, however I did point out that I can login using Xorg desktop setting and that there is no password error unless I deliberately type the wrong password.
Unrelated issue means I had to wipe my install anyway so we'll never know what the root cause was but I can promise it was not my CAPS LOCK, keyboard language or me fat fing*ring anyting
For future reference refer to my login loop solutions in the unofficial manual for Zorin 17 Core. I was going to suggest possible .Xauthority file corruption but because your issue relates to Wayland I don't know an answer to that.
Checkout this askubuntu thread:
Here is an interesting Brave A.I. answer:
how to resolve login issues on wayland
Based on the provided search results, it appears that login issues on Wayland can be attributed to various factors, including user configuration, proprietary NVIDIA drivers, and graphics card compatibility. Here’s a step-by-step approach to resolve login issues on Wayland:
Check user configuration: As mentioned in the first search result, the .config folder, specifically the dconf subfolder, might be causing the issue. Try renaming or deleting the .config/dconf folder and see if that allows you to log in to a Wayland session.
NVIDIA driver compatibility: If you’re using proprietary NVIDIA drivers, they might not be compatible with Wayland. Consider switching to open-source Nouveau drivers or using the NVIDIA binary driver with Xorg (x11) instead of Wayland.
Graphics card compatibility: Ensure your graphics card is compatible with Wayland. If you’re using a proprietary GPU, check for any known issues or limitations with Wayland support.
Verify Wayland session configuration: Check the wayland-session.log file for any errors or issues. You can find this file in your system’s log directory (e.g., /var/log). Look for messages related to your graphics card or driver versions.
Package updates: Ensure you’re running the latest packages for your distribution. Check the package manager for updates, especially for graphics-related packages like pixman.
Test with a different user account: As mentioned in the first search result, creating a new user account and logging in from there might help identify if the issue is specific to your current user account.
System log analysis: Review your system logs for any errors or warnings related to Wayland, Xorg, or your graphics card. This can help you pinpoint the cause of the issue.
Remember to be cautious when modifying system files or configuration, as this can potentially break your system. Make sure to create a backup before attempting any changes.
Here’s a code snippet illustrating the process of renaming the .config/dconf folder (in bash):
sudo mv ~/.config/dconf ~/.config/dconf.bak
This command renames the .config/dconf folder to .config/dconf.bak (backup) to temporarily disable its contents and allow you to log in to a Wayland session. After resolving the issue, you can restore the original folder by reversing the command:
sudo mv ~/.config/dconf.bak ~/.config/dconf
Keep in mind that this is a specific solution for the provided scenarios and might not apply to all Wayland login issues. If the problem persists, further troubleshooting or seeking expert advice might be necessary.
Well just didn't have luck finding the solution.