[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint

[Evren]

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

Evren  changed:

   What|Removed |Added

 CC||evren...@hotmail.com

--- Comment #26 from Evren  ---
Managing, setting up a new gpg key or modifying an existing expired key within
KDE is possible through Kleopatra application, this way you don't need to look
up for terminal commands. But i still believe KWallet should redirect the user
to launch Kleopatra application if there is no suitable gpg is found, so the
user would then find out what to do next easily on a user friendly gui.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint

[Jeff Stokes]

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

Jeff Stokes  changed:

   What|Removed |Added

 CC||jeffstokes1...@gmail.com

--- Comment #25 from Jeff Stokes  ---
This bug has been open 8 years now. Nice of some folks to put fixes in the
comments. Maybe the devs could use one with a button or option in the gui.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint

[soredake]

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

soredake  changed:

   What|Removed |Added

 CC|broaden_acid002@simplelogin |
   |.com|

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint

[Stig Grindland]

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

Stig Grindland  changed:

   What|Removed |Added

 CC||stig.grindl...@gmail.com

--- Comment #24 from Stig Grindland  ---
Hello, I'm also here regarding this user experience, as I have experienced it
myself ever since I switched to linux some months ago and trying different
distros. 

KDE feels unhelpful by telling me to "Please set-up at least an encryption key,
then try again.", as if I'm already an expert on this stuff. Which is making me
do the job of searching up how to do this the right way. Which again leads me
to all kind of info from years back which I'm not sure about.

If the error message could include a link to KDE documentation, or some
suggestion on how to proceed with setting up GPG, I think it would be a great
step forward here.

For context, I went through these steps and I hope new users doesn't have to:
Ask an AI for help -> reddit -> link to this issue -> understand why I should
set up GPG and not escape to blowfish.

I am now glad to see that I'm not alone here, and thanks to all you previous
commenters for the information collected here.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint

[Lars Gottlieb]

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

Lars Gottlieb  changed:

   What|Removed |Added

 CC||lars.gottl...@gmail.com

--- Comment #23 from Lars Gottlieb  ---
I've been distrohopping a little over this week, and every single KDE based
distro I've tried has had this happen every time the user tries to open a
Chromium based browse, or an application based on it. 

This issue has been open for 8 full years. 

That this is such a low priority for the KDE design team is frankly not a great
look. You can wipe it off on the chromium team if you like, but it appears the
message comes from KDE, not Chromium. 

I humbly suggest some ressources be allocated to fix this; if nothing else make
the message link to a user friendly solution.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint

[Fernando]

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

Fernando  changed:

   What|Removed |Added

 CC||fils2...@gmail.com

--- Comment #22 from Fernando  ---
Here to say this is still a problem. It'd be nice if a general user was guided
in a better way to a solution. 
The KDE Wallet Service seems like a great feature in Plasma, but the way it's
presented makes people shy away from it. If it's going to be enabled by default
(it was in Fedora 36), I think it should prompt for some kind of setup at the
beginning. Having said this, I don't know if this should be enabled by default.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint

[bugzilla_noreply]

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

bugs@lyle.33mail.com changed:

   What|Removed |Added

 CC||bugs@lyle.33mail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint

[soredake]

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

soredake  changed:

   What|Removed |Added

 CC||ndrzj1...@relay.firefox.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint

[bugzilla_noreply]

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

richard.j.e.co...@gmail.com changed:

   What|Removed |Added

 CC||richard.j.e.co...@gmail.com

--- Comment #21 from richard.j.e.co...@gmail.com ---
Seven years later and this bug is still here :-O.  Not even a help message.

Does Ubuntu have this bug as well as Kubuntu?  I'm thinking I should switch if
this is the first thing I encounter when trying to switch from Windows to
Linux.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint

[Andrey]

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

Andrey  changed:

   What|Removed |Added

 CC||sen...@yandex.ru

--- Comment #20 from Andrey  ---
I have been getting the dreaded error: "Encryption error while attempting to
save the wallet kdewallet. Error code is 53 (Unusable public key). Please fix
your system configuration, then try again. This error may occur if you are not
using a full trust GPG key. Please ensure you have the secret key for the key
you are using."

I went through different bug reports and this is the list of things what might
go wrong with GPG and are worth checking:

1. You don't have GPG certificate, then generate one using:
```bash
gpg --full-generate-key
```
2. Certificate does not have `ultimate` trust.
* To set it graphically follow:
https://bbs.archlinux.org/viewtopic.php?pid=1876589#p1876589
* To set it through interactive CLI follow this:
https://security.stackexchange.com/a/129477

3. Certificate has expired (this was my case, it sort of worked, but I couldn't
update any passwords and was constantly getting an error).
To fix this issue, either generate a new certificate or change expiry date
(don't worry, the key itself will still be the same):

```bash
# Find the key which needs to be updated.
# IMPORTANT: Keys can have sub keys, check all expiration dates!
gpg --list-secret-keys --keyid-format=long --verbose

# Enter interactive mode
KEY=
gpg --edit-key ${KEY}

# In interactive mode
list
# This will choose the second key (0-based index)
key 1
# Change expiration date
expire
# Choose validity length, for example, 3 years from now on:
3y
# IMPORTANT! Confirm to save changes
save
```

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint

[David Mortals]

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

--- Comment #19 from David Mortals  ---
Ubuntu 20.04 LTS, it is still here.

gpg --full-gen-key may fix this.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint

[David Mortals]

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

David Mortals  changed:

   What|Removed |Added

 CC||wheelcomp...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint

[Postix]

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

Postix  changed:

   What|Removed |Added

 CC||pos...@posteo.eu

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Priority|NOR |VHI

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint

[Andres Betts]

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

Andres Betts  changed:

   What|Removed |Added

 CC||anditosan1...@gmail.com

--- Comment #18 from Andres Betts  ---
If it is not too much to ask, can someone make a video of this?

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #17 from Nate Graham  ---
I'll see if I can work up a patch for this at some point soon. Not being a
cryptography expert, Comment 14 is especially helpful.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Keywords||usability
 CC||pointedst...@zoho.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||hendricks.j...@gmail.com

--- Comment #16 from Christoph Feck  ---
*** Bug 387881 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint

[SchnWalter]

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

--- Comment #15 from SchnWalter  ---
It would be nice to see more information or at least what is the actual
problem.

The message isn't helpful. Even if you try to search for a solution on the
internet, there isn't much info out there.

For those still searching, here's how I fixed the problem:
Open KGpg and go to the "Key Properties" screen and change the "Owner Trust", I
chose "Ultimately". But I'm not sure if this is the level required, I just went
with it. 

Alternatively, you can use the CLI command:
$ gpg --edit-key $KEYID
And then execute the `trust` command, to change the trust field to "5 = I trust
ultimately". 

To see a list of trusted keys:
$ gpg --update-trustdb

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint

[SchnWalter]

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

SchnWalter  changed:

   What|Removed |Added

 CC||exposemoldesoledksgub@schn.
   ||email

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint

[via KDE Bugzilla]

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

skim...@gmail.com changed:

   What|Removed |Added

 CC||skim...@gmail.com

--- Comment #14 from skim...@gmail.com ---
Personally, it would be nice to have some message that explain what to do next
and those who are familiar with gpg and linux will know what needs to be done.
Anyhow, I have done my best below to help those who are stuck and desires using
GPG.

Overview of the steps: KDE wallet is looking for something called public key
pairs that you register to the keyring. The keyring will be tied to your
username on your machine. You can generate your public key pairs using gpg.
After you generate your public key pairs, it will be listed in your KDE wallet
and you can select it.


1. Check if you have gpg. It normally comes with your linux distribution. Try
the following below (If not, replace gpg with gpg2):
>>which gpg
If you get a complaint that it is unavailable, you need to install gpg.

2. Generate your key pair:
>>gpg --gen-key
Select the default when it asks for the kind of key. Choose to have the key
never to expire. Follow the instructions to fill out your real name, email,
comments, and passphrase (The passphrase is the key that protects your private
key in case your private key is stolen). Generate random bytes by doing what it
asks you to do. It may take some time so be patient. For me, it took 5 minutes
or so. Eventually, you will get an output that it generated it and you will be
returned to the prompt.

3. Verify that your key pair has been generated:
>>gpg -K
You will see a list of keys in the keyring and you should see the one that you
generated.

The next time KDE wallet runs, your key will be available if you choose GPG
encryption. 

I hope this helps.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint

[Denis Revin via KDE Bugzilla]

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

Denis Revin  changed:

   What|Removed |Added

 CC||denis.re...@gmail.com

--- Comment #13 from Denis Revin  ---
Same issue for me. It's not clear from this error that you must to do. Can you
be more informative about it? For example, you can just tell user something
like: "Please, run `gpg2 --full-gen-key` to add at least one key"

Thank you :)

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint

[Mani via KDE Bugzilla]

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

Mani  changed:

   What|Removed |Added

 CC||mani.za...@gmail.com

--- Comment #12 from Mani  ---
I have the same issue, I am using linux starting by RedHat9 and Fedora since
2001, shifting to ubuntu on 2008 since Sep-2016 which I intalled Arch and KDE,
I am developer and sysadmin, I just mentiond my background to clear it that I
am not a novice Linux user or unprofessional one, but this Error "Seems that
your system has no keys suitable for encryption. Please set-up at least an
encryption key, then try again." is none sence! how about "Ops, an exception
occured!"; from KDE community I do expect more, its more than a year which this
issue didnt resolve. I do expect better UX from KDE community and better
communication attitude on response; this Error is almost took 30 mins to solve
it and around a year which didnt change. I just register the account and report
it because of some unfriendly user responce as I can see some others involved
with this!
Please try to provide better UX, Plasama5 is a great desktop. Thanks for your
efforts.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint

[Florian Jacob via KDE Bugzilla]

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

Florian Jacob  changed:

   What|Removed |Added

 CC||accounts+bugs.kde@florianja
   ||cob.de

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint

[justin gardiner via KDE Bugzilla]

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

justin gardiner  changed:

   What|Removed |Added

 CC||justin.m.gardi...@gmail.com

--- Comment #11 from justin gardiner  ---
I just hit this issue after trying linux again after a few years away. It is
not good that after my first boot I was asked to enter my wifi password and
then was presented with this. As I am a developer I knew what the message meant
but most people wouldn't.  This needs to be improved.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint

[via KDE Bugzilla]

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

--- Comment #10 from enkouy...@gmail.com ---
It's close to a year and the status of this issue is still "UNCONFIRMED."

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint

[Atle via KDE Bugzilla]

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

Atle  changed:

   What|Removed |Added

 CC||atle.peder...@gmail.com

--- Comment #9 from Atle  ---
I had the same problem. gpg --full-gen-key doesn't work for me, but gpg2
--full-gen-key does. It seems my system (kubuntu 16.04) has both v1 and v2 of
gpg, and gpg defaults to v1.

After doing this I had to quit and restart the process requesting to use the
wallet. Seems the "KDE Wallet System" creating a new wallet will not reload
available keys after first loading them.

So:
1. Cancel the dialog for creating a new wallet
2. Run gpg2 --full-gen-key and follow the instructions
3. Redo whatever triggered the request for a new wallet (for example connecting
to wireless)
(Optionally create the wallet using kwalletmanager5, for example
'kdewallet')

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint

[karsten via KDE Bugzilla]

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

karsten  changed:

   What|Removed |Added

 CC||i...@dr-burger.com

--- Comment #8 from karsten  ---
I had the same behaviour using CentOS 7.2. When I selected "Classic" bluefish
instead of GPG it prompted me for a password and its confirmation, and this
worked to create a kde wallet.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint

[via KDE Bugzilla]

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

--- Comment #7 from swpal...@gmail.com ---
Replacing the message, "Seems that your system has no keys suitable for
encryption. Please set-up at least an encryption key, then try again." with
something more user-friendly is important.  The current message is only
meaningful to system administrators, not end users.

The dialog should have a button to launch a key generation wizard.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint

[via KDE Bugzilla]

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

swpal...@gmail.com changed:

   What|Removed |Added

 CC||swpal...@gmail.com

--- Comment #5 from swpal...@gmail.com ---
Bad user experience?  Doesn't that pretty much define Linux and the UI-impaired
people that maintain it?
Yes, this is a significant issue.  An embarrassment really.  But on Linux,
everyone has to be a sysadmin.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint

[TimP via KDE Bugzilla]

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

TimP  changed:

   What|Removed |Added

 CC||tim.pi...@gmail.com

--- Comment #4 from TimP  ---
@Valentin 'Any patch welcome.'  is not a constructive or appropriate response. 
I came here because I too had a bad user experience, having no idea where to go
next. 
Your response was enough to get me to register. I am a returning KDE user,
having been in Ubuntu land for 10 years. This is one of  many little problems.

-- 
You are receiving this mail because:
You are watching all bug changes.