Bug 2003480 - libchipcard is missing
Summary: libchipcard is missing
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: aqbanking
Version: 37
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2035958
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-12 19:45 UTC by ingli
Modified: 2022-11-10 22:14 UTC (History)
3 users (show)

Fixed In Version: aqbanking-6.5.3-2.fc37
Clone Of:
Environment:
Last Closed: 2022-11-10 22:14:44 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description ingli 2021-09-12 19:45:58 UTC
Description of problem:

I want to use aqbanking via Gnucash. With aqbanking I want to access a chip card. When trying to add a chipcard in the "create user" interaction, aqbanking it misses "libchipcard or its plugins".



Version-Release number of selected component (if applicable):
 AqBanking    : 6.2.9.0


How reproducible:
from within gnucash -> tools -> online banking setup -> Next -> Start AqBanking Assiatant -> Create user -> Next -> HBCI backend -> Import an already used chipcard. Then I get an error message, saying "libchipcard or its plugins" may not be installed.



Actual results:
I cannot add a chipcard

Expected results:
I want to use my chipcard reader

Additional info:

ok, complete issue: I want to set up a reiner sct cyberjack card reader to access banking accounts via the HBCI protocol.

Comment 1 Ben Cotton 2022-05-12 15:28:48 UTC
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.

Comment 3 Ben Cotton 2022-08-09 13:12:04 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle.
Changing version to 37.

Comment 4 Fedora Update System 2022-10-11 13:27:29 UTC
FEDORA-2022-413ad16875 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-413ad16875

Comment 5 Fedora Update System 2022-10-11 15:52:42 UTC
FEDORA-2022-413ad16875 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-413ad16875`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-413ad16875

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2022-11-10 22:14:44 UTC
FEDORA-2022-413ad16875 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.