Setup vial on fedora requires extra steps

[gsouf]

Hi,

I followed the guide to setup vial on linux (https://get.vial.today/manual/linux-udev.html) but it didnt work out of the box...Apparently some fedora security layer block the rules to apply

I had to run lsusb to find the vendor id and device id of the keyboard, then I had to add these to the file /etc/udev/rules.d/59-vial.rules

I had to put this:

ATTRS{idVendor}=="replace with vendor id", ATTRS{idProduct}=="replace with device id"

I think it would be worth it documenting this on the setup page as it took me about 30 minutes to figure out.

Thank you!

[getreuer]

Does the Device-specific udev rules section cover it? At a glace, it seems so, but if there are significant missing details these would be good to add.

[gsouf]

@getreuer thank you for the link. It indeed explains how to do. My bad! With that being said it's explained in the device specific rules, which, if I remember well I considered not for me as I wanted to apply the "common" method.

If that makes sense to give more details, I have been using linux for over 15 years, but I never had to deal with hardware, keyboard and all these related things. Even if I'm comfortable using linux, I had no idea what was failing in the first place. That's what took me a while to figure out.

It was a month ago so I can't really remember what I did exactly, but today reading again at the guide I still feel a bit lost because I don't know about udev, hidraw, the difference between universal and generalized rules etc... I remember I did read about all of this when it didn't work, but I already forgot about it.

What could be interesting is to have a slightly more guided setup at the beginning. Maybe a have a callout saying, if you used generalized method but it's still not working, the manual method my be the way to go.

I mentioned specifically a callout because in such a technical pages it helps a lot to quickly spot troubleshooting information.

It could say:

If Vial opens normally but your keyboard does not appear, try the device-specific udev rules method below