[Bug 1590985] Re: Wifi non-functional after suspend (Intel 6205)
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/1590985 Title: Wifi non-functional after suspend (Intel 6205) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 745505]
(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 Windows in it and Linux host with wireshark to capture USB traffic. So it doesn't require any hw modifications at all. -- 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 recognized To manage notifications about this bug go to: https://bugs.launchpad.net/fingerprint-gui/+bug/745505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 745505]
(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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/745505 Title: [138a:0007] VFS451 fingerprint reader not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/fingerprint-gui/+bug/745505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 657031] Re: [08ff:2810] AuthenTec, Inc. AES2810 fingerprint reader not recognized (worked in 10.04)
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 error as Jonas. Windows 10 is using > the reader well, Ubuntu15.10 recognizes it, adds the aes2550 driver, but > the enroll stops with unknown error. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/657031 > > Title: > [08ff:2810] AuthenTec, Inc. AES2810 fingerprint reader not recognized > (worked in 10.04) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu-release-notes/+bug/657031/+subscriptions -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/657031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 657031] Re: [08ff:2810] AuthenTec, Inc. AES2810 fingerprint reader not recognized (worked in 10.04)
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 install libfprint0 fprint-demo libpam-fprintd gksu-polkit > > from the ppa ppa:fingerprint/fprint. > > My lsusb confirms the AES2810: > > Bus 004 Device 002: ID 08ff:2810 AuthenTec, Inc. AES2810 > > in a Lenovo X200. > The reader works in Windows10 without problems. > > $ fprintd-enroll > Using device /net/reactivated/Fprint/Device/0 > Enrolling right-index-finger finger. > Enroll result: enroll-unknown-error ## this is independent from me rolling > the finger > VerifyStop failed: Did not receive a reply. Possible causes include: the > remote application did not send a reply, the message bus security policy > blocked the reply, the reply timeout expired, or the network connection was > broken. > > $fprint_demo > > Neither works, but displays the chip and says it uses AES2550 driver. > If I run the same with sudo gives me the same result. > > If somebody could confirm this still working / not working anymore with > AES2810, I would appreciate that very much! > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/657031 > > Title: > [08ff:2810] AuthenTec, Inc. AES2810 fingerprint reader not recognized > (worked in 10.04) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu-release-notes/+bug/657031/+subscriptions -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/657031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 790183]
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 reader Validity Sensors not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/790183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 790183]
(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 behavior or it is just > my impression, but it worth to mention. > > Again, the patch for applying it on top of a debian build for master@35e356f > is in https://gist.github.com/diega/3b8a8cc5f5588076fd39 Thanks for testing! -- 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 notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/790183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 790183]
(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/bugs/790183 Title: [138a:0011] Fingerprint reader Validity Sensors not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/790183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 790183]
(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 taint this bug report with another file) Diego, please test it against git master. There were some changes since 0.5.1, such as several scans during enrollment for all imaging scanners. -- 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 notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/790183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 790183]
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 Validity Sensors not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/790183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 790183]
(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: reset full-speed USB > device number 3 using ehci-pci > Dec 18 21:07:54 v131 kernel: [26044.143346] traps: fprintd[20976] trap int3 > ip:7f1ca1119c13 sp:7fffbcfcecd0 error:0 Well, I've only replaced free() calls with g_free() and time() with g_get_real_time(). AceLan, could you check what's wrong? -- 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 notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/790183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 790183]
(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://bugs.launchpad.net/bugs/790183 Title: [138a:0011] Fingerprint reader Validity Sensors not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/790183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 602071]
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 reopen bug when patch with driver for libfprint will be ready. -- 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 go to: https://bugs.launchpad.net/dell/+bug/602071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 790183]
(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 a bit worrying that since scanner is not stopped properly it'll consume more power. -- 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 notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/790183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 790183]
(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 open the device, it won't continue to next state > if fpi_imgdev_open_complete() is not be called. > And we call it at open_loop_complete(), so that makes sure the transfers are > all done. There is no race condition. OK, you're right > 2. Please, no workarounds, let's fix an issue instead. > Okay, I removed them. > And this issue is not exist as explanation above. OK > 3. I guess it doesn't work on second time, because there's no proper deinit > sequence and device is still in active state. > I don't know the deinit commands. > Arseniy, please give me some advice if you know how to get the deinit > commands. > BTW, since we don't have the deinit commands, so we call > libusb_reset_device() every time when we open the device. > That will probably reset the device and then it can be init again. Anyway, I'm OK for libusb_reset_device() here for now, but only if someone will continue to investigate how to deinit device properly. Out of curiosity, is this device available as a standalone USB device? -- 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 notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/790183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 745505]
(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 developer could tunnel into if that > helps. Let me know if i can help. Hi Andreas, As I already said, it's close to impossible to develop a driver without device available at hands. But I can guide someone who want to develop driver for libfprint. -- 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 recognized To manage notifications about this bug go to: https://bugs.launchpad.net/fingerprint-gui/+bug/745505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 790183]
(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 = dev;
> >> + fpi_ssm_start(ssm, open_loop_complete);
> >
> >And no one waits for this ssm (and async USB reqs) to complete here. It's a
> >race >condition I've described earlier. Please move device initialization
> >into >dev_activate().
> The code is required and I can imagine the race condition you mentioned, but
> the fingerprint device won't work if move the code to dev_activate()
> function.
Because you need to wait for completion of these transfers, but probably
you don't.
> So, I add a check in dev_activate() function to make sure
> open_loop_complete() have finished to continue.
Please, no workarounds, let's fix an issue instead.
> And you had mentioned that do we need to do reset in dev_open()
> r = libusb_reset_device(dev->udev);
> if (r != 0) {
> fp_err("Failed to reset the device");
> return r;
> }
> I checked if I removed the code, the device doesn't work.
I guess it doesn't work on second time, because there's no proper deinit
sequence and device is still in active state.
> I'm learning libfprint by modifying the code, so please give me more
> explicit advise, so that I can know how to fix it.
> Thanks.
Take a look at other drivers, almost all for AuthenTec devices are
pretty simple. Try to catch me on IRC (#fpr...@irc.freenode.net) if you
have further questions.
--
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 notifications about this bug go to:
https://bugs.launchpad.net/libfprint/+bug/790183/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 790183]
(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 Title: [138a:0011] Fingerprint reader Validity Sensors not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/790183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 790183]
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 notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/790183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 790183]
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. Only debug logs via fp_dbg
are allowed.
@@ +321,5 @@
> +static void median_filter(int *data, int size, int filtersize)
> +{
> + int i;
> + int *result = (int *)malloc(size*sizeof(int));
> + int *sortbuf = (int *)malloc(filtersize*sizeof(int));
Please use g_malloc or g_malloc0 here.
@@ +329,5 @@
> + if (i1 < 0)
> + i1 = 0;
> + if (i2 >= size)
> + i2 = size-1;
> + memmove(sortbuf, data+i1, (i2-i1+1)*sizeof(int));
g_memmove()
@@ +330,5 @@
> + i1 = 0;
> + if (i2 >= size)
> + i2 = size-1;
> + memmove(sortbuf, data+i1, (i2-i1+1)*sizeof(int));
> + qsort(sortbuf, i2-i1+1, sizeof(int), cmpint);
I wonder if there's glib wrapper for that one...
@@ +364,5 @@
> + };
> + int i;
> + float y = 0.0;
> + int line_ind = 0;
> + int *offsets = (int *)malloc(input_lines * sizeof(int));
g_malloc()
@@ +372,5 @@
> +
> + if (debugpath != NULL) {
> + sprintf(name, "%s/offsets%d.dat", debugpath, (int)time(NULL));
> + debugfile = fopen(name, "wb");
> + }
Drop debug stuff except logs
@@ +945,5 @@
> + array_n_elements(vfs5011_initialization);
> + data->init_sequence.actions = vfs5011_initialization;
> + data->init_sequence.device = dev;
> + data->init_sequence.receive_buf =
> + malloc(VFS5011_RECEIVE_BUF_SIZE);
g_malloc()
@@ +989,5 @@
> + int r = libusb_reset_device(dev->udev);
> + if (r != 0) {
> + fp_err("Failed to reset the device");
> + return r;
> + }
Is it necessary? Btw, doc says that handle may be invalid after reset,
and you're reusing same handle later.
@@ +1000,5 @@
> +
> + struct fpi_ssm *ssm;
> + ssm = fpi_ssm_new(dev->dev, open_loop, DEV_OPEN_NUM_STATES);
> + ssm->priv = dev;
> + fpi_ssm_start(ssm, open_loop_complete);
And no one waits for this ssm (and async USB reqs) to complete here.
It's a race condition I've described earlier. Please move device
initialization into dev_activate().
@@ +1035,5 @@
> +}
> +
> +static void dev_deactivate(struct fp_img_dev *dev)
> +{
> + fpi_imgdev_deactivate_complete(dev);
How do you ensure that _all_ transfers are completed now?
fpi_imgdev_deactivate_complete should be called only after deactivation
has been completed. For this driver "cancel" button in fprint_demo won't
work.
--
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 notifications about this bug go to:
https://bugs.launchpad.net/libfprint/+bug/790183/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 790183]
(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 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 notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/790183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 790183]
(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, I can give it a try. > > I'm generally available, but Vasily has been somewhat impolite to me. I'm very sorry if I was impolite to you, it wasn't intended. I'm just a bit tired of arguing why drivers MUST be asynchronous. I'll write a libfprint driver guideline when I get some spare time > Never > answered my question in comment #17, for example. Missed that one. Anyway: > Hang on. Don't you need a pointer to fp_dev to activate a device? And you only > get this pointer from fp_dev_open_cb callback, which callback is invoked after > all async transfers in dev_open are completed. Am I missing something? See img_dev_open(), it doesn't wait for any async xfers from dev_open(), only if you explicitly wait for async transfers to complete in dev_open() > That's why I'm not putting > too much effort into speeding up the process, simply because it's not > exactly fun. Heh > There is, however, fully asynchronous version of the driver: > https://bugs.freedesktop.org/attachment.cgi?id=77562. OK, will take a look tonight. Could you squash 2 patches into single meanwhile? Thanks! P.S. You still can catch me in IRC for faster communication... -- 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 notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/790183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1065493] Re: The "08ff:168f AuthenTec, Inc. Fingerprint Sensor does not work on Ubuntu 12.04
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:168f AuthenTec, Inc. Fingerprint Sensor does not work on Ubuntu 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1065493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 745505]
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.launchpad.net/bugs/745505 Title: [138a:0007] VFS451 fingerprint reader not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/fingerprint-gui/+bug/745505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 745505]
(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 recognized To manage notifications about this bug go to: https://bugs.launchpad.net/fingerprint-gui/+bug/745505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1060059]
(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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1060059 Title: Xorg crashed with SIGABRT in ResFindAllRes() To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1060059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 745505]
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://bugs.launchpad.net/bugs/745505 Title: [138a:0007] VFS451 fingerprint reader not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/fingerprint-gui/+bug/745505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 602071]
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 go to: https://bugs.launchpad.net/libfprint/+bug/602071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 657031] Re: [08ff:2810] AuthenTec, Inc. AES2810 fingerprint reader not recognized (worked in 10.04)
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] AuthenTec, Inc. AES2810 fingerprint reader not recognized (worked in 10.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/657031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 657031] Re: [08ff:2810] AuthenTec, Inc. AES2810 fingerprint reader not recognized (worked in 10.04)
@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 Title: [08ff:2810] AuthenTec, Inc. AES2810 fingerprint reader not recognized (worked in 10.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/657031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 657031] Re: [08ff:2810] AuthenTec, Inc. AES2810 fingerprint reader not recognized (worked in 10.04)
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. AES2810 fingerprint reader not recognized (worked in 10.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/657031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 657031] Re: [08ff:2810] AuthenTec, Inc. AES2810 fingerprint reader not recognized (worked in 10.04)
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 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/657031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 657031] Re: [08ff:2810] AuthenTec, Inc. AES2810 fingerprint reader not recognized (worked in 10.04)
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 libfprint -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/657031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 657031] Re: [08ff:2810] AuthenTec, Inc. AES2810 fingerprint reader not recognized (worked in 10.04)
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/657031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 657031] Re: [08ff:2810] AuthenTec, Inc. AES2810 fingerprint reader not recognized (worked in 10.04)
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.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/657031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 657031] Re: [08ff:2810] AuthenTec, Inc. AES2810 fingerprint reader not recognized (worked in 10.04)
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 reader not recognized (worked in 10.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/657031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 657031] Re: [08ff:2810] AuthenTec, Inc. AES2810 fingerprint reader not recognized (worked in 10.04)
@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 examples ./enroll # Check if enroll works, may need sudo ./verify # Check if verify works, may need sudo It would be nice if someone can make ppa with this lib... -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/657031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 657031] Re: [08ff:2810] AuthenTec, Inc. AES2810 fingerprint reader not recognized (worked in 10.04)
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, 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/657031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 455615] Re: not everything is display correctly
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 455615] Re: not everything is display correctly
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.launchpad.net/bugs/455615 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 114312] Re: Lenovo 3000 N100 overheats when running 2.6.20-15-generic
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
