https://bugs.kde.org/show_bug.cgi?id=458085
mail+...@branleb.de changed:
What|Removed |Added
CC||mail+...@branleb.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=458085
mischa.sa...@gmail.com changed:
What|Removed |Added
CC||mischa.sa...@gmail.com
--
You are
https://bugs.kde.org/show_bug.cgi?id=458085
Vit Pelcak changed:
What|Removed |Added
Version|5.97.0 |5.111.0
Platform|Archlinux
https://bugs.kde.org/show_bug.cgi?id=458085
Vit Pelcak changed:
What|Removed |Added
CC||v...@pelcak.org
--- Comment #67 from Vit Pelcak
https://bugs.kde.org/show_bug.cgi?id=458085
Sam James changed:
What|Removed |Added
CC||s...@gentoo.org
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=458085
gudvinr+...@gmail.com changed:
What|Removed |Added
CC||gudvinr+...@gmail.com
--
You are
https://bugs.kde.org/show_bug.cgi?id=458085
Amin Vakil changed:
What|Removed |Added
CC||i...@aminvakil.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #66 from michaelk83 ---
(In reply to Thiago Macieira from comment #65)
> In any case, this doesn't prevent a race condition anyway. How about we try
> to fix it the right way first?
I think handling the Assuan protocol is our best bet for
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #65 from Thiago Macieira ---
> I don't know, but if you configure your system such that gpgconf can't do
> its job, then you have a broken configuration, IMO.
> If you really want ephemeral settings without writing to disk, you can mount
>
https://bugs.kde.org/show_bug.cgi?id=458085
Fushan Wen changed:
What|Removed |Added
CC|qydwhotm...@gmail.com |
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #64 from michaelk83 ---
(In reply to Thiago Macieira from comment #63)
> Does it support setting ephemeral settings not saved to disk? I didn't see
> that in the documentation.
>
> Otherwise, you're just asking to write to disk, only
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #63 from Thiago Macieira ---
(In reply to michaelk83 from comment #62)
> > It also wouldn't work if I had my ~/.gnupg directory protected against
> > unwanted reads and writes.
>
> The proposed patch doesn't attempt to write to ~/.gnupg
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #62 from michaelk83 ---
(In reply to Thiago Macieira from comment #61)
> A proper implementation would realise that
> the request for GPG to open the wallet is still pending and queue the
> request to be answered when the wallet got opened.
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #61 from Thiago Macieira ---
(In reply to michaelk83 from comment #60)
> Pinentry is asking for the passphrase through the same Secret Service API as
> any other client (see comment 31). KWallet has no way to tell it apart from
> any other
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #60 from michaelk83 ---
(In reply to Thiago Macieira from comment #59)
> But the fact is that if the query was asynchronous, then pinentry would have
> got its answer instead of timing out, and then would have prompted the user
> for the
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #59 from Thiago Macieira ---
> @Thiago, the issue is bigger than just synchronous vs asynchronous. The
> issue is that if you use a GPG wallet, with Secret Service provided by
> KWallet, and while allowing pinentry to read the key
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #58 from michaelk83 ---
(In reply to Thiago Macieira from comment #57)
@Thiago, the issue is bigger than just synchronous vs asynchronous. The issue
is that if you use a GPG wallet, with Secret Service provided by KWallet, and
while
https://bugs.kde.org/show_bug.cgi?id=458085
Thiago Macieira changed:
What|Removed |Added
CC||thi...@kde.org
--- Comment #57 from Thiago
https://bugs.kde.org/show_bug.cgi?id=458085
Zoltan Puskas changed:
What|Removed |Added
CC||zol...@sinustrom.info
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=458085
Kishore Gopalakrishnan changed:
What|Removed |Added
CC||kishor...@gmail.com
--
You are
https://bugs.kde.org/show_bug.cgi?id=458085
Nick Cross changed:
What|Removed |Added
CC||k...@goots.org
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=458085
mcarans changed:
What|Removed |Added
CC||mcar...@yahoo.co.uk
--- Comment #56 from mcarans
https://bugs.kde.org/show_bug.cgi?id=458085
michaelk83 changed:
What|Removed |Added
Version Fixed In|5.98|
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #54 from k...@trummer.xyz ---
I have updated my kwalletd5 package from 5.96 to 5.98 now, and the password
entry dialog still takes its sweet time to show up.
On 5.96 it shows up right after login.
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=458085
Nicolas Fella changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=458085
Nate Graham changed:
What|Removed |Added
Resolution|--- |FIXED
Version Fixed In|
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #51 from pipapo ---
Sorry for not replying. I was very busy. For that reason I stayed at version
0.96.
But now, with the upgrade to 5.98 everything is working fine again:
KDE neon 5.25
KDE-Plasma-Version: 5.25.5
KDE-Frameworks-Version:
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #50 from michaelk83 ---
(In reply to michaelk83 from comment #49)
> (In reply to pipapo from comment #48)
> > Here on kde neon option A is working in the sense that a dialog is asking
> > for the passphrase immediately. But the key is not
https://bugs.kde.org/show_bug.cgi?id=458085
michaelk83 changed:
What|Removed |Added
Blocks||458318
Referenced Bugs:
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #49 from michaelk83 ---
(In reply to pipapo from comment #48)
> Here on kde neon option A is working in the sense that a dialog is asking
> for the passphrase immediately. But the key is not used automatically with
> the login as before.
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #48 from pipapo ---
Here on kde neon option A is working in the sense that a dialog is asking for
the passphrase immediately. But the key is not used automatically with the
login as before.
Option B has no observable effect here.
Solution C
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #47 from Frank Kruger ---
(In reply to michaelk83 from comment #46)
> (In reply to Frank Kruger from comment #45)
> > Appreciated, but your solution seems to be restricted to a fix when setting
> > up a GPG wallet. What about current users?
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #46 from michaelk83 ---
(In reply to Frank Kruger from comment #45)
> Appreciated, but your solution seems to be restricted to a fix when setting
> up a GPG wallet. What about current users?
The proposed fix should work the same whether the
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #45 from Frank Kruger ---
(In reply to michaelk83 from comment #44)
> (In reply to Frank Kruger from comment #43)
> > Recommendation A works fine for me - thanks for the "solution". However, I
> > am really puzzled by the fact that the
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #44 from michaelk83 ---
(In reply to Frank Kruger from comment #43)
> Recommendation A works fine for me - thanks for the "solution". However, I
> am really puzzled by the fact that the regression definitely introduced by
> the upgrade to
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #43 from Frank Kruger ---
(In reply to michaelk83 from comment #36)
> Reopening because the fix should ideally be automated by KWallet when
> setting up a GPG wallet, or at least properly documented.
> To summarize:
>
> This affects GPG
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #42 from michaelk83 ---
(In reply to ioo+kde from comment #41)
> Will this solution allow users to again use a third party secret service
> agent along with kwallet again?
You don't need this patch to run a 3rd-party Secret Service
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #41 from ioo+...@posteo.net ---
(In reply to nic.chris...@gmail.com from comment #34)
> (In reply to michaelk83 from comment #33)
> > @nic.christin, one more thing to try:
> > https://man.archlinux.org/man/gpg-agent.1#no-allow-external-cache
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #40 from michaelk83 ---
(In reply to michaelk83 from comment #39)
> Option A (`no-allow-external-cache`) is the correct solution IMO
@Nicolas Fella, the patch would be something like the following (pseudo-code,
in backendpersisthandler.cpp
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #39 from michaelk83 ---
(In reply to Nicolas Fella from comment #38)
> we just needs to find one approach that works and stick with it
Option A (`no-allow-external-cache`) is the correct solution IMO, if you want
to use a GPG wallet with
https://bugs.kde.org/show_bug.cgi?id=458085
Nicolas Fella changed:
What|Removed |Added
Resolution|FIXED |---
Ever confirmed|1
https://bugs.kde.org/show_bug.cgi?id=458085
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=458085
michaelk83 changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|UPSTREAM
https://bugs.kde.org/show_bug.cgi?id=458085
michaelk83 changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #34 from nic.chris...@gmail.com ---
(In reply to michaelk83 from comment #33)
> @nic.christin, one more thing to try:
> https://man.archlinux.org/man/gpg-agent.1#no-allow-external-cache
> > --no-allow-external-cache
> >Tell Pinentry not
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #33 from michaelk83 ---
@nic.christin, one more thing to try:
https://man.archlinux.org/man/gpg-agent.1#no-allow-external-cache
> --no-allow-external-cache
>Tell Pinentry not to enable features which use an external cache for
>
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #32 from michaelk83 ---
(In reply to nic.chris...@gmail.com from comment #31)
> I can confirm that the process calling OpenSession is indeed pinentry-qt:
Thanks. Not surprising, but does make a full fix more difficult...
--
You are
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #31 from nic.chris...@gmail.com ---
I can confirm that the process calling OpenSession is indeed pinentry-qt:
method call time=1661860281.711391 sender=:1.137 -> destination=:1.6 serial=8
path=/org/freedesktop/secrets;
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #30 from michaelk83 ---
(In reply to nic.chris...@gmail.com from comment #29)
> Unfortunately I'm already using pinentry-qt.
Hmm.. that is unfortunate.
> I see gpg has a "--pinentry-mode loopback" option, that redirects the
> password
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #29 from nic.chris...@gmail.com ---
(In reply to michaelk83 from comment #28)
> @nic.christin, could you try entering the following line in your
> `gpg-agent.conf`:
> > pinentry-program /usr/bin/pinentry-qt
> You may need to install the
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #28 from michaelk83 ---
(In reply to michaelk83 from comment #27)
> A more robust approach is to check if the key/passphrase are already loaded
> into gpg-agent,
> and if not, display a prompt and pre-load the passphrase before trying to
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #27 from michaelk83 ---
(In reply to michaelk83 from comment #26)
> So short-circuiting `OpenSession` while waiting on GPG should fix this, IMO.
> It should return something like `InvalidMethodCall`, or simply `NotSupported`.
On further
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #26 from michaelk83 ---
(In reply to nic.chris...@gmail.com from comment #25)
> (In reply to michaelk83 from comment #20)
> > And two other experiments:
> > 1. After providing the passphrase, if you close the wallet, and then launch
> >
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #25 from nic.chris...@gmail.com ---
(In reply to michaelk83 from comment #20)
> @nic.christin, could you run `dbus-monitor
> "destination=org.freedesktop.secrets" "sender=org.freedesktop.secrets"`
> before launching the app that tries to
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #24 from michaelk83 ---
(In reply to ioo+kde from comment #23)
> Does anyone know which version of KDE neon I would need to downgrade to to
> get this working again?
You'll need to specifically downgrade the KWallet packages to any version
https://bugs.kde.org/show_bug.cgi?id=458085
Fushan Wen changed:
What|Removed |Added
Ever confirmed|0 |1
CC|
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #23 from ioo+...@posteo.net ---
(In reply to toastiwall from comment #2)
> I can confirm this started occurring after updating to to 5.97.0-1.1
> (Opensuse Tumbleweed rolling release, August 22nd, 2022).
> However, enabling or disabling
https://bugs.kde.org/show_bug.cgi?id=458085
ioo+...@posteo.net changed:
What|Removed |Added
CC||ioo+...@posteo.net
--- Comment #22 from
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #21 from Frank Kruger ---
(In reply to toastiwall from comment #2)
> I can confirm this started occurring after updating to to 5.97.0-1.1
> (Opensuse Tumbleweed rolling release, August 22nd, 2022).
> However, enabling or disabling Secret
https://bugs.kde.org/show_bug.cgi?id=458085
Frank Kruger changed:
What|Removed |Added
CC||fkrue...@mailbox.org
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #20 from michaelk83 ---
(In reply to michaelk83 from comment #18)
> A related question is where does GPG take its passphrase from when Secret
> Service is not running?
To answer my own question after re-reading the OP, the alternative
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #19 from nic.chris...@gmail.com ---
So it seems the issue is now understood, but just to confirm:
- I am indeed using a gpg wallet
- https://invent.kde.org/frameworks/kwallet/-/merge_requests/33.patch only
fixes the issue if "Secret
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #18 from michaelk83 ---
(In reply to michaelk83 from comment #17)
> (In reply to michaelk83 from comment #16)
> > A possible solution might be to temporarily disable the Secret Service API
> > while unlocking the wallet.
> However, this
https://bugs.kde.org/show_bug.cgi?id=458085
k...@trummer.xyz changed:
What|Removed |Added
CC||k...@trummer.xyz
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #17 from michaelk83 ---
(In reply to michaelk83 from comment #16)
> A possible solution might be to temporarily disable the Secret Service API
> while unlocking the wallet.
However, this can cause all sorts of race condition bugs, so a
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #16 from michaelk83 ---
A possible solution might be to temporarily disable the Secret Service API
while unlocking the wallet.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=458085
Felix Yan changed:
What|Removed |Added
CC||felixonm...@archlinux.org
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #15 from Nicolas Fella ---
kwalletd5 freezes with the following backtrace, which is consistent with my
theory
#0 0x7fe3d76d988f in __GI___poll (fds=fds@entry=0x14e1910,
nfds=nfds@entry=3, timeout=timeout@entry=1000) at
https://bugs.kde.org/show_bug.cgi?id=458085
sm1999 changed:
What|Removed |Added
CC||saurabhmhatre54...@gmail.co
|
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #14 from pipapo ---
(In reply to Nicolas Fella from comment #13)
> I have a theory what's going wrong:
>
> - Some application accesses kwallet
> - kwallet starts and unlocks the GPG wallet
> - During that kwallet invokes gpg
> - gpg calls
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #13 from Nicolas Fella ---
I have a theory what's going wrong:
- Some application accesses kwallet
- kwallet starts and unlocks the GPG wallet
- During that kwallet invokes gpg
- gpg calls org.freedesktop.secrets to get the key's passprase
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #12 from pipapo ---
Creating a new user account and configure a new wallet with gnugpg leads to the
same problem - The wallet does not open automaticly and after a minute or so a
dialog is asking for the passphrase to the key.
Interestingly
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #11 from Nicolas Fella ---
> The dialog asking for you wallet's password appears after a long delay of
> about 50 seconds.
50 seconds would be twice the default method call timeout in (Qt)DBus (25
seconds)
When I terminate kwallet, then
https://bugs.kde.org/show_bug.cgi?id=458085
Nicolas Fella changed:
What|Removed |Added
Resolution|DUPLICATE |---
CC|
https://bugs.kde.org/show_bug.cgi?id=458085
michaelk83 changed:
What|Removed |Added
Resolution|DOWNSTREAM |DUPLICATE
--- Comment #9 from michaelk83 ---
(In
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #8 from nic.chris...@gmail.com ---
(In reply to pipapo from comment #7)
> Good news! But the problem still exists here on kde neon.
The Arch patch in kwallet 5.97.0-3 is:
https://invent.kde.org/frameworks/kwallet/-/merge_requests/33.patch
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #7 from pipapo ---
Good news! But the problem still exists here on kde neon.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=458085
Nicolas Fella changed:
What|Removed |Added
CC||pi...@nimmerland.de
--- Comment #6 from
https://bugs.kde.org/show_bug.cgi?id=458085
nic.chris...@gmail.com changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=458085
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--- Comment #4 from
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #3 from nic.chris...@gmail.com ---
Disabling Secret Service DBus API doesn't help for me either.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=458085
toastiw...@yopmail.com changed:
What|Removed |Added
CC||toastiw...@yopmail.com
--- Comment #2
https://bugs.kde.org/show_bug.cgi?id=458085
Kevin Ottens changed:
What|Removed |Added
CC||er...@kde.org
--- Comment #1 from Kevin Ottens
https://bugs.kde.org/show_bug.cgi?id=458085
Celeste changed:
What|Removed |Added
CC||coelacant...@outlook.com
--
You are receiving this
84 matches
Mail list logo
