Bug 1910478
Summary: | KMyMoney crashes on each account update | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Eric L. <ewl+redhat> |
Component: | kmymoney | Assignee: | Rex Dieter <rdieter> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 36 | CC: | cricketc, grewater, marc-schmitzer, rdieter, smparrish, vascom2 |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | kmymoney-5.1.3-1.fc37 kmymoney-5.1.3-1.fc36 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-12-30 00:31:04 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1911707 | ||
Bug Blocks: |
Description
Eric L.
2020-12-24 06:24:15 UTC
Try version 5.1.1 https://bodhi.fedoraproject.org/updates/FEDORA-2020-99ee3aac27 I didn't see any difference, it also crashes and the stack trace looks very similar. Nevertheless, starting KMyMoney from the command line, I see the following: ``` $ kmymoney WebConnect: Running in server mode 4:2020/12/26 06-43-55:aqbanking(15584):banking_cfg.c: 668: No matching config groups found 4:2020/12/26 06-43-55:aqbanking(15584):banking_cfg.c: 668: No matching config groups found 4:2020/12/26 06-43-55:aqbanking(15584):banking_cfg.c: 668: No matching config groups found 4:2020/12/26 06-43-55:aqbanking(15584):banking_cfg.c: 668: No matching config groups found 4:2020/12/26 06-43-55:aqbanking(15584):banking_cfg.c: 668: No matching config groups found 4:2020/12/26 06-43-55:aqbanking(15584):banking_cfg.c: 668: No matching config groups found 4:2020/12/26 06-43-55:aqbanking(15584):banking_cfg.c: 668: No matching config groups found 4:2020/12/26 06-43-55:aqbanking(15584):banking_cfg.c: 668: No matching config groups found 3:2020/12/26 06-44-03:aqbanking(15584):dlg_setup.c: 214: Got id "23 id from "000023 <BLZ> <BANK><AccountNumber> <AccountName> <AccountOwner> AQHBCI" 3:2020/12/26 06-44-12:(null)(15584):cppgui.cpp: 141: CppGuiLinker::OpenDialog 3:2020/12/26 06-44-23:gwen(15584):dialog.c: 695: Widget [storePasswordCheck] not found Segmentation fault (core dumped) ``` Could it point at a missing library? I recently did some clean-up of unnecessary libraries, and I might have removed a required library which isn't listed as dependency by kmymoney. Can you find bug in upstream or report it? https://bugs.kde.org/ (In reply to Vasiliy Glazov from comment #3) > Can you find bug in upstream or report it? > https://bugs.kde.org/ Submitted the same issue to upstream here. Their diagnosis: It's related to version mismatch with aqbanking / gwenhyfwar https://bugs.kde.org/show_bug.cgi?id=430752 I will contact with maintainer of these packages and ask about update. Issue persists with kmymoney-5.1.1 I updated aqbanking and gwenhyfwar in rawhide. Can you check? Or I need to rebuild kmymoney with updated libs? I installed aqbanking 6.2.5 and gwenhyfwar 5.4.1 from rawhide. kmymoney (5.1.1) still crashed on account update. After F34 MassRebuild end try kmymoney from rawhide. Or you can give me steps to reproduce crash. I have not use this functionality. Sorry, I cannot give you steps to reproduce because you need access to a FinTS/HBCI-capable bank account. As a temporary fix, I'm using the kmymoney-AppImage https://kmymoney.org/appimage.html Then I will update libs for F33 and rebuild kmymoney with them. I will ping you for test ;) Fyi I just tested the current rawhide with F33 and the issue is still present. ➜ ~ rpm -q gwenhywfar kmymoney aqbanking && uname -r gwenhywfar-5.6.0-1.fc35.x86_64 kmymoney-5.1.1-2.fc34.x86_64 aqbanking-6.2.8-1.fc35.x86_64 5.10.22-200.fc33.x86_64 Also upgrading glibc to rawhide and then downgrading it back to release apparently broke my entire installing. So thanks for that idea… Any news from this? It's quite a pain that I can't do my banking since almost half a year. I can only update aqbanking to 6.2.9. This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. This issue persists in Fedora 34. Therefore, I ask the package maintainer to transfer the issue to version 34, so we don't have to re-report everything in a new issue. Issue persists in Fedora 35. ➜ ~ rpm -q kmymoney kmymoney-5.1.2-2.fc35.x86_64 This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed. Issue persists in Fedora 35. ➜ ~ rpm -q kmymoney kmymoney-5.1.2-2.fc35.x86_64 Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed. Please reopen for 36. FEDORA-2022-8b18c97f08 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-8b18c97f08 FEDORA-2022-3e9b3ed92d has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-3e9b3ed92d FEDORA-2022-8b18c97f08 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-8b18c97f08` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-8b18c97f08 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-3e9b3ed92d has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-3e9b3ed92d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-3e9b3ed92d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-3e9b3ed92d has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-8b18c97f08 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. |