https://bugs.kde.org/show_bug.cgi?id=505000
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=504656
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=501135
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=504678
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=502808
--- Comment #31 from michaelk83 ---
(In reply to Nicolas Fella from comment #30)
> Shipping /usr/bin/kwalletd5 would be a packaging bug. kwallet5 should only
> ship the library component, not the daemon.
>
> https://gitlab.archlinux.o
https://bugs.kde.org/show_bug.cgi?id=502808
--- Comment #29 from michaelk83 ---
(In reply to Eduard from comment #28)
> Probably Arch hasn't applied it yet then.
Probably. It should be out with the next version.
> putting another version in the version 6 kwallet package wou
https://bugs.kde.org/show_bug.cgi?id=502808
michaelk83 changed:
What|Removed |Added
Version Fixed In||6.15
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=502808
--- Comment #27 from michaelk83 ---
(In reply to Eduard from comment #26)
> When I check the Remmina code on gitlab (https://gitlab.com/Remmina/Remmina),
> I also see no references to kwallet 6, it's all kwalletd5.
I only see two re
https://bugs.kde.org/show_bug.cgi?id=502808
--- Comment #25 from michaelk83 ---
(In reply to Eduard from comment #24)
> Yes kwalletd5 is installed by package kwallet5.
> it's a required dependency (of) kio5 and qtkeychain-qt6.
Checking the package dependencies, qtkeychain-qt6 only
https://bugs.kde.org/show_bug.cgi?id=489916
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=502808
--- Comment #23 from michaelk83 ---
(In reply to Eduard from comment #22)
> Ok, because my problems with Remmina are still there (Arch Linux), I
> investigated some things myself ...
> Turns out that Remmina still uses kwalletd5. ...
> When
https://bugs.kde.org/show_bug.cgi?id=504709
Bug ID: 504709
Summary: KWallet: add more control over MigrateTo3rdParty
option
Classification: Frameworks and Libraries
Product: frameworks-kwallet
Version First 6.14.0
Reported In:
https://bugs.kde.org/show_bug.cgi?id=504709
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=504693
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=504693
Bug ID: 504693
Summary: UX: "Use KWallet for the Secret Service interface"
setting is not immediately applied
Classification: Applications
Product: kwalletmanager
Version First unspecified
https://bugs.kde.org/show_bug.cgi?id=504678
Bug ID: 504678
Summary: KWalletManager freezes if (first?) wallet creation is
aborted
Classification: Frameworks and Libraries
Product: frameworks-kwallet
Version First 6.14.0
Reporte
https://bugs.kde.org/show_bug.cgi?id=504656
michaelk83 changed:
What|Removed |Added
Summary|KWalletManager and other|kwallet 6.14: calls to
|calls
https://bugs.kde.org/show_bug.cgi?id=504656
--- Comment #15 from michaelk83 ---
(In reply to jackdinn from comment #14)
> Ohh, sorry i see now.
>
> [KSecretD]
> Enabled=true
>
> This setting is NOT the tickbox "Use KWallet for the Secret Service
> interface"
https://bugs.kde.org/show_bug.cgi?id=504656
--- Comment #12 from michaelk83 ---
(In reply to jackdinn from comment #11)
> ❱cat .config/kwalletrc
> [KSecretD]
> Enabled=false
As I mentioned earlier, this is not the correct setting for your case. It's
only intended if you want to u
https://bugs.kde.org/show_bug.cgi?id=504656
--- Comment #10 from michaelk83 ---
(In reply to jackdinn from comment #9)
> So you think if i remove the blank wallet from here and then update it might
> work?
It's worth a check. Other Manjaro users in
https://forum.manjaro.org/t/plasm
https://bugs.kde.org/show_bug.cgi?id=504656
--- Comment #8 from michaelk83 ---
(In reply to Marco Martin from comment #7)
> (In reply to michaelk83 from comment #2)
> > ❱journalctl --since -5m | grep ksecretd
> > May 21 16:31:41 greg-venusseries ksecretd[3459]: QDBusObjectPath: i
https://bugs.kde.org/show_bug.cgi?id=504539
--- Comment #10 from michaelk83 ---
No. The one in comment 2 was the closest to being useful, but it's missing all
the debug symbols, as you can see by the multitude of "??". You can try
installing the kwallet debug packages, and see
https://bugs.kde.org/show_bug.cgi?id=504656
--- Comment #5 from michaelk83 ---
(In reply to jackdinn from comment #4)
> But Aragorn the admin on manjaro forums said a downgrade would not work?
I'm not very familiar with Manjaro, but I understand it to mean that they can't
downgra
https://bugs.kde.org/show_bug.cgi?id=504014
michaelk83 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
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
https://bugs.kde.org/show_bug.cgi?id=504656
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=504656
--- Comment #2 from michaelk83 ---
Adding no-allow-external-cache to ~/.gnupg/gpg-agent.conf, nor disabling "Use
KWallet for the Secret Service interface" (as suggested in bug 458085 comment
36) did not help. For the latter, the user re
https://bugs.kde.org/show_bug.cgi?id=504656
--- Comment #1 from michaelk83 ---
We tried a number of debugging steps and workarounds, as can be seen bug 458085
comment 73 to bug 458085 comment 81, but to no avail. This does *not* look like
BUG 458085. It's also *not* bug 504014, since KWall
https://bugs.kde.org/show_bug.cgi?id=504656
Bug ID: 504656
Summary: KWalletManager and other calls to ksecretd hang with
kwallet 6.14 (kwallet is ENABLED).
Classification: Frameworks and Libraries
Product: frameworks-kwallet
Version 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.
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,
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, pleas
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=504193
--- Comment #28 from michaelk83 ---
(In reply to jackdinn from comment #27)
Hangs are a different problem than the one discussed in this bug report. Since
your kwalletd6 is running, and the hanging apps are not Chromium-based, this
doesn't look
https://bugs.kde.org/show_bug.cgi?id=504539
--- Comment #8 from michaelk83 ---
As I said earlier, we'll need a (good) backtrace, which shows the exact source
code location where the crash occurs, and the sequence of calls up to that
point. You've already provided the trace that you ha
https://bugs.kde.org/show_bug.cgi?id=502808
--- Comment #18 from michaelk83 ---
(In reply to dezzadk from comment #17)
> I have a feeling between updates either the .kwl file got corrupted or
> something changed that doesn't allow a passwordless wallet (as I have, what
> I store
https://bugs.kde.org/show_bug.cgi?id=504539
--- Comment #6 from michaelk83 ---
(In reply to ledo.kane from comment #5)
> You also mentioned that the backtrace doesn't include any kwallet code.
> Well, KDE's own "crash process viewer" registers this crash as a "ks
https://bugs.kde.org/show_bug.cgi?id=504193
--- Comment #26 from michaelk83 ---
(In reply to Arek Guzinski from comment #24)
> 1. What is keeping me from making some malware that identifies itself as
> "KDE System" to get access to all passwords?
> 2. What if an app should hav
https://bugs.kde.org/show_bug.cgi?id=504193
--- Comment #22 from michaelk83 ---
(In reply to Marco Martin from comment #19)
> no writing in anything from kwallet
ksecretd.cpp line 874-882 in KSecretD::isAuthorizedApp(), after the user
selects "Deny Forever" (response == 3), it gets
https://bugs.kde.org/show_bug.cgi?id=504193
--- Comment #23 from michaelk83 ---
(In reply to Rainer from comment #21)
> Another helpful change would be a message box when clicking the "open"
> button in KWalletManager saying "Access to the wallet has been rejected
>
https://bugs.kde.org/show_bug.cgi?id=504539
--- Comment #3 from michaelk83 ---
(In reply to ledo.kane from comment #2)
> The crash happens right after a boot and only once. Here is the crash info for
> the latest crash that i had:
> ...
Unfortunately, this crash trace isn't very h
https://bugs.kde.org/show_bug.cgi?id=504193
--- Comment #18 from michaelk83 ---
(In reply to Arek Guzinski from comment #17)
> I also can't remember to ever have put KDE System there. So the question is:
> how did it get there?
"KDE System" is the fallback string when the
https://bugs.kde.org/show_bug.cgi?id=490788
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=504539
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=502808
--- Comment #12 from michaelk83 ---
(In reply to Mariusz from comment #11)
> It's happening with distribution packages. I did a fresh openSUSE tumbleweed
> install with snapshot 20250514.
Is there a bug report for openSUSE?
https://inv
https://bugs.kde.org/show_bug.cgi?id=504312
--- Comment #6 from michaelk83 ---
(In reply to Marco Martin from comment #3)
> One ting i noted while using keepassXC is that every entry in the wallet is
> separatedly locked, but what should happen in that case is keepassxc popping
> up
https://bugs.kde.org/show_bug.cgi?id=504312
--- Comment #7 from michaelk83 ---
(In reply to turtoise from comment #5)
> Created attachment 181492 [details]
> DBus traces of entering WiFi password (password removed from traces)
Thanks!
What I see from this trace, is:
A. The network mana
https://bugs.kde.org/show_bug.cgi?id=504312
--- Comment #2 from michaelk83 ---
Now that we have a few more users here, it would be good to get some DBus
traces, so we can check if kwalletd is at fault. The relevant interfaces are
org.kde.kwalletd6 , org.kde.KWallet , org.freedesktop.secrets
https://bugs.kde.org/show_bug.cgi?id=504193
--- Comment #13 from michaelk83 ---
(In reply to Rainer from comment #12)
> Turns out the app "KDE System" was in the deny list of the wallet.
> Removing that item in the wallet settings, restarting kwalletd and
> ksecretd solve
https://bugs.kde.org/show_bug.cgi?id=504358
--- Comment #4 from michaelk83 ---
There was a big refactor for 6.14, so it's also possible that just that
transition alone caused the hiccup. And once you set the settings again, then
it's back to normal. But in any case, I think the root
https://bugs.kde.org/show_bug.cgi?id=502808
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=494264
michaelk83 changed:
What|Removed |Added
CC||major-ma...@t-online.de
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=504312
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=504358
michaelk83 changed:
What|Removed |Added
Status|REPORTED|RESOLVED
CC
https://bugs.kde.org/show_bug.cgi?id=504014
--- Comment #45 from michaelk83 ---
*** Bug 504334 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=504334
michaelk83 changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=504312
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=504014
--- Comment #39 from michaelk83 ---
(In reply to Eduard from comment #38)
kwallet-pam is BUG 502808.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=504193
--- Comment #9 from michaelk83 ---
Some notable points from your trace:
- The `walletAsyncOpened` is broadcast with the 2nd parameter set to -1. This
indicates that the open operation failed:
https://invent.kde.org/frameworks/kwallet/-/blob/master/src
https://bugs.kde.org/show_bug.cgi?id=504082
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=504082
michaelk83 changed:
What|Removed |Added
CC||andrea.i...@gmail.com
--- Comment #9 from
https://bugs.kde.org/show_bug.cgi?id=502808
michaelk83 changed:
What|Removed |Added
CC||matt.fagn...@bell.net
--- Comment #7 from
https://bugs.kde.org/show_bug.cgi?id=504251
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=504082
--- Comment #8 from michaelk83 ---
Actually, not sure if it's an exact duplicate of BUG 502808, but seems closely
related.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=502808
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=504254
michaelk83 changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=504082
michaelk83 changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=504251
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=502808
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=502808
michaelk83 changed:
What|Removed |Added
CC||philippe.roub...@free.fr
--- Comment #6 from
https://bugs.kde.org/show_bug.cgi?id=504248
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=504082
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=504193
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=504014
--- Comment #23 from michaelk83 ---
Ok, thanks for your input. It looks like the problem is in the master switch,
`[Wallet] Enabled=false`. There were some changes in how it's handled as part
of the refactor for 6.14 (along with some
https://bugs.kde.org/show_bug.cgi?id=504014
--- Comment #19 from michaelk83 ---
People who have this problem, please post your kwalletrc while the problem is
occurring.
> The fact that KWallet is still hooked into the browser when it's disabled is
> very problematic.
It's the
https://bugs.kde.org/show_bug.cgi?id=504014
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=491280
--- Comment #11 from michaelk83 ---
@Nate, everything that uses the legacy KWallet API directly still needs to be
migrated to QtKeyChain eventually. But I suppose that can be tracked elsewhere.
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=458318
michaelk83 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
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
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
https://bugs.kde.org/show_bug.cgi?id=156547
--- Comment #11 from michaelk83 ---
As discussed in the MR (
https://invent.kde.org/utilities/kwalletmanager/-/merge_requests/46#note_1146725
), there are two parts to this:
1. On KWallet's side, it absolutely *should* tell Klipper that "
https://bugs.kde.org/show_bug.cgi?id=458639
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=458318
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=491280
michaelk83 changed:
What|Removed |Added
CC||a...@cryptomilk.org
--- Comment #8 from
https://bugs.kde.org/show_bug.cgi?id=484045
michaelk83 changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=491280
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=179678
--- Comment #121 from michaelk83 ---
Is this considered resolved with KIO Admin
(https://invent.kde.org/system/kio-admin)?
The latest merge request for this has been closed:
https://invent.kde.org/frameworks/kio/-/merge_requests/1004#note_1070765
https://bugs.kde.org/show_bug.cgi?id=324254
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=179678
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=489021
--- Comment #1 from michaelk83 ---
@Nate Graham, although the steps to reproduce are with KDE Connect, the bug is
experienced in relation to xdg-desktop-portal-kde, unrelated to KDE Connect or
to Android. See for example
https://github.com
https://bugs.kde.org/show_bug.cgi?id=489021
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=468538
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=467534
michaelk83 changed:
What|Removed |Added
CC||mk.mat...@gmail.com
See Also
https://bugs.kde.org/show_bug.cgi?id=451039
michaelk83 changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=467533
michaelk83 changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=432713
michaelk83 changed:
What|Removed |Added
CC||pos...@posteo.eu
--- Comment #3 from michaelk83
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 b
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
1 - 100 of 300 matches
Mail list logo
