When I restart my system, it loads the kernel, it checks the clock, and inmidiately after, it says:

Initating udev: udevd[435]: add to rules: unknown key ´ATTRS{idVendor}´
udevd[435]: add to rules: unknown key ´ATTRS{idProduct}´
udevd[435]: add to rules: unknown key ´ATTRS{idVendor}´
udevd[435]: add to rules: unknown key ´ATTRS{idProduct}´
udevd[435]: add to rules: unknown key ´ATTRS{idVendor}´
udevd[435]: add to rules: unknown key ´ATTRS{idProduct}´
udevd[435]: add to rules: unknown key ´ATTRS{idVendor}´
udevd[435]: add to rules: unknown key ´ATTRS{idProduct}´
udevd[435]: add to rules: unknown key ´ATTRS{idVendor}´
udevd[435]: add to rules: unknown key ´ATTRS{idProduct}´
udevd[435]: add to rules: unknown key ´ATTRS{idVendor}´
udevd[435]: add to rules: unknown key ´ATTRS{idProduct}´
udevd[435]: add to rules: unknown key ´ATTRS{idVendor}´
udevd[435]: add to rules: unknown key ´ATTRS{idProduct}´
udevd[435]: add to rules: unknown key ´ATTRS{idVendor}´
udevd[435]: add to rules: unknown key ´ATTRS{idProduct}´

Why is this? It didn't happen always, I think something may have originated this. What could it be?

What's the solution to this?

Thank you very much!

You've installed kino, likely on Fedora, in which case this is a known bug. If this is not the case, please provide information on your distribution.

To correct the problem, edit the file /etc/udev/rules.d/kino.rules, and change all occurrences of ATTRS to SYSFS. With vi, you can do this with the command:

%s/ATTRS/SYSFS/g

Thank you a lot! The problem was solved doing this very thing you said.
But I'm a newbie, please, could you tell me what did I do?
What's that that loads at the begin when I start my machine? udev? and why the conflicts?

Thank you very much!

Wikipedia has a good article on udev. Basically, it creates the device entries (how software interacts with peripherals), and it uses the files in /etc/udev to control that process. The Kino software was created with rules for a newer version of udev, but the Kino packagers forgot to update the rules. The bug was reported to the Fedora developers, but was identified as an upstream issue (that is, the Kino developers need to correct it). I don't see the bug in the Kino bug list, but it's a relatively trivia issue. They'll likely correct it in the next release.