** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Medium
** Summary changed:
- U2f yubikey stopped working in chromium snap
+ [snap] U2f yubikey not recognized until unplugged and plugged back in
** Tags added: snap
--
You received this bug notification because you are a mem
Same problem here. Here are my observations, which match the behavior
already described.
- To reproduce: Insert YubiKey, start Chromium, attempt login (nothing happens
when tapping on YubiKey), replug YubiKey, attempt login (now it works).
- It works when done in this order: Start Chromium, go to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: chromium-browser (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884759
Ti
For now I can send udev event instead of replugging:
ls -l /sys/class/hidraw/ | grep :1050: | awk -F/ '{print $NF}' | xargs
-r -L1 -I T udevadm trigger -c add --name-match=T
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Hm, now I updated chrome to 84.0.4147.105 (1260) and can reproduce it
reliably by inserting yubikey and then starting chromium with new
profile (chromium --user-data-dir=./111).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Sorry for long delay. No I can't reproduce it anymore in a way I described
before, but it still happens to me. For now certain is that repluging yubikey
fixes the problem, reboot doesn't.
Upgrading the snap most probably triggering it, need to test it more times.
--
You received this bug notifi
The plot thickens. Can you reliably reproduce this situation, where
unplugging and plugging again the 5C makes it work, but it doesn't after
a reboot?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884
Funny thing. I have Yubikey 5C Nano and it is hard to get out of port.
So I plugged spare Yubikey 4 to get dmesg lines and it worked with
chromium. Then I replugged my yubikey 5c nano and it worked too. Then I
rebooted without unplugging yubikey and it not working in chromium again
but works in fir
Can you share the last few lines of `dmesg` after plugging in your
yubikey, to get more information about the device?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884759
Title:
U2f yubikey stopped
name: chromium
summary: Chromium web browser, open-source version of Chrome
publisher: Canonical*
contact:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
license: unset
description: |
An open-source browser project that aims to build a safer, faster, a
Still not working. And right link to test is https://demo.yubico.com
/webauthn-technical/registration
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884759
Title:
U2f yubikey stopped working in chro
Sorry for the lack of feedback Alexey.
I have just tested with my Yubikey 4, using
https://demo.yubico.com/playground, and U2F appears to work as expected.
Are you still seeing the problem with the latest chromium snap?
--
You received this bug notification because you are a member of Ubuntu
Bu
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884759
Title:
U2f yubikey stopped working in chromium snap
To manage notific
Log attached. Relevant line probably
[92777:92906:0709/115647.054273:ERROR:udev_watcher.cc(96)] Failed to
begin udev enumeration.
** Attachment added: "chrom3.log"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884759/+attachment/5390970/+files/chrom3.log
--
You received t
Can you run chromium with the following command, and share the output
after a failed attempt to use U2F to log in to github?
snap run chromium --enable-logging=stderr --v=1
** Changed in: chromium-browser (Ubuntu)
Status: New => Incomplete
--
You received this bug notification becaus
Tested firefox snap - u2f works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884759
Title:
U2f yubikey stopped working in chromium snap
To manage notifications about this bug go to:
https://bugs
I use it only for github, no special setup was needed (udev rules are
already there for PIV). I logged last time some months ago so I don't
know when it stopped working exactly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Thank you for your bug report. When did it stop working? Was there any
update around the time? Could you give some details on how you setup and
use the yubikey there?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
18 matches
Mail list logo
