New answers tagged udev
1
Following Emmanuel's two instructions, my gist is updated.
In your configuration.nix, try
services.udev.packages = [ px4_drv ]
You may also need to change the udev path in the installPhase to $out/lib/udev/rules.d, not $out/etc/udev/rules.d.
0
Follow my working solution for a Samsung Android device...
Write a script in /etc/udev/rules.d like this:
#!/bin/bash
su <NON_ROOT_USER> -c <YOUR_GUI_APPLICATION>
Run udevadm monitor -e to get your device path (e.g. /devices/pci0000:00/0000:00:08.1/0000:04:00.3/usb1/1-2) and write down it.
Run udevadm info -ap <YOUR_DEVICE_PATH> to get ...
1
Essentially this is a combination of a race condition and the difference in the behavior of xsetwacom when run from a udev rule compared to when run from a familiar graphical terminal, due to e.g. differences in environment variables.
Problem 1: environment variable.
Addressing the second issue first: this is similar to the situation where shell scripts ...
0
In my case, the issue was that I had to use ATTRS{name} rather than ATTRS{address}.
I found this out by issuing:
udevadm info -ap /devices/virtual/input/input160/event6
More info here.
0
It looks, my problem is solved by reloading the udev rules without reboot. An
udevadm control --reload-rules && udevadm trigger
did what I wanted.
answered Mar 25 at 12:29
peterh - Reinstate Monica
6,15513 gold badges40 silver badges68 bronze badges
0
I too was running into this situation where the source /dev/sdx device would disappear shortly after ddrescue's startup and knew that unplugging and re-plugging in the USB "toaster" I was using to attach the SATA drive to the system would cause it to be re-found. Restarting ddrescue would allow it to run for a few minutes, before crashing shortly thereafter. ...
0
You mention ATTR{idVendor} and similar. Should that be ATTRS{...} ?
I've also found minimal rules are better.
For example, I have the following on my Debian system:
% cat /etc/udev/rules.d/ols.rules
#Rules for Openbench Logix Snifferslogic. Creates a nice link to the ols
ATTRS{idVendor}=="04d8", ATTRS{idProduct}=="fc92", MODE="0666", ...
0
sudo -u X_user DISPLAY=:0 DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/X_userid/bus notify-send 'Hello world!'
Where X_user is the user you want to run as, and X_userid is group ID of the user
example bigbird and 1000
Top 50 recent answers are included
