Yes, udev is present. sudoing udevadm control --reload-rules && udevadm trigger shows a lot of permission denieds. su - and then udevadm control --reload-rules && udevadm trigger does not. The latter seems to work out of the box, without errors.
The txt file contains the output of the sudo udevadm control --reload-rules && udevadm trigger <enter> command.
I don't know how to iinterpret this.
Kind regards
Paul</enter>
:D
I have rebooted. Several times...
and buckle is a member of sudo as you can see in the added screenshot.
Somehow there is a difference between su - and sudo, resulting in the first to start usbpicprog and the other to do not.
ok, well I don't think it is my task to debug your sudo / su rights, and when you rebooted, the udevadm commands are not necessary anymore. Where did you install the udev rule? Your user must be in the plugdev group as well (or you have to edit the udev file with a group that you are in)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dear Frans
I found out that there are two places where the udev-rules are installed.
/etc/udev/rules.d/26-etc belonging to buckle buckle and
/usr/lib/udev/rules.d/26-etc belonging to root root
Changing ownership of the latter to buckle buckle had no effect.
Not after a reboot either.
And buckle is a member of the plugdev group as you can see in the posted Screenshot from 2025-01-28 16-54-09.png
Paul
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It only works in super user mode. In normal user mode the usbpicprog says not connected/ bootloader not found.
What am I missing?
Dear P. Bakker,
Did you install the udev rule from the repository?
After that you may also need to reboot the machine or trigger / reload udev:
|# udevadm control --reload-rules && udevadm trigger Regards, Frans |
On 1/27/25 19:02, P.Bakkker wrote:
Did you install the udev rule from the repository?
After that you may also need to reboot the machine or trigger / reload udev:
# udevadm control --reload-rules && udevadm triggerYes, udev is present. sudoing udevadm control --reload-rules && udevadm trigger shows a lot of permission denieds. su - and then udevadm control --reload-rules && udevadm trigger does not. The latter seems to work out of the box, without errors.
The txt file contains the output of the sudo udevadm control --reload-rules && udevadm trigger <enter> command.
I don't know how to iinterpret this.
Kind regards
Paul</enter>
I think you must be running into this issue: https://xkcd.com/838/
But seriously though, just reboot your system.
:D
I have rebooted. Several times...
and buckle is a member of sudo as you can see in the added screenshot.
Somehow there is a difference between su - and sudo, resulting in the first to start usbpicprog and the other to do not.
ok, well I don't think it is my task to debug your sudo / su rights, and when you rebooted, the udevadm commands are not necessary anymore. Where did you install the udev rule? Your user must be in the plugdev group as well (or you have to edit the udev file with a group that you are in)
buckle@tux:~$ su -
Password:
root@tux:~# usbpicprog
17:08:25: Error: Unable to initialize GTK+, is DISPLAY set properly?
root@tux:~#
exit
sudo usbpicprog asks for my password and starts usbpicprog
just
usbpicprog
still doesn't start the program.
did you read my previous comment?
No I missed out on that one...
Udev?
Dear Frans
I found out that there are two places where the udev-rules are installed.
/etc/udev/rules.d/26-etc belonging to buckle buckle and
/usr/lib/udev/rules.d/26-etc belonging to root root
Changing ownership of the latter to buckle buckle had no effect.
Not after a reboot either.
And buckle is a member of the plugdev group as you can see in the posted Screenshot from 2025-01-28 16-54-09.png
Paul