| 2023-04-18 18:41:19 |
Chorca |
bug |
|
|
added bug |
| 2023-04-18 18:41:19 |
Chorca |
attachment added |
|
Syslog snipped from crash loop https://bugs.launchpad.net/bugs/2016914/+attachment/5665043/+files/gsd-smartcard_crash_syslog.txt |
|
| 2023-04-18 22:28:47 |
Erich Eickmeyer |
gnome-settings-daemon (Ubuntu): status |
New |
Incomplete |
|
| 2023-04-19 00:31:55 |
Chorca |
description |
A smartcard reader attached to the computer on startup, containing a non-standard smartcard (in this case an NXP AV3 SAM card) causes gsd-smartcard to segfault and restart 200 times after login. |
A smartcard reader attached to the computer on startup, containing a non-standard smartcard (in this case an NXP AV3 SAM card) causes gsd-smartcard to segfault and restart 200 times after login.
System Info:
This is Ubuntu 22.04.2 LTS at Kernel 5.19.0-38-generic
The Smart Card reader is an Identiv uTrust 4711 F with both SAM and Contactless slots
The system is an HP ZBook Firefly 14 G7
Detailed issue:
When the smartcard reader is plugged into the system, and an NXP SAM AV3 card is inserted into the physical smartcard slot, upon login several (5) Ubuntu Error report windows will open asking to report a crash. The reader lights will flicker for about 5 minutes until they finally stop. No other issues are seen with the system during this time.
Upon looking at /var/log/syslog, the errors listed in the attachment are visible as it appears gsd-smartcard is in a loop of restarting and crashing following an error.
/var/crash contains two files from the crash loop, _usr_libexec_gsd_smartcard.1000.crash and _usr_libexec_gsd_smartcard_127.crash
Eventually the crashes seem to stop and the light stops flickering, but a logout and log back in will restart the issue again, as will rebooting the machine. Re-plugging the device while logged in does not seem to cause it to start the crash loop again.
To complete the standard questions:
1. I logged into my computer and saw error messages
2. I expected the smart card to be ignored if there was a card inserted that was unexpected or incompatible with the gnome settings daemon
3. I encountered several crash reporter messages upon logging in, which seem to have come from the gsd-smartcard program |
|
| 2023-04-25 14:40:14 |
Chorca |
gnome-settings-daemon (Ubuntu): status |
Incomplete |
New |
|
| 2023-05-04 14:36:58 |
Launchpad Janitor |
gnome-settings-daemon (Ubuntu): status |
New |
Confirmed |
|
| 2023-05-04 14:53:14 |
Sebastien Bacher |
gnome-settings-daemon (Ubuntu): importance |
Undecided |
High |
|
| 2023-05-04 14:53:14 |
Sebastien Bacher |
gnome-settings-daemon (Ubuntu): status |
Confirmed |
Incomplete |
|
| 2023-07-09 04:17:35 |
Launchpad Janitor |
gnome-settings-daemon (Ubuntu): status |
Incomplete |
Expired |
|
| 2024-04-29 13:09:46 |
Timothée COCAULT |
gnome-settings-daemon (Ubuntu): status |
Expired |
Incomplete |
|
| 2024-05-02 09:29:25 |
Sebastien Bacher |
gnome-settings-daemon (Ubuntu): status |
Incomplete |
Triaged |
|
| 2024-05-05 14:06:36 |
Timothée COCAULT |
bug watch added |
|
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/795 |
|
| 2024-05-05 16:09:20 |
Sebastien Bacher |
bug task added |
|
gnome-settings-daemon |
|
| 2024-05-06 17:03:28 |
Bug Watch Updater |
gnome-settings-daemon: status |
Unknown |
New |
|
