udev creates dvb directory with wrong permissions

Bug #993868 reported by Andreas Moog
42
This bug affects 8 people
Affects Status Importance Assigned to Milestone
udev (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I have a dvb-S tv tuner card (Technisat SkyStar 2) installed, the drivers are loaded and udev creates the appropriate device nodes. Except, the permissions and ownership of the /dev/dvb and /dev/dvb/adapter0 directories are wrong (root:root instead of root:video). This results in a ordinary user not being able to access the card.

helmut@helmut-desktop:~$ groups
helmut adm lp dialout cdrom video plugdev lpadmin admin sambashare vboxusers
helmut@helmut-desktop:~$ ls /dev/ -la | grep dvb
drw-r----- 3 root root 60 Mai 3 11:55 dvb
helmut@helmut-desktop:~$ ls /dev/dvb
ls: Öffnen von Verzeichnis /dev/dvb nicht möglich: Keine Berechtigung
helmut@helmut-desktop:~$ sudo ls /dev/dvb -la
[sudo] password for helmut:
insgesamt 0
drw-r----- 3 root root 60 Mai 3 11:55 .
drwxr-xr-x 17 root root 4460 Mai 3 11:55 ..
drw-r----- 2 root root 120 Mai 3 11:55 adapter0
helmut@helmut-desktop:~$ sudo ls /dev/dvb/adapter0 -la
insgesamt 0
drw-r----- 2 root root 120 Mai 3 11:55 .
drw-r----- 3 root root 60 Mai 3 11:55 ..
crw-rw----+ 1 root video 212, 0 Mai 3 11:55 demux0
crw-rw----+ 1 root video 212, 1 Mai 3 11:55 dvr0
crw-rw----+ 1 root video 212, 3 Mai 3 11:55 frontend0
crw-rw----+ 1 root video 212, 2 Mai 3 11:55 net0
helmut@helmut-desktop:~$

The udev rules file is unchanged, the matching entry being:
(/lib/udev/rules.d/50-udev-default.rules)

SUBSYSTEM=="dvb", GROUP="video"

sudo udevadm info --query=all --attribute-walk --name=/dev/dvb/adapter0/demux0 brings:

  looking at device '/devices/pci0000:00/0000:00:14.4/0000:03:03.0/dvb/dvb0.demux0':
    KERNEL=="dvb0.demux0"
    SUBSYSTEM=="dvb"
    DRIVER==""

  looking at parent device '/devices/pci0000:00/0000:00:14.4/0000:03:03.0':
    KERNELS=="0000:03:03.0"
    SUBSYSTEMS=="pci"
    DRIVERS=="b2c2_flexcop_pci"
    ATTRS{vendor}=="0x13d0"
    ATTRS{device}=="0x2103"
    ATTRS{subsystem_vendor}=="0x13d0"
    ATTRS{subsystem_device}=="0x2103"
    ATTRS{class}=="0x028000"
    ATTRS{irq}=="21"
    ATTRS{local_cpus}=="00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000003"
    ATTRS{local_cpulist}=="0-1"
    ATTRS{numa_node}=="0"
    ATTRS{dma_mask_bits}=="32"
    ATTRS{consistent_dma_mask_bits}=="32"
    ATTRS{enable}=="1"
    ATTRS{broken_parity_status}=="0"
    ATTRS{msi_bus}==""

As a workaround I use a script to set the correct permissions, however it would be nice to have this working out of the box.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: udev 175-0ubuntu9
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
CheckboxSubmission: 1fbcf2fff5a20e144142fab6a590f695
CheckboxSystem: 0531969bcfd4f03af7405c98dc94a948
CustomUdevRuleFiles: 71-dvb.rules 98_smfpautoconf_samsung.rules 99_smfpautoconf_samsung.rules
Date: Thu May 3 12:02:46 2012
MachineType: MICRO-STAR INTERANTIONAL CO.,LTD MS-7373
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: root=UUID=d68114ca-0252-4593-9d0a-c9e596d607a3 ro xforcevesa quiet splash
SourcePackage: udev
UpgradeStatus: Upgraded to precise on 2012-04-27 (5 days ago)
dmi.bios.date: 10/31/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.1
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: MS-7373
dmi.board.vendor: MICRO-STAR INTERANTIONAL CO.,LTD
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.1:bd10/31/2007:svnMICRO-STARINTERANTIONALCO.,LTD:pnMS-7373:pvr1.0:rvnMICRO-STARINTERANTIONALCO.,LTD:rnMS-7373:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: MS-7373
dmi.product.version: 1.0
dmi.sys.vendor: MICRO-STAR INTERANTIONAL CO.,LTD

Revision history for this message
Andreas Moog (ampelbein) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in udev (Ubuntu):
status: New → Confirmed
Revision history for this message
YAFU (yafu) wrote :

Old and still unresolved bug in Kernel patched by Ubuntu.

@Andreas Moog, could you share the workaround or script that you used to change permissions?
Thank you.

Tags: ubuntu dvb dvb-t does not work vlc kaffeine totem

Revision history for this message
YAFU (yafu) wrote :

Sorry. I'm seeing that the permissions are apparently right using the Kernel 3.2.0-29 (Kubuntu 12.04 64bits). Likewise, no program can have access to my USB tuner (MyGica S870 using "dvb_usb_dib0700" module driver). When I try to watch TV VLC freezes and I have to kill the process. MPlayer, Kaffeine and Totem (GNOME dvb-daemon) not working too.
Kaffeine message:
kaffeine(6273) DvbLinuxDevice::tune: ioctl FE_SET_FRONTEND failed for frontend "/dev/dvb/adapter0/frontend0"

Using the PPA mainline kernels VLC works (the other programs still can not access the device)

$ groups
yafu adm disk cdrom sudo audio dip video plugdev scanner lpadmin netdev sambashare debian-tor vboxusers jupiter

Revision history for this message
bluearcus (mike-miller-gmx) wrote :

Both 32 and 64 bit 12.04 are showing this problem for me, with two different USB DVB tuner dongles.

/dev/dvb and all device nodes beneath are created with user and group ownership of root. By default the group ownership should be video.

At the moment I have to add local udev rules based on the USB device IDs to change the ownership with a script.

Revision history for this message
Simon Davis (davis-decent) wrote :

Interestingly, the bug is still present in 19.10.

$ ls -l /dev/dvb/adapter0/
total 0
crw-rw----+ 1 root video 212, 0 Feb 24 09:57 demux0
crw-rw----+ 1 root video 212, 1 Feb 24 09:57 dvr0
crw-rw----+ 1 root video 212, 3 Feb 24 09:57 frontend0
crw-rw----+ 1 root video 212, 2 Feb 24 09:57 net0

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.