I'm still facing this problem. I just switched to 19.10 and the snap package
has been installed. It does not work.
I tried to do the "snap connect chromium:u2f-devices" but this will not solve
the problem.
My dmesg out put shows a lot of DENIED:
audit: type=1107 audit(1572541712.846:243): pid=954 uid=106 auid=4294967295
ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call"
bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager"
member="GetManagedObjects" mask="send" name="org.bluez" pid=20568
label="snap.chromium.chromium" peer_pid=946 peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=106 hostname=? addr=?
terminal=?'
[ 7036.430639] audit: type=1400 audit(1572541713.042:244): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7036.430641] audit: type=1400 audit(1572541713.042:245): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
[ 7049.256201] audit: type=1400 audit(1572541725.870:246): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/sys/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-2/i2c-ELAN1200:00/0018:04F3:3022.0001/report_descriptor"
pid=20568 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000
ouid=0
Can you please advise how to fix this? Thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1738164
Title:
[snap] U2F doesn't work with yubikey
Status in chromium-browser package in Ubuntu:
Fix Released
Status in gnome-software package in Ubuntu:
Fix Released
Status in gnome-software source package in Xenial:
Fix Released
Status in gnome-software source package in Bionic:
Fix Released
Status in gnome-software source package in Cosmic:
Won't Fix
Bug description:
[Impact]
Installing a snap that requires the u2f-devices interface doesn't show a UI
element to enable/disable this in GNOME Software. Initially Chromium didn't
have this enabled by default, and thus the feature wouldn't work without going
to the command line. It now is enabled by default.
[Test Case]
1. Open GNOME Software
2. Install the Chromium snap
3. Click "Permissions"
Expected result:
A switch is shown to control "Read/write access to U2F devices exposed".
Clicking it connects/disconnects the u2f-devices interface.
Observed result:
No switch is shown for this interface.
[Regression Potential]
A string for this interface was added to GNOME Software, low risk of
introducing a new bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1738164/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
