Bug 451039

Summary: Show which application tries to access keyring
Product: [Applications] kwalletmanager Reporter: qaz.cetelic <qaz.cetelic>
Component: generalAssignee: Valentin Rusu <valir>
Status: REPORTED ---    
Severity: wishlist CC: bugsKde, kde-2011.08, kde-bugs, lemma, mh+kde-bugs, mk.mateng, post, postix, PVince81, uwu, vkrevs
Priority: HI    
Version: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=467534
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description qaz.cetelic@gmail.com 2022-03-02 13:50:27 UTC 
SUMMARY
I'm noticing that the keyring is triggered seemingly randomly, and there doesn't seem to be a way to see what triggered it.

EXPECTED RESULT
Replace "an application" in the pop-up with the actual application or process name.

SOFTWARE/OS VERSIONS
Operating System: Fedora 34
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2
Kernel Version: 5.16.11-100.fc34.x86_64 (64-bit)
Graphics Platform: X11
Comment 1 michaelk83 2022-09-06 07:33:03 UTC 
*** Bug 457807 has been marked as a duplicate of this bug. ***
Comment 2 michaelk83 2022-09-06 07:34:29 UTC 
FYI, KeePAssXC uses `/proc/$PID/exe` to determine this.
https://github.com/keepassxreboot/keepassxc/pull/6915
https://github.com/keepassxreboot/keepassxc/pull/4733#issuecomment-633679091
Comment 3 michaelk83 2022-09-06 10:36:02 UTC 
*** Bug 340189 has been marked as a duplicate of this bug. ***
Comment 4 michaelk83 2022-09-06 10:38:31 UTC 
*** Bug 323188 has been marked as a duplicate of this bug. ***
Comment 5 michaelk83 2022-09-06 12:17:37 UTC 
*** Bug 438823 has been marked as a duplicate of this bug. ***
Comment 6 michaelk83 2022-09-06 15:28:53 UTC 
*** Bug 180504 has been marked as a duplicate of this bug. ***
Comment 7 michaelk83 2022-09-06 15:31:25 UTC 
*** Bug 216658 has been marked as a duplicate of this bug. ***
Comment 8 postix 2023-03-23 11:39:24 UTC 
*** Bug 216823 has been marked as a duplicate of this bug. ***
Comment 9 postix 2023-03-23 11:39:45 UTC 
*** Bug 187889 has been marked as a duplicate of this bug. ***