Package: udev
Version: 254-1
Severity: normal

Dear maintainer,

The computer this report is sent from runs sid and is upgraded almost
daily. The problem described here appeared on the first boot of
2023-07-20 and is still present today.

This computer has the following rule in
/etc/udev/rules.d/90-local-uinput.rules (and no other rule in that
file):

  SUBSYSTEM=="misc", KERNEL=="uinput", GROUP="a_user_group", MODE="0664"

This has been working fine for years, until 2023-07-20. Now, after
booting, one sees that the MODE="0664" action either hasn't been
applied, or has been cancelled by something else:

  # ls -l /dev/uinput
  crw------- 1 root a_user_group 10, 223 Jul 30 11:04 /dev/uinput
  #

(which causes failures in a program that relies on /dev/uinput being
writable by a_user_group).

If, after boot, I manually run as root:

  udevadm control --reload-rules && udevadm trigger'

then the rule is properly applied:

  # ls -l /dev/uinput
  crw-rw-r-- 1 root a_user_group 10, 223 Jul 30 11:09 /dev/uinput
  #

Many thanks in advance for your help. Regards

Florent

-- Package-specific info:

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.4.0-1-amd64 (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages udev depends on:
ii  adduser      3.137
ii  libacl1      2.3.1-3
ii  libblkid1    2.39.1-3
ii  libc6        2.37-6
ii  libcap2      1:2.66-4
ii  libkmod2     30+20230519-1
ii  libselinux1  3.5-1
ii  libudev1     254-1
ii  systemd-dev  254-1

udev recommends no packages.

udev suggests no packages.

Versions of packages udev is related to:
ii  systemd  254-1

-- debconf information:
  udev/new_kernel_needed: false
  udev/title/upgrade:
  udev/sysfs_deprecated_incompatibility:
  udev/reboot_needed:

Reply via email to