This bug was fixed in the package ccid - 1.4.22-1ubuntu0.1
---
ccid (1.4.22-1ubuntu0.1) xenial-proposed; urgency=low
* debian/patches/close-libusb-on-failure.patch: Make sure
close_libusb_if_needed is called even if no device was opened,
otherwise it triggers a segfault.
Thanks Martin. I've confirmed that the package solves the issue for me.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
Hello Casey, or anyone else affected,
Accepted ccid into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/ccid/1.4.22-1ubuntu0.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Sorry about that, Martin. Not sure what happened. Just re-uploaded
without the noise.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1551897
Title:
Excessive CPU utilization
Evan: d/patches/close-libusb-on-failure.patch looks fair enough, but
what is debian/patches/test? It's a patch of a patch, not
referenced/explained in the changelog, what does that do? Please either
explain in the changelog or if it is just noise please remove and
reupload. Thanks!
--
You
Hello,
I've the same problem with my laptop (Dell Latitude E7450).
If I can help don't hesitate to ask me. I can give you some logs if you want.
Best regards,
Sylvain
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
** Changed in: ccid (Ubuntu Xenial)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1551897
Title:
Excessive CPU utilization
Status in ccid
** Description changed:
+
+ [DESCRIPTION]
+
+ When hotplugging a composite USB device that expose multiple interfaces
+ (such as a Yubikey NEO or Yubikey 4), libccid does not correctly de-
+ initialize the USB library when it skips over the non-CCID interface.
+
+ This subsequently results in
This is actually a bug in ccid's handling of composite USB devices, and
has been fixed upstream (https://alioth.debian.org/plugins/scmgit/cgi-
bin/gitweb.cgi?p=pcsclite/CCID.git;a=commitdiff_plain;h=3c21f452543983f3625a1965ce234074cbda6865).
My experience was that this bug caused pcscd to
** Also affects: ccid (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ccid (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: pcsc-lite (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: ccid (Ubuntu Xenial)
Status:
** Changed in: pcsc-lite (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1551897
Title:
Excessive CPU utilization
Status in
** Changed in: pcsc-lite (Debian)
Status: Unknown => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1551897
Title:
Excessive CPU utilization
Status in pcsc-lite
** Also affects: pcsc-lite (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812087
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
Thank you Ludovic.
Laptop is quiet again.
(needed to install -dev files to get over /configure errors, if anyone else is
confused)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
Johnny, you can disable support of the Broadcom device.
- Get the source code of the libccid driver from
https://alioth.debian.org/frs/?group_id=30105#title_ccid.
- edit the file readers/supported_readers.txt
- remove the line "0x0A5C:0x5800:Broadcom Corp 5880"
- run the commands
$ ./configure
$
I reported the bug upstream to libudev project
https://github.com/systemd/systemd/issues/2946
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1551897
Title:
Excessive CPU
I use my non-integrated omnikey 1021 usb smartcard-reader, so pcscd is
still needed, correct?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1551897
Title:
Excessive CPU
Johnny, you can remove the pcscd package if you do not use it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1551897
Title:
Excessive CPU utilization
Status in pcsc-lite package
Is there a way to disable the device in software, so i could just use my
usb card-reader?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1551897
Title:
Excessive CPU utilization
It looks like the problem is related to some specific readers only:
Broadcom Corp 5880 and Yubico Yubikey NEO U2F+CCID
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1551897
Title:
So in my case it triggers when i connect some usb device (mouse,
usb-flash-memory, phone). Sometimes it calms down after unmount and unplug of
usb-memory, and does not come back until i logout of lubuntu desktop (and login
and plugin again).
Another way of triggering 100% is in my case having
** Attachment added: "lsusb-v.txt"
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1551897/+attachment/4615641/+files/lsusb-v.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
Johnny, can you attach the result of the command "lsusb -v"?
Thanks
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1551897
Title:
Excessive CPU utilization
Status in pcsc-lite
Sorry again, Ludovic, i have no idea what this pcscd does so i thought its some
general error.
Is this bug device specific? Then i have an Dell laptop with integrated
smart-card reader (which im not using physically, since some metal is bended on
the way of the card.)
(The most used here is
Casey, it looks like the problem is related to the use of a "Yubico Yubikey NEO
U2F+CCID" device.
Unfortunately I do not have such a device myself so I can't reproduce the
problem here :-(
Johnny, why do you say "Probably most people using Estonian ID-Card on those
distros will be affected?"?
hey, sorry, total noob here, what i got is:
pcscdaemon.c:263:main() pcscd set to foreground with debug send to
stdout
0021 debuglog.c:312:DebugLogSetCategory() Debug options: APDU
0016 pcscdaemon.c:268:main() Force colored logs
0037 pcscdaemon.c:403:main() file
Can you do:
sudo LIBUSB_DEBUG=99 pcscd -dfaT | tee log.txt
and add to this bug the created log.txt file?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1551897
Title:
Excessive CPU
Hmm, conveniently just had a crash. No idea if there is anything useful there :
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1561702
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
Probably most people using Estonian ID-Card on those distros will be
affected? Not good :(
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1551897
Title:
Excessive CPU utilization
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pcsc-lite (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
I installed Ubuntu Xenial (beta) in a VirtualBox virtual machine and I
can't reproduce the problem :-(
I could connect a CCID reader and a USB mass storage with no problem on pcscd.
Can you reproduce the problem in a Virtual Machine on your side?
--
You received this bug notification because
I can work around this with my custom build of pcscd with udev disabled,
but it seems that this issue will still affect Debian and Ubuntu users
who install the package.
Can we mark this bug as Confirmed, since my symptoms are so similar to
the descriptions in the Debian bug[1] you've linked
If you use --disable-libudev you use use the older hotplug mechanism.
See
http://ludovicrousseau.blogspot.com/2011/02/pcscd-now-uses-libudev-instead-of.html
At least that will avoid the 100% CPU issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Recompiling with --disable-libudev gets rid of the 100% CPU problem and
I can still use my smartcard.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1551897
Title:
Excessive CPU
** Attachment added: "pcscd binary and core dump"
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1551897/+attachment/4588521/+files/pcscd-core-bin.tar.bz2
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
Here's a core dump with the corresponding pcscd binary I built from
source, which was taken in the above-mentioned gdb session.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1551897
Ran it with gdb, reproduced, and then interrupted when it started
consuming 100% CPU:
Thread 1 "pcscd" received signal SIGINT, Interrupt.
0x774e2853 in select () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0 0x774e2853 in select () from /lib/x86_64-linux-gnu/libc.so.6
#1
Oh, here's /var/log/syslog from unplugging and replugging in my camera.
I Ctrl-C killed pcscd after it went to 100% each time.
pcscd segfaulted.
Mar 4 12:04:11 mawhrin-skel pcscd: debuglog.c:289:DebugLogSetLevel() debug
level=debug
Mar 4 12:04:13 mawhrin-skel kernel: [14604.513268] usb 3-1:
It starts consuming 100% CPU after this:
02341452 hotplug_libudev.c:642:HPEstablishUSBNotifications() USB Device removed
0217 hotplug_libudev.c:619:HPEstablishUSBNotifications()
0068 hotplug_libudev.c:642:HPEstablishUSBNotifications() USB Device removed
0149
Does your log trace include the moment when pcscd consumed 100% of CPU?
I ask because I could not find anything strange in the trace.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
I ran pcscd as you suggested, capturing output. Made sure the smart card
was working by using my SSH key. I was then able to reproduce the 100%
cpu condition by plugging in my Logitech USB webcam.
Attached the output, but I redacted the hex dumps before posting here
because I'm not sure if they
It looks like https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812087
Can you rebuild pcscd with hotplug debug enabled. No need to install
pcscd so you can't break your installation.
1. Get the source code of pcsc-lite, for example from
This is what I've got installed ^^
c@mawhrin-skel:~/omnibus-layers$ dpkg -l | grep pcscd
ii pcscd 1.8.14-1ubuntu1
amd64Middleware to access a smart card using PC/SC
(daemon side)
--
You received this bug notification
43 matches
Mail list logo
