On Tue, Oct 20, 2015 at 11:31:05PM +0100, Luca Boccassi wrote: > Could you please make sure that both your user and your DM user (sddm I > believe?) are in the video group and try again and report the result?
Yes, this solves the problem, but it is ridiculous. First of all it is security issue. The "video" group is system group that provide write access to video device. It is using not only for nvidia. For example I am using special system user "webcam" for streaming from my web camera to RTMP server. To do this I've added it to video group. So normal non-system user should not be included into this group. Second, tell us please how do You make sure the normal user being included into video group? For example, if You add new user with useradd utility? Yes, You can do this with something like hook or trigger, but this is not only way to create new user - there are unlimited number of ways to do this. Or may be You are going notify all sysadmins about this? No. This is really crazy idea to provide non-system ordinary user with write access to video device in order to provide access to glx library. And Andreas Beckmann's post: http://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/2015-October/011948.html explains nothing about this. There are no answer to the question: what for glx requires write access to video device for normal live user? This is something new in world fashion. Why only glx require this? How do other video works without such requirements? ### Vladimir Stavrinov ###
