This bugreport has had no activity and has eol. Closing.
** Changed in: pcsc-lite (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366152
Title:
System crash
Does the SIGSEGV, Segmentation fault happens inside
udev_monitor_receive_device()?
In that case can you update libudev?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366152
Title:
System crash whe
It looks that the program is crashing somewhere on a process-fork
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb7cfcb40 (LWP 9526)]
0xb7d0b442 in ?? ()
(gdb) bt
#0 0xb7d0b442 in ?? ()
#1 0xb7cfc340 in ?? ()
#2 0xb7ec24ce in clone () at ../sysdeps/unix/sysv/linux/i
$ gdb /usr/local/sbin/pcscd
(gdb) set args -dfa
(gdb) run
remove the reader do make pcscd crash
(gdb) backtrace
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366152
Title:
System crash when Vasco-c
I'm able to build these packages (./configure, make and sudo make
install - after installing the missing packages). I know how to debug
C/C++-programs, but I have never done this for such a type of
application. If you can help me with some commands in order to start the
debugging of the build softw
Could you rebuild pcsc-lite and libccid yourself and install them in
/usr/local/ or somewhere else to try to debug the problem?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366152
Title:
System cr
Hi,
I fear that that the backtrace will be rather disappointing, as the gdb
doesn't find any symbols for the pcscd-binary. Now the odd thing is, if
you start the gdb if you then remove the card-reader for the first time,
it doesn't crash. It is only the second time when the read is removed
that th
LogCardReader%40Powerup.txt indicates that the device is not responding
correctly:
0024 -> 00 65 00 00 00 00 00 00 00 00 00
05000412 ccid_usb.c:751:WriteUSB() write failed (1/4): -7 Resource temporarily
unavailable
-7 is LIBUSB_ERROR_TIMEOUT
So the device is not visible at the PC/SC lev
Thank you Ludovic for your quick response.
I generated to log-files,
logcardrea...@powerup.txt in case it goes wrong (only when the card-reader is
plugged in while the computer is starting-up or rebooting
LogCardReaderOK.txt after the crash - removed the reader and sudo
service pcscd start
/usr
And log-file when the reader is ok
** Attachment added: "LogCardReaderOK.txt"
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1366152/+attachment/4196928/+files/LogCardReaderOK.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Please generate a pcscd trace as described at
http://pcsclite.alioth.debian.org/pcsclite.html#support
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366152
Title:
System crash when Vasco-card-reader
11 matches
Mail list logo