| Summary: | Kwallet crash if you don't accept the crypt type | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-kwallet | Reporter: | Daniele Scasciafratte <mte90net> |
| Component: | general | Assignee: | Valentin Rusu <valir> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | kdedev, kdelibs-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=504678 | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Daniele Scasciafratte
2025-03-06 09:26:57 UTC
If something crashed, we need a backtrace of it so we can figure out what's going on. Can you please re-create the crash and attach a backtrace of the crash using the coredumpctl command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl? Thanks! I am not able to replicate it as I deleted that kwl file with issues. I think that to replicate it is hould be enough to close the wizard to not set the password and start using the kwallet, so it will create the file with the issue. 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! AS I said I am not able to replicate it now and generate the database without the crypt type. on a KDE Neon Testing VM 1. Killed the kwallet6 process 2. Renamed the existing wallet and rebooted - no wizard at this point 3. Opened KDE Wallet, clicked the button to create a new wallet, saw the wizard 4. Chose Blowfish and at the pw prompt, clicked Cancel 5. Rebooted again I didn't see any crashes There is only one very old bug report with a back trace with KWalletD::internalOpen and BACKEND_CIPHER_UNKNOWN - bug 404378. This is for a very old version of kwallet. I don't see any crashes like this on Sentry (our crash aggregation tool). There is only one crash reported for kwallet at all, and it doesn't contain KWallet::BACKEND_CIPHER_UNKNOWN, which means it hasn't been reported in a long time. Without a backtrace, I'm afraid we aren't able to investigate the cause of the crash in the code. It's possible this was a one time fluke. If you do see the crash again, please send a backtrace. You can also see if your system has any crash dumps with crashdumpcl. Thanks. Perfect, in case it will happen again I will keep the kwl file with the issue :-) I am facing the same issue now. mag 20 10:11:53 KITT org.kde.kwalletd6[8296]: kwalletd6: ./src/runtime/kwalletd/kwalletd.cpp:603: int KWalletD::internalOpen(const QString&, const QString&, bool, WId, bool, const QString&): Assertion `b->ciphe$ mag 20 10:11:53 KITT org.kde.kwalletd6[8296]: KCrash: Application 'kwalletd6' crashing... crashRecursionCounter = 2 mag 20 10:11:53 KITT systemd-coredump[8315]: Process 8296 (kwalletd6) of user 10000 terminated abnormally with signal 6/ABRT, processing... mag 20 10:11:53 KITT systemd[1]: Created slice system-drkonqi\x2dcoredump\x2dprocessor.slice - Slice /system/drkonqi-coredump-processor. ░░ Subject: L'unità system-drkonqi\x2dcoredump\x2dprocessor.slice ha terminato la fase di avvio I was thinking of this ticket https://bugs.kde.org/show_bug.cgi?id=504082 as it happens at every boot and the kwallet doesn't work. I sent multiple time with konqi the coredump and installed also the debug symbols. I had the issue again, I had to remove the kwl file and put an old version to fix it again. There has been more information discovered about crashes with KWalletManager, please follow bug 504678 if you want to follow the progress on this. If the crashes you see are not fixed after that bug is fixed, please set this report to REOPENED. |