Created attachment 149586 [details] It makes me hate him. The crux of the problem is that I seem to have met the necessary requirements to ensure that KDE Wallet is not the reason that I cannot have automatic login capability. I set it to classic Blowfish encryption. The name of the wallet is "kdewallet". Left the password fields blank. I can't do without KDE Wallet in openSUSE because I need it to automatically save the password for my Wi-Fi. Maybe I did something wrong or maybe there really is such a problem with KDE Wallet. I should have also noted that I had the window in openSUSE Tumbleweed pestering me so very intrusively to create my Wallet that even after I refused, I still had no way to get rid of it after the next time I started my computer. Tried openSUSE Tumbleweed on a virtual machine and it seems like because of the virtual network, KDE Wallet doesn't show itself and isn't the reason for not being able to log in automatically. I hope you can fix such an annoying problem for me, which makes me frustrated. https://wiki.archlinux.org/title/KDE_Wallet#Unlock_KDE_Wallet_automatically_on_login From there I took information about automatic login with KDE Wallet. SOFTWARE/OS VERSIONS Linux: openSUSE Tumbleweed KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2
What's also odd is that it was found out earlier that if you turn on automatic login right after the session ends, for some reason it works, but it's still weird.
Created attachment 149587 [details] Weirdness.
Can you back up and describe the problem? What is going wrong, exactly? What did you expect to happen, and what happened instead? See also https://community.kde.org/Get_Involved/Issue_Reporting#Steps_to_Reproduce
Maybe this problem with the KDE Wallet is only present in the openSUSE distribution, but can this be replicated on other distributions? I don't know for sure. Here are the steps to reproduce this problem. 1. Choose classic Blowfish encryption. Could GnuPG change something? 2. Wallet name "kdewallet". 3. Leave the password fields blank. 4. We make sure that there is an automatic login under something else. 5. Restart your computer and draw conclusions about this problem. Yes. I can't refuse the KDE Wallet because otherwise it would constantly annoy my eyes with its window about creating my wallet and the fact that without it I would not automatically connect to a Wi-Fi network. Then I installed pam_kwallet and later deleted it. I also want to note that YaST has a "Manage Users and Groups" section and my account there has an automatic login. I don't think that YaST would be involved in this case, as the experience with the virtual machine clearly points to something else.
I hope you understand my clumsy English.
Perhaps I may have written something wrong from the beginning. I suspect that KDE Wallet may be the reason why my automatic login doesn't work in openSUSE. Even though I have met the necessary requirements to do so. As for the other distributions, I don't know. KDE Wallet seems to behave differently in openSUSE. Next time I need to be more careful with my text when writing something myself.
>5. Restart your computer and draw conclusions about this problem. I'm afraid that isn't good enough. You need to explain what happens to *you*. Because if I try it and I can't reproduce the problem, then I still don't know what the issue is. I can't tell if auto-login isn't working for you, or if it is working but your wallet doesn't automatically unlock, or if the problem is something different.
Briefly speaking. I recently reinstalled the openSUSE Tumbleweed distribution and set it up. The point at which auto-login stops working is when you enable the Nvidia repositories and then restart your computer. I have previously installed proprietary Nvidia drivers via YaST, and when I recently reinstalled the distribution, I decided to follow the command path in the terminal. What terminal commands did I run to install proprietary Nvidia drivers? 1. sudo zypper ar -f https://download.nvidia.com/opensuse/tumbleweed nvidia 2. sudo zypper inr 3. sudo reboot And after that, there is a problem with automatic login. Strangely, on other distributions such as Kubuntu or Fedora KDE Plasma, after installing proprietary Nvidia drivers and rebooting the computer, there were no problems with automatic login. Here the problem may be on the side of the Nvidia repository for openSUSE or the openSUSE distribution itself or SDDM. I don't know the exact reason. And if anything, I have an office 700-series video card with a version of Nvidia 470 proprietary video drivers. The oddity with SDDM also lies in the fact that if you activate such a parameter as "Log in again immediately after logging of" in the SDDM behavior, then automatic login to the system works. The KDE wallet has nothing to do with it. Since I managed to get to know him again during the reinstallation, and after the reboot everything was fine. Automatic login only stopped working when I installed proprietary Nvidia drivers on my system and rebooted the computer after that. It may be that such problems would not have appeared if I had a fresher Nvidia video card with fresh proprietary drivers or just a good AMD video card. I suspect Nvidia may be worse at testing their proprietary drivers for their older graphics cards.
I heard from a friend of mine that he had an old Nvidia video card and openSUSE Leap was very problematic to work with it. The problem is with updates. Then he switched to Fedora Linux, where Nvidia worked well for him. If anything, this problem does not concern KDE Plasma at all. This was most likely a problem with the openSUSE distribution.
So auto-login isn't working, right? What happens when you restart the computer? You see the login screen and have to log in manually?
Yes, that's right. And I have no idea how you will solve this problem. Because if this is a problem with the openSUSE distribution, it's probably not your responsibility unless you have something to do with it.
Thanks for the info. I'm not sure KWallet has anything to do with it here. You're using SDDM as your login manager, right?
Yes.
And I also had this problem in KDE Plasma 5.25.0. At least it's good that the bug mode opacity was fixed.
Thanks again for the bug report. Unfortunately we were not able to get to it yet. Can I ask you to please check if it's still an issue with Plasma 5.27? Thanks a lot!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!