What line in which file?
You haven’t said anything about which desktop/WM session you are trying to log into.
Anyway, it seems you are doing the opposite of what was needed, IIUC (with more info, it would be a better assumption).
When you want to use a DM for login, you don’t need/use .xinitrc, since a DM is using any installed session files.
If you login from TTY, then you need/use .xinitrc.
ls -an "$HOME" | grep -v "^d"
grep . "$HOME/.dmrc"
grep . "$HOME/.xprofile" 2>/dev/null
ls -l /usr/share/xsessions/
I have no idea what you have been messing with but hopefully you can straighten that out and then add the following kernel parameter at boot to test. If it works then you could add it to the default grub command line permanently and also update grub after.
ok uh I installed nvidia package and wrote ibt=offin grub permanently.
Gave up and restored timeshift snapshot. System was up running before I messed up with the copied .xinitrc file in home folder and pacman update. Nope. Idk why it still persist after timeshift restore so I’m gonna get it a clean reinstall.
You have marked it as solved after a package update. Was this by mistake, or just trolling ?
There is much info you haven’t shared about your system, so everyone makes different assumptions.
Was this system ever working?
Was this user account/session ever working?
Did you implement a user/local nvidia setting?
Have you modified your user group, or anything on your user account?
It seems the group ID is not same with user ID.
There is a nvidia-settings-rc file in your $HOME.
The error messages suggest there might be a permissions problem, but not sure.
Restoring a snapshot does not (normally) restore user folders contents.
I agree with all that you are saying. I am not an expert and it makes things difficult when users don’t share all the information and also the information that is necessary to make some kind of determination. It is only solved based on my assumptions because I’m guessing at a lot of things based on reading through the lines. I’ll be the first to admit there is a lot i don’t know but i try to use what i do know to help. That is difficult when having to guess at what’s really happened to cause the problem. I’m glad that the user has got it working again. If it was restored and still didn’t work then most likely it was more of a problem.