I never setup kdewallet,but I just started getting prompts (2) from it asking for my password. For shits and giggles the second time, I just entered my user PW, and it's not prompted me since. I am not sure if the second prompt was a repeat of the first after canceling out. I don't think I even have it installed, I searched the start menu and the system settings for Kded, kdewallet: Nothing *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.17.7-arch1-2 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor Memory: 62.8 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1050/PCIe/SSE2 ADDITIONAL INFORMATION Just in case this is a breach of security (I'm being hacked) although unlikely, I marked this as "Critical": Better safe than sorry! I use stringent security, and am not foolish with it, nor my privacy.
(In reply to Bob English from comment #0) > I never setup kdewallet,but I just started getting prompts (2) from it > asking for my password. For shits and giggles the second time, I just > entered my user PW, and it's not prompted me since. I am not sure if the > second prompt was a repeat of the first after canceling out. > > I don't think I even have it installed, I searched the start menu and the > system settings for Kded, kdewallet: Nothing > *** > NOTE: If you are reporting a crash, please try to attach a backtrace with > debug symbols. > See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports > *** > > > STEPS TO REPRODUCE > 1. > 2. > 3. > > OBSERVED RESULT > > > EXPECTED RESULT > > > SOFTWARE/OS VERSIONS > Operating System: EndeavourOS > KDE Plasma Version: 5.24.5 > KDE Frameworks Version: 5.94.0 > Qt Version: 5.15.4 > Kernel Version: 5.17.7-arch1-2 (64-bit) > Graphics Platform: X11 > Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor > Memory: 62.8 GiB of RAM > Graphics Processor: NVIDIA GeForce GTX 1050/PCIe/SSE2 > > ADDITIONAL INFORMATION > Just in case this is a breach of security (I'm being hacked) although > unlikely, I marked this as "Critical": Better safe than sorry! I use > stringent security, and am not foolish with it, nor my privacy. OH: Steps to reproduce: Just boot up, and co about your business and: Expected Results: No clue! I never used KDE wallet!
More info: After restarting it happened again, here's the message from KDE Wallet Service: "The application 'kded' has requested the wallet 'kdewallet' please enter the password for this wallet below." I never set it up, but if so I would have used a name other than the default. Again using my user password worked. Here's the message I got from Gnome evolution Email client when it opened: "Unlock login keyring. "The login keyring did not get unlocked when you logged into your computer." I had to install gnomekeyring (GPG) to use Evolution because it wouldn't accept any other keyring (incompatible) and how I have been using it for nearly a decade. Suspicion: The last update (Yesterday evening before shutdown) must have added a hard dependency for the KDE Login service, and adopted my Gnome keyring, without asking or even telling me; if so, that's unwarranted! Besides that, I can live with this new compatibility, but need to know a few things like: Can get rid of gnomekeyring, and use kdewallet instead or iscnomekeyring still required and if so how? Install and use kdewallet-manager? Some important do's and don'ts (not general, but platform specific) that may cause trouble, since I never used any of it.
I cannot edit my messages after adding, but there are little colored (edit) widgets for nearly everything els here; I like the new look and layout :<) Thanks!
Hellooooooooooooooooooooooooooooooooooooooooooooo!!! Is anyone there???
This started happening on my system on 2022-05-25; I have also not set up or consciously used KWallet. I was initially prompted for my WiFi credentials after rebooting my system and logging on. I tried logging off and on again. No prompt for WiFi credentials, and WiFi was working, but I received the same KWallet prompt as OP. I also see a prompt if I try to open the desktop programs Skype or Element (both which use Electron). Operating System: Ubuntu 20.04 KDE Plasma Version: 5.18.8 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.4.0-113-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz Memory: 11.5 GiB of RAM
I don't understand what you are saying the bug is. >I never setup kdewallet It was done for you. > I don't think I even have it installed You do. It's headless. kwalletmanager is shipped separately if you want it. You can find a settings modules in system settings. To avoid password prompts set it to your user password.
Well, if it's not a bug, then it came without warning out of nowhere. My system has been running for years with just updates, and I never had Kwallet manager installed, nor ever seen any prompts from kded, ever, and it just started about a week or a little more ago. So it is an unexpected behavior that never happened! So therefore something changed, and it looks and acts like a bug, or worse: a security breach! That should not be all that hard to understand. I did use my user password, but had no way of knowing it would work, and that still says nothing about why this is happening now, when it never did before. I had it ask for the password again this morning, but not in a few days, so not every time I boot up, making it random too, and not giving any reason why, so no, just giving it my password after I just logged on with it is odd, as well as annoying! So it is at minimum an undesired behavior and unexplained too, where just giving it my user password every time it just randomly occurs is not a solution, but a workaround.
Sounds more like: - kwallet was set up and working exactly as indented - we have a startup order race with something requesting a password before kwallet Pam kicks in. We've seen that before. I'll search for dupes. Ultimately this is a bug tracker for a product. Comments such as suggesting a security breach based on nothing are counter productive. Can you attach output of "env" in a terminal and ideally journalctl --user -b after login.
Thanks for looking into it, and I will check, and attache the outputs of environment and the journal as soon as it happens again. I wasn't suggesting kded or Kwallet... KDE anything was or could be a security breach, only that it would be an insidious well working way for malware to fish for a user password, and that's why it was scary when I first encountered it! I do have Clam running at all times, and never, ever heard a peep from it! I actually run a scan every once in a while, just to relieve my mind: Still on edge from my Windows days over a decade ago: PTOSSD (Post Traumatic OS Stress Disorder)!
I just added the outputs of "ENV", and "journalctl --user -b" as attachments.
Created attachment 149294 [details] Bob's output of "env" right after boot
Created attachment 149295 [details] Bob's output of journalctl --user -b after boot, but after Evolution auto-loaded (1min delay)
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
I provided the info asked for nearly 15 days ago, and no replies from anyone!
The problem still persists too!
That journalctl log is truncated, it ends saying "lines 1-54" I can see the first half of kwallet auto-unlock get set up, but we can't see when someone first requests the wallet but not when that completes. Can you run the "journalctl --user -b --no-pager" so I can have the full thing.
Created attachment 149641 [details] Better Journalctl Hope this one is more telling: Some of it raises red flags, but not as to this issue AFAIK. Oh dear! )<:
The problem has gone away, but there is nothing here to tell me why, as I purposely did not install Kwalletmanager to track it's progress and provide any other info asked of me. So even if resolved, an answer as to how would help, so just in case it pops up again or anyone else has the problem they can read this report.
Also: the "bug janitor" (cute) is asking me to mark this as reported: I already did weeks ago, and I have no way of doing it again! This makes no sense. Looks like a bug (<:
Just found how to re-report it. My bad.
Jun 12 08:46:26 COMPUTERNAME plasma_session[1682]: org.kde.plasma.session: Starting autostart service "/etc/xdg/autostart/pam_kwallet_init.desktop" ("/usr/lib/pam_kwallet_init") Jun 12 08:46:26 COMPUTERNAME dbus-daemon[1653]: [session uid=1001 pid=1653] Activating service name='org.kde.kwalletd5' requested by ':1.9' (uid=1001 pid=1717 comm="/usr/bin/kded5") Interesting observations: - you're using the legacy (non sytsemd) boot. - in that nothing is ensuring order between kded and pam_kwallet_init. If anything kded is first. - the networking kded modules is in "X-KDE-Kded-phase": 1,