Nachdem ich nun alle beteiligten Programme mit den Quellen auf die aktuellesten Versionen gebracht habe, komme ich leider auch nicht weiter.
Die Chipkarte wird zwar vom pcscd erkannt, aqhbci-tool3 kann sich aber scheinbar nicht verbinden.

alle Bibliotheken und auch aqbanking-2.9.2beta sind ohne Fehlermeldung durch gelaufen und installiert.
Folgende Versionen habe ich installiert:

aqbanking-2.9.2beta.tar.gz
gwenhywfar-2.9.1beta.tar.gz
libchipcard-3.9.1beta.tar.gz
libofx-0.8.3.tar.gz
scr3xxx_2.6.x_v4.6.5_Release.tar.gz


Hier die Ausgabe vom Programmaufruf:

# aqhbci-tool3 addmedium -t card
Loading plugin "starcoscard"
Checking plugin "starcoscard"
3:2007/07/07 16-56-38:gwen(13073):inetsocket.c: 225: connect(): No such file or directory
3:2007/07/07 16-56-38:gwen(13073):ipc.c: 1141: Could not connect
3:2007/07/07 16-56-38:gwen(13073):ipc.c: 593: Could not send request
3:2007/07/07 16-56-38:chipcard3-client(13073):clientlcc.c: 497: Could not send command
3:2007/07/07 16-56-38:chipcard3-client(13073):clientlcc.c: 1006: Could not start connecting to server
3:2007/07/07 16-56-38:chipcard3-client(13073):clientlcc.c: 1197: Errors on all servers
3:2007/07/07 16-56-38:chipcard3-client(13073):clientlcc.c: 1806: Error working on client
3:2007/07/07 16-56-38:chipcard3-client(13073):clientlcc_cmd.c: 114: No response for request "startWait"
3:2007/07/07 16-56-38:chipcard3-client(13073):starcoscard.c: 132: Could not send Start request
Plugin "starcoscard": Unexpected error (-103)
Loading plugin "ddvcard"
Checking plugin "ddvcard"
3:2007/07/07 16-56-38:gwen(13073):inetsocket.c: 225: connect(): No such file or directory
3:2007/07/07 16-56-38:gwen(13073):ipc.c: 1141: Could not connect
3:2007/07/07 16-56-38:gwen(13073):ipc.c: 593: Could not send request
3:2007/07/07 16-56-38:chipcard3-client(13073):clientlcc.c: 497: Could not send command
3:2007/07/07 16-56-38:chipcard3-client(13073):clientlcc.c: 1006: Could not start connecting to server
3:2007/07/07 16-56-38:chipcard3-client(13073):clientlcc.c: 1197: Errors on all servers
3:2007/07/07 16-56-38:chipcard3-client(13073):clientlcc.c: 1806: Error working on client
3:2007/07/07 16-56-38:chipcard3-client(13073):clientlcc_cmd.c: 114: No response for request "startWait"
3:2007/07/07 16-56-38:chipcard3-client(13073):ddvcard.c: 130: Could not send StartWait request
Plugin "ddvcard": Unexpected error (-103)
3:2007/07/07 16-56-38:(null)(13073):hbci.c: 608: Token is not supported by any plugin
3:2007/07/07 16-56-38:(null)(13073):addmedium.c: 142: Medium not supported

Äh, die ganze von dir verwendete Reihe ist noch *instabil*. Bitte bleib bei gwenhywfar-2.6.x, aqbanking-2.3.x und libchipcard-3.1.x und wechsle noch nicht zu den x.9.x Versionen, sofern du nicht selber daran herumprogrammieren willst.

Das bedeutet, Du hast Libchipcard nicht korrekt eingerichtet. Die Adresse des Servers muss in der Client- und der Daemondatei gleich sein, und der Libchipcard daemon muss laufen.


Gruss
Martin

thanks for your help.
Apperantly I was mixing the two installations
One from the ubuntu repository and one from source.
As I figured that out. Everything seemed to be fine.
At first
chipcard-tool list shows me my reader:
# chipcard-tool list
Server: 46ab9489
Readers:
- auto1-ccid_scm_335 (ccid_scm_335, port 0)

But the server log shows:

5:2007/07/28 21-32-13:chipcardd(22183):clr_clientready.c: 93: Client "46ab996d" started (chipcard3-tool, Gwen 2.9.1beta, ChipCard 3.9.1.0beta)
5:2007/07/28 21-32-13:chipcardd(22183):clr_notification.c: 468: Client 46ab996d: SetNotify [chipcard3-tool/nobody]
5:2007/07/28 21-32-13:chipcardd(22183):cs_callbacks.c: 31: One of my connections is down
5:2007/07/28 21-32-13:chipcardd(22183):clientmanager.c: 355: Removing client 46ab996d [chipcard3-tool/nobody]

May "One of my connections is down" be a problem ?
Because if I try "chipcard-tool check" I get an error:
In the server log:
5:2007/07/28 21-33-09:chipcardd(22183):clr_clientready.c: 93: Client "46ab9972" started (chipcard3-tool, Gwen 2.9.1beta, ChipCard 3.9.1.0beta)
5:2007/07/28 21-33-09:chipcardd(22183):clr_notification.c: 468: Client 46ab9972: SetNotify [chipcard3-tool/nobody]
5:2007/07/28 21-33-09:chipcardd(22183):clr_startwait.c: 63: Client 46ab9972: StartWait [chipcard3-tool/nobody]
5:2007/07/28 21-33-11:chipcardd(22183):devicemanager.c: 2014: Driver "46ab995b" (ccid_ifd) is up (Library loaded)
3:2007/07/28 21-33-12:chipcardd(22183):devicemanager.c: 1328: Driver reported error on startup of reader "auto1-ccid_scm_335": Unknow error code
5:2007/07/28 21-33-12:chipcardd(22183):cs_callbacks.c: 31: One of my connections is down
5:2007/07/28 21-33-12:chipcardd(22183):clientmanager.c: 355: Removing client 46ab9972 [chipcard3-tool/nobody]

5:2007/07/28 21-33-43:chipcardd(22183):devicemanager.c: 1158: Driver "ccid_ifd" is too long idle, stopping it
5:2007/07/28 21-33-44:chipcardd(22183):cs_callbacks.c: 31: One of my connections is down
5:2007/07/28 21-33-44:chipcardd(22183):devicemanager.c: 1737: Connection of driver "ccid_ifd" (46ab995b) just went down
4:2007/07/28 21-33-44:chipcardd(22183):devicemanager.c: 965: Driver terminated normally

And the client shows:
Readers:
- auto1-ccid_scm_335 (ccid_scm_335, port 0, ): error
Event log:
21:33:09 Reader listing
21:33:12 Reader error (Unknow error code)

So the communication between server and client should be fine.
But the reader seems to make some problems...

Any ideas ?

BTW: That is not a problem, if you disconnect (e.g. the client application ends) then the connection naturally is terminated, and that's all this message is about.


That's the real problem: You should consult the reader logs to see what error the device reports.


Regards
Martin