I changed my gpu profile to nvidea. I have a gnome plugin that adds an option for this in the dropdown menu where wifi, bluetooth, … is located aswell. After rebooting I can’t login anymore. If I type in my password I just go bach to profile selection.
If this plug-in you’re mentioning[1] is causing the issue, you could switch to a tty console (with Ctrl+Alt+F2) and from there disable user-enabled extensions with:
gsettings set org.gnome.shell disable-user-extensions true
Then switch to GDM (with Ctrl+Alt+F1 or reboot) and try to log in again. If it’s working, then re-enable extensions without the one causing the issue.
If the above is not working, you could also try to reset the dconf database:
dconf dump / > ~/Documents/dconf.backup # Back up the dconf db
dconf reset -f / # Reset the whole db
If this works, you would have to perform several GNOME-specific configurations again.
Could you detail what it is and what it actually does? ↩︎
So I just figuered out 5 minutes ago that the reason I can’t acces my account is that I don’t have permission to my home directory anymore. I can’t figure out how to give myself permission.
What is the output of ls -laZ $HOME?
What operations did you perform that you consider this could be the issue?
If i do ctrl + alt+ f2 and I log in I get “/home/senne: change directory failed: Permission denied”
This is the output of the command
This seems rather an SELinux issue.
In order to boot into a graphical session and try to find out what did cause the loss of security contexts, you can temporarily boot with SELinux permissive mode (by editing the GRUB entry and adding the kernel args enforcing=0 at the end of the line beginning with linux).
Afterwards you can relabel the entire filesystem (or only the home directory if the issue is only there) by running the command sudo fixfiles -F onboot and rebooting.
But it would be advisable to find out what is it that caused this.
1 Like
It dien’t change anything.
Then try to run from tty console sudo fixfiles -F onboot and reboot. The boot process should take more than a usual boot.
It took longer and said it was doing it’s thing, but in the end nothing changed
Then maybe the issue is connected to NVIDIA, and SELinux was a red herring. What is the “plug-in” you’ve been referring to in the OP?
Do you have rd.driver.blacklist=nouveau and modprobe.blacklist=nouveau as boot parameters in GRUB’s menu entry? Can you boot with them removed?
In the meantime someone more experienced with NVIDIA drivers might chime in.
That worked ty! I swear, next time I buy a laptop I will pick an amd gpu.
1 Like
There are really no issues in setting up systems with NVIDIA GPU that can’t be solved. One only has to go the recommended route. Should you want to set it up properly, please have a look at RPM-Fusion’s HowTo.
You can come back here (maybe opening a new topic) in case you encounter issues with the setup. Add the output of inxi -Fzxx to such a post.
Also, in order for others to find your issue in case they experience something similar, could you confirm this is the extension you’ve been using?
yes, it is.