[kde] [Bug 455107] New: Suspicion of an automatic login problem because of the KDE wallet.

Corvurius bugzilla_noreply at kde.org
Fri Jun 10 05:20:45 BST 2022


https://bugs.kde.org/show_bug.cgi?id=455107

            Bug ID: 455107
           Summary: Suspicion of an automatic login problem because of the
                    KDE wallet.
           Product: kde
           Version: unspecified
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: corvurius at gmail.com
  Target Milestone: ---

Created attachment 149586
  --> https://bugs.kde.org/attachment.cgi?id=149586&action=edit
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

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Unassigned-bugs mailing list