https://bugs.kde.org/show_bug.cgi?id=458085
michaelk83 changed:
What|Removed |Added
Version First|5.111.0 |5.97.0
Reported In|
https://bugs.kde.org/show_bug.cgi?id=458085
Lenzoid changed:
What|Removed |Added
CC||strong.drum0...@fastmail.co
|
https://bugs.kde.org/show_bug.cgi?id=458085
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
|
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #83 from michaelk83 ---
(In reply to jackdinn from comment #81)
> Ok i set :-
> ...
>
> i rebooted, but now its just gone back to hanging for 60 secs when i try to
> open my NAS or open the kde wallet or kwalletmanager
Ok, this does not lo
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #82 from jackdinn ---
I need help, i cant even login to my wifi either it says it can't save the
password and i don't know what to do. The system is falling apart without the
wallet. If i roll back my system to before the kwallet update its
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #81 from jackdinn ---
Ok i set :-
[KSecretD]
Enabled=true
[Wallet]
Close When Idle=false
Close on Screensaver=false
Enabled=true
First Use=false
Idle Timeout=10
Launch Manager=true
Leave Manager Open=false
Leave Open=true
Prompt on Open=f
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #80 from michaelk83 ---
(In reply to jackdinn from comment #78)
> I noticed it has
> Exe=/usr/bin/gnome-keyring-daemon
> CommandLine=/usr/bin/gnome-keyring-daemon --foreground
> But iv never had gnome-keyring installed, ever.
Yes, as I sai
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #79 from jackdinn ---
ok well i just removed any gnome-keyring stuff i could/might find.
systemctl --user stop gnome-keyring-daemon.service
systemctl --user disable gnome-keyring-daemon.service
systemctl --user mask dbus-org.freedesktop.sec
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #77 from jackdinn ---
❱busctl --user status org.freedesktop.secrets
PID=98412
PIDFD=yes
PPID=1219
TTY=n/a
UID=1000
EUID=1000
SUID=1000
FSUID=1000
OwnerUID=1000
GID=1001
EGID=1001
SGID=1001
FSGID=1001
SupplementaryGIDs=3 90 98 108 956 991 998
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #78 from jackdinn ---
I noticed it has
Exe=/usr/bin/gnome-keyring-daemon
CommandLine=/usr/bin/gnome-keyring-daemon --foreground
--components=pkcs11,secrets --control-directory=/run/user/1000/keyring
CGroup=/user.slice/user-1000.slice/user@1
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #76 from michaelk83 ---
(In reply to jackdinn from comment #75)
> However, someone has just suggested adding the following to .config/kwalletrc
> [KSecretD]
> Enabled=false
This is an advanced (and experimental) setting, which is desig
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #75 from jackdinn ---
I dont know if i was using GPG, i assume i was.
I tried adding no-allow-external-cache :-
❱cat .gnupg/gpg-agent.conf
default-cache-ttl 900
max-cache-ttl 99
no-allow-external-cache
i logged out and back in but i s
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #73 from michaelk83 ---
(In reply to jackdinn from comment #71)
> kwalletd6 is running.
> ksecretd is running and registered as the Secret Service provider,
> but any call to it hangs
Are you using a GPG wallet? If so, please try the workar
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #74 from michaelk83 ---
If you were using a different Secret Service provider prior to the upgrade to
6.14, then you can try Option B instead.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #72 from jackdinn ---
EDIT:- "When trying to open an SFTP bookmark in Dolphin, it hangs for about 60
seconds"
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=458085
jackdinn changed:
What|Removed |Added
CC||j...@jackdinn.co.uk
--- Comment #71 from jackdinn -
https://bugs.kde.org/show_bug.cgi?id=458085
John Kizer changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
|
https://bugs.kde.org/show_bug.cgi?id=458085
michaelk83 changed:
What|Removed |Added
Blocks|458318 |
See Also||h
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #70 from michaelk83 ---
> if pinentry always uses the same lookup attributes, KWallet could potentially
> detect those
I forgot that the deadlock is in the `OpenSession()` call, so this is not
possible.
I think that handling the Assuan pro
https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #69 from michaelk83 ---
> as long as pinentry makes the request via the Secret Service API, KWallet has
> no way to know that it's its own password that is being requested here.
On 2nd thought, if pinentry always uses the same lookup attri
https://bugs.kde.org/show_bug.cgi?id=458085
wrought.iron...@gmail.com changed:
What|Removed |Added
CC||wrought.iron...@gmail.com
--
You ar
https://bugs.kde.org/show_bug.cgi?id=458085
Nate Graham changed:
What|Removed |Added
CC||matejm98m...@gmail.com
--- Comment #68 from Nate
https://bugs.kde.org/show_bug.cgi?id=458085
m.k...@irregular.at changed:
What|Removed |Added
CC||m.k...@irregular.at
--
You are receiving
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 rece
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 bec
https://bugs.kde.org/show_bug.cgi?id=458085
gudvinr+...@gmail.com changed:
What|Removed |Added
CC||gudvinr+...@gmail.com
--
You are receiv
https://bugs.kde.org/show_bug.cgi?id=458085
Amin Vakil changed:
What|Removed |Added
CC||i...@aminvakil.com
--
You are receiving this mail
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 a
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
> t
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 indire
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 dir
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 c
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 pas
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 passphrase
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 allowing
https://bugs.kde.org/show_bug.cgi?id=458085
Thiago Macieira changed:
What|Removed |Added
CC||thi...@kde.org
--- Comment #57 from Thiago Ma
https://bugs.kde.org/show_bug.cgi?id=458085
Zoltan Puskas changed:
What|Removed |Added
CC||zol...@sinustrom.info
--
You are receiving thi
https://bugs.kde.org/show_bug.cgi?id=458085
Kishore Gopalakrishnan changed:
What|Removed |Added
CC||kishor...@gmail.com
--
You are receiv
https://bugs.kde.org/show_bug.cgi?id=458085
Nick Cross changed:
What|Removed |Added
CC||k...@goots.org
--
You are receiving this mail bec
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 |1
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:
Yo
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: 5.98.
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 us
https://bugs.kde.org/show_bug.cgi?id=458085
michaelk83 changed:
What|Removed |Added
Blocks||458318
Referenced Bugs:
https://bugs.kde.org/sho
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.
@pi
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 regre
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 KD
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 wal
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 provider
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 l
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 Sec
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
> passphra
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 receivi
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; interface=org.freedes
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 promp
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 `pin
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 thou
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
> > that
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 acc
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 Secre
https://bugs.kde.org/show_bug.cgi?id=458085
ioo+...@posteo.net changed:
What|Removed |Added
CC||ioo+...@posteo.net
--- Comment #22 from ioo
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 Ser
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 passp
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 Service
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 can
https://bugs.kde.org/show_bug.cgi?id=458085
k...@trummer.xyz changed:
What|Removed |Added
CC||k...@trummer.xyz
--
You are receiving this m
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 bett
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 thi
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
../sysdeps/unix/
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 o
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 o
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.
1 - 100 of 107 matches
Mail list logo
