Package Details: trezor-udev 1-3

Git Clone URL: https://aur.archlinux.org/trezor-udev.git (read-only, click to copy)
Package Base: trezor-udev
Description: Udev rules to connect trezor hardware wallets to your linux box
Upstream URL: https://github.com/trezor/trezor-common
Keywords: bitcoin cryptocurrency wallet
Licenses: LGPL3
Submitter: pizzaman
Maintainer: pizzaman
Last Packager: pizzaman
Votes: 11
Popularity: 0.54
First Submitted: 2020-11-11 23:19 (UTC)
Last Updated: 2021-09-05 09:58 (UTC)

Latest Comments

veox commented on 2026-07-21 15:24 (UTC)

@jancici (and anyone else wondering), the group used to be created by the "Trezor Bridge" package(s), e.g. these two:

https://aur.archlinux.org/cgit/aur.git/tree/sysusers.d.conf?h=trezord-go https://aur.archlinux.org/cgit/aur.git/tree/trezor-bridge-bin.install?h=trezor-bridge-bin

But see discussion at trezord-go:

Dendrocalamus64 commented on 2025-11-04 02:04 (UTC) Just a note that Trezor daemon a.k.a Trezor Bridge is deprecated by Trezor now, so it should no longer be needed for Trezor Suite (...)

The package works as-is for me locally, even without the group present. I squint and ignore the udev rule error message.

jancici commented on 2023-12-13 09:03 (UTC)

durring the boot I am getting a error in log

/usr/lib/udev/rules.d/51-trezor.rules:12 Unknown group 'trezord', ignoring.

yes, I dont have that group in my system, I did install trezor-suite-appimage from aur. question: which package should be responsible to create trezord group, this or suite-appimage package?

pizzaman commented on 2021-09-05 10:03 (UTC)

@andrej Thanks for the suggestion. Changed plugdev to trezord.

andrej commented on 2021-09-04 00:23 (UTC)

This package is (sort of) broken from a trezord-git perspective: You need GROUP="trezord" instead of GROUP="plugdev". Otherwise the app will display nonsensical error messages about missing udev rules (which are not missing for sure) and trezord will show the device on its (no clue why IPv4-only) HTTP interface as if everything was OK, but won’t show any diagnostics related to the permissions.

Long story short, permissions need to be set to something accessible to trezord, not (necessarily) to the human user.