I've noticed a bug in #Plasma when running #Wayland I'm not able to run #sshagent so I only need to put my passphrase once in. I always get the passphrase question before each #SSH session But when running in #X11 I get a question as soon as I log in from a #GUI tool (#Kwallet I think) for me to unlock the key and everything works fine.

#2: Chrome logged-in pages

#Firefox remembers what websites I'm logged into and will keep me logged in there without any issues. #Chrome however will forget everything whenever I start it. In #Gnome #Chrome works fine. The solution seems to be the difference in how KDE uses #KWallet to store various data vs how #Gnome stores it. But Firefox seems to be indifferent to it.

How do I change this "Default keyring" password? #kubuntu #kde #password #keyrings #kwallet

https://askubuntu.com/q/1475138/612

Дошли руки до #fprint настроить на моем новом ноуте. Оказалось не просто, а очень просто. Теперь открываю локскрин одним прикосновением пальца.

Два момента. В современной Плазме совсем нестрашно не ставить ввод пароля впереди остальных методов, как советует #archwiki. #Плазма всё равно спросит пароль, если всё остальное не сработает.

Второй момент, я не стал ставить фпринт в #SDDM, потому что на старте всё равно пароль нужен, чтобы расшифровать #KWallet. Ну а раз пароль всё равно надо вводить, то почему бы и не ввести его в положенном месте.

А вы какие ещё интересные моменты знаете про сканер пальца на ноутбуках?

@LinuxGuides
Benutze nur #libreoffice von den aufgezählten, und denke meine Auswahl ist für mich auf #opensuse #tumbleweed ist für mich persönlich besser:
#spectacle #kontact #kwallet #kdeconnect #kate #neochat #whalebird #falkon #KDEdolphin #KDEkonsole

Just a question to the devs who make password wallets etc using GPG: Why do you tell the user, they got only 3 attempts at entering their private key's password?

They don't. They have infinite attempts because they own the key file. I've seen this in #KDE and #Gnome now.

#Software #GPG #KWallet

So, yeah, I could have saved several hours of work if, when I tried to use the "import XML" option, #KWallet had just popped up a dialog saying "This feature requires en existing wallet into which to import. Either open one or create a new one."

Offering to create a new wallet if you don't already have one would also have been helpful, but just that information alone could have saved all that time.

Alternatively, they could have put all the features that work with an open wallet into a menu-entry called "wallet", or similar, and have it greyed out when you don't have an open wallet selected.

#softwareGripe

#kwallet needs to give more useful error messages, and also when it can't open a dialog box it needs to give a message explaining why.
#softwareGripe

@Photor I am using #neomutt as well, storing passwords in #KDE's #kwallet. The approach works as follows: Neomutt's config options 'imap_pass' or 'smtp_pass' allow to specify executables inside #backticks (command substitution like in Bash), expecting the program or script to provide the #password on stdout. In my case, I am using a #Bash script that does some #DBus invocation to access kwallet and to extract the requested password.

That fix has just hit servers...

#Ubuntu #Bionic #KWallet