# Onlykey Duo on chromeOS

**URL:** <https://onlykey.discourse.group/t/onlykey-duo-on-chromeos/1187>\
**Category:** Uncategorized\
**Created:** [December 3, 2023, 8:49am UTC](https://onlykey.discourse.group/t/onlykey-duo-on-chromeos/1187 "2023-12-03T08:49:07Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nicolas](https://avatars.discourse-cdn.com/v4/letter/n/67e7ee/32.png) [@Nicolas](https://onlykey.discourse.group/u/Nicolas)\
**Post date:** [December 3, 2023, 8:49am UTC](https://onlykey.discourse.group/t/onlykey-duo-on-chromeos/1187/1 "2023-12-03T08:49:07Z")

</div>

Hello,

Today , onlykey doesn"t work for Container ChromeOS due to issue below

> <https://github.com/systemd/systemd/issues/28156>
>
> \### systemd version the issue has been seen with
> 
> 249.11-0ubuntu3.9
> 
> \### Use…d distribution
> 
> Ubuntu 22.04.2
> 
> \### Linux kernel version used
> 
> 5.19.0-45-generic
> 
> \### CPU architectures issue was seen on
> 
> x86\_64
> 
> \### Component
> 
> udevadm
> 
> \### Expected behaviour you didn't see
> 
> \`udevadm trigger\` return success / no errors
> 
> \### Unexpected behaviour you saw
> 
> \`udevadm trigger\` throws errors
> 
> \### Steps to reproduce the problem
> 
> \_No response\_
> 
> \### Additional program output to the terminal or log subsystem illustrating the issue
> 
> \`\`\`sh
> \# udevadm trigger
> SELinux enabled state cached to: disabled
> sd-device-enumerator: Scan all dirs
> sd-device-enumerator: Scanning /sys/bus
> sd-device-enumerator: Scanning /sys/class
> LNXSYSTM:00: Failed to write 'change' to '/sys/devices/LNXSYSTM:00/uevent': Permission denied
> ACPI0008:00: Failed to write 'change' to '/sys/devices/LNXSYSTM:00/ACPI0008:00/uevent': Permission denied
> INT339B:00: Failed to write 'change' to '/sys/devices/LNXSYSTM:00/INT339B:00/uevent': Permission denied
> INT3420:00: Failed to write 'change' to '/sys/devices/LNXSYSTM:00/INT3420:00/uevent': Permission denied
> \[...\]
> 
> Full log here: https://gist.github.com/JBau32/526acd01eae9ecfabf1fed5717dcdce0
> \`\`\`

Recently a flag have been added ( [chrome://flags/#permissive-usb-passthrough) and device is now recognized.  
Any solution to workaround issue ?