Only root can access devices

[Super Vegeta]

I have recently replaced Fedora 16 with 18 and now I have a problem with accessing devices.

USB flash drives and partitions not listed in fstab require a root password to mount, which is actually good and it could stay that way.

But my real problem is that neither my mouse nor my webcam don't want to work for anyone apart from root. I tried changing permissions in /dev and adding users to groups, but that didn't help.

When I attach a device, the TTYs get spammed with:
systemd-udevd[]: Failed to set security context (null) for *file*: File exists
Where *file*, in case of mouse, is either '/dev/input' or '/dev/input/by-id', and in case of webcam it can also be '/dev/v4l' or '/dev/snd'.

If it could be related in any way, I changed lxdm.conf to run the X server on vt7 instead of vt1.

[Dies]

Possible SELinux issue?

Have you tried temporarily disabling it to see if that's the case?

[richip]

I have (possibly) the same problem. In my case, CPU utilization hits >90% and I get hundreds (if not thousands) of messages from `journalctl` similar to below which causes the system to be UI unresponsive:

Feb 12 07:44:48 wrx.richip.dhs.org systemd-udevd[18404]: Failed to set security context (null) for /dev/input/by-id: File exists
Feb 12 07:44:48 wrx.richip.dhs.org systemd-udevd[18406]: Failed to set security context (null) for /dev/input: File exists
Feb 12 07:44:48 wrx.richip.dhs.org systemd-journal[519]: Missed 304072 kernel messages
Feb 12 07:44:48 wrx.richip.dhs.org systemd-udevd[18406]: Failed to set security context (null) for /dev/input/by-id: File exists
Feb 12 07:44:48 wrx.richip.dhs.org systemd-udevd[18474]: Failed to set security context (null) for /dev/input: File exists
Feb 12 07:44:48 wrx.richip.dhs.org systemd-udevd[18405]: Failed to set security context (null) for /dev/input: File exists
Feb 12 07:44:51 wrx.richip.dhs.org systemd-journal[519]: Missed 164414 kernel messages
Feb 12 07:44:51 wrx.richip.dhs.org systemd-udevd[18406]: Failed to set security context (null) for /dev/input/by-id: File exists
Feb 12 07:44:51 wrx.richip.dhs.org systemd-udevd[18473]: Failed to set security context (null) for /dev/input: File exists
Feb 12 07:44:52 wrx.richip.dhs.org systemd-journal[519]: Missed 40730 kernel messages
Feb 12 07:44:52 wrx.richip.dhs.org systemd-udevd[18472]: Failed to set security context (null) for /dev/input/by-id: File exists

Assuming it's a SELinux issue, how would one fix this particular issue? Do SELinux issues get fixed in updates? In this case, I'm not seeing any messages from setroubleshoot.

[Super Vegeta]

Setting the SELinux enforcing mode to permissive (via system-config-selinux) fixes this (devices can be accessed, mounts are still passworded), but I guess I won't surprise anyone if I say I don't consider it a permanent solution.