I recently deleted my ~/.config/dconf directory to try and reset my Ubuntu GNOME to its defaults (link to the post here). It worked but led to its own set of issues.
After I boot into Ubuntu, I don’t get my login page. It directly opens up my desktop and I get this “The login keyring did not get unlocked when you logged into your computer”. Typing my password out unlocks it.
Remmina automatically opens by itself at the start.
Some of my applications like ProtonVPN, GNU Octave got removed. I had a hard time reinstalling ProtonVPN as some parts of it were installed and others weren’t.
I find some new applications like Rhythmbox. There weren’t present when I initially installed Ubuntu. I didn’t choose the extended installation.
How should I proceed? Also, I can solve some of these issues separately, but I believe unless I address the central issue that’s causing them all, problems like these will keep on popping in the future. Is this a sound approach to troubleshooting Ubuntu issues? Thanks.
This is normal expected behavior when you set GDM to auto login. When you log in manually you type your password into the field and gdm will hand that to the keyring manager which then unlocks automatically. In case of auto login there is no password field and no value it could hand over.
The only way to avoid that prompt with Autologin enabled is to set the password of the keyring manager to be empty but that indeed degrades security…
>> cat /etc/gdm3/custom.conf
# GDM configuration storage
#
# See /usr/share/gdm/gdm.schemas for a list of available options.
[daemon]
AutomaticLoginEnable=True
AutomaticLogin=arjun
# Enabling automatic login
# Enabling timed login
# TimedLoginEnable = true
# TimedLogin = user1
# TimedLoginDelay = 10
[security]
[debug]
# Uncomment the line below to turn on debugging
# More verbose logs
# Additionally lets the X server dump core if it crashes
#Enable=true
I disabled the automatic login setting. Now a password is asked but at the login screen.
Furthermore, Remmina opened up by itself because “Automatically run on Startup” was enabled.
But why did this happen in the first place? Can deleting the dconf directory lead to issues like this? I just want to be sure that there are no other underlying issues. Thanks.
The only way to avoid that prompt with Autologin enabled is to set the password of the keyring manager to be empty but that indeed degrades security…
So, even when auto-login is enabled, we will be asked to login again by the prompt. But, what even is the purpose of auto-login then? I disabled the auto-login setting and I am now asked the password at the login screen. So, I am fine with it. Also, Remmina opened up by itself because “Automatically run on Startup” was enabled. But why did these things happen in the first place? Was it due to deleting the dconf directory? I just want to be sure that there are no other underlying issues. Thanks.
You said in the linked discussion that you tried many different commands from different sources. It is impossible to guess what you tried and what effect these commands could have.
So, you are saying that deleting the ~/.config/dconf directory is totally unrelated to the auto login configuration. But, I only had this issue after deleting the dconf directory.
That’s a fair point. But, I am getting all these issues only after deleting the dconf directory. I had rebooted just before deleting the dconf directory, but noticed no such issues.
~/.config/dconf only stores your user desktop preferences (dock, icons, wallpaper). It physically cannot modify /etc/gdm3/custom.conf - which requires root/sudo - or install/uninstall packages.
You likely toggled Automatic Login in Settings earlier, and it only took effect on the reboot. Resetting dconf simply restored your default desktop shortcuts…
You likely toggled Automatic Login in Settings earlier
Maybe. But I don’t remember changing anything in the settings.
I solved most of the issues that I had mentioned. The only thing that’s unanswered for is why did all of these changes happen just after deleting the dconf directory? Again, I had rebooted just before deleting the directory, so I would’ve noticed if there were any changes. Anyways, I don’t think I am going to take this any further. If there is a central issues that’s the cause of all this, I will deal with it later when problems arise. Thanks.
Likely one of these “commands from other sources” caused it … but in the other post you also show that you tinkered a lot with packages which likely also had some effect on your installation… You simply did a lot more than “just deleting the dconf directory”
You simply did a lot more than “just deleting the dconf directory”
True. It may be due to that. But, as I’ve said before, I rebooted after every major change I made. I would have noticed these changes then. Anyways, I don’t think I will worry about it much as I don’t face any problems for the time being. I have learnt a good lesson not to stress about problems that don’t affect me at present. Thanks for helping a newbie out
