I’m not sure if this is the right forum for this issue, but perhaps I can get some guidance on it. I have two similar Dell machines, a M6500 and a M6800, both running Ubuntu 18.04.2. The M6500 was updated from 16.04 to 18.04 while the M6800 was a fresh install. Using snap I installed Acestreamplayer on the M6800 without any problems, however on the M6500 the installation fails, giving me the following messages:
- Setup snap "acestreamplayer" (8) security profiles (cannot setup udev for snap "acestreamplayer": cannot reload udev rules: exit status 2 udev output:)
- Setup snap "acestreamplayer" (8) security profiles (cannot reload udev rules: exit status 2 udev output:)
- Connect acestreamplayer:opengl to core:opengl (cannot setup udev for snap "acestreamplayer": cannot reload udev rules: exit status 2 udev output:)
- Connect acestreamplayer:opengl to core:opengl (cannot reload udev rules: exit status 2 udev output:)
I see that in your response you link to a program called udev.go, is something that I should have done prior/after typing ‘udevadm control --reload-rules’?
Well as the command executed properly at your end (it shouldn’t return anything) I currently have no idea what the problem is right now. @chipaca can you shed some lights to us?
The pastebinit hangs because the URL does not respond, so I piped and compressed the output, but I don’t see anyway to upload a non-image file in here. Can you please give me an alternative?
I found that hid2hci is something related to bluetooth. Since I don’t use bluetooth I issued "sudo apt purge “bluez*” - but apparently that doesn’t stop hid2hci from spamming the result of journalctl - I searched for the executable hid2hci and doesn’t appear anywhere. (???)
The proper way to disable a udev rule should be locate it in /lib/udev/rules.d and override it in /etc/udev/rules.d, for example to override /lib/udev/rules.d/97-hid2hci.rules do sudo touch /etc/udev/rules.d/97-hid2hci.rules
I didn’t find anything related to hid2hci in /lib/udev/rules.d, but I touch’ed the file you suggested in /etc/udev/rules.d/ - would that be OK? Is there any way to reload this mod without rebooting the system?