Something's wrong with scan after resume. Not sure if it's NM or kernel
bug, but doing 'sudo iw wlan0 scan' fixes the issue till next
suspend/resume.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/15909
(In reply to ncdehnel from comment #19)
> I have a laptop with one of these devices and am thinking about either
> volunteering for instruction or mailing it to you for you to do it. I assume
> reverse engineering the device won't require destructive modification of it?
Usually I use VM with Windo
(In reply to ncdehnel from comment #16)
> Roughly how much effort would it take to make this driver?
Depends. If protocol is not encrypted and device doesn't require any
fancy handshake, it takes 2-3 days for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Please recompile libfprint with --enable-debug-log passed to
configure, try to enroll with fprint_demo and then attach logs that
were produced.
On Fri, Dec 4, 2015 at 2:20 AM, Kevin wrote:
> I also have the AES2810 reader in my X200s ThinkPad, also installed
> fprint from PPA, and get the same er
On Mon, Nov 23, 2015 at 4:45 PM, Jonas Strassel wrote:
> Hi there,
>
> can somebody confirm this working in 14.04 or newer?
I'm not running Ubuntu, but it used to work for me half a year ago.
I've no idea what could be broken. Have no access to the device ATM.
> I installed
>
> sudo apt-get inst
Merged.
http://cgit.freedesktop.org/libfprint/libfprint/commit/?id=dc537ef2c9b1ee62e88db02560abcead4f9486f9
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790183
Title:
[138a:0011] Fingerprint reade
(In reply to Diego López León from comment #64)
> Vasily,
> Thanks for your recommendation, I just tested it against current master and
> it seems to work fine.
>
> I can even notice a better matching rate comparing with 5.1. I don't know if
> the differences between 5.1 and master justifies this
(In reply to Bastien Nocera from comment #66)
> Vasily, let me know when you've merged/reviewed, and I'll do a release.
> I'm a bit lost on the status :)
Sure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
(In reply to Diego López León from comment #62)
> I can confirm this patch works fine applied on top of libfprint_0.5.1-1 from
> the Debian Archives. I just _debianized_ it for ease applying at
> https://gist.github.com/diega/2e1d2d7700480de0 (I though it was better
> to upload there instead of
Created attachment 110999
0001-lib-Add-VFS5011-driver.patch
Please test if this version works for you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790183
Title:
[138a:0011] Fingerprint reader Val
(In reply to Whoopie from comment #58)
> With the lastest version, I get the error message:
>Enroll result: enroll-unknown-error
>VerifyStop failed: Message did not receive a reply (timeout by message
> bus)
>
> The syslog shows:
> Dec 18 21:07:52 v131 kernel: [26042.424432] usb 2-1.3: res
(In reply to comment #43)
> What is chance to include this path in next release?
It'll be included. I still need to finish several features and a single
driver for a next release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Guys, I must admit that it's close to impossible to reverse device
protocol without device available. So unless there's a standalone USB
scanner with broadcom sensor available I won't work on its support for
libfprint. So reversing protocol and implementing libfprint driver is up
to you.
Please re
(In reply to comment #37)
> I don't get any reply from Validity Sensors for a whole week.
> So, I think this is probably the best we can do for now.
Could you also estimate power consumption (via powertop) before first
use of the fingerprint scanner (i.e. after fresh boot) and after first
use? I'm
(In reply to comment #33)
> Sorry to take so long to re-submit the patch,
> I'm not familiar with the lib, so takes some time to study it.
>
> For your questions.
> 1. Because you need to wait for completion of these transfers, but probably
> you don't.
> Actually, we don't have to wait.
> When op
(In reply to comment #13)
> Hi, I own a device with this reader and would like to help to get it
> supported. I am not a developer, but capable of entering console commands,
> testing an output, modifying a config file, compiling in a kernel module. I
> could also create a clean account that a deve
(In reply to comment #30)
> Created attachment 83699 [details] [review]
> 0001-lib-Add-VFS5011-driver.patch
>
> Sorry to take so long to resend the patch.
>
> @@ +1000,5 @@
> >> +
> >> + struct fpi_ssm *ssm;
> >> + ssm = fpi_ssm_new(dev->dev, open_loop, DEV_OPEN_NUM_STATES);
> >> + ssm->priv =
(In reply to comment #28)
> Sorry for reply late, I was on vacation, I'll try to revise those part of
> code soon.
No pb, I was busy as well :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790183
Ti
Btw, I feel like not all issues from previous patch were fixed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790183
Title:
[138a:0011] Fingerprint reader Validity Sensors not recognized
To manage
Comment on attachment 82310
0001-lib-Add-VFS5011-driver.patch
Review of attachment 82310:
-
::: libfprint/drivers/vfs5011.c
@@ +33,5 @@
> + }
> + fp_dbg(s);
> +#endif
> +}
> +
Please drop all debugging stuff from driver. Onl
(In reply to comment #18)
> *poke*
> Could you please speed up the review process?
> There are many users suffered from this.
> Thanks.
It's already reviewed, and there were no new version to review.
I won't accept driver with synchronous transfers.
--
You received this bug notification because
(In reply to comment #21)
> (In reply to comment #20)
> > Could you advice us which driver is good for reference, so that Arseniy
> > could follow that one to rewrite it.
>
> There's no need to rewrite my driver, just minor changes here and there.
>
> > Or if Arseniy is unavailable to do it now,
It's supported by latest libfprint-0.5.0, you can install it from this
ppa: https://launchpad.net/~fingerprint/+archive/fprint
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065493
Title:
The "08ff:
Please capture at least 3 sniffs with similar conditions, i.e. start
capture on _clean_ boot, do capture of same event. Need them to analyze
what part of traffic changes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
(In reply to comment #8)
> If needed, I can provide usb sniffs about it.
It would be nice
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/745505
Title:
[138a:0007] VFS451 fingerprint reader not recog
(In reply to comment #6)
> Created attachment 70823 [details] [review]
> call rrprovider init where it should be called
>
> this implements option 3, no idae where this hunk got lost.
This patch fixes crash for me, thanks!
--
You received this bug notification because you are a member of Ubuntu
Is it available as a standalone USB device? Any chance to get logs
captured by USBSniff under windows? See
http://www.freedesktop.org/wiki/Software/fprint/libfprint/USB%20sniffing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
You can disable/enable it in device manager.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/602071
Title:
[0a5c:5801] Broadcom fingerprint reader not working
To manage notifications about this bug g
fprint ppa was updated recently and now supports AES2550 and AES2810,
see https://launchpad.net/~fingerprint/+archive/fprint
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/657031
Title:
[08ff:2810] A
@sandrefuego: not yet, at least in libfprint, probably you should ask
AuthenTec for specs... Anyway, I have only AES2501 and AES2550
scanners...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/657031
Ti
Well, it depends completely on device. Driver sends "set idle mode"
command to it right after imaging session
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/657031
Title:
[08ff:2810] AuthenTec, Inc.
High freq sound is weird anyway, no such issue here... Maybe it's not
fingerprint issue, I hear high pitch sound when ac adapter is unplugged
(Lenovo 3000 N100 laptop), even with fingerprint scanner disconnected
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
You should build updated libfprint package and install it into system.
GDM (and Gnome3) use fprintd, so you'll be able to scan finger instead
of entering password, not sure about unity/kde4. Btw I've asked fprint
ppa team (https://launchpad.net/~fingerprint/+archive/fprint) to build
updated libfpri
Just invoke ./autogen.sh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/657031
Title:
[08ff:2810] AuthenTec, Inc. AES2810 fingerprint reader not recognized
(worked in 10.04)
To manage notification
Please provide log produced by ./enroll or ./verify
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/657031
Title:
[08ff:2810] AuthenTec, Inc. AES2810 fingerprint reader not recognized
(worked in 10.
Uh, also do "git checkout origin/aes2550-v2 -b aes2550-v2 --track" right
after "git clone"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/657031
Title:
[08ff:2810] AuthenTec, Inc. AES2810 fingerprint
@Zeth:
You can compile it manually (but don't install it into the system, wait
for someone who can make ppa with this lib)
sudo apt-get install build-essential libusb-1.0-0-dev
cd ~
git clone git://github.com/anarsoul/libfprint.git
cd libfprint
./configure --enable-debug-log
make all
cd exa
I've implemented AES2550/AES2810 driver for libfprint, my libfprint repo
is here: https://github.com/anarsoul/libfprint branch aes2550-v2. I need
some testers with AES2550 and AES2810 devices. Any volunteers?
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Actually, problem is fixed in swt-gtk-3.5.2, so if it's possible to bump
version in releases with swt-gtk-3.5.x it's better to do this. No need
in swt-gtk-3.6 for these releases.
--
not everything is display correctly
https://bugs.launchpad.net/bugs/455615
You received this bug notification becau
I've created PPA with updated version of libswt (it's cause of a
problem), just upgrade libswt from my ppa and problem should gone away.
sudo apt-add-repository ppa:anarsoul/anarsoul
sudo apt-get update
sudo apt-get upgrade
--
not everything is display correctly
https://bugs.launchpa
It seems to be BIOS bug. So it's better report directly to Lenovo. But
unfortunately they don't care, and they do not support Linux anymore.
--
Lenovo 3000 N100 overheats when running 2.6.20-15-generic
https://bugs.launchpad.net/bugs/114312
You received this bug notification because you are a mem
41 matches
Mail list logo
