Please, provide a coredump or backtrace from the crashing process. Without it, I can not even guess what could go wrong in opensc nor in gnome.

It would be also useful to see some more information about the card, if it is readbale using pkcs11-tool or p11tool.

Created attachment 1327633 [details]
This is the abrt output from the customer

The backtrace in the attachment ends in the pam_pkcs11 (moving to this component). Investigating the coredump further we can see the following:

#1  0x00007f0c53b76602 in scconf_item_find (parser=0x7fffa9299130, parser=0x7fffa9299130, 
    key=<optimized out>) at parse.c:85
85			    strcasecmp(item->key, parser->key) == 0) {
(gdb) l
80	{
81		scconf_item *item;
82	
83		for (item = parser->block->items; item; item = item->next) {
84			if (item->type == SCCONF_ITEM_TYPE_VALUE &&
85			    strcasecmp(item->key, parser->key) == 0) {
86				return item;
87			}
88		}
89		return item;
(gdb) p item
$1 = (scconf_item *) 0x55d7e4717310
(gdb) p *item
$2 = {next = 0x55d7e46f4f40, type = 2, key = 0x55d7e4713480 "nullok", value = {
    comment = 0x55d7e4714e50 "", block = 0x55d7e4714e50, list = 0x55d7e4714e50}}
(gdb) p *item->key
$3 = 110 'n'
(gdb) p parser
$4 = (scconf_parser *) 0x7fffa9299130
(gdb) p *parser
$5 = {config = 0x55d7e4714fc0, block = 0x55d7e4713550, last_item = 0x55d7e4717c80, 
  current_item = 0x55d7e4717c80, key = 0x0, name = 0x55d7e4717cb0, state = 17, last_token_type = 2, 
  line = 33, error = 0, warnings = 0, emesg = '\000' <repeats 255 times>}
(gdb) p *parser->key
Cannot access memory at address 0x0

This is happening during parsing of the file /etc/pam_pkcs11/pam_pkcs11.conf (can you attach the content of this file from customer machine -- it is not in the sosreport). Even though the file can have a typo, the pam_pkcs11 should not crash.

need the /etc/pam_pkcs11/pam_pkcs11.conf on the crashing machine.

Created attachment 1329590 [details]
pam_pkcs11 conf

fixed in pam_pkcs11-0.6.2-28.el7

[root@dhcp129-107 ~]# rpm -qi pam_pkcs11
Name        : pam_pkcs11
Version     : 0.6.2
Release     : 28.el7
Architecture: x86_64
Install Date: Tue 28 Nov 2017 04:11:05 PM EST
Group       : System Environment/Base
Size        : 1101210
License     : LGPLv2+
Signature   : RSA/SHA256, Wed 01 Nov 2017 08:33:05 PM EDT, Key ID 199e2f91fd431d51
Source RPM  : pam_pkcs11-0.6.2-28.el7.src.rpm
Build Date  : Wed 01 Nov 2017 07:05:25 PM EDT
Build Host  : x86-030.build.eng.bos.redhat.com
Relocations : (not relocatable)
Packager    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
Vendor      : Red Hat, Inc.
URL         : http://www.opensc-project.org/pam_pkcs11
Summary     : PKCS #11/NSS PAM login module

[root@dhcp129-107 ~]# rpm -qi opensc
Name        : opensc
Version     : 0.16.0
Release     : 7.20170227git777e2a3.el7
Architecture: x86_64
Install Date: Mon 18 Dec 2017 01:10:47 PM EST
Group       : System Environment/Libraries
Size        : 3262790
License     : LGPLv2+
Signature   : RSA/SHA256, Thu 09 Nov 2017 08:06:31 AM EST, Key ID 199e2f91fd431d51
Source RPM  : opensc-0.16.0-7.20170227git777e2a3.el7.src.rpm
Build Date  : Thu 09 Nov 2017 07:40:40 AM EST
Build Host  : x86-039.build.eng.bos.redhat.com
Relocations : (not relocatable)
Packager    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
Vendor      : Red Hat, Inc.
URL         : https://github.com/OpenSC/OpenSC/wiki
Summary     : Smart card library and applications
.
[root@dhcp129-107 ~]# rpm -qi gdm
Name        : gdm
Epoch       : 1
Version     : 3.26.2.1
Release     : 3.el7
Architecture: x86_64
Install Date: Tue 28 Nov 2017 04:09:08 PM EST
Group       : User Interface/X
Size        : 2270157
License     : GPLv2+
Signature   : (none)
Source RPM  : gdm-3.26.2.1-3.el7.src.rpm
Build Date  : Wed 15 Nov 2017 11:14:53 AM EST
Build Host  : x86-020.build.eng.bos.redhat.com
Relocations : (not relocatable)
Packager    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
Vendor      : Red Hat, Inc.
URL         : http://download.gnome.org/sources/gdm
Summary     : The GNOME Display Manager


Does not see the issues mentioned in the bug bug description. Successful gdm login using alt token and other CAC cards.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0961